Date: Thu, 4 Feb 1999 13:37:39 +0200 (IST) From: Eli Zaretskii X-Sender: eliz AT is To: Paul Derbyshire cc: djgpp AT delorie DOT com Subject: Re: Q: Forcing mode CO80 In-Reply-To: <3.0.6.32.19990203213804.00892dc0@pop.netaddress.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Reply-To: djgpp AT delorie DOT com On Wed, 3 Feb 1999, Paul Derbyshire wrote: > 1. What header needs to be included to get _dos_ds? The info file has > nothing to say (there is no node for _dos_ds). There's the `grep' package for such cases. A command such as "fgrep _dos_ds %DJDIR%/include/.../*.h" will find you the header in seconds. > 2. What header needs to b included to get _farpeekb? The info file > has nothing to say (the info node for _farpeekb is a copy of the > info node for free!) What kind of libc.info do you have, anyway? The _far* node was right even in v2.01, and it *does* show the header you should include. Type "info libc alpha _far" from the command line, and you should see the right docs, including the header name. > 3. I assume that I need _dpmi_int to invoke 10h? Yes. > 4. How do I invoke _dpmi_int with a particular function number (e.g. > 0x10) and parameters? You fill the members of __dpmi_regs structure as the function requires. E.g., if you need to put 1234h in AX, say something like "r.x.ax = 0x1234;". The node "DPMI Overview" describes the __dpmi_regs structure in full. > The > _dpmi_int info node merely says to check the DPMI specification. There are several working examples in the FAQ; use them (be sure to get the latest version 2.11 of the FAQ). > The link for the DPMI specification just lists a bunch of phone > numbers and Internet addresses instead of actually displaying the > specification info! The FAQ has the URLs for the DPMI spec.