Date: Thu, 13 Mar 1997 13:05:16 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: David Wilson <s335194 AT student DOT uq DOT edu DOT au>
cc: djgpp AT delorie DOT com
Subject: Re: problem with malloc in djgpp?
In-Reply-To: <5g7b20$uc$1@nargun.cc.uq.edu.au>
Message-ID: <Pine.SUN.3.91.970313130450.6426C-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On 12 Mar 1997, David Wilson wrote:

> With DPMI you need to realize that the values returned from
> __dpmi_get_free_memory_information (yes it is a long name), and the
> corresponding _go32_dpmi_remaining_*() functions, are subject to change at
> the whims of Windows/CWSDPMI/... 

AFAIK, this is incorrect.  The reported *physical* memory might
sometimes change on Windows (although I never saw this myself), but
the total *virtual* memory should never change during a program's
run.  With CWSDPMI, it *never* changes.  If you can describe a test
which shows such changes in reported virtual memory, please post the
description.