My operating System: Windows XP "C" drive NTFS "D" drive FAT32 "E" drive FAT32
Message displayed at start up below

C:\WINDOWS\SYSTEM32\CONFIG.NT. The system file is not suitable for running MS-DOS and Microsoft Windows applications. Choose 'Close' to terminate the application.

Ever since I had unintentionally converted "C" drive from Fat32 to NTFS using a free disk supplied from "Netguide" magazine I have had nothing but problems. Most of my original software I was using with FAT32 won't work because the above message is displayed if I try and open it. Please what can I do.

This is the most common fix for your error:

Error message when you install or start an MS-DOS or 16-bit Windows-based program

You can also attempt to convert NTFS to FAT32, but it requires a 3rd party program such as Partition Magic which has its' problems as well as seen here:

Converting NTFS to FAT32

Here are 3 google groups searches for further reading:

google 1

google 2

google 3

Good luck! Let us know if we can help further

Thanxs heaps for your advise, yes it work fine, got rid of the dialogue box that was always so annoying at start up, several attempts though, gave up in the end, following day turn on the computer and could not believe the dialogue box wasn't there had to shut down the pc and start up again to believe it. Stll unable to download any of my original software, for example one of my software Panosonic digital camera disc a new message is displayed with the header "16 bit Windows Subsystem" inside a new dialogue with this message below it C:\WINDOWS\SYSTEM32\CONFIG.NT. The system file is not suitable for running MS-DOS and Microsoft Windows applications. Choose 'Close' to terminate the application. Is there any further steps besides converting my C drive back to FAT32 to enable downloading my software. Thanks again for your timely advise, really really much appreciated.

Found some more reading for you

Troubleshooting MS-DOS-based programs in Windows XP

Windows XP tuning for DOS programs

Let us know if you find anything good there!

Check the Config.nt and Autoexec.nt files in the SystemRoot%\System32 folder for non-standard settings.

Use a REM statement to remark out all entries except the following default entries:

Sorry I am not sure where to start or begin. To check Config.nt and Autoexe.nt or what is System%........etc

The first thing to test when you are having problems with MS-DOS-based programs is the Windows Virtual DOS Machine (NTVDM) subsystem. You can use the Command.com utility to test whether the NTVDM subsystem is running properly. To start Command.com, follow these steps:

1. Click the Start button, and then click Run.

2. In the Open box, type command.com, and then click OK.
This should start a command prompt window.


Does it?

Yes when I typed in command.com click ok the command prompt window and a dialogue box with the heading 16 bit MS-DOS Subsystem under this heading is the same message C:\WINDOWS\SYSTEM32\CONFIG.NT. The system file is not suitable for running MS-DOS and Microsoft Windows applications. Choose 'Close' to terminate the application. Choosing close or ignore terminate the command prompt window. Any suggestion thanxs

Just btw; is your XP an upgrade installed over 98? or a full install? XP Pro or Home? XP is on C:\? Have you tried downloading to your other drives?

When you ran the files off your CD did you run command.com?

1) Put in your XP CD. Exit if it autostarts.

2) Go to Start > Run, and type:

cmd <Enter>

3) Then, at the command prompt, type (where D: is your CD-ROM drive letter
and "Windows" is your installation directory):

expand D:\i386\config.nt_ c:\windows\system32\config.nt <Enter>
expand D:\i386\autoexec.nt_ c:\windows\system32\autoexec.nt <Enter>
expand D:\i386\command.co_ c:\windows\system32\command.com <Enter>
exit <Enter>

Just another thought summing up the many posts on the net dealing with this issue all seem to focus on the issues covered by:

http://support.microsoft.com/default...b;en-us;324767

The 2nd step of which follows the disclaimer.

Like altering system files, modifying the registry can be risky and D-A-L.com and its members cannot accept liability for any adverse effects caused by following advice freely given on this site.

1) Start Notepad.

2) In Notepad, type the following entries:
dos=high, umb
device=%SYSTEMROOT%\system32\himem.sys
files=40

3) On the File menu, click Save As.

4) In the File Name box, type Config.nt, and then click Save. Close the
Config.nt file.

5) On the File menu, click New.

6) In the new blank document, type the following entries:
@echo off
lh %SYSTEMROOT%\system32\mscdexnt.exe
lh %SYSTEMROOT%\system32\redir
lh %SYSTEMROOT%\system32\dosx
SET BLASTER=A220 I5 D1 P330 T3

7) On the File menu, click Save As.

8) In the File Name box, type Autoexec.nt, and then click Save. Close the
Autoexec.nt file.

9) Start Windows Explorer. Locate the Config.nt file, right-click the
Config.nt file, and then click Copy.

10) Right-click the %SYSTEMROOT%\System32 (usually Windows\System32) folder,
and then click Paste.

11) Locate the Autoexec.nt file, right-click the Autoexec.nt file, and then
click Copy.

12) Right-click the %SYSTEMROOT%\System32 folder, and then click Paste.

13) Locate the Command.com file, right-click the expanded Command.com file,
and then click Copy.

14) Right-click the %SYSTEMROOT%\System32 folder, and then click Paste.

15) Restart your computer.

To prevent continual corruption:

Change the attributes of these three files to "read only" after you've copied it into the system32 directory.

To get the best results from your programs:

Completely uninstall the app, make the fixes above, and then try installing it in Compatibility Mode. Right-click the setup file and choose the Compatibility tab. Turn off visual themes since many older apps don't do well with these. Set the compatible OS to whatever was intended for the app originally. Install. Set Compatibility Mode options on the program after it is installed by right-clicking the shortcut to it. Open the folder where the app resides and set compatibility options on any exe in that folder (Many apps call another exe when running. Even if the first is set to run compatibly, the others may not be.).

This problem is often associated with malware/ spyware issues, especially when these three files are repaired and corrupted continuosly. That being said you might want to follow all of Owen's instructions HERE once you have completed that post your log on the Spyware, Adware and Viruses board.