1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Strange error message regarding DOSX??

Discussion in 'Windows XP' started by DUPDUP69, 2002/05/07.

Thread Status:
Not open for further replies.
  1. 2002/05/07
    DUPDUP69

    DUPDUP69 Inactive Thread Starter

    Joined:
    2002/05/07
    Messages:
    3
    Likes Received:
    0
    When attempting to install some programs, ones designated to work with WIndows XP (or even programs that simply extract files), I get the following error message:

    16-bit Windows Subsystem

    An application has attempted to load a 16-bit device driver, which cannot be supported. This may cause the application to function incorrectly. Choose 'Close' to terminate the application.

    Choosing 'Close' simply exits... Choosing "Ignore" brings up the following error message:

    System Error:

    The Win16 Subsystem was unable to enter Protected Mode, DOSX.EXE must be in your AUTOEXEC.NT and present in your PATH.

    The things is, DOSX.EXE *is* present in that file, and in the path. I've been able to install these programs on other Windows XP systems, so I *know* the problem is not these applications. Short of re-installing all of Windows XP, can anyone tell me how to fix this?

    When I try to run DOSX.EXE manually, ironically I get the same error... then some brief error about "Unable to load 16-bit application... Cannot find HMA... running DOS low..." How the heck can there be a High Memory Area in Windows XP? I thought that died with the end of Windows 9x??

    Thanks in advance!

    Yours,
    Matthew R. Doebler
    DUPDUP@psu.edu
     
  2. 2002/05/08
    Newt

    Newt Inactive

    Joined:
    2002/01/07
    Messages:
    10,974
    Likes Received:
    2
    Do you have the default settings (below)?

    Config.nt contains the following commands by default:
    dos=high, umb
    device=%SystemRoot%\system32\himem.sys
    files=40

    Autoexec.nt contains the following commands by default:
    @echo off
    lh %SystemRoot%\system32\mscdexnt.exe
    lh %SystemRoot%\system32\redir
    lh %SystemRoot%\system32\dosx
    SET BLASTER=A220 I5 D1 P330 T3
     
    Newt,
    #2

  3. to hide this advert.

  4. 2002/05/08
    Zephyr

    Zephyr Inactive

    Joined:
    2002/01/21
    Messages:
    1,519
    Likes Received:
    0
    Here's mine for what it's worth:

    config.nt

    dos=high, umb
    device=%SystemRoot%\system32\himem.sys
    files=40


    autoexec.nt

    @echo off
    lh %SystemRoot%\system32\mscdexnt.exe
    lh %SystemRoot%\system32\redir
    lh %SystemRoot%\system32\dosx
    SET BLASTER=A220 I5 D1 P330 T3

    It looks like it bears out what you're saying Newt.
     
  5. 2002/05/08
    DUPDUP69

    DUPDUP69 Inactive Thread Starter

    Joined:
    2002/05/07
    Messages:
    3
    Likes Received:
    0
    Guys,

    Thanks for the prompt replies...

    Unfortunately, I do have the correct CONFIG.NT and AUTOEXEC.NT settings.

    When I try to manually load any of the programs in AUTOEXEC.NT, I get the same error message that I mentioned above when I try to run DOSX.EXE manually. I get the same 16-bit error subsystem error, followed by a quick DOS screen that says, "HMA not available... Loading DOS low ", and then it disappears, failing to run the program.

    I think the problem is deeper than I wish it were. Something fundamental is not happening. I wonder if it has to do with even a memory issue with my BIOS or motherboard. Ironically, other programs (perhaps pure 32-bit??) are working just fine. My system is amazingly stable, and it has yet to crash fatally.

    Any more advice on troubleshooting would be greatly appreciated!

    Thanks!

    Yours,
    Matthew R. Doebler
    DUPDUP@psu.edu
     
  6. 2002/05/08
    unixfan

    unixfan Inactive

    Joined:
    2002/01/26
    Messages:
    282
    Likes Received:
    0
    Have you tried extracting the original dosx.exe and himem.sys from the XP CD in case they are corrupt?
     
  7. 2002/05/08
    DUPDUP69

    DUPDUP69 Inactive Thread Starter

    Joined:
    2002/05/07
    Messages:
    3
    Likes Received:
    0
    Wow... you guys are good... The DOSX.EXE file was fine, but the HIMEM.SYS file was only 945 bytes... even worse, it was a TEXT message about the HyperTerminal program!!! Don't ask me how in the world this got corrupt. Regardless, I copied the 4,768 byte HIMEM.SYS from the Windows XP CD, and all is well. Looks like despite Microsoft's claims, "legacy" DOS files like HIMEM.SYS are still needed to do things in Windows XP. (Yeah, I know, it is only *emulating* DOS in protected mode, blah blah blah)

    Thanks so much for your insight. Despite Windows pointing the error to DOSX.EXE, the real culprit was HIMEM.SYS

    This board ROCKS!!!! :)

    Yours,
    Matthew R. Doebler
     
  8. 2002/05/08
    Zephyr

    Zephyr Inactive

    Joined:
    2002/01/21
    Messages:
    1,519
    Likes Received:
    0
    All credit goes to Unixfan.

    I would recommend a full virus scan with the latest dope just to be sure something isn't renaming your files for you.

    Good luck.
     
Thread Status:
Not open for further replies.

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.