From: Eli Zaretskii Newsgroups: comp.os.msdos.djgpp Subject: Re: DPMI swap space Date: Sun, 19 Dec 1999 10:01:18 +0200 Organization: NetVision Israel Lines: 26 Message-ID: References: <89w64.446$Px5 DOT 36703 AT news1 DOT rdc1 DOT ab DOT home DOT com> NNTP-Posting-Host: is.elta.co.il Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Trace: news.netvision.net.il 945590377 21068 199.203.121.2 (19 Dec 1999 07:59:37 GMT) X-Complaints-To: abuse AT netvision DOT net DOT il NNTP-Posting-Date: 19 Dec 1999 07:59:37 GMT X-Sender: eliz AT is In-Reply-To: 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 Sat, 18 Dec 1999, Damian Yerrick wrote: > > On NT: 16 MB / 0 MB > > > > How much swap space do I need and how do I change the > > amount of swap space available on the NT machine? > > It seems that some Pinocchio wrote the "report memory > available" code in NT's DPMI. This is unfair, even though we all love to bash MS. It is not easy to report available memory on an advanced OS; the related DPMI functions were designed with simple-minded one-process DOS in mind. For example, you could have several DOS boxes open at a time: what would you expect NT to report as available memory in that case--memory available to all of the boxes, or to each one of them? The latter is next to impossible, since it depends on what the other DPMI clients do. From my small experience, it seems that NT allocates DPMI memory dynamically, and reports whatever is currently allocated. When the application asks for more than that, the allocation gets larger. NT always reports zero swap space, but that shouldn't matter, as a DJGPP program should only care about the sum of the two numbers reported by go32-v2, when it runs on enything other than DOS.