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 gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

NTVDM encountered a hard error

Status
Not open for further replies.

ChuckG

MIS
Feb 28, 2001
211
US
Have a 2003 SP1 Server that has several 16bit programs that run, and have been running fine for a while.

I loaded VMWare onto the system and now I keep getting
NTVDM encountered a hard error and a Close/Ignore box.

If I close it, it stops the program. Ignore continues, but I can't be at the console everytime one of these programs runs.

Everything I'm seeing references 16bit programs being part of the cause and suggested a couple of items which I've tried as follows:

Make the TEMP and TMP folders be c:\temp instead of the default because the 16bit programs can't handle extended folder names.

Take a look at the Config.nt file, it's pretty basic and is still set to the default settings which used to work.

Check a registry setting for 8.3 file/folder restrictions.
I checked and mine was set as suggested on 0 already.

Anyone have any suggestions? I need to get this cleaned up ASAP.

Thanks
ChuckG
 
Try the following. 16bit programs do not like long file space names.

Select My Computer
Properties
Advanced
Environment Variables
User Environment Variables
Set TEMP and TMP to c:\temp




Jim W MCSE CCNA
Network Manager
 
Jim,
Thanks for the tip, but if you read my original message, I did just that. Unfortuantly that hasn't helped.

ChuckG
 
Sorry. Should have read the post more closely.

Jim W MCSE CCNA
Network Manager
 
No sweat, I appreciate any and all help with this.
I've been searching for a solution for a while.

Even found a reference to a registry entry that left a VDD
that was pointing at a non-existant DLL from Symantec (used to have Symantec Antivirus on here) that someone else said had caused some of their errors, but removing that VDD entry from the registry that hasn't helped either.

ChuckG
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top