Date:	Tue, 7 Oct 1997 18:59:14 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To:	Charles Sandmann <sandmann AT clio DOT rice DOT edu>
cc:	djgpp-workers AT delorie DOT com
Subject:	Re: CWSDPMI r4 beta
In-Reply-To:	<9710071553.AA12865@clio.rice.edu>
Message-ID:	<Pine.SUN.3.91.971007185343.26471A-100000@is>
MIME-Version:	1.0

On Tue, 7 Oct 1997, Charles Sandmann wrote:

> In a fit which can only be described as temporary (?) insanity, I have 
> put some bug fixes into CWSDPMI and fallen victim to the enhancement
> syndrome.  I am looking for some victims^H^H^H^H^H^H beta testers to try 
> out the new release before infecting the rest of the known universe.

My time is limited lately, but if you can write a couple of words under 
each new feature that gives some idea how to test it, I can test at least 
some of them.

>  Something someone nags me enough about

May I nug you about a switch or another optional way that'd make CWSDPMI 
print max memory usage by the client when it exits?

(I leave the list of the new features attached, so you won't need to look 
it up.)

> Things I tried to do:
>  Map HMA for non-VCPI clients
>  Fix 0x800 mapping for 0x1... addresses
>  Check 0x800 mapping for invalid addresses
>  Use XMS extensions to support >64K XMS memory (NEED A TESTER!)
>  More code size reduction tricks
>  New license agreement (GPL + binaries, just leave me alone...)
>  Dynamic allocation for swapfile usage bitmap; a new cwsparam field for 
>     max swap usage.  So the user can decide how much virtual memory to
>     allow in exchange for 32 bytes of real memory per Mb swap.  Thus
>     the base footprint drops by 4Kb and runtime footprint increases 
>     between 0 and 8Kb, depending on the amount of swap you want and how
>     much disk you have free.  Now limited to 256Mb virtual.

- Raw text -