🚀 go-pugleaf

JD,

I found the same information. I got a listing of all of the DLLS and had the 
client
match them up with version and file size on his side. I had him create a 
file using
that Process Explorer that listed the same info and send it to me, so that 
we both
looked it over.

I'll try the test program and see how it goes. Do I need to load every DLL 
or just
the primary ones from the previous post? Reason I ask is that I have a 
feeling that
one of the sub-dll's is failing and that's why the DLL name isn't given.


-Tom



"JD" <nospam@nospam.com> wrote in message 
news:431e2d54@newsgroups.borland.com...
>
> "Tom" <thomasf1021@hotmail.com> wrote:
>>
>> [...] but anyone else have any ideas?
>
> A quick google tells me that the error that your getting can
> be caused by a file size of zero or conflicting dll versions.
>
> The file sizes can be easily confirmed by the user and a
> simple test program should tell you where it fails. Just use
> LoadLibrary to see if and when one fails and while you're at
> it, check for it's version. For example:
>
>    WORD Major = 0;
>    HINSTANCE hDll = ::LoadLibrary( "Some.dll" );
>    if( hDll )
>      {
>          DLLGETVERSIONPROC lpDllGetVersion = (DLLGETVERSIONPROC) 
> ::GetProcAddress( hDll, "DllGetVersion" );
>          if( lpDllGetVersion )
>            {
>                DLLVERSIONINFO dvi = { sizeof(DLLVERSIONINFO), 0 };
>                if SUCCEEDED(lpDllGetVersion(&dvi)) Major = 
> dvi.dwMajorVersion;
>            }
>          ::FreeLibrary( hDll );
>      }
>
> ~ JD
>