To: Charles Sandmann <sandmann AT new-orleans DOT NeoSoft DOT com>
Cc: djgpp AT sun DOT soe DOT clarkson DOT edu
Subject: Re: v2 & descriptors 
Date: Mon, 28 Nov 1994 09:57:48 EST
From: David Goldschmidt <gold AT ccr-p DOT ida DOT org>


>>>>> "Charles" == Charles Sandmann <sandmann AT new-orleans DOT NeoSoft DOT com> writes:
    >> Will v2 allow you to bind the DPMI provider to your executable so that
    >> the user doesn't have to worry about whether or not it needs to be
    >> installed?  I think this is important for end users who have no idea
    >> what DPMI means.

    Charles> The way it works (and this is pretty polished code, probably
    Charles> close to done):

    Charles> The 2K stub sees if DPMI is present.  If not, it then execs a
    Charles> program (named in the editable stub) which should provide DPMI
    Charles> services.  This program is searched for in the following places:
    Charles> 1) same directory as the image itself (for easy distribution) 2)
    Charles> path 3) current directory

Following up on the original poster's line of thought: Although us user-level
types have no need to know, I suspect some of us (myself certainly included)
are curious about what DPMI is, what it does, and how it works.  (Not to
mention the myterious VCPI ...) Is there any enlightenment available?

David Goldschmidt