#2002 closed task (invalid)
The ordinal 32 could not be located in the dynamic link library proj.dll
Reported by: | rezagrass | Owned by: | |
---|---|---|---|
Priority: | critical | Milestone: | 6.4.4 |
Component: | Python | Version: | 6.4.2 |
Keywords: | wingrass | Cc: | andreas |
CPU: | x86-64 | Platform: | MSWindows XP |
Description
I have successfully installed the GRASS 6.4.2 on my Windows XP SP3.
I have already a python24 installed. On the 'Welcome to GRASS' box at the start up, every time I press 'Start Grass' button, an error message pops up reading: "The ordinal 32 could not be located in the dynamic link library proj.dll"
Would you please advise on a solution. It is greatly appreciated.
Thanks Reza
Change History (4)
comment:1 by , 11 years ago
Keywords: | wingrass added |
---|
comment:2 by , 11 years ago
Thanks for the reference to the grasswiki page, where I found the suggestion. I tried the same and it worked.
While I have kept a back up of the old .dll files in my system32 directory, I am not sure whether or not the updated dll files may affect other programs already using them!
Thanks and regards, Reza
comment:3 by , 11 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
Glad you solved it. I have extended the Wiki page accordingly: http://grasswiki.osgeo.org/wiki/WinGRASS_errors
Closing as invalid since no action item for the GRASS GIS package but duplicated DLLs at user side.
comment:4 by , 11 years ago
Cc: | added |
---|
Same here with libeay32.dll
German message: Die Ordnungszahl 4540 wurde in der DLL "libeay32.dll" nicht gefunden.
Renaming system32/libeay32.dll (v-0.9.8.8) to libeay-o.dll and copy GRASS-GIS/extralib/libeay32.dll (v-1.0.1.3) to system32/libeay32.dll works.
But I don't know if other programms are compatible with libeay32.dll (v-1.0.1.3).
Wouldn't it be better to force GRASS-GIS to run with its own DLLs?
This error sounds similar to:
http://grasswiki.osgeo.org/wiki/WinGRASS_errors
Q: Error message "The ordinal 63 could not be located in the dynamic link libexpat.dll."
Perhaps a similar solution applies here?