Date: Sun, 14 Jan 2001 20:33:59 +0200
From: "Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Sender: halo1 AT zahav DOT net DOT il
To: taupin <taupin AT lps DOT u-psud DOT fr>
Message-Id: <2950-Sun14Jan2001203359+0200-eliz@is.elta.co.il>
X-Mailer: Emacs 20.6 (via feedmail 8.3.emacs20_6 I) and Blat ver 1.8.6
CC: djgpp AT delorie DOT com
In-reply-to: <3A61B945.5D1055DF@lps.u-psud.fr> (message from taupin on Sun, 14
	Jan 2001 15:35:49 +0100)
Subject: Re: DPMI
References: <B5E044AF4430D311B24D0060089CD8B1023ECB97 AT hydmail01 DOT hyd DOT wilco-int DOT com> <93mcbr$apb2a$1 AT ID-57378 DOT news DOT dfncis DOT de> <3a6107a1 DOT sandmann AT clio DOT rice DOT edu> <3A61B945 DOT 5D1055DF AT lps DOT u-psud DOT fr>
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

> Date: Sun, 14 Jan 2001 15:35:49 +0100
> From: taupin <taupin AT lps DOT u-psud DOT fr>
> 
> Charles Sandmann wrote:
> > 
> > > What's new in CWSDPMI release 5 in comparison to realease 4?
> > 
> > http://clio.rice.edu/cwsdpmi/r5change.txt
> > 
> > > And why there is no any file that tells what's what's new since version X???
> > 
> > Umm, because I'm lucky to get it released at all, and don't have the change
> > log in my build script? :-)
> 
> 
> For your info: I recently got the diagnostic "No DPMI" and everything
> failed.
> 
> In order to locate the problem I stopped all non needed tasks.
> Especially, I killed my Netscape which was trying (and failing) to print
> a A4*300DPI GIF picture. Then thins came bas to the nirmal behaviour.
> 
> Thus, I think that sometime, DPMI failures comme from the fact that ALL
> the DPMI memory is occupied. In the same way, I gat many page faults on
> a Win95 with 32Mbyte RAM and no more than 40Mbyte of disk available, but
> these page faults disappear when all the memory is available.

Obviously, this has nothing to do with CWSDPMI, since it is not used
on Windows.  What you see are misfeatures of the DPMI server built
into Windows, and the sloppy algorithm it uses to allocate and expand
the amount of virtual memory it makes available to DPMI clients.