Date: Mon, 12 Jun 2000 15:34:26 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: djgpp AT delorie DOT com
Subject: Re: far pointers
In-Reply-To: <3943754D.B490E34C@the_messasge_body.com>
Message-ID: <Pine.SUN.3.91.1000612153402.5082E-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Sun, 11 Jun 2000, Alexei A. Frounze wrote:

> Do you wanna say __dpmi_int has nothing about V86???

Yes, that's exactly what I'm saying.  __dpmi_int works with or without
V86.  All it needs is a DPMI server that catches Int 31h.  CWSDPMI is
one such server, and CWSDPMI *can* run without V86.

> If host OS is DOS, DOS extender/ DPMI host switches to V86 to handle
> that request.

Not true.  CWSDPMI does NOT switch the CPU into V86.  If it finds the
CPU in V86, that's what it will use.  If not, it will switch it to
real mode when it needs to issue a DOS call.  The CWSDPMI sources show
this very clearly.