home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!cs.utexas.edu!qt.cs.utexas.edu!yale.edu!jvnc.net!rutgers!njitgw.njit.edu!hertz.njit.edu!dic5340
- From: dic5340@hertz.njit.edu (David Charlap)
- Newsgroups: comp.os.os2.programmer
- Subject: Re: DOS Box Programming
- Message-ID: <1992Dec18.220158.3726@njitgw.njit.edu>
- Date: 18 Dec 92 22:01:58 GMT
- References: <boh.724320875@sfu.ca> <1992Dec14.180704.29564@wicat.com> <1992Dec17.230826.5577@midway.uchicago.edu>
- Sender: news@njit.edu
- Organization: New Jersey Institute of Technology, Newark, N.J.
- Lines: 28
- Nntp-Posting-Host: hertz.njit.edu
-
- In article <1992Dec17.230826.5577@midway.uchicago.edu> sip1@midway.uchicago.edu writes:
- >In article <1992Dec14.180704.29564@wicat.com> kevin@wicat.com (Kevin Vigor) writes:
- >>> 1. Is there a way to detect if a programme is operation in OS/2 2.0's
- >>> dos box ?
- >
- >How about looking for an OS/2 2.x-specific file that will always be in
- >the same location?
-
- Like what? Any file you can name will also be present if the user is
- running straight DOS on a dual-boot machine. All this can tell you is
- whether or not OS/2 was installed. It won't tell you if you're
- running OS/2 or not.
-
- The dos version number will tell you if you're running the emulator
- (look for version 10 or greater, or call "ver" and note that it will
- say "OS/2..."), but I can think of know way to tell a VMB from a
- normal DOS boot. Unless you want to play around with protected mode.
-
- What about this: Detect the CPU type. If it's a 386, try to go into
- protected mode. If it fails, you're in a VMB - probably OS/2, but
- Windows 3.1 may also cause this effect. Of course, there are standard
- ways to check if you're running Windows.
-
- --
- |) David Charlap | .signature confiscated by FBI due to
- /|_ dic5340@hertz.njit.edu | an ongoing investigation into the
- ((|,) | source of these .signature virusses
- ~|~
-