16 bit MS-DOS subsystem error

[racontijr]

Everytime a user logs onto the domain there is a pop up window with a
16 bit MS-Dos subsystem error...

C:\windows\system32\cmd.exe
config.net. The system file is not suitable for running MS-Dos and
Microsoft Windows applications. Choose "close' to terminate the
application.

This error does not pop up when you log in as an administrator. This
error will happen at any desktop on our network that a user tries to
log onto. I have searched quite a bit and I really havent found
anything useful. I have already tried to replace the files that were
possibly corrupt and that did not solve the problem.

Anyone have any other suggestions?

 

[Wesley Vogel]

cmd.exe has nothing to do with 16 bit MS-DOS subsystem.

cmd.exe has nothing to do with config.nt.

You have some sort of malware. A trojan/virus/worm.

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.

You might want to start in Safe Mode to run your antivirus and anti-spyware
software.

Running a full system antivirus scan or anti-spyware scan in Safe Mode can
be a good idea. Some viruses and other malware like to conceal themselves
in areas Windows protects while using them. Safe mode will prevent those
applications access and therefore unprotect the viruses or other malware
allowing for easier removal.

How to start Windows in Safe Mode Windows XP
http://www.bleepingcomputer.com/forums/index.php?showtutorial=61#winxo

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

 

[Peter Foldes]

If after you did what Wesley suggested (I recommend that also 1st) and still have the issue after then read the following

http://windowsxp.mvps.org/16bit.htm
http://support.microsoft.com/default.aspx?scid=kb;en-us;324767

 

[Wesley Vogel]

Peter,

You can try this for yourself.

Autoexec.nt and config.nt have nothing to do with cmd.exe (Windows Command
Processor). These files are used with command.com (MS-DOS Prompt), not
cmd.exe.

You can move, delete or otherwise mess with autoexec.nt and config.nt and
this will have absolutely *no* affect on cmd.exe.

Command.com will not open if either autoexec.nt or config.nt are missing,
messed up or whatever.

I moved my config.nt out of C:\Windows\System32 to my Desktop.

I opened cmd.exe, typed netstat and it worked fine.

I tried to open command.com and got this error message:
---------------------------
16 bit MS-DOS Subsystem
---------------------------
C:\WINDOWS\system32\command.com
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
---------------------------

I moved config.nt back to C:\Windows\System32 and command.com opened
correctly.

I moved my autoexec.nt out of C:\Windows\System32 to my Desktop.

I opened cmd.exe, typed netstat and it worked fine.

I tried to open command.com and got this error message:
---------------------------
16 bit MS-DOS Subsystem
---------------------------
C:\WINDOWS\system32\command.com
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
---------------------------

I moved both my autoexec.nt AND config.nt out of C:\Windows\System32 to my
Desktop.

I opened cmd.exe and typed netstat and it worked fine.

I tried to open command.com and got this error message:
---------------------------
16 bit MS-DOS Subsystem
---------------------------
C:\WINDOWS\system32\command.com
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
---------------------------

Command.com looks for CONFIG.NT first, then AUTOEXEC.NT.

The gist of this is that cmd.exe works fine without either autoexec.nt or
config.nt being where they belong.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

 

[Peter Foldes]

Wesley

I will give it a try as soon as my daughter gets home with the laptop that has XP on it. Right now my Desktop is a W2K3 production and I am not going to try it on this.

Interesting as to the results that you show. I am very curious and I will definitely give it a go and see.

I will repost to this thread on what I got.

Thanks Wes

 

[Wesley Vogel]

Have fun, I did. ;-)

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In