Re: Error: The Win16 Subsytem was unable to enter...



Charles Roberts
07-10-2005, 02:00 AM
After half a dozen back and forth messages with Microsoft support,
Microsoft's only solution was to boot from the XP Cd and repair
( REINSTALL ) XP. My installed programs and settings did remain intact and
the 16bit subsystem was fixed, but I did have to reinstall SP2 and all the
other updates, as my XP CD is SP1. Sorry folks, no other fix.


"Betz" <Betz@discussions.microsoft.com> wrote in message
news:90B4FC1B-1041-488F-A880-EE438724DB2F@microsoft.com...
>I am getting basically the same message:
> 16-bit MS-DOS Subsystem
> path to the program that you are trying to start or install
> C:\Winnt\System32\config.nt The system file is not suitable for running
> MS-DOS and Microsoft Windows applications. Choose 'Close' to terminate the
> application.
>
> I am not that computer literate and the link was very confusing. There
> are
> several programs that make this error message pop up.
>
>
> "Charles Roberts" wrote:
>
>> I read and followed the instructions in that article already. I've
>> exhaustively searched all KB articles at Microsoft as well. That's why
>> I'm
>> asking here.
>>
>> "putasolutions" <iwolstencroft.nospam@gmail.com> wrote in message
>> news:66A62608-09C1-4F68-80C6-51C360338C06@microsoft.com...
>> > Follow the instructions here
>> >
>> > http://support.microsoft.com/default.aspx?scid=kb;en-us;324767
>> >
>> > "Charles Roberts" wrote:
>> >
>> > >
>> > >
>> > > I don;t know what caused it, but any 16-bit app (for instance, hp
>> printer
>> > > installation) now generates the following error:
>> > >
>> > > The Win16 Subsytem was unable to enter Protected Mode, DOSX.EXE must
>> > > be
>> in
>> > > your AUTOEXEC.NT and present in your path.
>> > >
>> > > I have restored from the Windows XP CD the
>> > > Windows\System32\AUTOEXEC.NT,
>> > > Windows\System32\CONFIG.NT, Windows\System32\DOSX.EXE, and
>> > > COMMAND.COM
>> > > files. They never were missing, but I restored them anyway. I have
>> > > read
>> > > about trojans/malware that removes these files, but they are not
>> > > being
>> > > removed. They are there, and Windows\System32 is in my user and
>> > > system
>> > > paths. Here is a hint: if I run \Windows\System32\Command.com, it
>> > > will
>> not
>> > > execute the three lh commands (mscdexnt.exe, redir.exe, dosx.exe) in
>> > > autoexec.nt, showing three File Not Found error messages, and then
>> > > the
>> shell
>> > > prompt, even if I remove the "lh". However, if I then type dosx at
>> > > the
>> > > prompt, I get no error. Any ideas? Could this be a permission
>> > > problem? I
>> did
>> > > recently turn off "Use simple file sharing" as I needed to give full
>> access
>> > > to folders I wanted to leave in place to multiple users. HELP!!!
>> > >
>> > >
>> > >
>> > >
>> > >
>>
>>
>>

MAP
07-10-2005, 02:00 AM
Charles Roberts wrote:
> After half a dozen back and forth messages with Microsoft support,
> Microsoft's only solution was to boot from the XP Cd and repair
> ( REINSTALL ) XP. My installed programs and settings did remain
> intact and the 16bit subsystem was fixed, but I did have to reinstall
> SP2 and all the other updates, as my XP CD is SP1. Sorry folks, no
> other fix.
>
>
> "Betz" <Betz@discussions.microsoft.com> wrote in message
> news:90B4FC1B-1041-488F-A880-EE438724DB2F@microsoft.com...
>> I am getting basically the same message:
>> 16-bit MS-DOS Subsystem
>> path to the program that you are trying to start or install
>> C:\Winnt\System32\config.nt The system file is not suitable for
>> running MS-DOS and Microsoft Windows applications. Choose 'Close' to
>> terminate the application.
>>
>> I am not that computer literate and the link was very confusing.
>> There are
>> several programs that make this error message pop up.
>>
>>
>> "Charles Roberts" wrote:
>>
>>> I read and followed the instructions in that article already. I've
>>> exhaustively searched all KB articles at Microsoft as well. That's
>>> why I'm
>>> asking here.
>>>
>>> "putasolutions" <iwolstencroft.nospam@gmail.com> wrote in message
>>> news:66A62608-09C1-4F68-80C6-51C360338C06@microsoft.com...
>>>> Follow the instructions here
>>>>
>>>> http://support.microsoft.com/default.aspx?scid=kb;en-us;324767
>>>>
>>>> "Charles Roberts" wrote:
>>>>
>>>>>
>>>>>
>>>>> I don;t know what caused it, but any 16-bit app (for instance, hp
>>>>> printer installation) now generates the following error:
>>>>>
>>>>> The Win16 Subsytem was unable to enter Protected Mode, DOSX.EXE
>>>>> must be
>>> in
>>>>> your AUTOEXEC.NT and present in your path.
>>>>>
>>>>> I have restored from the Windows XP CD the
>>>>> Windows\System32\AUTOEXEC.NT,
>>>>> Windows\System32\CONFIG.NT, Windows\System32\DOSX.EXE, and
>>>>> COMMAND.COM
>>>>> files. They never were missing, but I restored them anyway. I have
>>>>> read
>>>>> about trojans/malware that removes these files, but they are not
>>>>> being
>>>>> removed. They are there, and Windows\System32 is in my user and
>>>>> system
>>>>> paths. Here is a hint: if I run \Windows\System32\Command.com, it
>>>>> will
>>> not
>>>>> execute the three lh commands (mscdexnt.exe, redir.exe, dosx.exe)
>>>>> in autoexec.nt, showing three File Not Found error messages, and
>>>>> then the
>>> shell
>>>>> prompt, even if I remove the "lh". However, if I then type dosx at
>>>>> the
>>>>> prompt, I get no error. Any ideas? Could this be a permission
>>>>> problem? I
>>> did
>>>>> recently turn off "Use simple file sharing" as I needed to give
>>>>> full access to folders I wanted to leave in place to multiple
>>>>> users. HELP!!!

--
I'm glad that it finally working, as a precaution you might want to double
check that AUTOEXEC.NT is set to "read only"
http://www.diamondcs.com.au/processguard/index.php?page=download
Mike Pawlak


Re: Error: The Win16 Subsytem was unable to enter...