Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Dll.s for Windows 2000

Status
Not open for further replies.

Pinpoint

Programmer
Dec 23, 2001
49
GB
Hi,

I have developed a VC++ 6.0 app for Windows XP, which runs fine, but under Windows 2000 it will not run due to missing dll.s. It is a bog-standard dialog-based app. Does anyone have a list of dll.s needed for the different versions of Windows so I'll know which to include with the app ?

Thanks,

Pinpoint
 
????? I have no trouble of any dll missing in W2K.
Do you know which dll is missing?
On this site : you can download the dependency walker program for free. This program can examine your executable file and list all the dll's it needs.


Marcel
 
Marcel,

Thanks, I will try that program.

The missing dll was MFC42D.dll. This was when trying to run on Win 2000 in Gibraltar. Dont know whether that makes a difference...

Pinpoint.
 
Thd 'D' in MFC42D.dll means Debug version.
Debug libraries shouldn't be distributed.

Create a release version of your program, and you should be in business.

/JOlesen
 
You will still need to distribute the "MFC42.dll" (without the D) with your application. This dll contains all the Microsoft Foundation Classes and is not automatically installed on a machine running a version of the Windows OS.

Hope this helps you.
 
Thanks, I have recompiled as suggested, but then it asks for MSVCRTD.dll. Does MFC42.dll include all others required. Or is there a whole list I need to install ?

Pinpoint
 
MSVCRTD.DLL is the MS Visual C runtime dll - again a debug version
You shouldn't really distribute debug builds (run slower, and are larger). You need to distribute the msvcrtd.dl if you insist on using debug code (you will also need to the release version if you release release code too).
One way around this is to build statically linked apps (in the app build wizard it is an option. This way all the DLLs are linked in, and you can just hand out your exe file. Downside here is that these exees are then larger than otherwise.
M.

Hollingside Technologies, Making Technology work for you.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top