From:	firewind AT constellation DOT stu DOT rpi DOT edu (firewind)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: CWSDPMI problem
Date:	20 Apr 1997 02:29:50 GMT
Organization:	Rensselaer Polytechnic Institute, Troy NY, USA
Lines:	30
Message-ID:	<5jbv2u$7bc@usenet.rpi.edu>
References:	<97Apr18.173655gmt+0100 DOT 21890 AT internet01 DOT amc DOT de>
NNTP-Posting-Host:	constellation.stu.rpi.edu
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

Chris Croughton (crough45 AT amc DOT de) wrote:
: 
: I'm running under DesqView, and letting DJGPP and the programs
: it generates load CWSDPMI as they want.  That works fine.
: However, if I run one program in a window, and another in
: a different window (typically gcc and info) then whenever one
: tries to exit it comes up with a sharing violation because 
: they're using the same swap file.  I haven't had any other
: problems with them sharing (yet).
: 
: If I load CWSDPMI permanent before running DesqView, that works,
: but it takes up quite a lot of space and some non-DJGPP programs
: have problems.  It also seems to crash some programs, I assume 
: because they are trying to use 16-bit DPMI services.
: 
: Any solutions?  (Apart from running Linux instead!  I do intend
: to do that at some point, after I've bought a VGA monitor and 
: card.)
: 
: Admittedly, I do have the source, and if I could find my DesqView
: API spec then I could probably change it to use a different swap
: file in each window, but that's not very elegant.  Having an
: environment variable would be preferable.

If you feel confident that you have enough memory, you can use CWSPARAM to
disable swapping, or you can configure your DJGPP programs to use CWSDPR0,
which does not have swapping.

firewind

- Raw text -