[ psqlodbc-Bugs-1010862 ] Will not run on Windows 2000 and older, missing symbols

Bugs item #1010862, was opened at 2010-08-05 18:20
You can respond by visiting:
http://pgfoundry.org/tracker/?func=detail&atid=538&aid=1010862&group_id=1000125

Category: None
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Darrell Walisser (mediak)
Assigned to: Nobody (None)
Summary: Will not run on Windows 2000 and older, missing symbols

Initial Comment:
psqlODBC version: 8.04 0200

Attempting to use the driver under Windows 2000 in ODBC driver manager yields this:

"The setup routines for the PostgreSQL ANSI ODBC driver could not be loaded due to system error code 127"

then another dialog:

"Driver's ConfigDSN, ConfigDriver, or ConfigTranslator failed"
"Could not load the setup or translator library"

I turns out that the psqlodbc*.dll is missing these symbols in WS_32.dll: freeaddrinfo, getaddrinfo, getnameinfo

This article explains why they are missing, these were added in XP but there is a trick to make them work in earlier versions. Basically this could be fixed with a recompile. I could not compile with VS6 but I am having a go with Visual Studio Express 2008 (I usually use mingw for all Windows development so this may not work).

http://msdn.microsoft.com/en-us/library/ms737931%28VS.85%29.aspx

----------------------------------------------------------------------

>Comment By: Hiroshi Inoue (hinoue)
Date: 2010-09-22 15:36

Message:
Could you please try the drivers on testing for 8.4.0202 at
http://www.ne.jp/asahi/inocchichichi/entrance/psqlodbc/
?

----------------------------------------------------------------------

Comment By: Cesare Leonardi (celeonar)
Date: 2010-09-19 21:14

Message:
I can confirm this bug: 8.04 0200 under Win2000 SP4 gives the same error as Darrel and also for me the previous 0100 works. At least one step further, since SSL is not activable, but it's another story...

Cesare.

----------------------------------------------------------------------

Comment By: Darrell Walisser (mediak)
Date: 2010-08-05 18:43

Message:
I discovered that rolling back to 804_0100 solves the
problem, for now. I hope this works as well as 0804_0200.

----------------------------------------------------------------------

You can respond by visiting:
http://pgfoundry.org/tracker/?func=detail&atid=538&aid=1010862&group_id=1000125