From: sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id: <9706052130.AA11850@clio.rice.edu>
Subject: Re: DPMI and I/O question
To: ericl AT emu DOT com (Eric W. Lange)
Date: Thu, 5 Jun 1997 16:30:02 -0600 (CDT)
Cc: eliz AT is DOT elta DOT co DOT il, djgpp AT delorie DOT com
In-Reply-To: <1.5.4.32.19970605191433.00905c68@tritone> from "Eric W. Lange" at Jun 5, 97 12:14:33 pm
Content-Type: text
Precedence: bulk

> There must be some way to do it.  DesqView has to do it for disk drive
> access or separate DOS sessions would walk all over eachother.  And,
> DesqView simply sits atop QEMM.

QEMM has special hooks for DesqView.  And DesqView handles most of the 
conflicts via interrupt tables, not port access.  It's not a trivial
problem.  You need the source to the V86 monitor.

> I'm not sure what I mean.  I just want this to peacefully coexist with
> DPMI/VCPI/EMM, etc. compliant DOS programs.

It probably can't, unless you plan to write a full EMM386 replacement.
You might check the not-yet-finished EMM386 stuff for freedos, or some
of the linux source, but this will not be a quick project.  If it is 
fully EMM/VCPI compliant it should work with software such as CWSDPMI
which lives on top of it.

See my post to the newgroup on more ugly details.