16 bit on XP

[Guest]

Several prexisting programs are no longer able to run on XP. I keep getting
this message
"16 bit Windows Subsystem"
"C:\WINDOWS\SYSTEM32\AUTOEXEC.NT. The system file is not suitable for
running MS-DOS and Microsoft Windows applications, Choose "Close" to
terminate the application".
Is the cause of an update? And how can I fix this so that I can use older
programs that worked fine a few months ago?

 

[Michael Solomon \(MS-MVP\)]

Please check the following Knowledge Base Article for help with this issue:
http://support.microsoft.com/default.aspx?scid=kb;en-us;324767

 

[Guest]

Hi,

I have tried the articles on MS help- page but get the following errors: -

Unable to open CD file: -

This is because there is no I386 directory on the CD, nor are there the
AUTOEXEC etc.. files on the CD.

I followed the expand instructions and received the 'unable to open file'
I then when onto create the files and copy them into SYSTEM32 directory. I
rebooted, but still receive the same errors.

The CD's I am trying to use are SATS tests by EUROPRESS.

Any help appreciated.....

 

[Michael Solomon \(MS-MVP\)]

Go to C:\WINDOWS\repair and copy autoexec.nt back into the
C:\WINDOWS\system32 folder.

 

[Guest]

Thanks...

I had already tried this but still had the same error.

Read in some other threads about running XP_Fix.EXE at
http://www.visualtour.com/downloads/default.asp.

Ran that and it allows the programs to run. However when the PC is
rebooted, it loses the files again and requires re-running.

Have been unable to locate the issue. Have also read up about trojan
WINDUPDATE. Could not locate any reference in registry. Also ran Ad-aware
and Norton Antivirus. Both run clean.

Afraid I am stuck now on what it could be.....

 

[Michael Solomon \(MS-MVP\)]

It sounds as though something on your system is causing this.

There's a malware called WinAdTools and when it is deleted by spyware
cleaners, it causes this issue.

I'm not saying this is the cause of your problem but sometimes, malware has
a nasty habit of reinstalling itself depending upon how it was removed. If
you have any background tools that might be removing it, it could cause this
issue to reappear. The key is not the removal so much as finding out how
and why the malware is being reinstalled.

I'm just providing additional information.

Something else, if the applications are truly 16-bit apps, they were likely
borderline to begin with. If that's the case, often as the system is
updated, new security updates, various other updates, it can push such
applications over the line from borderline to incompatible.