Thread: 8.3 libpq.dll not working on some versions of windows

Hi,
We have been running into issues where the 8.3.x versions of libpq.dll
will not load in certain
versions of windows and WINE(does not load at all on wine).

It seems to be hit and miss on Windows XP, mostly seems to affect SP3
and some SP2 installs of XP.

I have only been able to get around this by installing a much older
version of libpq.dll.

And I did have all the dependencies installed along with the DLL, it
just plain refuses to load.  I also check that there were no
rouge copies of the files in system32.

Thanks,

Tony

--- On Sat, 15/11/08, Tony Caduto <tony_caduto@amsoftwaredesign.com> wrote:
> Hi,
> We have been running into issues where the 8.3.x versions
> of libpq.dll will not load in certain
> versions of windows and WINE(does not load at all on wine).
>
> It seems to be hit and miss on Windows XP, mostly seems to
> affect SP3 and some SP2 installs of XP.
>
> I have only been able to get around this by installing a
> much older version of libpq.dll.
> And I did have all the dependencies installed along with
> the DLL, it just plain refuses to load.

Pretty sure I've used most 8.3.x versions here on both sp2 and 3.

How have you chacked you have all the dependencies? (I like depends.exe)

http://www.dependencywalker.com/

Glyn Astill wrote:
>
> Pretty sure I've used most 8.3.x versions here on both sp2 and 3.
>
> How have you chacked you have all the dependencies? (I like depends.exe)
>
> http://www.dependencywalker.com/
>
>
>
>
>
hmm, the problem seems to be that MSVCR71.DLL has a problem with some
versions of Kernel32.DLL,
dependency walker reports this:
Error: At least one module has an unresolved import due to a missing
export function in an implicitly dependent module.
I have all the required files in the same dir as my exe

I did this test on the latest version of wine (libpq.dll always worked
in wine before), and I was getting the exact same behavior on the
PCs at work.  WINE is not a good test for this I know, but all I have at
the moment.

I will have to try this on the PCs at work(on Monday) that are having
the issue.  I know one of them is a really old XP (6 years) that was
just recently updated to SP3.