Date:	Wed, 29 Sep 1999 11:17:41 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	djgpp-workers AT delorie DOT com
cc:	Charles Sandmann <sandmann AT clio DOT rice DOT edu>
Subject:	Re: __dpmi_free_physical_address_mapping does not work - why? (fwd)
Message-ID:	<Pine.SUN.3.91.990929111403.11087d-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp-workers AT delorie DOT com

I added a blurb to the docs of all the __dpmi_XXX functions which are 
defined bt DPMI 1.0 only, telling that they aren't supported by CWSDPMI 
and Windows (except a few exceptions that are supported by CWSDPMI,
which I documented as such).

---------- Forwarded message ----------
Date: Tue, 28 Sep 1999 23:35:38
From: Charles Sandmann <sandmann AT clio DOT rice DOT edu>
To: djgpp AT delorie DOT com
Newgroups: comp.os.msdos.djgpp
Subject: Re: __dpmi_free_physical_address_mapping does not work - why?

> When releasing the resources of a memory mapped device, why does
> __dpmi_free_physical_address_mapping fail?

Because it's a DPMI 1.0 function which isn't implemented by any DPMI
provider (except maybe 386MAX).  

- Raw text -