Xref: news2.mv.net comp.os.msdos.djgpp:8385
From: Charles Sandmann <sandmann AT clio DOT rice DOT edu>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: CWSDPMI V3 - what's new versus V2?
Date: Sat, 07 Sep 1996 12:42:29 CDT
Organization: Rice University, Houston, Texas
Lines: 17
Message-ID: <3231b405.sandmann@clio.rice.edu>
References: <323128DA DOT 3938 AT drao DOT nrc DOT ca>
Reply-To: sandmann AT clio DOT rice DOT edu
NNTP-Posting-Host: clio.rice.edu
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

> Downloaded CWSDPMI3 and was unable to find any info in the readme on 
> what's changed from V2. 

A list of many changes was in the announce that I sent out about a week
ago - check the mailing list archives or a news archive site.  In a nutshell,
a lot of bugs were fixed.  Most of the fixed bugs would only be observed
in program development, not running currently working images.  The only
fixes that someone might notice using a previously built image would be
using linear frame buffers in the 256Mb address range and some buggy
clone caches which didn't work in "raw" (non himem/emm) environments.

> I noticed that full Quake 1.01 did not did not like V3 (FP exception
> on startup). 

I am able to reproduce this bug report.  I think I'll go puke now.  
The hazards of inadequate testing.  So, maybe there will be an R4...
but not until I see if anyone notices other problems with R3...