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.

DOS under XP

Discussion in 'Windows XP' started by ludger, 2004/04/07.

Thread Status:
Not open for further replies.
  1. 2004/04/07
    ludger

    ludger Inactive Thread Starter

    Joined:
    2004/04/07
    Messages:
    1
    Likes Received:
    0
    I am using Quickbasic programs that access the serial ports (COM1, COM2) under MS-DOS. I had no problems with WINDOWS 98. After upgrading to WINDOWS XP serial port calls don't work any more.
    How can this be cured?
     
  2. 2004/04/07
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    Hi Ludger - welcome to the Board :)

    Basically there is no DOS in XP, just an emulator. This may be the cause of your problems.

    No doubt someone with more knowledge of these matters will chip in here.
     

  3. to hide this advert.

  4. 2004/04/07
    TonyT

    TonyT SuperGeek Staff

    Joined:
    2002/01/18
    Messages:
    9,072
    Likes Received:
    400
    You could try running Quicken in compatability mode.
     
  5. 2004/04/08
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
  6. 2004/04/08
    Newt

    Newt Inactive

    Joined:
    2002/01/07
    Messages:
    10,974
    Likes Received:
    2
    ludger - could be a problem with the way the app is trying to make the hardware calls.

    The NT systems (NT4 and all the later ones) do not allow an app to work directly with hardware. There is a layer/utility/applet/thingy in there called the Hardware Abstration Layer (HAL) whose only function is to trap hardware calls, examine them and if they are found to be safe, to make the calls rather than letting the app do it.

    Possible problems include unsafe calls that HAL won't allow and calls that confuse HAL so it tries to do the wrong thing.

    As noted, you could try running the app in compatibility mode. That often works but not always. The command line app in XP that mimics DOS is very similar but absolutely not identical.
     
    Newt,
    #5
  7. 2004/04/10
    Top Dog

    Top Dog Inactive

    Joined:
    2002/01/07
    Messages:
    102
    Likes Received:
    0
    I initially wrote a large bunch of my engineering tools in QuickBasic and then later translated them into Visual-Basic-for-DOS. VBDOS was the object oriented GUI sucessor to QuickBasic. VBDOS only came out with the Version One original issue but it was quick and fabulous for my use.

    So I did some checking around when Win2K came out to see if my Visual-Basic-for-DOS programs would still run in that system.
    It was my understanding at that time that M$ intentionally maintained Win2k compatability (and therefore, likely WinXP compatibility) with Visual Basic for DOS but NOT for QuickBasic.

    All my compiled VBDOS apps still work fine even in XP but the editor/compiler is getting quirky. I tried to continue writing engineering tools in VBDOS but eventually ran into enough hassle with XP that I eventually had to go and convert my apps to the Visual Studio packages. (I didn't know what hassle was until I started using Visual Basic 6.)

    I have seen some hacks in the internet through the years to allow some of the earlier Basic packages to work in Win2K/XP but .... it's probably better that the dead are buried.

    Good luck
    Top Dog
     
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.