| delorie.com/archives/browse.cgi | search | 
| From: | dan AT phascolarctid DOT rebellion DOT co DOT uk (Daniel J Mitchell) | 
| Newsgroups: | comp.os.msdos.djgpp | 
| Subject: | Re: DPMI call 0x50b -- get memory info | 
| Date: | Tue, 27 May 1997 20:56:24 GMT | 
| Organization: | Ye 'Ol Disorganized NNTPCache groupie | 
| Message-ID: | <slrn5omik9.to2.dan@phascolarctid.rebellion.co.uk> | 
| References: | <slrn5ok1vk DOT ok9 DOT dan AT phascolarctid DOT rebellion DOT co DOT uk> <338ae2ca DOT sandmann AT clio DOT rice DOT edu> | 
| NNTP-Posting-Host: | rebelhq.demon.co.uk | 
| Cache-Post-Path: | phascolarctid.rebellion.co.uk!dan AT phascolarctid DOT rebellion DOT co DOT uk | 
| Lines: | 12 | 
| 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. Yup, that's what I'm now doing. (and, thanks to the cwsdpmi source ( <grin> ) I can also translate the somewhat abstruse numbers that that call gives me into numbers that are actually useful. Thanks, -- dan @ rebellion
| webmaster | delorie software privacy | 
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |