16 bit windows subsystem error message when installing software

  • Thread starter Frankie V. Fernandez, MD
  • Start date
F

Frankie V. Fernandez, MD

Hello!

I have begun having problems installing older programs on my Windows XP Pro
SP2 machine. The programs were installed to the pc before I upgraded the
operating system and worked fine. However, when I uninstalled the programs
and tried reinstalling them, I get the following error message at setup:

16 bit windows subsystem error message

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.

Whether I choose close or ignore, nothing happens. These are old medical
software that use 16-bit quicktime apps and other database applets. Please
help! Thanks!

Frankie
 
P

Paul Heslop

Frankie V. Fernandez said:
Hello!

I have begun having problems installing older programs on my Windows XP Pro
SP2 machine. The programs were installed to the pc before I upgraded the
operating system and worked fine. However, when I uninstalled the programs
and tried reinstalling them, I get the following error message at setup:

16 bit windows subsystem error message

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.

Whether I choose close or ignore, nothing happens. These are old medical
software that use 16-bit quicktime apps and other database applets. Please
help! Thanks!

Frankie

This is all over the place at the moment Frankie and has been posted
in here (including by myself). It seems for some reason the file
autoexec.nt is being corrupted or removed. One of the earlier answers
was

Error message when you install or start an MS-DOS or 16-bit
Windows-based
program
http://support.microsoft.com/?kbid=324767

This should help resolve this common problem. Basically, you will have
to
expand new copies of command.com, autoexec.nt, and config.nt to the
system32
folder from the WinXP CD or I386 folder on your hard drive. Sometimes,
you
need to create new ones and overwrite the existing ones - the method
is
described in the article. (posted by Rick)

Personally as I didn't have a windows cd handy I had to do a search on
google for the file and downloaded it, then popped it into the
system32 folder.
 
R

Rick \Nutcase\ Rogers

Hi Frankie,

Error message when you install or start an MS-DOS or 16-bit Windows-based
program
http://support.microsoft.com/?kbid=324767

This should help resolve this common problem. Basically, you will have to
expand new copies of command.com, autoexec.nt, and config.nt to the system32
folder from the WinXP CD or I386 folder on your hard drive. Sometimes, you
need to create new ones and overwrite the existing ones - the method is
described in the article.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Associate Expert - WindowsXP Expert Zone

Windows help - www.rickrogers.org
 
F

Frankie V. Fernandez, MD

Thanks!

Paul Heslop said:
This is all over the place at the moment Frankie and has been posted
in here (including by myself). It seems for some reason the file
autoexec.nt is being corrupted or removed. One of the earlier answers
was

Error message when you install or start an MS-DOS or 16-bit
Windows-based
program
http://support.microsoft.com/?kbid=324767

This should help resolve this common problem. Basically, you will have
to
expand new copies of command.com, autoexec.nt, and config.nt to the
system32
folder from the WinXP CD or I386 folder on your hard drive. Sometimes,
you
need to create new ones and overwrite the existing ones - the method
is
described in the article. (posted by Rick)

Personally as I didn't have a windows cd handy I had to do a search on
google for the file and downloaded it, then popped it into the
system32 folder.
 
F

Frankie V. Fernandez, MD

Thanks!

Rick "Nutcase" Rogers said:
Hi Frankie,

Error message when you install or start an MS-DOS or 16-bit Windows-based
program
http://support.microsoft.com/?kbid=324767

This should help resolve this common problem. Basically, you will have to
expand new copies of command.com, autoexec.nt, and config.nt to the
system32 folder from the WinXP CD or I386 folder on your hard drive.
Sometimes, you need to create new ones and overwrite the existing ones -
the method is described in the article.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Associate Expert - WindowsXP Expert Zone

Windows help - www.rickrogers.org
 
R

Rock

Hello!

I have begun having problems installing older programs on my Windows XP Pro
SP2 machine. The programs were installed to the pc before I upgraded the
operating system and worked fine. However, when I uninstalled the programs
and tried reinstalling them, I get the following error message at setup:

16 bit windows subsystem error message

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.

Whether I choose close or ignore, nothing happens. These are old medical
software that use 16-bit quicktime apps and other database applets. Please
help! Thanks!

Frankie

Also can be caused by a Trojan installing a file windupdater.exe and
creating registry entries for that file. Do a thorough scan for malware.
http://groups.google.com/[email protected]

AVAST (free antivirus software) can be the cause if SP2 is installed:
http://groups.google.com/[email protected]

You can put back the standard version of autoexec.nt by copying a backup
copy held in windows\repair to windows\system32.
 
P

Paul Heslop

Rick said:
Hi Frankie,

Error message when you install or start an MS-DOS or 16-bit Windows-based
program
http://support.microsoft.com/?kbid=324767

This should help resolve this common problem. Basically, you will have to
expand new copies of command.com, autoexec.nt, and config.nt to the system32
folder from the WinXP CD or I386 folder on your hard drive. Sometimes, you
need to create new ones and overwrite the existing ones - the method is
described in the article.

Hah, I already gave him this from you :O)
 
R

Rick \Nutcase\ Rogers

<heh> Note though that our posting time is exactly the same.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Associate Expert - WindowsXP Expert Zone

Windows help - www.rickrogers.org
 
P

