From: sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id: <9607270609.AA13817@clio.rice.edu>
Subject: Opinion
To: djgpp-workers AT delorie DOT com (DJGPP developers)
Date: Sat, 27 Jul 1996 01:09:56 -0600 (CDT)
Content-Type: text

Now that PMODE/DJ is getting a shakedown (and some improvements for V1.1) it
looks like it will be superior in every way to the CWSDPMI ring 0 version
in the next release.  Because of this, I plan to remove CWSDPR0.EXE from
the r3 release (which will make the binary distribution a bit smaller) and
recommend use of PMODE/DJ for ring 0 usage.  Do you see any problems with this
reasoning?

R3 has the turboc startup code and I/O pulled out, so the CWSDPMI.EXE image
has dropped about 4Kb in size (to a little over 21K).  If there are any
features you ever considered (or wanted bugfixes), ask now, since this will
probably be the last "feature" release (and hopefully the last release)
of the silly thing.  No promises, however.  Since DOS/4G apps (games, etc)
seem to work under R3, I'm pretty sure it's "right" now.

Suggested features, open for comments:
 1) Optionally commit all memory, so locking wouldn't be required usually,
 2) A flag to disable 1.0 extensions,
 3) A flag to not delete the swap file on exit.