From: Eli Zaretskii Newsgroups: comp.os.msdos.djgpp Subject: Re: newbie question about RAM, DPMI's, and the FAQs Date: Wed, 10 Nov 1999 13:52:48 +0200 Organization: NetVision Israel Lines: 18 Message-ID: References: <38233649 DOT 41A4B696 AT spammersdie DOT muohio DOT edu> <3826DAEB DOT 6866D2F AT spammersdie DOT muohio DOT edu> <806oq8$hvt$1 AT antares DOT lu DOT erisoft DOT se> <38271764 DOT 18B2E167 AT spammersdie DOT muohio DOT edu> NNTP-Posting-Host: is.elta.co.il Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Trace: news.netvision.net.il 942234682 7245 199.203.121.2 (10 Nov 1999 11:51:22 GMT) X-Complaints-To: abuse AT netvision DOT net DOT il NNTP-Posting-Date: 10 Nov 1999 11:51:22 GMT X-Sender: eliz AT is In-Reply-To: <38271764.18B2E167@spammersdie.muohio.edu> To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On Mon, 8 Nov 1999, robin wrote: > Maybe it's my Unix contamination, but I interpreted "Swap space" as using the hard > disk as virtual memory. I'm not sure why there would be a distinction between > memory available and swap space if it all comes from RAM. Think a bit how would *you* write the module inside Windows that reports the free memory, and you will see why. Since Windows provides memory to many different programs, including to itself, how in the world can it know at any given moment which part of what the DPMI program will consume is going to be in RAM and which part on disk? The DPMI spec intentionally leaves this vague, and most ``advanced'' operating systems that provide built-in DPMI services use some arbitrary logic to subdivide the maximum amount of memory they provide to DPMI clients. For example, NT always reports zero as the swap space, which is clearly a lie.