From: "John M. Aldrich" <fighteer AT cs DOT com>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Forcing CWSDPMI usage
Date: Sat, 14 Jun 1997 15:52:37 +0000
Organization: Two pounds of chaos and a pinch of salt
Lines: 21
Message-ID: <33A2BE45.5696@cs.com>
References: <33A2E957 DOT 2CCA AT pukopn1 DOT puk DOT ac DOT za>
Reply-To: fighteer AT cs DOT com
NNTP-Posting-Host: ppp202.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
Precedence: bulk

acebear AT pukopn1 DOT puk DOT ac DOT za wrote:
> 
> Is there any way to force the usage of CWSDPMI as DPMI server even when
> another server is already availabe? Would one want to do this? Is
> CWSDPMI better to use than another available DPMI?

No, Sometimes, and Usually.  Unfortunately, there is no way to tell
another DPMI host to "shut down".  CWSDPMI has some DPMI 1.0 extensions
that other hosts don't have, such as NULL pointer protection and linear
framebuffer support.  The only DPMI host that has full 1.0 support is
386MAX.  It is not always good to force CWSDPMI to be resident, however,
because it is incompatible with some other DPMI hosts, particularly
Borland's 16-bit DPMI and the DOS4GW extender.

-- 
---------------------------------------------------------------------
| John M. Aldrich, aka Fighteer I  |     mailto:fighteer AT cs DOT com     |
|    *  Proud user of DJGPP!  *    |   http://www.cs.com/fighteer   |
|    ObJoke:  If Bill Gates were a robber, not only would he        |
|     shoot you, but he'd send you a bill for the bullets.          |
---------------------------------------------------------------------