Date: Mon, 1 May 2000 14:06:08 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: "Alexei A. Frounze" <alex DOT fru AT mtu-net DOT ru>
cc: djgpp AT delorie DOT com
Subject: Re: 3rd Try: Maybe an asm problem? (Problems linking)
In-Reply-To: <390D472E.34491066@mtu-net.ru>
Message-ID: <Pine.SUN.3.91.1000501140345.10196A-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 Mon, 1 May 2000, Alexei A. Frounze wrote:

> > Unfortunately, you cannot rely on DPMI being correctly supported and
> > on V86 monitor working properly.  For example, last year we found that
> > function 1680h of the interrupt 2Fh, if issued directly (through
> > int86) in nested DPMI programs, wedges the DOS box on some versions of
> > Windows 9X, while the same function call that goes through __dpmi_int
> > works correctly.  (See the end of section 6.1 of the FAQ for more
> > about this.)
> 
> 1680h of 2fh. :)) I used it only once. I think there are a lot of people who
> never used it at all.

Actually, most of them do, especially if they use RHIDE, Emacs, Less, 
Info, and other programs.  2Fh/1680h is the function called by the 
library function __dpmi_yield; most interactive programs call that 
function inside their idle loop (or if they don't, they should).