gdi32.dll on Windows XP

[Esha]

I developed some features in VB6 project. They are based on using gdi32.dll.
My application works fine on Windows XP machines. User who has Windows 2000
Pro reported me the problem with that part of the application (Out of memory
message). I asked him to upgrade to Windows XP. He did it, but still has
that problem.
I was wondering if anybody met the different behavior of programs on full
Windows XP and XP upgraded from Windows 2000?
We compared versions of gdi32.dll on his machine and some other machines.
The user with problems has an older version than everybody else.
I made some research on internet and people say that simple replacement of
gdi32.dll file doesn't work, because this dll has some dependencies.

Any suggestions (except full reinstallation of Windows) please

Thank you

Esha

 

[Ken Halter]

I developed some features in VB6 project. They are based on using
gdi32.dll. My application works fine on Windows XP machines. User who has
Windows 2000 Pro reported me the problem with that part of the application
(Out of memory message). I asked him to upgrade to Windows XP. He did it,
but still has that problem.
I was wondering if anybody met the different behavior of programs on full
Windows XP and XP upgraded from Windows 2000?
We compared versions of gdi32.dll on his machine and some other machines.
The user with problems has an older version than everybody else.
I made some research on internet and people say that simple replacement of
gdi32.dll file doesn't work, because this dll has some dependencies.

Any suggestions (except full reinstallation of Windows) please

Thank you

Esha

Are you positive the error's coming from that DLL? What components are you
installing along with your app? You're not packaging that DLL, right? Are
you using any controls from FM20.dll or packaging Riched32.dll?

 

[MikeD]

I developed some features in VB6 project. They are based on using
gdi32.dll. My application works fine on Windows XP machines. User who has
Windows 2000 Pro reported me the problem with that part of the application
(Out of memory message). I asked him to upgrade to Windows XP. He did it,
but still has that problem.
I was wondering if anybody met the different behavior of programs on full
Windows XP and XP upgraded from Windows 2000?
We compared versions of gdi32.dll on his machine and some other machines.
The user with problems has an older version than everybody else.
I made some research on internet and people say that simple replacement of
gdi32.dll file doesn't work, because this dll has some dependencies.

You mean this user upgraded from Win2000 to WinXP SOLEY to run your
application because you asked them to? Wow!