From:	Chris Croughton <crough45 AT amc DOT de>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Bash as the only shell
Date:	Tue, 19 May 1998 07:54:22 +0200
Message-ID:	<35611E8E.69D8@amc.de>
References:	<Pine DOT SUN DOT 3 DOT 91 DOT 980518191449 DOT 19237A-100000 AT is>
NNTP-Posting-Host:	bob.bob.bofh.org
MIME-Version:	1.0
Lines:	28
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

Eli Zaretskii wrote:
> 
> On Mon, 18 May 1998, Chris Croughton wrote:
> 
> > I now use QDPMI (part of the QEMM memory manager) loaded before DesqView
> > and no problems (except if I want to run Borland C++, I have to turn
> > DPMI off first because it wants to use its own memory manager).
> 
> Desqview should be used with its native DPMI.  I'm surprised it even lets
> you load CWSDPMI (Windows, for example, doesn't).

DesqView itself doesn't use (or provide) DPMI at all, it uses EMS to do
its work.  QEMM (which is the best memory manager to use with DV because
they were designed to work together, but DV will work with other memory
managers which provide EMS like EMM386) provides EMS and XMS and also
includes a TSR DPMI manager QDPMI.  This gives DPMI services which are
sufficient for DJGPP (mainly 0.9, it also provides some but not all 1.0
functionality) but which aren't enough for Borland C++ (which then
crashes because it can't work out what it has got).  QDPMI can be
switched off easily, though (QDPMI OFF), which allows Borland to run its
own DPMI manager (which incidentally /won't/ work with DJGPP!)...

> Thanks for the info.

Since I was the one who originally reported problems with multiple
applications I thought I ought to dispell any fears I'd raised <g>...

Chris C

- Raw text -