T
Tal Kol
I had the exact same thing with installation of a Xerox printer.
After checking the whole thing out, I've noticed my Windows 2000
did NOT have the file "ntvdm.exe" in my winnt\system32 folder.
Some trojan probably deleted it. I recovered the file from the
winnt\dllcache folder (also recovered "autoexec.nt"). Simply search
your entire HD for these 2 and copy them to the winnt\system32 folder.
After the files where recovered, the problem disappeared.
The problem occured since many propery sheets (like the printer settings)
are implemented using this Smart UI library which is a 16-bit
application. Since win2k is native 32-bit, the ntvdm (virtual dos machine)
is needed to emulate a 16-bit environment for the execution.
Original message:
After checking the whole thing out, I've noticed my Windows 2000
did NOT have the file "ntvdm.exe" in my winnt\system32 folder.
Some trojan probably deleted it. I recovered the file from the
winnt\dllcache folder (also recovered "autoexec.nt"). Simply search
your entire HD for these 2 and copy them to the winnt\system32 folder.
After the files where recovered, the problem disappeared.
The problem occured since many propery sheets (like the printer settings)
are implemented using this Smart UI library which is a 16-bit
application. Since win2k is native 32-bit, the ntvdm (virtual dos machine)
is needed to emulate a 16-bit environment for the execution.
Original message: