Re: 16 bit windows subsystem

Rick,
Thank you muchly! - I had the same problem - will see if it works now....

"Rick "Nutcase" Rogers" wrote:

> Hi,
>
> 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
>
> "Deepa" <Deepa.1rltpm@xxxxxxxxxxxx> wrote in message
> news:Deepa.1rltpm@xxxxxxxxxxxxxxx
> >
> > Does anyone know why I get the following error now when I try to run
> > several of my desktop icons? They used to all work fine; now all of a
> > sudden I get this error:
> >
> > 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.
> >
> >
> > --
> > Deepa
>
>
>
.

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 ... C:\Windows\system32 folder, change the "save as file" type to "all types" ... then click save (if prompted to overwrite the ... Windows help - www.rickrogers.org ...
    (microsoft.public.windowsxp.help_and_support)
  • 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)