Message-Id: <5.0.0.25.0.20001020150433.03509060@mail.subdimension.com>
X-Sender: matt DOT l AT mail DOT subdimension DOT com
X-Mailer: QUALCOMM Windows Eudora Version 5.0
Date: Fri, 20 Oct 2000 15:08:01 -0700
To: djgpp AT delorie DOT com
From: Matt Lewandowsky <matt DOT l AT techie DOT com>
Subject: Re: Announce: CWSDPMI r5 public beta
In-Reply-To: <39f055bc.sandmann@clio.rice.edu>
References: <8sq0ld$208k$1 AT news DOT itfs DOT nsk DOT su>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

At 07.25 10/20/2000, Charles Sandmann wrote:
>As R5 is currently beta'ed, there's not much you could do, short
>of installing a TSR to decrease the memory or getting me to add
>some limit to it's page table appetite.  I'm open to suggestions.
>
>One thing I have considered it to change the "max paging file
>size" parameter to be "maximum address space supported".  This
>would allow you to more easily target a particular system if you
>knew a bit about your application's memory requirements.
>
>The other thing I could do is to put a hard limit of like 64Mb of
>physical address space (64K pagetables) allocated on the first
>pass, with increases as needed at run time if DOS memory is available.

I think both of those suggestions would be good... That way if the system 
only has, say, 64MB of RAM, it still is possible to prevent it all from 
being eaten...

Just my 2 cents...

--Matt