Date:	Fri, 2 Jun 2000 17:30:31 +0530
Message-Id:	<200006021200.RAA00779@vsnl.net.in>
From:	Prashant TR <prashant_tr AT yahoo DOT com>
To:	djgpp AT delorie DOT com
In-reply-to:	<393762BC.82B0E8F@the_message_body.com>
	(see_below AT the_message_body DOT com)
Subject:	Re: DPMI
References:	<393682e4$0$81880 AT SSP1NO17 DOT highway DOT telekom DOT at> <3936B3A0 DOT 64342D2 AT the_message_body DOT com> <200006020041 DOT GAA00609 AT vsnl DOT net DOT in> <393762BC DOT 82B0E8F AT the_message_body DOT com>
Reply-To:	djgpp AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

> 88h/int 15h is not capable to tell you about RAM above 64MB. :)

> > You need to try EAX=E820, AX=E801, AH=88h/INT 15H all in that order. But then, most
> > memory managers hook these interrupts, so you won't get the right value unless you
> > are running uder plain DOS.

Yes, and that's exactly why I mentioned the other two calls. Unfortunately, there
are some old 386 BIOSes that return erroneous values; so there's no easy way to do
this other than by following the sequence I mentioned above.

- Raw text -