From: dyad255 AT aol DOT com (Dyad255)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Allegro WIP (virtual memory exausted)
Date: 24 Sep 1997 21:12:01 GMT
Lines: 24
Message-ID: <19970924211201.RAA16297@ladder01.news.aol.com>
NNTP-Posting-Host: ladder01.news.aol.com
Organization: AOL http://www.aol.com
References: <Pine DOT SUN DOT 3 DOT 91 DOT 970924123128 DOT 18049P-100000 AT is>
SnewsLanguage: English
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

Eli put forth:
>On 23 Sep 1997, Dyad255 wrote:
>
>> >Did it ever occured to you that GCC might be telling the truth, and
>> >that it *really* has run out of virtual memory?  Virtual memory
>> >doesn't mean unlimited memory, you know ;-)
>> 
>> Well, with '95 the swap normally dynamically grows to fill the HD, so it
>> is hard for users to figure out what kind of memory the program thinks it
>> has (or doesn't have).
>
>The dynamic growth only happens for Windows' own sake; the amount of
>DPMI memory that Windows lets DOS programs use is limited by the
>setting in the property sheets of that DOS box.  The default is 16MB
>(cleverly disguised by Microsoft as "Auto", whose precise meaning I
>have yet to see documented).  When your program uses up that much, it
>doesn't get more, even when Windows has no problems to give you more.
>
>
>That's why the FAQ advises to set that limit to 64MB (the maximum
>value allowed by Windows).  See section 15.6 of the FAQ.

Yes, this is in the FAQ... I've memorized lots of it.