C:\WINDOWS\SYSTEM32\AUTOEXEC.NT

  Exeter_surfer 11:41 30 Nov 04
Locked

C:\WINDOWS\SYSTEM32\AUTOEXEC.NT. the system file is not suitable for running MS-DOS and microsoft windows applications.

What does this mean? Im trying to install software and this keeps coming up!!

help!

  ACOLYTE 11:46 30 Nov 04

click here may help.

  AndySD 11:56 30 Nov 04

Or if that doesnt work then Open Notepad and Copy and Paste in the following

@echo off

REM AUTOEXEC.BAT is not used to initialize the MS-DOS environment.
REM AUTOEXEC.NT is used to initialize the MS-DOS environment unless a
REM different startup file is specified in an application's PIF.

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

REM The following line enables Sound Blaster 2.0 support on NTVDM.
REM The command for setting the BLASTER environment is as follows:
REM SET BLASTER=A220 I5 D1 P330
REM where:
REM A specifies the sound blaster's base I/O port
REM I specifies the interrupt request line
REM D specifies the 8-bit DMA channel
REM P specifies the MPU-401 base I/O port
REM T specifies the type of sound blaster card
REM 1 - Sound Blaster 1.5
REM 2 - Sound Blaster Pro I
REM 3 - Sound Blaster 2.0
REM 4 - Sound Blaster Pro II
REM 6 - SOund Blaster 16/AWE 32/32/64
REM
REM The default value is A220 I5 D1 T3 and P330. If any of the switches is
REM left unspecified, the default value will be used. (NOTE, since all the
REM ports are virtualized, the information provided here does not have to
REM match the real hardware setting.) NTVDM supports Sound Blaster 2.0 only.
REM The T switch must be set to 3, if specified.
SET BLASTER=A220 I5 D1 P330 T3

REM To disable the sound blaster 2.0 support on NTVDM, specify an invalid
REM SB base I/O port address. For example:
REM SET BLASTER=A0


Now go File then SAVE

SAVE IN C:\WINDOWS\SYSTEM32

File name AUTOEXEC.NT

Save as type ALL FILES

Encoding ANSI

  Danoh 12:20 30 Nov 04

Be careful when copy and pasting AndySD's reply above. Some line breaks are lost which would render some commands as being part of a "REMark" or plain comment line, started with "REM".

The critical lines which are not just comments or "REMarks" are;

@echo off

lh %SystemRoot%\system32\mscdexnt.exe

lh %SystemRoot%\system32\redir

lh %SystemRoot%\system32\dosx

SET BLASTER=A220 I5 D1 P330 T3


Hope you don't mind my qualifying your response, AndySD.

  AndySD 12:28 30 Nov 04

Ooops sorry

NP Danoh

  Gemma 19:57 01 Dec 04

I had the same symptom after my wayward son installed "Rome - Total War" on the family PC. A compiler I keep there for "nocturnal cries of distress" from the office, refused to run giving the autoexec.nt message. I just dropped the batch file into system32 to replace the one that had gone missing courtesy of a lousy installation routine. Thanks for saving me a lot of time.

  Danoh 02:00 02 Dec 04

.. from whose table I have picked up more than a few really useful tips and hints!!

  Exeter_surfer 13:32 02 Dec 04

im sorry what do you mean, start with REM?

what I run cmd and then type what? REM and then the lines or REM b4 each line.

Sorry to be a pain.

lee

  j3nks 20:19 21 Dec 04

A much easier fix
On most PC's the autoexec.nt file is stored in a folder called repair or I386 (sorry the last one may not be correct as the file is not in there on my PC)
If you run a search for autoexec.nt you should find at least one copy of it. If not it should be on your windows XP cd if you have one. Once copied paste the file into c:\windows\system32. (You may find if it is in the repair folder it is called autoexec.nt_ in this case you will need to rename it removing the underscore to enable it to be recognised after pasting)
Once you have pasted it into c:\windows\system32 right click on the file and change the properties to read only and hidden, this is because some PC's will remove the file when restarted changing the properties prevents this happening.
This very rarely fails to fix the problem unless all versions of the file on the PC are corrupted in which case you will need to copy from your windows XP cd or from another PC.
I work for a software company and we use this on a regular basis but if the PC is new/under waranty we always sugest they may want to go to their provider first as changing the windows files could invalidate their waranty.
Having spoke to a very large PC retailer who when pressed admited it was a known problem and they beleived it was a problem with windows update corrupting or removing the file. Remember this is not a problem with the software you are trying to open but a problem with Windows XP (can happen on Windoes 2000 as well)

  Nellie2 20:51 21 Dec 04

This occurs when either autoexec.nt or config.nt are missing or corrupt.

You can run this file for Windows XP: click here

It will replace autoexec.nt, config.nt, and command.com.

Other methods: Copies of autoexec.nt/config.nt should be located in C:\WINDOWS\Repair in both Win2K and WinXP. You should also have a copy on your 2K/XP CD's in the i386 folder.

Proper place for AUTOEXEC.NT, CONFIG.NT, and COMMAND.COM:

(XP) - C:\WINDOWS\System32
(2K) - C:\WINNT\System32

Hope this helps

  thicasabrick 20:57 21 Dec 04

I had this exact same problem yesterday and recieved the fix from this forum. First do a scan for spyware (I used Adaware & Spybot) after the scan do this. If you have a c:\windows\repair folder copy AUTOEXEC.NT from there to c:\windows\system32\. This cured my problem hope it helps.

This thread is now locked and can not be replied to.

What is Amazon Go and will it come to the UK? The store without checkouts or queues

1995-2015: How technology has changed the world in 20 years

Why ecommerce hasn't taken off on social media

New MacBook Pro 2016 review | MacBook Pro with Touch Bar review: Apple's expensive and powerful…