Got Some Info Mate
Chief, I got this information on how to fix this maybe, not sure though, but however read all of this and see what you can do to fix your problem.
Also changing the subject a little an ''asker'' means an answer.
Chief just uses this synonym or whatever for a quick word to say answer.
And Chief also, if you want answers go to the Microsoft site and then Google it! Best way!
I do it the other way around for some reason though really.
SUMMARY
When using a Virtual DOS Machine (NTVDM) to run an MS-DOS or 16-bit-based application on a non-VME (Virtual Mode Extensions) processor, the session may stop responding. In addition, you may receive the following error message:
Program Error
NTVDM.EXE has generated errors and will be closed by Windows.
You will need to restart the program.
An error log is being created.
Dr. Watson creates a log, and the only option that you can click is OK. At this point, you have to quit the NTVDM process manually.
MORE INFORMATION
Virtual-8086 mode is used by Windows to provide MS-DOS and 16-bit applications the ability to run in their own environment without interfering with other applications. Most processors (CPUs) in the market today have support for Virtual Mode Extensions (VME), which provides enhancements to virtual 8086 mode. However, it is possible that a processor may not have or fully support VME.
Although Windows NT Virtual DOS Machine (Ntvdm.exe) does have the code path to also support non-VME processors, it was not tested in Windows 2000 and there are no plans to ensure 100% compatibility for non-VME processors in future versions of the OS. As a result, under certain configurations of hardware, drivers, memory, and application usage, systems that have non-VME processors may exhibit the symptoms listed earlier when you use NTVDM.
There was some other article about it on the Microsoft site but everytime I went to it I got redirected to the updated article which had ''irrelevent'' information about it.
Chris_OJB_DF645 --