Opened 10 years ago

Closed 8 years ago

#961 closed task (duplicate)

WinGRASS-6.4.0SVN-r40852-1 installs GRASS, but it doesn't run

Reported by: stoyan Owned by: stoyan
Priority: normal Milestone: 6.4.0
Component: Installation Version: 6.4.0 RCs
Keywords: winGRASS, problems, start Cc: grass-dev@…
CPU: Unspecified Platform: MSWindows XP

Description

I downloaded WinGRASS-6.4.0-r40852-1 and installed GRASS on my laptop on Windows XP Pro Platform, but I cannot start it. When I am trying to execute wxPython inder Windows start menu, the window with cmd only flashes and dissappears. When I am trying MSys Icon it says: "Echo C\GRASS\Msys\lib is not a valid executable or operable command. The window will close"... Press any button to continue I installed GRASS in C:\GRASS directory. When I tried to install it on another machine with Windows XP Professional installed it runs OK. I have read all mailing lists, but couldn't find such a problem so far. I don't know what should be the problem with my operation system or my computer. Please help!

Change History (21)

comment:1 Changed 10 years ago by hamish

Component: defaultInstallation
Keywords: winGRASS added; GRASS removed

can you try the latest nightly build?

http://josef.fsv.cvut.cz/wingrass/grass64/

Hamish

comment:2 in reply to:  1 Changed 10 years ago by neteler

Replying to hamish:

can you try the latest nightly build?

http://josef.fsv.cvut.cz/wingrass/grass64/

Additionally, please check, when installing, if the files are properly extracted or if a "skipped" appears. Please report here.

Markus

comment:3 Changed 10 years ago by stoyan

Owner: changed from grass-dev@… to stoyan
Status: newassigned

I think they are extracted, not skipped, but how can I be sure. Extracting happens too fast. Is there something like log file? I installed QGIS with GRASS add-on prior to installing WinGRASS. Could it cause the problem?

Stoyan

comment:4 in reply to:  3 ; Changed 10 years ago by neteler

Replying to stoyan:

I think they are extracted, not skipped, but how can I be sure. Extracting happens too fast. Is there something like log file?

No, but it is possible to read it since *many* files are extracted. Please try again.

I installed QGIS with GRASS add-on prior to installing WinGRASS. Could it cause the problem?

I don't think so...

Markus

comment:5 Changed 10 years ago by hamish

Cc: grass-dev@… added

comment:6 in reply to:  4 ; Changed 10 years ago by stoyan

Replying to neteler:

I tried to find out if all files were extracted and I think they were. It's the same, I cannot start the program. I tried to copy c:\GRASS from another computer, where it works to my computer. Probably it is silly, I don't know. :) But nothing gets better. Still doesn't work. Obviously there is something in my OS that prevents running GRASS. Any other ideas?

Stoyan

comment:7 in reply to:  6 Changed 10 years ago by hellik

Replying to stoyan:

Replying to neteler:

I tried to find out if all files were extracted and I think they were. It's the same, I cannot start the program. I tried to copy c:\GRASS from another computer, where it works to my computer. Probably it is silly, I don't know. :) But nothing gets better. Still doesn't work. Obviously there is something in my OS that prevents running GRASS. Any other ideas?

Stoyan

still valid with an actual nightly build from http://josef.fsv.cvut.cz/wingrass/grass64/?

Helmut

comment:8 Changed 10 years ago by stoyan

Yes, it is. I still cannot run Grass from my system. It doesn't start after install. It doesn't matter if I install the actual nightly build or not. I think about formatting the disk and create new installation of my system (windows XP).

comment:9 in reply to:  8 Changed 10 years ago by hellik

Replying to stoyan:

Yes, it is. I still cannot run Grass from my system. It doesn't start after install. It doesn't matter if I install the actual nightly build or not. I think about formatting the disk and create new installation of my system (windows XP).

do you see in C:\GRASS\ following files and folders?

AUTHORS
bin
bwidget
CHANGES
COPYING
docs
driver
etc
extrabin
extralib
fonts
GPL.TXT
gpsbabel
GRASS-WebSite.url
grass64svn.bat
icons
include
lib
locale
msys
proj
Python25
REQUIREMENTS.html
scripts
sqlite
tcl-tk
tools
Uninstall-GRASS.exe
WinGRASS-README.url

