Referenced DLLs Missing, But Code Works. Ignore Warning When Packaging?

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

MSDN - 20 Feb 2005 05:29 GMT

I downloaded some code that enables me to capture and print the active form
and added it to my VB6 application. Strange thing is it works fine on my
development workstation, but I'm not sure how it's working because it
depends on a whole slew of API Declares that refer to GDI.dll, oc25.dll, and
USER.dll and I have none of those on my computer.

I'm developing on a Windows Me. I didn't realize I was missing the three
DLLs until I tried to package the application. The Package & Deployment
Wizard complains that it can't find those three DLLs.

I'm wondering how it can work without those DLLs. I downloaded the oc25.dll
so I now have that one, but the GDI.dll seems to be difficult to get ahold
of. Does it automatically bump up to the 32 version of the other two?
Would it make sense to ignore the warning about the now missing GDI.dll and
USER.dll? Thanks.

Reply to this Message

Ralph - 21 Feb 2005 12:12 GMT

> I downloaded some code that enables me to capture and print the active form
> and added it to my VB6 application. Strange thing is it works fine on my
[quoted text clipped - 11 lines]
> Would it make sense to ignore the warning about the now missing GDI.dll and
> USER.dll? Thanks.

These files are a fundamental part of the Windows Operating System. Never
install, upgrade, or swap out system files (whether 16-bit or 32-bit). Never
copy system files from one platform to another. (Use only SPs or System
upgrades) Never include system files in an install package. Otherwise you
may render the target OS inoperable.

16-bit applications work on 32-bit systems because the older calls are
automatically wrapped and redirected to newer services.

-ralph

Reply to this Message

VB Forum / COM / February 2005

Referenced DLLs Missing, But Code Works. Ignore Warning When Packaging?