ftp.delorie.com/archives/browse.cgi | search |
Xref: | news2.mv.net comp.os.msdos.djgpp:2028 |
From: | nicolas AT dsys DOT ceng DOT cea DOT fr (Eric NICOLAS) |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | Free memory detection (again...) |
Date: | 21 Mar 1996 10:40:57 GMT |
Organization: | Commissariat a l'energie atomique |
Lines: | 15 |
Message-ID: | <4irbnp$a3c@news.cea.fr> |
Reply-To: | nicolas AT dsys DOT ceng DOT cea DOT fr |
NNTP-Posting-Host: | hudson.ceng.cea.fr |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
How can I get some real memory available information (how memory is available to malloc() and new...) ?? My goal is to show free memory information in a sort of 'perf meter'. (I know that _go32_dpmi_remaining_physical_memory() and _go32_dpmi_remaining_virtual_memory() don't do that, because they deal with DPMI free blocks). Thanks. -- Eric Nicolas <nicolas AT dsys DOT ceng DOT cea DOT fr>
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |