It looks like you're using an Ad Blocker.

Please white-list or disable in your ad-blocking tool.

Thank you.


Some features of ATS will be disabled while you continue to use an ad-blocker.



page: 1

log in


posted on Dec, 20 2004 @ 09:45 AM
I have a couple of programs, yet to be installed, that give me an error when I click on the .exe file.

System file not suitable for running MS-DOS and Microsoft Windows applications.

-is what it says when .exe file is clicked.

I have messed around a 'little' w/ Micro$oft components, removed IE, and use Firefox. I also use the Litestep Shell - if that can help in any way.

I believe the autoexec file may have been corrupted by a virus caught by AVG, (before I switched to BitDefender), and when trying to remove AVG from the program file list, it came up w/ a similar message about "cannot open in 16-bit", and the .ini file for the programs I want to install is 16on16.

Knowing that I have 'screwed' around w/ Micro$oft, is there anything else I can do, or something else I can use, to execute these program files?

posted on Dec, 20 2004 @ 06:21 PM
Probably you have XP and the file you listed is corrupt.

Here are some of the possible fix's"
This installaton program will reinstall the missing or corrupt Windows XP system files, autoexec.nt and config.nt.

Manually or if you dont have XP

Its the same if you have windows 2000 also:
Operating System: Windows 2000 Professional with service pack 4.

Background: Wanting to upgrade to the latest version of AVG, I decided to first uninstall the old version. When running the AVG uninstall procedure I received the error message:

C:\WINNT\System32\Autoexec.nt The system file is not suitable for running MS-DOS and Microsoft Windows applications. Choose 'Close' to terminate the application.

Resolution Steps: Apparently this error message, or a similar one mentioning config.nt, can occur when one of the following files is missing or corrupt:

The erorr can occur when installing or uninstalling a program.

In my case Autoexec.nt was missing from the C:\WINNT\System32 directory. Looking in the C:\WINNT\Repair directory I found that Windows had automatically made a backup copy of Autoexec.nt, so I just copied this into C:\WINNT\System32 and the problem was fixed.

Note: The C:\WINNT directory on my computer may be C:\WINDOWS on other systems. Substitute as necessary when following the above instructions.

Note: If you can't find a copy of the missing file in your Repair directory, use your original Windows OS disk to get the missing files. At the command prompt type the following commands:

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\
Ref:win2k fix autoexec.nt error

If I remember right, this can also be caused by Symantec-Norton Antivirus.
If the above does not help, and you are desperate to install an application, you may be able to stop the service, then install your app, then restart the service.

posted on Dec, 22 2004 @ 11:04 PM
Ty so much, Makeitso - I found the backup and will try that suggestion first, if that doesn't work, I'll try the fix.exe.

I never had the installation disk, my brother put XP on my primary hard drive so I can learn other OS's and connect to the internet easier. I've proceeded to tear up Windows a 'bit', but I've usually found programs to replace or at least, 'go around' the ones I tore up.

My next move will be away from Micro$oft!

posted on Dec, 27 2004 @ 09:59 AM
Had some folks at work w/ the same exact problem. They each had been infected w/ the same spyware which was causing it, and they needed to run a 16-bit mainframe emulator to do their job, which wouldn't run w/ out that file.

Everytime they would reboot that file would get deleted until the spyware was finally removed. So, check for spyware also.

posted on Dec, 27 2004 @ 12:37 PM
humm..maybe just open it in "notepad" and edit you want

posted on Dec, 27 2004 @ 09:06 PM
Bob - Got rid of all spyware.

It was the autoexec.nt file that was missing or corrupted, so I did what Makeitso suggested and found the 'spare'. Put it back in sys32 and the program works now!

Mauigateway - I thought about that, but was informed that the program wouldn't run in a bigger emulator. Might work for something else, but not this one.

posted on Dec, 28 2004 @ 09:37 AM
ohh..I problem then. Try the windowns programm WordPad..this will work to edit your autoexec file



new topics

top topics


log in