Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!usc!gate.oxy.edu!oxy!rafetmad
From: rafetmad@oxy.edu (David Ronald Giller)
Newsgroups: comp.windows.ms
Subject: 386 enhanced mode (was: FAQ, comp.windows.ms edition)
Message-ID: <134268@tiger.oxy.edu>
Date: 4 Jan 91 01:56:43 GMT
Distribution: usa
Organization: Occidental College, Los Angeles, CA  90041
Lines: 27


>>/ hplsla:comp.windows.ms / jbs@Congruent.COM (Jeffrey Siegal) /  1:30 pm  Jan  3, 1991 /
>>> Do remember, though, that some
>>> applications require 386 enhanced mode (wdeb386 is one example).

>>This is not true.  Wdeb386 requires a 386 processor, but it works
>>perfectly well with Windows in standard mode.

>>Jeffrey Siegal
>>--------------

>I believe that some new applications, such as Corel Draw 2.0, do require
>386 enhanced mode.

>Reed Jacobson

According to the Windows SDK, there is no programmer's interface difference
between standard and 386 enhanced modes.  They are both called 'protected'
mode.  The only differences are in the way that Windows handles non-Windows
applications, and how they are swapped out to disk, as well as some added
expanded-memory emulation features.  The 'protection' that is offered in
these modes is supposed to be exactly the same for both.  The SDK says that
there are some significant differences in the development procedure as far
as the programmer's own system goes, but I don't see how a windows app would
really care about the differences, seeing as they don't affect them.

David Giller (rafetmad@oxy.edu)