XP Pro & ntvdm.exe: 16 bit doesn't work, what to do?

[Ruediger Wolf-Sebottendorff]

Hi,

I've searched a lot but nothing helped, so I hope somebody here knows
something about that issue:

I need to install software for a medical device on a notebook, which runs on
XP Pro (upgraded from XP Home, most patches via Windows Update). The device
needs a serial port which the notebook doesn't have, so I installed a
USB/serial adapter.
The software is a collection of smaller programs which are mixed 32 and 16
bit mode. The 32 bit applications work fine, but every 16 bit program i try
to start - even command.com - dies shortly after it's corresponding
ntvdm.exe died, without any error message and no 'zombie' ntvdm.exe in
process list.
All I found was KB314106 which describes how to check the ntvdm-subsystem,
like i did.

The software works fine on a desktop system (XP Pro), even with the USB
adapter, so I checked the NTVDM components (Ntio.sys, Ntdos.sys, ntvdm.exe,
redir.exe and all the other stuff) against the other installation, but
found no difference.

If there are other ways to fix this problem than to reinstall XP, please
tell me, it would save a lot of time :-/

Rüdiger

 

[Malke]

Hi,

I've searched a lot but nothing helped, so I hope somebody here knows
something about that issue:

I need to install software for a medical device on a notebook, which
runs on XP Pro (upgraded from XP Home, most patches via Windows
Update). The device needs a serial port which the notebook doesn't
have, so I installed a USB/serial adapter.
The software is a collection of smaller programs which are mixed 32
and 16 bit mode. The 32 bit applications work fine, but every 16 bit
program i try to start - even command.com - dies shortly after it's
corresponding ntvdm.exe died, without any error message and no
'zombie' ntvdm.exe in process list.
All I found was KB314106 which describes how to check the
ntvdm-subsystem, like i did.

The software works fine on a desktop system (XP Pro), even with the
USB adapter, so I checked the NTVDM components (Ntio.sys, Ntdos.sys,
ntvdm.exe, redir.exe and all the other stuff) against the other
installation, but found no difference.

Since the program works on your XP Pro desktop, this obviously isn't a
problem with XP not being able to run the 16-bit program parts. Check
in the BIOS of the laptop and make sure the serial port is enabled. I
definitely don't think reinstalling XP is the answer, but I don't have
anything more specific. Good luck.

Malke

 

[Ruediger Wolf-Sebottendorff]

Hi,

OK, I got it:

Since the program works on your XP Pro desktop, this obviously isn't a
problem with XP not being able to run the 16-bit program parts.

What confused me was the fact that every 16-bit program quit after a short
time (command.com, sysedit.exe, etc.) with ntvdm.exe dying.
Sysinterals file monitor showed a svchost.exe with an illegal call which
caused the crash. That was a second malicious C:\WINDOWS\svchost.exe and
all worked fine after deleting it.
And to keep it gone it was really helpful to update my antivirus protection
which found a nice little trojan.

Since I'm working with Linux most of the time, I'm just too spoiled in
security issues ;-)

I definitely don't think reinstalling XP is the answer, but I don't have
anything more specific. Good luck.

Thanks for answering!
Rüdiger

 

[Malke]

Hi,

OK, I got it:


What confused me was the fact that every 16-bit program quit after a
short time (command.com, sysedit.exe, etc.) with ntvdm.exe dying.
Sysinterals file monitor showed a svchost.exe with an illegal call
which caused the crash. That was a second malicious
C:\WINDOWS\svchost.exe and all worked fine after deleting it.
And to keep it gone it was really helpful to update my antivirus
protection which found a nice little trojan.

Since I'm working with Linux most of the time, I'm just too spoiled in
security issues ;-)


Thanks for answering!
Rüdiger

Hi, I'm delighted you got it working. Yes, I know we Linux users are
spoiled, but we mustn't get sloppy. With Windows, unless smoke is
pouring out of the machine, the first troubleshooting steps are always
to check for viruses and spyware. However, I must say that if you keep
your WinXP box nice and clean, it will be stable and well-behaved for
you. But it is key to do the proper maintenance.

Cheers,

Malke (SUSE 9.0 with 9.1 on order!)