Re: Windows error message

From: Torgeir Bakken \(MVP\) (Torgeir.Bakken-spam_at_hydro.com)
Date: 01/31/05


Date: Mon, 31 Jan 2005 22:45:48 +0100

Laurel wrote:

> Over the past few months, I've received this error message in various
> contexts (see end of message). It hasn't ever clearly caused any problems,
> but I'm wondering if it might be tied to some problems I've experienced here
> and there. The only autoexec.nt file I have is in a folder called
> c:\Windows\repair. Should I copy it to some other place? I used to run NT,
> but I'm running XP now.
>
> 16 bit Windows Subsystem
>
> c:\WINDOWS\SYSTEM32\AUTOEXEC.NT. The system file is not suitable for running
> MS-DOS andMicrosoft Windows applications.
Hi

Your autoexec.nt problem is most likely caused by a worm or if you have
WinXP SP2 and AVAST (antivirus software) installed, it also can cause
this error.

To solve the problem:

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

Alternatively:

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 (see further down for instructions on how).

Could be caused a trojan or something similar, e.g.
TrojanDownloader.Win32.Dia.a, more about this here:
http://groups.google.com/groups?selm=5f6f139.0409140618.749324fe%40posting.google.com

Also, AVAST (antivirus software) can be the cause if you
have WinXP SP2 installed:
http://groups.google.com/groups?threadm=8PCdnSzBqtmadsPcRVn-gQ%40comcast.com

If you want to copy the file from the repair folder, you can use
this procedure:

Open a command prompt, using e.g. Start/Run --> cmd.exe

In the command prompt, type in the following two commands exactly as
you see them in this post (you need to press enter for each command
to execute them):

cd /d %windir%
copy repair\autoexec.nt system32\*.*

Here is a "screen dump" from how it looks when I do it on my computer:

------------------------------------------
C:\>cd /d %windir%

C:\WINDOWS>copy repair\autoexec.nt system32\*.*
             1 file(s) copied.
------------------------------------------

-- 
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


Relevant Pages

  • Re: WinXP "Search" window opens totally blank
    ... To reinstate the "Install" command, apply the .INF file association fix from ... Ramesh Srinivasan, Microsoft MVP [Windows XP Shell/User] ... Right-click the Srchasst.inf file, and then click Install. ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: Crypt32.cll
    ... After the service pack install you have ... Run Disk CleanUp on your computer first, then try to run the Windows updates ... I typed in the command and was prompted to ... regsvr32 wuapi.dll ...
    (microsoft.public.windowsxp.help_and_support)
  • re:a quick question
    ... oh and i saw an error more or less when i esit the so called startx it ... I am a windows user but i have some experince ... > the install for some reason i log into root and i use the startx command ... This will cause FreeBSD to issue the "startx" command on a per-user basis. ...
    (freebsd-questions)
  • RE: Explorer.exe will not load, no icons or task manager
    ... Windows Defender. ... Used system restore from the cmd prompt, but it did not help, no ... when I enter that in the command prompt it says the path is invalid ... I did all of the remaining critical updates after the install of SP2. ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: Many KBxxxxx.log failure files after trying to patch SP2
    ... I tried running this command from the default documents and settings prompt ... updates" box, and all 54 now showed up, and said they are intalled and on. ... listed is the windows 1.3 installer, and the windows service pack 2. ... I ran the install program, ...
    (microsoft.public.windowsupdate)

Loading