Unsolved
This post is more than 5 years old
7 Posts
0
10922
September 26th, 2004 16:00
Win XP PRO Ser Pk 2 and 16 Bit Windows Subsystem Error
Having installed Ser PK 2 my system worked fine until I tried to run my payroll program for my small business. The following message came up:
16 BIT WINDOWS SUBSYSTEM
C:\WINDOWS\SYSTEM32\AUTOEXEC.NT. The system file is not suitable for running MSDOS and Microsoft Windows applications. Choose close to terminate the application.
I was referred to Windows Knowledge 324767, I followed the advice about allowing Windows firewall to permit my payroll program and have followed all the steps up to and including creating Config.nt and Autoexec.nt Notebook files. I am struggling to get the last part done from steps 14 onwards. Can anyone help?
No Events found!


jwatt
4.4K Posts
0
September 26th, 2004 20:00
Were you unable to restore autoexec.nt as shown in Step 4 (expand CD-ROM Drive Letter:\i386\autoexec.nt_ c:\windows\system32\autoexec.nt)? Was there an error message when you tried to expand the file? If so, what exactly was the error message?
Jim
Marky13
7 Posts
0
September 26th, 2004 22:00
Hi Jim thanks for getting back to me. I tried all the steps shown in the KBA, and steps 4 and so on made no difference. I moved on step by step following the KBA and have made the Autoexec.nt and Config.nt file which I have left on my desktop for ease to find. I am not at all sure how I a) join them as the KBA says, I can't get the file when windows explorer finds it I can't get it to right click to copy it. b) I don't know where the %SYSTEMROOT%\System32 folder is? And therefore can't execute that instruction in step 15.
I am pretty much a novice at this level of Windows so if I have came across as a dummy it is probably true with this stuff.
Thanks
jwatt
4.4K Posts
0
September 27th, 2004 00:00
For Windows XP, "%SYSTEMROOT%" is C:\Windows. So the full path to the System32 folder is C:\Windows\System32.
You may find that there's a correct copy of autoexec.nt in the folder C:\Windows\repair. If so, you should be able to copy the one there to the C:\Windows\System32 folder.
Did you try to run the program after completing Step 4? Were there still errors reported? The remaining steps should not be needed if the only problem is a corrupt copy of autoexec.nt!
Jim
Marky13
7 Posts
0
September 27th, 2004 05:00
Jim,
I have redone the 1st 5 steps of the KBA to write down the exact messages so you can see what is happening.
When I open the command window the cursor starts after the following C:\Documents and Settings\Mark>
At that I input the line as shown in step 4. The following msg comes up after all 3 inputs with the obvious last few words changed to match the config.nt autoexec.nt and command.com
I have omiited the copyright info etc "Destination is not a directory :Letter:\i386\config.nt_c:\windows\system32\config.nt.
I tried to run the program anyway after all 3 inputs but nothing changed. On the matter of the files being in Windows\repair, I opened that and looked and sure enough there is 2 of the files in there the autoexec.nt and the config.nt Autoexec shows as being modified on 29/8/04 and the config.nt modifeied on the 3/9/04. Both of these dates are pre service pack 2 instal. Do you think you could talk me through copying them and them running them in the %systemroot% folder?
Thanks.
jwatt
4.4K Posts
0
September 27th, 2004 15:00
Marky13,
Let's give it a try.
Open a cmd.exe window. In that window, type the following lines:
copy c:\windows\repair\autoexec.nt c:\windows\system32
copy c:\windows\repair\config.nt c:\windows\system32
If that fixes the problem, I wouldn't bother with command.com. The file that SP2 somehow damages seems to be autoexec.nt. Then start your payroll program and see if it works.
Jim
jwatt
4.4K Posts
0
September 27th, 2004 17:00
You're welcome! It's a puzzle as to why XP SP2 results in autoexec.nt being clobbered, but this is by now an all too common report. And naturally, the reason people are still running 16-bit programs is that they can't be easily replaced, so when the problem is encountered, it's almost always a crisis.
Happily, the fix is pretty easy. The Microsoft article makes fixing the problem sound a lot more difficult than it is.
Jim
Marky13
7 Posts
0
September 27th, 2004 17:00
Jim,
I don't know where you are or what you do for a living but you have seriously saved my bacon. Truly appreciate your time and consideration. I just opened cmd.exe and pasted your lines and it worked great. Again thanks very much.
Best wishes
Mark