Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!att!cbnewsk!markg
From: markg@cbnewsk.att.com (mark.r.gibaldi)
Newsgroups: comp.windows.ms
Subject: Re: Loading Appl SW that requires Protect Mode
Message-ID: <1990Jun11.173025.6120@cbnewsk.att.com>
Date: 11 Jun 90 17:30:25 GMT
References: <322.266cfea5@sunset.sedd.trw.com> <1990Jun7.150839.21981@cbnewsk.att.com> <1990Jun8.181622.16005@bach.amd.com>
Distribution: usa
Organization: AT&T Bell Laboratories
Lines: 23

In article <1990Jun8.181622.16005@bach.amd.com> phil@pepsi.amd.com (Phil Ngai) writes:
>In article <1990Jun7.150839.21981@cbnewsk.att.com> markg@cbnewsk.att.com (mark.r.gibaldi) writes:
>|Windows 3.0 runs your 386 in protected mode.  There can only be one protected
>|mode on a 386.  In order to run protected mode software under Windows 3.0,
>|you have to run Windows in real mode like so "win /r".  This is a limitation
>|of the processor.  Until there are "virtual *protected* mode machines"
>|available on an Intel Processor, things will be this way.
>
>Not so, once DPMI is approved and implemented, everything will work
>together. The history of the previous standard, VCPI, indicates
>that it's in everyone's interest to have a good standard and vendors
>will quickly comply.
>
>--
>Phil Ngai, phil@amd.com		{uunet,decwrl,ucbvax}!amdcad!phil

Phil is correct DPMI will take care of multiple programs requiring
protected mode.  DPMI had slipped  my mind when I wrote the article.
The work-around is valid however until DPMI is available.

Mark R. Gibaldi
AT&T Bell Labs
mrg@cblph.att.com