Date: Thu, 11 Jan 2001 10:01:39 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: "Mark E." <snowball3 AT bigfoot DOT com>
cc: djgpp-workers AT delorie DOT com
Subject: Re: possible bootstrap fix
In-Reply-To: <3A5CA4FB.12401.D51689@localhost>
Message-ID: <Pine.SUN.3.91.1010111100119.15305I-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Wed, 10 Jan 2001, Mark E. wrote:

> > 2) Top priority: xvalloc: currently it wastes twice the
> > allocated memory. This means windows users can use only
> > 32MB for GCC. Not too good, to say the least.
> 
> Now this part of your note puzzles me. I now have 192M of memory, and the 
> go32-v2 under Win98 DOS VM reports the same as usable.

I think Laurynas was thinking about systems with less than 64MB
physically installed.  On such systems, Windows doesn't let you use
more than 64MB VM, and even that only after you tinker with the DOS
box properties, because the default is ridiculously low.

If you have more than 64MB physical memory, the default amount of DPMI
memory is what you physically have, which is reasonable for most
users.  (But I don't think you can have more than that through
properties, can you?)