- comerr32.dll
gssapi32.dll
k5sprt32.dll
krb5_32.dll
libeay32.dll
libiconv-2.dll
libintl-8.dll
libpq.dll
msvcr71.dll
ssleay32.dll
And some tips for Inno setup.
- avoid storing dlls in windows\system32 dir. Put it in you app directory and be sure that applications working directory is properly set in app shortcut or code (see MS SDK, SetDllDirectory function).This will save you a lot of problems (and sleepless nights in my case).
Here is why:
On some client machines I found ssleay32.dll and libeay32.dll with ridiculously high version numbers (Don't now who distribute this and in which application, but author probably want to be sure that HIS dll will always be installed). This prevents correctly written installer to install effectively newer versions of this dll's (but with smaller version numbers). Those dlls are loaded indirectly (libpq tries to load them while your app loads libpq) and, if they are too old with some functions missing, libpq "breaks". From application point of view - libpq can't be loaded/found!
- keep in mind that library search path was changed in win2k (see MS SDK Dynamic-Link Library Search Order or SafeDllSearchMode )
- if still wont work - help yourself with MS Dependency Walker utility (comes in resource kit) and/or sysinternals process expored.
- if you want database accessible from other hosts in lan, dont forget to chage pg_hba.conf and allow that. This can be easily automated in Inno setup.
- WinXP SP2 or WinXP sp3 - doesn't really matter in this case.