From: Charles Sandmann <sandmann AT new-orleans DOT NeoSoft DOT com>
Subject: Re: Virtual memory and DPMI (and Win 3.1)
To: eliz AT is DOT elta DOT co DOT il (Eli Zaretskii)
Date: Sun, 20 Nov 1994 11:06:36 -0600 (CST)
Cc: dj AT stealth DOT ctron DOT com, rgrunwal AT bluering DOT cowan DOT edu DOT au, MRMILLER AT delphi DOT com,
        djgpp AT sun DOT soe DOT clarkson DOT edu

> >> I think that from previous queries on this list it was also specified that
> >> QEMM's virtual memory management under QDPMI is incompatible with GO32.
> >> >From my own experiences this was found to be true, since the only memory
> >> GO32 is given from QDPMI is actual memory. If more memory was required
> >> than was physically available, the message "DPMI: Not enough memory"
> >> would come up.
> >
> > Yes, and I've reported this to Quarterdeck.
> 
> It is still uncorrected in QEMM 7.50 (QDPMI 1.06).

So, it sounds like it's not going to get fixed anytime real soon.  And
the extended memory + low memory overhead are outrageous for QDPMI.

Question for you guys:  What are the reasons for not just disabling 
QDPMI outright?  I use it for testing purposes, but actually use the
free DPMI for day to day V2 development anymore.  Sure, the free dpmi
has some limitations currently, but most bugs I encounter are in QDPMI.
Please send me the "must have" features to be able to replace QDPMI.
Thanks.