[Fwd: RE: [GRASS5] GRASS 6 automatic start - minor glitches in Cygwin GRASS installation

[Michael Barton]

I just helped someone install GRASS on Cygwin/Windows XP this morning.
First, I want to say that the installer is VERY nice. Huidae Cho has done a
great job of making the installation of GRASS on Windows as painless as
possible.

We ran into a few glitches that might inform on Ricardo's experience.

First, we installed GRASS 6.1 CVS. The installer offers a choice of 6.0 or
6.1. This is really great. When we went to start it up using the batch file,
it would flash open a Cygwin terminal window and then close down. On a
hunch, I looked at the batch file. It is set for GRASS 6.0. You need to
replace grass60 with grass61 (2 places, one critical) for GRASS 6.1 cvs to
start.

Second, GRASS couldn't find wish--even though wish is in a relatively
standard location (/usr/local/bin) and in the bash path. I set the
GRASS_WISH variable to wish. I tried setting it in a couple places without
success, and it finally worked when I set it in .bash_profile, .bashrc, and
.grassrc6. I probably just need to set it once, but didn't have time to
selectively go through each one. Maybe someone can tell me.

Third, even after GRASS_WISH is set, I can't get GRASS to start in graphic
mode. I've set GRASS_GUI: gui and GRASS_GUI: tcltk in .grassrc6 repeatedly,
but it keeps getting reset to GRASS_GUI: text.

The GIS Manager works fine, but something is resetting GRASS to text mode
every time I start it. I assume it is somewhere in init.sh but haven't had a
chance to look at it yet. I don't think it is in the starting batch file
because I've searched for the word "text" and it is not there.

I'm going to try to install GRASS Cygwin on another computer to see if these
glitches are somehow machine specific. But I thought it would be helpful to
document them.

Michael
______________________________
Michael Barton, Professor of Anthropology
School of Human Evolution and Social Change
Arizona State University
Tempe, AZ  85287-2402
USA

voice: 480-965-6262; fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton


> From: Moritz Lennert <mlennert at club.worldonline.be>
> Reply-To: <mlennert at club.worldonline.be>
> Date: Fri, 20 May 2005 16:19:01 +0200 (CEST)
> To: Grass Developers List <grass5 at grass.itc.it>
> Subject: [Fwd: RE: [GRASS5] GRASS 6 automatic start]
> 
> ------------------------------ Original Message ------------------------------
> Subject: RE: [GRASS5] GRASS 6 automatic start
> From:    "Ricardo Armas" <rgoncalves at criticalsoftware.com>
> Date:    Fri, May 20, 2005 16:15
> To:      mlennert at club.worldonline.be
> ------------------------------------------------------------------------------
> 
> 
> Hello.
> 
> I'm a new GRASS user.
> I'm trying to develop a system in which GRASS has to start automatically
> trough a script. Usually, it does not start at the first attempt, even when I
> try to run it manually. I wait for some minutes but it does not start. I have
> to run it again and again until it starts. I tried to install it in a
> different computer but the same is happening.
> 
> Thanks and regards,
> Ricardo
> 
>> I have some problems with GRASS 6. Sometimes, even after a couple of
> tries,
>> GRASS does not start.
> 
> I you want us to help you, you have to tell us a bit more:
> 
> - How are you starting GRASS?
> 
> Running grass60.bat
> 
> - What exactly happens? Do you get any error messages?
> 
> I have to run grass60.bat for several times until it starts. No, I don't have
> any error message
> 
> - What OS are you using (GNU/Linux, MacOSX, etc)?
> 
> Windows NT
> 
> 
> 
> 
> 
> DISCLAIMER: This message may contain confidential information or privileged
> material and is intended only for the individual(s) named. If you are not a
> named addressee and mistakenly received this message you should not copy or
> otherwise disseminate it: please delete this e-mail from your system and
> notify the sender immediately. E-mail transmissions are not guaranteed to be
> secure or error-free as information could be intercepted, corrupted, lost,
> destroyed, arrive late or incomplete or contain viruses. Therefore, the sender
> does not accept liability for any errors or omissions in the contents of this
> message that arise as a result of e-mail transmissions. Please request a hard
> copy version if verification is required. Critical Software.
> 
> 
> 
> 
>