Article ID: 247925
Article Last Modified on 11/1/2006
APPLIES TO
- Microsoft Windows NT Server 4.0 Standard Edition
- Microsoft Windows NT Workstation 4.0 Developer Edition
This article was previously published under Q247925
SYMPTOMS
When you try to install 32-bit programs using InstallShield (Setup.exe), InstallShield may stop responding (hang).
CAUSE
This behavior can occur when the Microsoft Windows NT 4.0 virtual DOS machine (VDM) files are corrupted.
RESOLUTION
To resolve this behavior, rename the following files by using the .old file name extension at a command prompt, expand the original files from your Windows NT 4.0 CD-ROM, and then reapply the latest Windows NT 4.0 service pack:
| Autoexec.nt | |
| Config.nt | |
| Vdmredir.dll | (MS-DOS redirector driver) |
| Krnl386.exe | (16-bit kernel) |
| User.exe | (16-bit subsystem file) |
| Gdi.exe | (16-bit and 32-bit handles video calls) |
| Wowexec.exe | (Win16-bit subsystem) |
| Ntvdm.exe | (MS-DOS subsystem) |
| Ntio.sys | (I/O driver) |
| Ntdos.sys | (MS-DOS driver) |
| Redir.exe | (network redirector) |
Additional query words: ntvdm sbs
Keywords: kbprb KB247925
