[winGRASS] vanishing window

[Gerald Nelson]

My windows don't vanish now. What changed in the meantime was that I removed
all traces of cygwin and grass 6.1 from my computer. Since the computer
where wingrass worked never had cygwin, it seems likely that cygwin was the
problem. It might have been some of the environment variables or something
in the registry. I cleaned out all of that manually following the directions
in http://cygwin.com/faq/faq-nochunks.html#faq.setup.uninstall-all.

Regards, Jerry

-----Original Message-----
From: Moritz Lennert [mailto:mlennert at club.worldonline.be] 
Sent: Thursday, October 26, 2006 3:38 AM
To: JerryNelson
Cc: wingrass at grass.itc.it
Subject: Re: [winGRASS] vanishing window

JerryNelson wrote:
> On a different computer, I get the same message 
> "Warning: Attention!
> Warning: Locking is not supported on Windows!"
> 
> but grass proceeds to the graphical interface. 

The warning messages is just that, a warning, and you don't have to
worry about it.
It just means that in windows the current GRASS locking mechanism which
makes it impossible for two people to work on the same location/mapset
at the same time does not work under windows. But since generally
windows users are single users, this probably is not a big problem (but
I might be wrong).

>> When I point wingrass (v6.3, just installed today) to either a new mapset
>> or
>> an old one, the cmd window flashes some message about not able to lock 

see above

> and
>> then both it 

What is 'it' here, the error message ?

>>and the cmd window disappear. 

This should not happen. Any idea what is different between the two
computers ?

>> I'm not sure what the error
>> messages are because the window disappears so quickly. I suspect postgres
>> but don't know anything about the various installation options. I just
>> clicked next, except that I did choose to include the PostGIS option.

As long as postgresql is installed and its path correctly defined in
grass.bat (default: set PATH=%PATH%;C:\Program
Files\PostgreSQL\8.1\bin), postgresql shouldn't interfere. If you
installed postgresql in a different location, this should cause the 
"infamous" 'can't read "parts(n)": no such variable while executing' 
error, but not kill the cmd window.

Moritz