From: "John M. Aldrich" <fighteer AT cs DOT com>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: System & Other DOS Extenders
Date: Mon, 23 Dec 1996 19:06:43 -0800
Organization: Two pounds of chaos and a pinch of salt
Lines: 27
Message-ID: <32BF48C3.4CA5@cs.com>
References: <32BE4CA5 DOT 7501 AT stud DOT warande DOT ruu DOT nl>
Reply-To: fighteer AT cs DOT com
NNTP-Posting-Host: ppp108.cs.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

Elliott Oti wrote:
> 
> This also happens the other way round; calling a djgpp program from
> within a Watcom/DOS4GW program results in a crash also.
> 
> My question: how can this unpleasant behaviour be circumvented/avoided?

As Eli said, try using a neutral DPMI host like Windows 3.x/95. 
CWSDPMI, Watcom, and DOS4GW programs will all use any resident DPMI that
already exists in the environment as opposed to their own.  Obviously,
if CWSDPMI is already loaded, Watcom/DOS4GW programs will try to use it
and crash, and vice versa.  99.9% of DJGPP programs run under Windows,
but you may need to test this with the DOS4GW ones... and put a caveat
in your program's docs saying that they can't be run under plain DOS.

BTW, DOS4GW is a _terrible_ DOS extender.  250K for the same
functionality as CWSDPMI's 20K?  I don't think so.  Plus, the price
tag...  ugh.  Just look at Quake to see how good a game can be made
using CWSDPMI.  :)

-- 
---------------------------------------------------------------------
| John M. Aldrich, aka Fighteer I      |   mailto:fighteer AT cs DOT com   |
| God's final message to His Creation: | http://www.cs.com/fighteer |
| "We apologize for the inconvenience."| Fight against proprietary  |
|                      - Douglas Adams | software - support the FSF!|
---------------------------------------------------------------------