Paul Heslop

Rick said:
<heh> Note though that our posting time is exactly the same.

Burger me! The reason I didn't notice is yours didn't show til much
later on my isp's wonderful servers. I stand corrected :O)
 
S

Starz_Kid

Rock said:
Frankie V. Fernandez, MD wrote:


Also can be caused by a Trojan installing a file windupdater.exe and
creating registry entries for that file. Do a thorough scan for malware.
http://groups.google.com/[email protected]

AVAST (free antivirus software) can be the cause if SP2 is installed:
http://groups.google.com/[email protected]

You can put back the standard version of autoexec.nt by copying a backup
copy held in windows\repair to windows\system32.

Hello Group, I too am having problems with the 16 bit warning...!

I've done everything that is on the list....

I've checked for the directory windupdate and don't have it...!

I scanned for virus' - - NEGATIVE

I scanned for adware/malware and that is not the problem...!

The replacement autoexec.nt and config.nt and the command.com are in my
C:windows\system32 folder...

BUT... I'm getting a NEW error message: "Windows is unable to go into
protect mode, dosx.exe must be in your autoexec.nt file and present in your
path"
****** but I've checked the contents of the autoexec.nt & the config.nt and
they contain the default statements.

So... I still can't install the 16bit programs...!

Soooooooo Microsoft... what is the solution??????????

Starz_Kid...
 
R

Rock

Starz_Kid said:
Hello Group, I too am having problems with the 16 bit warning...!

I've done everything that is on the list....

I've checked for the directory windupdate and don't have it...!

I scanned for virus' - - NEGATIVE

I scanned for adware/malware and that is not the problem...!

The replacement autoexec.nt and config.nt and the command.com are in my
C:windows\system32 folder...

BUT... I'm getting a NEW error message: "Windows is unable to go into
protect mode, dosx.exe must be in your autoexec.nt file and present in your
path"
****** but I've checked the contents of the autoexec.nt & the config.nt and
they contain the default statements.

So... I still can't install the 16bit programs...!

Soooooooo Microsoft... what is the solution??????????

Starz_Kid...

You're not talking with Microsoft. This is a user group with
volunteers. MS staff do not officially offer help here. If you want MS
contact MS tech support directly.
 
A

Alex Nichol

Starz_Kid said:
BUT... I'm getting a NEW error message: "Windows is unable to go into
protect mode, dosx.exe must be in your autoexec.nt file and present in your
path"
****** but I've checked the contents of the autoexec.nt & the config.nt and
they contain the default statements.

Have you checked to make sure that there is a Windows\system32\dosx.exe?

Use MSConfig.exe and its Expand files button to expand dosx.ex_ from
the \i386 folder of the CD (or maybe a Windows\i386 one on the hard disk
if the machine came with windows pre-installed) putting it as
system32\dosx.exe
 
S

Starz_Kid

Rock said:
You're not talking with Microsoft. This is a user group with
volunteers. MS staff do not officially offer help here. If you want MS
contact MS tech support directly.

Yes, this is a user group with people trained my MS, hence the MVP status of
most who respond.!!!

Starz_Kid...
 
A

Alex Nichol

Starz_Kid said:
Yes, this is a user group with people trained my MS, hence the MVP status of
most who respond.!!!

It is not. It is a peer to peer user group, and everyone (apart from an
occasional comment from an MS employees using [MSFT] in the handle) is
here of his/her own volition in order to help others, There is no
training - it is a pool of expertise built up from experience. Then
those who are seen by MSoft as exhibiting a lot of good helpful advice
over a substantial time are given an MVP award as a thank you
 
K

Ken Blake

In
Starz_Kid said:
Yes, this is a user group with people trained my MS, hence the
MVP
status of most who respond.!!!


No, Rock is correct. MVPs aren't trained by Microsoft, and aren't
Microsoft employees. MVPs are individual computer users just like
everyone else here. The only difference is that MVPs are
individuals who have been recognized by Microsoft for
consistently supplying accurate information.

See
 
G

Guest

Alex Nichol said:
Have you checked to make sure that there is a Windows\system32\dosx.exe?

Use MSConfig.exe and its Expand files button to expand dosx.ex_ from
the \i386 folder of the CD (or maybe a Windows\i386 one on the hard disk
if the machine came with windows pre-installed) putting it as
system32\dosx.exe
 
G

Guest

Hi I am also having these same problems. Have tried everything that has been
suggested and still no luck. Noticed that DOSX file in XP Cd is 12KB while on
my computer (after SP2) is 53Kb, is this normal?
 
R

Rock

Eddie said:
Hi I am also having these same problems. Have tried everything that has been
suggested and still no luck. Noticed that DOSX file in XP Cd is 12KB while on
my computer (after SP2) is 53Kb, is this normal?

:

Mine with SP2 is 53 kb too.
 
A

Alex Nichol

Eddie said:
Hi I am also having these same problems. Have tried everything that has been
suggested and still no luck. Noticed that DOSX file in XP Cd is 12KB while on
my computer (after SP2) is 53Kb, is this normal?

THat is correct: the one on the CD is in fact dosx.ex_ meaning it is
compressed
 
G

Guest

Thanks,
However I'm still having the problem, only now its giving the second message
mentioned above. Any suggestions?
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top