Date: Fri, 12 Mar 1999 10:35:26 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Sebastian Schuberth <sebastian DOT schuberth AT gmx DOT net>
cc: djgpp AT delorie DOT com
Subject: Re: dpmi address mapping
In-Reply-To: <36E7E9AE.6D259B61@gmx.net>
Message-ID: <Pine.SUN.3.91.990312102807.29491E-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 Thu, 11 Mar 1999, Sebastian Schuberth wrote:

> for some reason I don't like to use DJGPP's
> _dpmi_free_physical_address_mapping function. Unfortunately a standard
> DPMI call to function 0x0801 doesn't seem to work.

I don't understand.  __dpmi_free_physical_address_mapping is nothing more 
than a bare-bones C wrapper around the DPMI function 0x0801.  So why do 
you want to do this?

Function 0x0801 is not part of the DPMI 0.9 specification, it is only 
supported by DPMI v1.0, and most DPMI servers are only compatible with 
version 0.9.