comdlg32.dll

Dear All,

I am using WindowsNT 4.0 workstation. I installed a new software on it.
and when I try to run it, it gives an error like "**the procedure entry
point printdlgexw could not be located in the dynamic link library
comdlg32.dll**" what should I do to avoid this type of error and run the
application properly.

Thank you.

Amitha:)


--
amithad
Posted via http://ms-os.com Forum to Usenet gateway

Hi,

amithad wrote:
> I am using WindowsNT 4.0 workstation. I installed a new software on it.
> and when I try to run it, it gives an error like "**the procedure entry
> point printdlgexw could not be located in the dynamic link library
> comdlg32.dll**" what should I do to avoid this type of error and run the
> application properly.

You probably need to update comdlg32.dll to a later version. This task
is usually left to Internet Explorer to accomplish - but if you don't
install IE you may still have the original comdlg32 that shipped with
WinNT4.

You may get a later version from http://www.dlldump.com/

Be careful however - updating any .dll file on a system can lead to
unpredictable results. You may also discover that when you try to
replace the .dll that the file is in use and access to overwrite it is
denied. I have often managed to solve this problem by doing the following:

1. Open a cmd prompt.
2. Change directory to your winnt/system32 folder.
3. Rename the 'locked' (access denied) .dll file
(eg: in your case = ren comdlg32.dll comdlg32.old)
4. Copy the new comdlg32.dll into place in winnt/system32
5. Reboot the system and the new .dll should now be in use.
6. If all is well you can delete the comdlg32.old

There is NO guarantee this will make your app run. It may require other
..dll 'updates' which you won't get notified about until the comdlg32
problem is solved. It is also possible that the app plain isn't meant to
work on NT4 (and is badly written and doesn't trap this condition) so
'fixing' the .dll files still won't let your app run

Let us know how you progress.

Calvin.