Autoexec.nt problem

[Guest]

I have an eSpanish Professor disk that I've been able to run dozens of times
on my computer with XP Home before (SP1) and now, when I go to install the
prog again, I get an error:

16 bit Windows Subsystem
-------------------------------
C:\WINDOWS\SYSTEM32\AUTOEXEC.NT. The system file is not suitable for running
MS-DOS or Mivrososft Windows applications. Choose 'Ckose' to terminate the
application.

|Close| |Ignore|

What might be the problem and how can I fix it? Thnx...

 

[David H. Lipman]

Go to; Start --> Run
enter; cmd.exe

{ assuming the WinXP CDROM disk is in drive "D:" }
In the Command Prompt enter...
expand D:\i386\autoexec.nt_ %windir%\system32\autoexec.nt

Dave



| I have an eSpanish Professor disk that I've been able to run dozens of times
| on my computer with XP Home before (SP1) and now, when I go to install the
| prog again, I get an error:
|
| 16 bit Windows Subsystem
| -------------------------------
| C:\WINDOWS\SYSTEM32\AUTOEXEC.NT. The system file is not suitable for running
| MS-DOS or Mivrososft Windows applications. Choose 'Ckose' to terminate the
| application.
|
| |Close| |Ignore|
|
| What might be the problem and how can I fix it? Thnx...

 

[Guest]

Thanks, Dave! I got the problem fixed earlier, but I appreciate the response.

Neo

 

[Malke]

I have an eSpanish Professor disk that I've been able to run dozens of
times on my computer with XP Home before (SP1) and now, when I go to
install the prog again, I get an error:

16 bit Windows Subsystem
-------------------------------
C:\WINDOWS\SYSTEM32\AUTOEXEC.NT. The system file is not suitable for
running MS-DOS or Mivrososft Windows applications. Choose 'Ckose' to
terminate the application.

|Close| |Ignore|

What might be the problem and how can I fix it? Thnx...

Error message when you install or start an MS-DOS or 16-bit
Windows-based program:

http://support.microsoft.com/default.aspx?scid=kb;en-us;324767&Product=winxp

This can also be caused by malware.

Also, AVAST (antivirus software) can be the cause if you have WinXP SP2
installed:

http://groups.google.com/[email protected]

You can put back the standard version of autoexec.nt/config.nt by
copying a backup copy held in %windir%\repair\ to %windir%\system32\
(%windir% is typically C:\Windows) instead of using the procedure in
the KB article above.

Make sure you have a current version (not earlier than 2003) antivirus
installed using updated definitions.

Malke

 

[Alex Nichol]

Go to; Start --> Run
enter; cmd.exe

{ assuming the WinXP CDROM disk is in drive "D:" }
In the Command Prompt enter...
expand D:\i386\autoexec.nt_ %windir%\system32\autoexec.nt

There is no needs to be so complex. There is a reserve copy of
Autoexec.nt in C:\windows\repair, and all that is needed is to *copy*
that into windows\system32

And then trace down what is causing the damage to it; probably a trojan

 

[David H. Lipman]

Maybe its is more complex than a copy from the ..\repair folder but that too may be altered.
My suggestion bypasses that possibility and restores the stock distribution file.

Dave



| David H. Lipman wrote:
|
| >Go to; Start --> Run
| >enter; cmd.exe
| >
| >{ assuming the WinXP CDROM disk is in drive "D:" }
| >In the Command Prompt enter...
| >expand D:\i386\autoexec.nt_ %windir%\system32\autoexec.nt
|
| There is no needs to be so complex. There is a reserve copy of
| Autoexec.nt in C:\windows\repair, and all that is needed is to *copy*
| that into windows\system32
|
| And then trace down what is causing the damage to it; probably a trojan
|
|
| --
| Alex Nichol MS MVP (Windows Technologies)
| Bournemouth, U.K. (e-mail address removed)8E8L.org (remove the D8 bit)

 

[Torgeir Bakken \(MVP\)]

Maybe its is more complex than a copy from the ..\repair folder
but that too may be altered. My suggestion bypasses that
possibility and restores the stock distribution file.

Hi

Note that many don't have a WinXP CDROM...

I also always mention that the missing Autoexec.nt could be caused by
a trojan or something similar, e.g. TrojanDownloader.Win32.Dia.a, more
about this in the post by Hal here:

http://groups.google.com/[email protected]

 

[David H. Lipman]

Torgeir:

That's a good point if there is NO CDROM or if there is NO i386 directory then the ..\repair
directory would be the way to go.

And it is true that there are infectors associated with AUTOEXEC.NT as a loading vector.

I'll adjust my reply accordingly...

Thanx...
Dave




| David H. Lipman wrote:
|
| >
| >> There is no needs to be so complex. There is a reserve copy of
| >> Autoexec.nt in C:\windows\repair, and all that is needed is to
| >> *copy* that into windows\system32
| >>
| >> And then trace down what is causing the damage to it; probably
| >> a trojan
| >
| >
| > Maybe its is more complex than a copy from the ..\repair folder
| > but that too may be altered. My suggestion bypasses that
| > possibility and restores the stock distribution file.
| Hi
|
| Note that many don't have a WinXP CDROM...
|
| I also always mention that the missing Autoexec.nt could be caused by
| a trojan or something similar, e.g. TrojanDownloader.Win32.Dia.a, more
| about this in the post by Hal here:
|
| http://groups.google.com/[email protected]
|
|
| --
| torgeir, Microsoft MVP Scripting and WMI, Porsgrunn Norway
| Administration scripting examples and an ONLINE version of
| the 1328 page Scripting Guide:
| http://www.microsoft.com/technet/scriptcenter/default.mspx