can you try to install the latest installer from the nightly builds (http://josef.fsv.cvut.cz/wingrass/grass64/) in C:\Program Files\GRASS-64-SVN (this should be proposed by the wininstaller)?

and compare afterwards the list of above files and folders in C:\Program Files\GRASS-64-SVN. any difference to the situation in C:\GRASS ?

Helmut

comment:10 Changed 10 years ago by stoyan

Yes I installed the latest installer in C;\Program Files\GRASS-64-SVN and saw all of the listed files and folders. But there is another interesting thing. The last rows of the install window were: "Create folder: C:\Program Files\GRASS-64-SVN\msys\home Create folder: C:\Program Files\GRASS-64-SVN\msys\home\C\Documents and Settings\Stoyan Create folder: C:\Program Files\GRASS-64-SVN\msys\grass Copy to C:\Program Fies\GRASS-64-SVN\msys\home\C:\Documents and Settings\Stoyan Copy failed Completed" I don't know why it cannot copy this and why it should be copied, but can it be the reason for not starting?

comment:11 in reply to:  10 ; Changed 10 years ago by hellik

Replying to stoyan:

Yes I installed the latest installer in C;\Program Files\GRASS-64-SVN and saw all of the listed files and folders. But there is another interesting thing. The last rows of the install window were:

these are the relevant lines in the installer script:

"Create folder: C:\Program Files\GRASS-64-SVN\msys\home

(http://trac.osgeo.org/grass/browser/grass/branches/releasebranch_6_4/mswindows/GRASS-Installer.nsi#L703)

CreateDirectory $INSTALL_DIR\msys\home

Create folder: C:\Program Files\GRASS-64-SVN\msys\home\C\Documents and Settings\Stoyan

(http://trac.osgeo.org/grass/browser/grass/branches/releasebranch_6_4/mswindows/GRASS-Installer.nsi#L704)

$INSTALL_DIR\msys\home\$USERNAME

Create folder: C:\Program Files\GRASS-64-SVN\msys\grass

(http://trac.osgeo.org/grass/browser/grass/branches/releasebranch_6_4/mswindows/GRASS-Installer.nsi#L770)

CreateDirectory $INSTALL_DIR\msys\grass

Copy to C:\Program Fies\GRASS-64-SVN\msys\home\C:\Documents and Settings\Stoyan Copy failed Completed"

(http://trac.osgeo.org/grass/browser/grass/branches/releasebranch_6_4/mswindows/GRASS-Installer.nsi#L801)

CopyFiles $PROFILE\.grassrc6 $INSTALL_DIR\msys\home\$USERNAME

very interesting:

"Copy to C:\Program Fies\GRASS-64-SVN\msys\home\C:\Documents and Settings\Stoyan"

this should be

"Copy to C:\Program Fies\GRASS-64-SVN\msys\home\Stoyan"

comment:12 in reply to:  11 Changed 10 years ago by hellik

Replying to hellik:

very interesting:

"Copy to C:\Program Fies\GRASS-64-SVN\msys\home\C:\Documents and Settings\Stoyan"

this should be

"Copy to C:\Program Fies\GRASS-64-SVN\msys\home\Stoyan"

I've tested the latest nightly build on my laptop:

[...]
Create folder: C:\Program Files\GRASS-64-SVN\msys\home
Create folder: C:\Program Files\GRASS-64-SVN\msys\home\syringia
Create folder: C:\Program Files\GRASS-64-SVN\msys\home\grass
Copy to C:\Program Files\GRASS64-64-SVN\msys\home\syringia
Completed

so there seems to be something with your %USERNAME%-variable in your windows installation.

could you start a normal windows console (start menue -> run -> cmd) and type in:

echo %USERNAME%

and paste in the result in the bug report.

Helmut

comment:13 Changed 10 years ago by stoyan

This is the result: Stoyan

comment:14 in reply to:  13 Changed 10 years ago by hellik

Replying to stoyan:

This is the result: Stoyan

this is ok.

could you start a normal windows console and type in

echo %USERPROFILE%

paste in the result in the bug report?

comment:15 Changed 10 years ago by stoyan

The result is: C:\Documents and Settings\Stoyan

comment:16 in reply to:  15 ; Changed 10 years ago by hellik

Replying to stoyan:

The result is: C:\Documents and Settings\Stoyan

also ok.

WinGrass-Installer and/or WinXp? seem to mix the two variables %USERNAME% and %USERPROFILE% during installation:

Create folder: C:\Program Files\GRASS-64-SVN\msys\home\
'''C:\Documents and Settings\Stoyan'''

this isn't a valid path, so the last copy-action by the installer can't complete.

I couldn't find anything helpfull in NSIS-manuals at the moment.

comment:17 in reply to:  16 Changed 10 years ago by hellik

Replying to hellik:

Replying to stoyan:

The result is: C:\Documents and Settings\Stoyan

also ok.

WinGrass-Installer and/or WinXp? seem to mix the two variables %USERNAME% and %USERPROFILE% during installation:

Create folder: C:\Program Files\GRASS-64-SVN\msys\home\
'''C:\Documents and Settings\Stoyan'''

this isn't a valid path, so the last copy-action by the installer can't complete.

I couldn't find anything helpfull in NSIS-manuals at the moment.

I've opened a thread for this issue on the nsis-forum (http://forums.winamp.com/showthread.php?t=317856)

comment:18 Changed 9 years ago by hamish

seem to mix the two variables %USERNAME% and %USERPROFILE% during installation

...

I've opened a thread for this issue on the nsis-forum

any resolution?

comment:19 in reply to:  18 Changed 9 years ago by hellik

Replying to hamish:

seem to mix the two variables %USERNAME% and %USERPROFILE% during installation

...

I've opened a thread for this issue on the nsis-forum

any resolution?

no response from the nsis-forum.

so any additional info about the situation with recent builds of WinGrass64-installers would be helpfull.

Helmut

comment:20 Changed 8 years ago by hamish

the symptom sounds like the classic missing dll problem (but which one?). try installing the Microsoft .net Frameworks and see if it helps. see also #1354, #1428, #1450 http://grass.osgeo.org/wiki/WinGRASS_Current_Status#XP.2F2000

"Copy to C:\Program Fies\GRASS-64-SVN\msys\home\C:\Documents and Settings\Stoyan"

do you still see that bad path name from the installer script?

Hamish

comment:21 Changed 8 years ago by hamish

Resolution: duplicate
Status: assignedclosed

merged into bug #1428 "WinGRASS 6.4.1 fails to start after installation"

Hamish

Note: See TracTickets for help on using tickets.