Re: 16 bit windows subsystem

From: Rick \ (rick_at_mvps.org)
Date: 02/20/05 

Date: Sun, 20 Feb 2005 13:39:54 -0500

Hi jean paul,

The simplest method to resolve this common problem is to copy autoexec.nt
from C:\Windows\repair to C:\Windows\system32 and overwrite the one that is
currently there.

Alternately, you can create a new autoexec.nt file and save it to the
\windows\system32 folder to overwrite the corrupted one. Click start/run and
type notepad, then click ok. Copy/paste the below code into it (instead of
typing it in to prevent errors), then click file/"save as". Navigate to the
C:\Windows\system32 folder, change the "save as file" type to "all types"
and name the file autoexec.nt, then click save (if prompted to overwrite the
existing one, do so).

@echo off
lh %SystemRoot%\system32\mscdexnt.exe
lh %SystemRoot%\system32\redir
lh %SystemRoot%\system32\dosx
SET BLASTER=A220 I5 D1 P330 T3

Reboot when finished. This usually fixes it, but you will find further steps
here if it doesn't:

Error message when you install or start an MS-DOS or 16-bit Windows-based
program
http://support.microsoft.com/?kbid=324767

Basically, you will have to expand new copies of command.com, autoexec.nt,
and config.nt to the system32 folder from the WinXP CD or I386 folder on
your hard drive. Sometimes, you need to create new ones and overwrite the
existing ones - the method is described in the article. 

-- 
Best of Luck,
Rick Rogers, aka "Nutcase" - Microsoft MVP
http://mvp.support.microsoft.com/
Associate Expert - WindowsXP Expert Zone
www.microsoft.com/windowsxp/expertzone
Windows help - www.rickrogers.org
"jean paul monmart" <monmart.jp@videotron.ca> wrote in message 
news:u5m8V92FFHA.3648@TK2MSFTNGP10.phx.gbl...
> hello every time I reboot or want to open some application this window 
> pops up:
> windows/system.32/autoexect.nt
> the system file is not suitafor running MS-DOS microsoft windows 
> applications choose close to terminate the application
> tried a few simples things but no luck. thank you .JP
>

Relevant Pages

  • Re: 16 BIT WINDOW SUBSYSTEM PROBLEM
    ... The simplest method to resolve this common problem is to copy autoexec.nt ... and name the file autoexec.nt, then click save (if prompted to overwrite the existing one, do so). ... Basically, you will have to expand new copies of command.com, autoexec.nt, and config.nt to the system32 folder from the WinXP CD or I386 folder on your hard drive. ... Windows help - www.rickrogers.org ...
    (microsoft.public.windowsxp.general)
  • Re: installing software
    ... The simplest method to resolve this common problem is to copy autoexec.nt ... then click save (if prompted to overwrite the ... and config.nt to the system32 folder from the WinXP CD or I386 folder on ... MS-DOS and Microsoft Windows applications. ...
    (microsoft.public.windowsxp.general)
  • Re: 16 bit windows subsystem
    ... > The simplest method to resolve this common problem is to copy autoexec.nt ... > \windows\system32 folder to overwrite the corrupted one. ... > and config.nt to the system32 folder from the WinXP CD or I386 folder on ... >> running MS-DOS and Microsoft Windows applications. ...
    (microsoft.public.windowsxp.general)
  • Re: Software wont work
    ... The simplest method to resolve this common problem is to copy autoexec.nt ... \windows\system32 folder to overwrite the corrupted one. ... and config.nt to the system32 folder from the WinXP CD or I386 folder on ... Windows help - www.rickrogers.org ...
    (microsoft.public.windowsxp.newusers)
  • Re: 16 bit windows subsystem
    ... The simplest method to resolve this common problem is to copy autoexec.nt ... \windows\system32 folder to overwrite the corrupted one. ... and config.nt to the system32 folder from the WinXP CD or I386 folder on ... > running MS-DOS and Microsoft Windows applications. ...
    (microsoft.public.windowsxp.general)
Loading