Date: Sun, 15 Aug 1999 15:07:53 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Chris Giese <NoEmailAds AT execpc DOT com>
cc: djgpp AT delorie DOT com
Subject: Re: OS/BIOS dependencies in libc
In-Reply-To: <7p5j2b$akj@newsops.execpc.com>
Message-ID: <Pine.SUN.3.91.990815150241.1935p-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Sun, 15 Aug 1999, Chris Giese wrote:

> Is there a list of such functions already available?

No.  You might want to look at the functional categories in libc.info to 
get a first approximation.

> Failing that,
> what should I look for in the libc source? Maybe look for all
> occurences of "__dpmi_int"? Anything else?

__dpmi_int and int86 would find most of the cases.

Note that functions that call the DPMI Int 31h are also ones that you 
should look for.  These aren't called via __dpmi_int, but looking for 
__dpmi (and filtering out the lots of __dpmi_regs) should probably find 
them as well.

You should also look for functions that use _farpeekX/_farpokeX, since 
those usually depend on DOS and BIOS data structures.