Subject:	Re: QEMM's VM manager, V2, and CWSDpmi
To:	babcock AT cfa DOT harvard DOT edu
Date:	Thu, 22 Dec 1994 09:55:05 +0100 (MET)
From:	Henrik Storner <storner AT olicom DOT dk>
Cc:	djgpp AT sun DOT soe DOT clarkson DOT edu

Bob Babcock writes:

> 
> > I hope to take a look at the QDPMI virtual memory issue soon.  If I can't
> > find a workaround, getting CWSDPMI in top shape becomes an even higher
> > priority.
> 
> Even getting CWSDPMI to work won't really solve the problem.  An installation
> procedure which requires replacing/disabling QDPMI isn't going to be popular
> with QEMM users.

I don't see why not ? If CWSDPMI implements the same services as QDPMI
(i.e., the DPMI 0.9 spec for use by any application asking for DPMI), then
I cannot see any problems in replacing one with the other.

  Funny thing is, I thought QDPMI used to work?

Never has worked reliably for me. Fortunately, I have very little use for
DPMI, but of course that will change with DJGPP v2.

> And if it is broken, wouldn't that interfere with Windows as well?

No. QEMM/QDPMI effectively disables itself when Windows start up, leaving
all memory management to Windows itself. While inside MS-Win, Windows
procides the DPMI services, even with QDPMI loaded.
-- 
Henrik Storner (storner AT olicom DOT dk)

- Raw text -