It does not help much at all.
What program do you think that you are opening when you get the error
message??? This is important!
If you were using command.com, it runs under ntvdm.exe, you will not see
command.com listed in the Task Manager.
command.com is the MS-DOS command interpreter and runs under ntvdm.exe (NT
Virtual Dos Machine). ntvdm.exe emulates an Intel 80286 machine running
MS-DOS. NT uses a VDM that contains an extra software layer called the
Win16 on Win32 (WOW) layer and wowexec.exe (Windows On Windows Execution
Process) supplies that extra layer.
ntvdm.exe and wowexec.exe should only run if you're running a 16-bit
application like command.com or some application that was placed on your
machine by a trojan/virus/worm. Something like CMD.COM, NETSTAT.COM,
PING.COM, REGEDIT.COM, TASKKILL.COM, TASKLIST.COM or TRACERT.COM.
None of these files are XP files.
The 16 bit MS-DOS Subsystem uses a special version of command.com and
command.com uses autoexec.nt and config.nt. command.com will not open if
either autoexec.nt or config.nt are missing, messed up or whatever. You
will get an error message:
---------------------------
16 bit MS-DOS Subsystem
---------------------------
C:\WINDOWS\System32\command.pif
C:\WINDOWS\SYSTEM32\AUTOEXEC.NT. The system file is not suitable for running
MS-DOS and Microsoft Windows applications. Choose 'Close' to terminate the
application.
---------------------------
Close Ignore
---------------------------
or
---------------------------
16 bit MS-DOS Subsystem
---------------------------
C:\WINDOWS\System32\command.pif
C:\WINDOWS\SYSTEM32\CONFIG.NT. The system file is not suitable for running
MS-DOS and Microsoft Windows applications. Choose 'Close' to terminate the
application.
---------------------------
Close Ignore
---------------------------
The command.pif for command.com looks for CONFIG.NT first, then AUTOEXEC.NT.
CONFIG.NT and AUTOEXEC.NT [[are parsed each time a VDM is started. If there
are problems with these files, you may see error messages such as:
16 Bit Windows Subsystem - Hidden Console of WOWVDM.
The NTVDM CPU has encountered an illegal instruction. Source
Either restore the Config.nt or Autoexec.nt file, or remark (REM) any
nonstandard lines in the existing files to determine which file is the
source of the errors. Remove the offending lines.
You should also make sure that there is only one copy of the Windows
Command.com file, in the System32 folder. ]]
from...
Entries in Config.nt or Autoexec.nt May Cause NTVDM Errors
http://support.microsoft.com/kb/156687
COMMAND.COM or some other file may be corrupted. Or you may have a
trojan/virus/worm. Or your Config.nt and/or Autoexec.nt files have
nonstandard lines in them.
Update your antivirus software and run a full system scan.
Update whatever anti-spyware applications that you have and run a full
system scan with each one.
Then run the System File Checker, sfc.exe. SFC fixes screwed up system
files.
To restore config.nt and autoexec.nt, copy the autoexec.nt and config.nt
files from C:\Windows\Repair to C:\Windows\System32 And set Attributes for
autoexec.nt to Read-only.
Or %systemroot%\Repair to %systemroot%\System32
Read-only
[[Specifies whether this file is read-only, which means that it cannot be
changed or accidentally deleted.]]
1. Right click the file.
2. Properties.
3. Select: Read-only.
4. Click: Apply.
5. Click: OK.
--
Hope this helps. Let us know.
Wes
MS-MVP Windows Shell/User
In
