[winGRASS] RE: Problem starting Grass

Thu Oct 14 10:01:07 EDT 2004

Glynn, you were right, there was an old libx11.dll(1998 old) in the
windows/system directory.  I'm guessing it must have been put there by vis5d
when I installed it, as that is when the problems started.  Anyway, thanks
for the help everyone, its good to have this working again.

Martin

-----Original Message-----
From: wingrass-admin at grass.itc.it [mailto:wingrass-admin at grass.itc.it]On
Behalf Of wingrass-request at grass.itc.it
Sent: Thursday, October 14, 2004 4:05 AM
To: wingrass at grass.itc.it
Subject: winGRASS digest, Vol 1 #224 - 3 msgs

Send winGRASS mailing list submissions to
	wingrass at grass.itc.it

To subscribe or unsubscribe via the World Wide Web, visit
	http://grass.itc.it/mailman/listinfo/wingrass
or, via email, send a message with subject or body 'help' to
	wingrass-request at grass.itc.it

You can reach the person managing the list at
	wingrass-admin at grass.itc.it

When replying, please edit your Subject line so it is more specific
than "Re: Contents of winGRASS digest..."

Today's Topics:

   1. Re: Re: problem starting grass (Gerrit P. Haase)
   2. Problem starting Grass (Martin Perra)
   3. Re: Problem starting Grass (Glynn Clements)

--__--__--

Message: 1
Date: Wed, 13 Oct 2004 21:49:14 +0200
From: "Gerrit P. Haase" <gp at familiehaase.de>
Organization: Esse keine toten Tiere
To: mperra at petrelrob.com
CC: wingrass at grass.itc.it
Subject: Re: [winGRASS] Re: problem starting grass

Martin Perra wrote:

> I don't recall if when I installed vis5d I had to get cygwinb19 from
> somwhere to make it work, It was awhile ago.  I think I may have though,
> because it was requesting it, and I would have put it in c:\cygwin\bin.
> That may be what caused the problem, but like I said, I have since deleted
> all traces of it.

Lets try it the other way around.  Go to the path were your executables
are installed and run:

for i in `ls *.exe`; do cygcheck $i ; done 2>&1 | tee log.output

This runs cygcheck on all exes in the directory where it is issued and
captures the output in the file log.output.

You may run also manually `cygcheck executable.exe' on suspicious
executables or DLLs.

And do the same for all DLLs, then look through the output if there is
an exe or DLL linked against cygwinb19.dll, IIRC the mysql client exe
was linked against cygwinb19, don't know if it is still the same mess
with MySQL.  Another old exe is sendmail for Cygwin which is available
via FTP somewhere.

There must be a DLL which is in PATH before the one you have new
installed so this other DLL which is linked against b19 is picked
up at first.

>  Your group is currently \"mkgroup\".  This indicates that
>   the /etc/group (and possibly /etc/passwd) files should be rebuilt.
>   See the man pages for mkpasswd and mkgroup then, for example, run
>   mkpasswd -l [-d] > /etc/passwd
>   mkgroup  -l [-d] > /etc/group
>   Note that the -d switch is necessary for domain users.
>
>
> I'm not sure aht it means though.

That means that you should run these both commands:
mkpasswd -l > /etc/passwd
mkgroup  -l > /etc/group

on a standalone computer with local (-l) accounts, or

mkpasswd -d > /etc/passwd
mkgroup  -d > /etc/group

on a PC in a domain where you logon with a domain account.

Gerrit
--
=^..^=

--__--__--

Message: 2
Reply-To: <mperra at petrelrob.com>
From: "Martin Perra" <mperra at petrelrob.com>
To: "Wingrass \(E-mail\)" <wingrass at grass.itc.it>
Date: Wed, 13 Oct 2004 17:00:20 -0600
Subject: [winGRASS] Problem starting Grass

Glynn, I tried your suggestions:

The most common filesystem problem with running GRASS on Cygwin is if
the GRASS database directory is on a filesystem which is mounted in
text mode (i.e. where Cygwin does automatic CRLF<->LF translation).
Either add "binmode" to the value of the CYGWIN environment variable,
or use Cygwin's "mount" program to change the mode to binary.

All drives are mounted as binary, so no luck there .. .

This might be an issue. GRASS requires that you own the mapset
directory which you select in the startup screen, so you need a valid
user ID (in /etc/passwd). Check that the output from the "id" and
"whoami" programs makes sense.

id brought up my user id, and whoami listed my domain credentials.  I'm
assuming that is fine as well. . .

I'm lost on this one.  I even tried installing it on my system at
home(almost identical hardware), and it worked, so I copied the cygwin
directory over to this system and tried running grass, and got the error!
I'm wondering if windows is somehow affecting this, although I couldn't find
any registry entries after searching for Cygwin that would indicate that . .
.

Martin Perra, BSc., Geog.
Petrel Robertson Consulting Ltd.
#500, 736 - 8th Avenue S.W. Calgary, Alberta
T2P 1H4
(403) 218-1615
www.petrelrob.com

--__--__--

Message: 3
From: Glynn Clements <glynn.clements at virgin.net>
Date: Thu, 14 Oct 2004 00:30:21 +0100
To: <mperra at petrelrob.com>
Cc: "Wingrass \(E-mail\)" <wingrass at grass.itc.it>
Subject: Re: [winGRASS] Problem starting Grass

Martin Perra wrote:

> I'm lost on this one.  I even tried installing it on my system at
> home(almost identical hardware), and it worked, so I copied the cygwin
> directory over to this system and tried running grass, and got the error!
> I'm wondering if windows is somehow affecting this, although I couldn't
find
> any registry entries after searching for Cygwin that would indicate that .
.

OK, having gone back and read your original message, my suggestions
aren't relevant to this particular problem.

Just to clarify, you are still getting the error message:

	"This application failed to start because cygwinb19.dll was
	not found. Re-installing the application may fix this problem"

right?

In the xtcltk package which I created (xtcltk-8.3.4.tar.gz, 2,289,326
bytes, 2002-03-28, MD5 2983750b94c52b8a5ce1aa3e39e54e45), wish8.3.exe
is linked against cygwin1.dll, not cygwinb19.dll. So, it must be one
of the other libraries which wish8.3.exe uses which requires b19.
AFAICT, wish8.3.exe requires 3 DLLs:

	libX11.dll
	cygwin1.dll
	KERNEL32.dll

KERNEL32.dll certainly won't require cygwinb19.dll, so it must be
libX11.dll (from XFree86).

Check whether you have multiple copies of libX11.dll; if you do, the
search order is the current directory, then the directories in $PATH,
then the /windows/system directory.

If you only have one copy (the one in Cygwin's /usr/X11R6/bin
directory), your Cygwin XFree86 package would appear to be rather out
of date.

If you have multiple copies, you should remove all except the one in
/usr/X11R6/bin.

--
Glynn Clements <glynn.clements at virgin.net>

--__--__--

_______________________________________________
winGRASS mailing list
winGRASS at grass.itc.it
http://grass.itc.it/mailman/listinfo/wingrass

End of winGRASS Digest