Archived from groups: microsoft.public.windowsxp.general (
More info?)
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
"Hason Mortney" <kenmartining@yahoo.ca> wrote in message
news:1123543531.357937.283280@g49g2000cwa.googlegroups.com...
>I get this too. No problems on Windows 2000 or XP Home though.
>
Facebook
Twitter
Instagram