From: fesenko AT pacific DOT net DOT sg (Victor)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Remaining memory under OS/2 question
Date: Tue, 01 Sep 1998 01:14:05 GMT
Organization: Subscriber of Pacific Internet, Singapore
Lines: 16
Message-ID: <35eb49be.27826391@news>
References: <Pine DOT SUN DOT 3 DOT 91 DOT 980831121628 DOT 22974W-100000 AT is>
NNTP-Posting-Host: dyn120ppp173.pacific.net.sg
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

On Mon, 31 Aug 1998 12:16:52 +0300 (IDT), Eli Zaretskii
<eliz AT is DOT elta DOT co DOT il> wrote:


>It's the largest block you can allocate in one chunk.  If it changes,
>then it means that the OS/2 DPMI server *does* track and report the
>available memory correctly, it just doesn't tell you anything useful
>about *physical* memory.  This is expected from a multi-processing OS,
>since ideally there should be *no* free physical memory there
>(otherwise, it means that the system uses less RAM than it could).
That means there is no way to determine the remaining physical memory.
But is there a way to find the amount of used memory then? That was
actually a real  purpose of checking remaining memory. I was looking
that  the remaining memory didn't go too low. If it did it meant I had
memory leaks somewhere.