From: dyad255 AT aol DOT com (Dyad255)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Allegro WIP (virtual memory exausted)
Date: 23 Sep 1997 18:23:39 GMT
Lines: 20
Message-ID: <19970923182301.OAA03131@ladder02.news.aol.com>
NNTP-Posting-Host: ladder02.news.aol.com
Organization: AOL http://www.aol.com
References: <Pine DOT SUN DOT 3 DOT 91 DOT 970923131057 DOT 14928N-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 Mon, 22 Sep 1997, Andrew Ellem wrote:
>
>> src/colblend.c:227: virtual memory exhausted
>
>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).

>
>What does go32-v2 print when run with no arguments in the same
>environment (i.e., in the same DOS box on Windows 95) where you tried
>to compile Allegro?

It shows that DPMI doesn't know it has virtually unlimited swap space.