From:	ao950 AT FreeNet DOT Carleton DOT CA (Paul Derbyshire)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: DPMI call 0x50b -- get memory info
Date:	30 May 1997 06:09:04 GMT
Organization:	The National Capital FreeNet
Lines:	15
Message-ID:	<5mlqu0$315@freenet-news.carleton.ca>
References:	<slrn5ok1vk DOT ok9 DOT dan AT phascolarctid DOT rebellion DOT co DOT uk> <338ae2ca DOT sandmann AT clio DOT rice DOT edu> <slrn5omik9 DOT to2 DOT dan AT phascolarctid DOT rebellion DOT co DOT uk>
Reply-To:	ao950 AT FreeNet DOT Carleton DOT CA (Paul Derbyshire)
NNTP-Posting-Host:	freenet5.carleton.ca
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

On Tue, 27 May 1997 13:34: 2, Charles Sandmann <sandmann AT clio DOT rice DOT edu> wrote:
>>  Alternatively, is there a better way to get memory usage information? 
>
>Use the DPMI 0.9 status call (0x500), which is supported on all DPMIs.

0x500? That looks like an interrupt... ack!

__dpmi_get_bla_bla_information   ... Ow, that's a headache
__dpmi_int (0x500,&dmpi_regs)    ... That's a Motrin headache!
--
    .*.  Where feelings are concerned, answers are rarely simple [GeneDeWeese]
 -()  <  When I go to the theater, I always go straight to the "bag and mix"
    `*'  bulk candy section...because variety is the spice of life... [me]
Paul Derbyshire ao950 AT freenet DOT carleton DOT ca, http://chat.carleton.ca/~pderbysh

- Raw text -