From: "A.Appleyard" <A DOT APPLEYARD AT fs2 DOT mt DOT umist DOT ac DOT uk>
Organization: Materials Science Centre
To: DJGPP AT DELORIE DOT COM
Date: Tue, 10 Dec 1996 15:40:56 GMT
Subject: v2 dpmi double-trouble
Message-ID: <5F41B004AA@fs2.mt.umist.ac.uk>

  I have been trying out my new V2 again.
  I found that with the A.OUT stubified by the compiler to make A.EXE, it will
run OK under DOS and with Windows, but when I go to transfer the .EXE to a PC
that hasn't got its own DPMI, there is the nuisance of taking a separate copy
of CWSDPMI.EXE along with it and wondering where to put it.
  So I tried PMODE/DJ, prefixing PMODSTUB.EXE to A.OUT to make an independent
.EXE . This ran OK under DOS, but under Windows it jammed tight on entry. I
suspect that, as Windows is a DPMI, and PMODSTUB.EXE is a DPMI, (calling my
program by clicking it in File-Manager in Windows) tried to install a DPMI on
top of another DPMI, and thus caused a ghastly jam-up. Does PMODSTUB.EXE check
if there is a DPMI there already before it tries to install its own?