From: "M. Schulter" <mschulter AT value DOT net>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Interrupt handlers
Date: 22 Dec 1997 23:50:20 GMT
Organization: Value Net Internetwork Services Inc.
Lines: 29
Message-ID: <67mubs$qtl$1@vnetnews.value.net>
References: <Pine DOT LNX DOT 3 DOT 95 DOT 971218150120 DOT 5860A-200000 AT orkide DOT cs DOT itu DOT edu DOT tr> <67lgll$afn AT freenet-news DOT carleton DOT ca>
NNTP-Posting-Host: value.net
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

Paul Derbyshire <ao950 AT FreeNet DOT Carleton DOT CA> wrote:

: > It works when I turn on my computer in Windows 95 and run it through MSDOS
: > prompt of it. But it doesn't work under MSDOS Operating System only.

: You need CWSDPMI to get DPMI under DOS only.
: To run with no Winblows that is.
: Look for csdpmi3b.zip or csdpmi4b.zip (I think?) for latest version in the
: Simtel djgpp v2 tree.

Hello, there, and I might just add that certain memory management products
such as Quarterdeck QEMM, which includes QDPMI, also supply DPMI for DOS
without Windows. As Eli and I have noted, some DOS/4GW programs such as
Ghostscript or Image Alchemy PS have been incompatible at least in part
with CWSDPMI, so having such an alternative DMPI can be helpful for some
users.

However, CWSDPMI has some special advantages with handling some kinds of
pointer errors, for example, so even those of us with QDPMI or the like
might consider trying it. One nice feature is that it's possible with a
couple of quick batch files to alternate between CWSDPMI and QDPMI,
loading CWSDPMI high with QEMM and then unloading it when running under
QDPMI to avoid incompatibilities.

Most respectfully,

Margo Schulter
mschulter AT value DOT net