Date: Mon, 31 Aug 1998 12:16:52 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Victor <fesenko AT pacific DOT net DOT sg>
cc: djgpp AT delorie DOT com
Subject: Re: Remaining memory under OS/2 question
In-Reply-To: <35eae674.2404551@news>
Message-ID: <Pine.SUN.3.91.980831121628.22974W-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


On Mon, 31 Aug 1998, Victor wrote:

> As for other functions the trouble is that I'm not sure what the
> values in the structures returned by these functions should be.
> I tried the function __dpmi_get_free_memory_information() and the
> value of largest_available_free_block_in_bytes changes in the course
> of the program, but I'm not sure how to interpret it.

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).