home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!pilchuck!fnx!nazgul!bright
- From: bright@nazgul.UUCP (Walter Bright)
- Newsgroups: comp.os.msdos.programmer
- Subject: Re: MS-DOS in 386 protected mode
- Message-ID: <1546@nazgul.UUCP>
- Date: 27 Dec 92 00:30:13 GMT
- References: <1992Nov20.193105.5699@ucselx.sdsu.edu> <10060@blue.cis.pitt.edu.UUCP> <1525@nazgul.UUCP> <Bz4L8D.BzF@ais.org>
- Reply-To: bright@nazgul.UUCP (Walter Bright)
- Organization: Zortech, Seattle
- Lines: 20
-
- In article <Bz4L8D.BzF@ais.org> empath@ais.org (Tim Triemstra) writes:
- /No, the 32bit and 16bit protected mode applications you run every day are
- /not "pretending to work." However, they are NOT working under UNMODIFIED
- /msdos (as you even quoted.) 32bit requires a DOS extender, as does 16bit
- /(16bit has different types like DPMI etc, not always called an extender.)
-
- Most DOS extenders do not modify DOS. They don't modify DOS on the disk,
- they don't require a device driver (at least the better ones don't!).
- The better ones don't require a DPMI host either. A DOS extender is a
- block of code that sits partly in protected mode and partly in real mode.
- It's job is to catch calls to DOS from protected mode, switch to real mode,
- pass the call on to DOS, catch the result, and switch back to protected mode.
- I suppose we are quibbling terms here, but since it looks to the user like
- an ordinary executable, and leaves no "trail" of installed TSR's or modified
- disk files, and requires no special installation of DOS (i.e. no CONFIG.SYS
- modifications), I'd call that not modifying DOS.
-
- /Don't try to make people look stupid by saying something stupid yourself.
-
- I was trying to be a bit humorous, sorry.
-