Mail Archives: djgpp/1994/12/22/09:21:42
> 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.
There are reasons. CWSDPMI, at least at first, won't provide
16 bit DPMI services. So 16 bit clients like Borland C++
will still need some other DPMI host, and QDPMI fills this
niche nicely because of its extremely small resident footprint
(compared to Borland's server which comes with BC).
However, disabling QDPMI is very simple (type ``QDPMI OFF''),
so I don't see any problem here, either.
- Raw text -