Date:	Thu, 27 May 1999 10:54:48 +0300 (IDT)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	Tom Friedel <tfriedel AT ix DOT netcom DOT com>
cc:	djgpp AT delorie DOT com
Subject:	Re: Need Expanded Memory access (really) with DJGPP
In-Reply-To:	<7ii8e0$fc2@dfw-ixnews8.ix.netcom.com>
Message-ID:	<Pine.SUN.3.91.990527105422.9561S-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 Wed, 26 May 1999, Tom Friedel wrote:

> Having read the FAQ's and documentation, I see that I can access memory
> below 1 MB, but am not clear if there is an explict Expanded Memory
> interface.

EMS interface is a bunch of functions of Interrupt 67h, so you should
be able to access it via the DJGPP library function `__dpmi_int'.

> I need the TopSpeed equivalent of ALLOWLOWSEG and FREESEG, which
> return and take selector.

Unless you are lucky to find TopSpeed veterans here, you will need to
give more info about these and other features, if you want to get
meaningful help.  ALLOWLOWSEG and FREESEG don't reveal much about what
they should do; posting some description from any docs you might have
is probably a wise thing.  In particular, it's not clear to me what
does the word ``selector'' do in this context (how could a real-mode
application use protected-mode selectors?).

One place to look for answers is to read the descriptions of the EMS
functions in the Ralf Brown's Interrupt List.  Comparing those with
the docs of the TopSpeed/driver interface might tell you which
functions are called behind the scenes.

- Raw text -