Networks

That is common when the Autoexec.NT file has been modified (virus or spyware) or deleted.

Two ways out, first;

Run the system file chcecker START>RUN type 'sfc.exe /scannow' without quotes and hit enter, you will be asked for a CD or a path to the install directory, often C:/I386

Second is to search for Autoexec.nt and copy it to the proper system file,c:/WINNT or C:/Windows depending on whether your file system is an upgrade or OEM install(Windows usually ceates a backup when that file is changed). OR extract it straight

From a command prompt:

expand e:\i386\config.nt_ c:\windows\system32\config.nt
expand e:\i386\autoexec.nt_ c:\windows\system32\autoexec.nt
expand e:\i386\command.co_ c:\windows\system32\command.com
exit

Substitute "e:\" for your CD-ROM driver letter, and "c:\windows" for where your OS is located (probably C:/WINNT

The autoexec.nt file takes the place of the AUTOEXEC.BAT file for DOS sessions on Win2K and XP. It's basically a plain text file with some DOS type commands in it. Mine looks like so (with lots of comments removed):

----------------------------------
REM Install CD ROM extensions
lh %SystemRoot%\system32\mscdexnt.exe

REM Install network redirector (load before dosx.exe)
lh %SystemRoot%\system32\redir

REM Install DPMI support
lh %SystemRoot%\system32\dosx

SET BLASTER=A220 I5 D1 P330 T3
----------------------------------

If all else fails, rename the one on your system, then create a new one with the above lines, and see if your problem goes away.

Autoexec.Nt is similiar to the Autoexec.bat
for DOS and Windows 9X based machines.

You can edit this file, just like you
can edit the autoexec.bat file to see what
commands are running on startup.

Search for the autoexec.nt file, when you find
it, you can open it with NOTEPAD and look through
it to see what command may be causing the error!
Simply put a REM statement in front of the line/command in question, and re-boot to see if
it still gives you the error.

Good luck!

Bappy