This is most likely caused by the 16-bit application you run, not by
ntvdm.exe. You can easily prove it:
1. Reboot your machine.
2. Click Start / Run / cmd {OK}
3. Type debug.exe {Enter}
4. Check your CPU loading
You will find that even though ntvdm is now running, the
CPU loading is low. This is because debug.exe is a
well-behaved 16-bit application.
This is most likely caused by the 16-bit application you run, not by
ntvdm.exe. You can easily prove it:
1. Reboot your machine.
2. Click Start / Run / cmd {OK}
3. Type debug.exe {Enter}
4. Check your CPU loading
You will find that even though ntvdm is now running, the
CPU loading is low. This is because debug.exe is a
well-behaved 16-bit application.
Did you run the experiment I suggested? If it cleared ntvdm.exe
then your Java application may be flawed. What makes you in
fact think that it is the Java application? I would have expected
it to be a 32-bit application, unless it shells out to a 16-bit
legacy program.
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.
