[GRASS-user] g.list ... -1073741701

[Edmund Swylan]

Dear Helmut,

HK> (1) could you open a normal windows console provided by the operating system
HK>     and type: where sqlite3.dll
HK>     and post the result

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\es>cd ..\..

C:\>where sqlite3.dll
'where' is not recognized as an internal or external command,
operable program or batch file.

C:\>


But ... I believe that sqlite3.dll is the one .dll I have dealt with.

HK> (2) could you try the OSGeo4W-winGRASS [A] without any change in your
HK>     settings or files in the OSGeo4W-winGRASS installation and try winGRASS
HK>     there; type 'where sqlite3.dll' in the OSGeo4W-windows console

Maybe. But, surely, a network installer has more, not fewer, options than
a stand-alone one?

HK> (3) and as Markus suggested in the other mail: try Dependency Walker to
HK>     check dll-dependencies

Done ... to an extent.

HK> (4) any chance to use another windows box than winXP?

I have a 95 and several versions of 98.

HK> the dll-issues looks like a mismatch and mixing of dlls and their
HK> dependencies in %PATH% variable.

Yes. And that is why I think I stand a slightly better chance with 6.4.4
whose PATH seems to be set by three .bats and not by a GRASS...py.

HK> AFAICT starting from scratch may be an option.

What's scratch? Uninstalling all GRASSes and killing the remaining weeds
in, say, Documents and Settings? Has been - almost - done once or twice.
`Almost', since I did not weed out the stuff "within" QGIS.

I have also done a 7.2.1 (and Spearfish) installation on another (XP)
computer - one without any SQLite or QGIS. Same result.

Since
(1) in your experiment the problem has not arisen, and
(2) all GRASS specific .dlls (should) occur on the PATH before their
    possible competitors,
it would seem that there is an indispensable .dll which is not part of
the GRASS distribution and which I have not or have an unsuitable version
of. The DependencyWalker has already come up with EFSADU.dll and MSJAVA.dll.
The former can hardly be indispensable, the latter I have now introduced
into C:\WINDOWS\system32. Unsuitable versions are more difficult.

Yours,

Edmund