Re: Software question

From: John A. Dormer 2 (
Date: Thu Dec 27 2007 - 02:38:53 UTC

  • Next message: Brad Young: "Binocular Chair OT"

    Hash: SHA1
    Sayyed Hamid Reza Ahmadi wrote:
    > Instead, go to RUN, and type "cmd" + Enter  to run the
    > command line.
    This is probably the simplest way to go, but the down side is that
    apparently there's only one 16-bit operating space created for >all< the
    DOS-type programs. They share it, and may leave "droppings" around which
    would trip up subsequent programs.
    The issue is backwards compatibility, and extends to many other hobbies:

    The above link touches on all common Windows dialects, and is about the
    best article I can find. It even mentions Vista, which will be of help
    to some of our readers.
    The best thing is to tell the Windows system to run the program in a
    separate memory space:

    Short but sweet, the above link is a little bit more jargon-filled. I
    hope it doesn't put anyone off, but it's succinct. It covers the pieces
    which make backward compatibility work in more detail than the first link.
    If the previous link didn't cow you, here's some even deeper detail:
    Watch out, the link is long and wraps. The content is aimed at Windows
    2000, but Vista and XP share a lot of their functional design with
    Win2K. The article will apply well to XP, though I'm not sure if Vista
    will use the same syntax to do the same things. I'm giving Vista six
    more months to get more bugs worked out, but it does look promising.
    Disclaimer: I'm a UNIX guy, but my jobs over the past 18 years have
    brought me in deep contact with Windows on a regular basis.
    Version: GnuPG v1.4.7 (MingW32)
    Comment: Using GnuPG with Mozilla -
    -----END PGP SIGNATURE-----
    Subscribe/Unsubscribe info, Frequently Asked Questions, SeeSat-L archive:

    This archive was generated by hypermail 2b29 : Thu Dec 27 2007 - 02:41:33 UTC