ntdvm cpu error - can I fix it?

[Guest]

http://www.btinternet.com/~steveswickedwebsite/ntvdm.jpg

I run Windows XP Home SP2. I can't really think of anything I may have
installed, uninstalled, deleted or changed that might have caused this, but
I'm not the only user of my PC.

Trust me, I have searched the web extensively for advice on this. I've done
all the usual fixes for "16 bit subsystem" errors even though they're not
quite mine - expanding of autoexec.nt, config.nt, command.com from disc,
deleting the VDD entry in the registry and made sure it was blank, etc. etc.

The fact remains, when I try to open any 16 bit app, such as pcpbios.exe
(shown in the picture, which opens when you run a test at pcpitstop.com), or
command.com or whatever it may be, I get this error. Does anyone know if it's
possible to fix this without a repair/reinstallation of the whole of Windows.
It's not too much of a problem right now - I don't really need to run any 16
bit apps, but it's certainly annoying and not something I'd like to leave
without fixing!

 

[Guest]

The following is an excerpt from the below website (URL). It is quite
extensive with a lot of reading. It is from Chap 9. It may be of interest
to you.

Windows NT 4.0 Workstation Architectur
http://www.microsoft.com/resources/documentation/windowsnt/4/workstation/reskit/en-us/archi.mspx

To run a 16-bit application in its own address space, you can do any of the
following:

1. Click Start, then click Run. When you enter the name of the 16-bit
process, the Run in a Separate Memory Space option is enabled. Click the
option and click OK.

2. From the command line, type

start /separate processname

You can also type:

start /shared processname

to run in the shared NTVDM process.

3. Create a shortcut to the process: Click the right mouse button on the
shortcut, then click Properties. Click the Shortcut tab, then click the Run
in Separate Memory Space option.


Tip Create two shortcuts to each of your 16-bit processes: One to run it in
a separate memory space and one to run it in the shared memory space.


In Task Manager and Performance Monitor, two instances of the NTVDM process
appear in the Process object Instances box. You can use their process IDs to
distinguish between them.

 

[Guest]

Thanks for replying. I had a quick look through, not really sure of its
relavance but thanks anyway.

PS. When I open command.com, if I chose to Ignore, the program will actually
load and function as normal apart from the line "Divide overflow" at the
start. I can run 16 bit apps I guess, but not entirely successfully.