WIN16 Subsystem error, Help

[Mark_H]

Greeting to ALL,

Few days ago, after downloading some upgrades from Microsfot my
system developed some problems running older programs ( which worked
OK previously ).
The message : "The Win16 Subsystem was unable to enter Protected Mode,
DOSX.EXE must be in your AUTOEXEC.NT and present in your PATH".
This problem has been widely discussed on the Net but I could not find
any solution other then suggested in all other posts which
unfortunately don't work for me.
My Autoexec.nt, Config.nt, Dosx.exe, Ntvdm.exe, Command.com, himem.sys
are all in the right places. I expanded all the files from Windows XP
Pro with SP1 CD-Rom.
I can run cmd, but can't command .com. I have checked the contents of
Config.nt and Autoexec.nt. They are OKand have all the lines correct.
Checked the PATH in Environment Variables, everything there is OK.
I run the latest Kaspersky and Norton 2005 AV. I run Spy Sweeper v.3
and Trojan Hunter.
I have just run out of ideas.
Has anyone have any solution. I live in Poland, Microsoft Tech.
Support there, sucks ! You people, are my only hope.
Thanks, Marek

 

[Rick \Nutcase\ Rogers]

Hi,

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

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Associate Expert - WindowsXP Expert Zone

Windows help - www.rickrogers.org

 

[S.Sengupta]

XP_Fix.EXE by TRF Systems, Inc.
http://www.visualtour.com/downloads/xp_fix.exe

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

regards,
ssg MS-MVP
pronetworks.org

 

[Mark_H]

Thanks for your advice, but this is what I did at the very begining. I
think I read all the articles regarding this issue on Microsoft pages.
Any other suggestions, please.

 

[Mark_H]

Many thanks ! The FIX has solved my problem ( I think ). I can start
older programs now. Thank you again.
Best Wishes
Marek

 

[Rick \Nutcase\ Rogers]

Hi,

I've often found that I need to kill all associated processes (ntvdm and
wowexec) when this occurs.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Associate Expert - WindowsXP Expert Zone

Windows help - www.rickrogers.org