From: Glen Miner <gminer AT ca DOT newbridge DOT com>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Calling 16bit interrupts
Date: Mon, 18 Nov 1996 07:56:01 -0500 (EST)
Organization: Newbridge Networks Corporation
Lines: 27
Message-ID: <Pine.SUN.3.90.961118075517.499E-100000@coop10>
NNTP-Posting-Host: 138.120.136.238
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
In-Reply-To: <Pine.SUN.3.91.961117101154.12547a-100000@is>
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp


> > What's the difference between __dpmi_int() and int86()? 
> > 
> > I have read the docs under the libc.a reference but I think I need a
> > translation. 
> 
> Any attempt to understand how library functions *really* work requires 
> that you look into the library sources, IMHO.
> 
> The most significant difference is that `int86' invokes the 
> protected-mode INT instruction, which is caught by the DPMI server and 
> reflected to real mode, while `__dpmi_int' calls the interrupt-reflection 
> DPMI service directly.

Okay, maybe I'll do that ;)

> I suggest you use `__dpmi_int' unless compatibility to other compilers is 
> an issue, because `int86' has some subtle aspects which have to do with 
> the 16/32 bit issue of the registers that you pass.

Hmm, okay. Thanks!

Peace
===[ Gabo / [ABC] : gaminer AT undergrad DOT math DOT uwaterloo DOT ca ]===================
Latest ABC Shogi: http://www.undergrad.math.uwaterloo.ca/~gaminer/shogi.html
"What Greenpeace spends in a year General Motors spends in four hours" -Moby