Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

After upgrade W98 to W2K - NTVDM error when run Dos base program

Status
Not open for further replies.

thuynguyen

Technical User
Aug 3, 2003
11
SG
Hi,
I am recently upgraded a W89 PC to w2K - it worked fine with almost all programs that installed under W98.

But there is a problem when I run a DOS base program, it displayed with error as :

"The NTVDM CPU has encountered an illigal
instruction, CS:2565 IP:94fa OP:8f21Oe 04 56
Choose Close to terminate the application.

With the same DOS base program, I run it OK on 3 different machines (with OS is W2K, SP4, NTFS file system - with the same settings as the machine I have problem runnung DOS base program)

What did I do wrong?
Please help.
 
I have a very large LOG full of messages relating to NTDVM errors. This type of message has become the bane of my life because I have a number of batch programs used to control my workstation. After a rather lengthy series of tests and much re-building of W2K environments my problems appear directly related to the Virus Protection. Now if you look at the Service Pack 3 for W2K you will find that NTDVM has a known problem with Trend (I use Trend). However, it can not be that simple because I have SP4 installed and if I want to use NTDVM I can not use the AV. My suspicion is that lurking somewhere in the dark recesses of the Registry is a conflict caused by the network drivers.

I have tried approaching the software OEMs involved and their response leads me to hope that I can get a little bit more info from people like yourself! I hope that something in my comments can help you.
 
I am not sure what to do, should PC needs to change the settings, may be somewhere in W2K config files or the registry?
 
This is just a guess. Compare the versions of command.com from one system where it works versus where it doesn't work and see if they are the same version.

I am guessing they are not.

joegz
"Sometimes you just need to find out what it's not first to figure out what it is."
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top