From:	sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id:	<10004191325.AA12359@clio.rice.edu>
Subject:	Re: CWSDPMI r5
To:	eliz AT is DOT elta DOT co DOT il (Eli Zaretskii)
Date:	Wed, 19 Apr 2000 08:25:44 -0500 (CDT)
Cc:	djgpp AT delorie DOT com
In-Reply-To:	<Pine.SUN.3.91.1000419103009.10023Y-100000@is> from "Eli Zaretskii" at Apr 19, 2000 10:32:46 AM
X-Mailer:	ELM [version 2.5 PL2]
Mime-Version:	1.0
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

> > It doesn't do much for anyone unless
> > they have and need to use big chunks of memory (more than 128Mb physical or
> > more than 255Mb total virtual).  And it still has some physical memory 
> > performance issues around 512Mb physical - so it solves a very narrow range
> > of people's problems.
> 
> I'd say that machines with more than 128MB of physical memory are 
> becoming widespread enough to make this range of problems
> not-too-narrow.

But how many of those people boot their machine with more than 128Mb of
memory into DOS, and then need to use more than 128Mb of memory in DJGPP
programs?  So far I've found most of those people end up using Linux or
Windows NT - so they can do something else with the box while they are
waiting...

There are about 5 people who have asked for and gotten it.

> So I think it would be great if r5 could be released some time soon ;-).

Understood - but the last bug I found would hard hang the machine if you
booted with EMM386 and then exhausted all the VCPI memory.  Noone who was
testing found or reported that bug - which tells me it wasn't tested in
many configurations (expected, since most people needing > 128Mb can't use
VCPI).  It needs a bunch of testing before it's unleashed on unsuspecting
newbies...

- Raw text -