Date:	Sun, 12 Dec 1999 14:18:13 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	Frederico Jeronimo <fjds AT rnl DOT ist DOT utl DOT pt>
cc:	djgpp AT delorie DOT com
Subject:	Re: Map physical memory.
In-Reply-To:	<Pine.GSO.4.10.9912101602570.5274-100000@camoes>
Message-ID:	<Pine.SUN.3.91.991212141757.19096d-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Fri, 10 Dec 1999, Frederico Jeronimo wrote:

> 	I'm having a little problem and I was wondering if you could help
> me  out. I'm trying to map a range of physical memory over a set of
> addresses using '__djgpp_map_physical_memory()'.

This is a bad idea, IMHO.  __djgpp_map_physical_memory only works with
DPMI servers which implement DPMI v1.0 spec; most of them don't.

Why can't you use the function __dpmi_physical_address_mapping, as
explained in section 18.7 of the FAQ.

> 	Ps: How can I check what DPMI host I'm using?

In general, you can't.  Some hosts support the function
__dpmi_get_capabilities, which returns that info, but this, too, is a
DPMI 1.0 function.

- Raw text -