Xref:	news2.mv.net comp.os.msdos.djgpp:6904
From:	davis AT space DOT mit DOT edu (John E. Davis)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Binding CWSDPMI
Date:	7 Aug 1996 18:00:07 GMT
Organization:	Center for Space Research
Lines:	20
Message-ID:	<slrn50hmd7.elu.davis@aluche.mit.edu>
References:	<4tlvhp$9b8 AT eis DOT wfunet DOT wfu DOT edu> <31ffbe3d DOT sandmann AT clio DOT rice DOT edu>
Reply-To:	davis AT space DOT mit DOT edu
NNTP-Posting-Host:	aluche.mit.edu
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

On Wed, 31 Jul 1996 15:12:45 CDT, Charles Sandmann <sandmann AT clio DOT rice DOT edu>
wrote:
 : > a way to bind the CWSDPMI.exe file to my executable, so I won't have to 
 : > worry about people running it having access to a DPMI server.
 : 
 : Short answer, no.  I suggest you put it in the same directory, and your
 : DJGPP built image will automatically find it, even if it's not in the
 : path.  This allows you to upgrade CWSDPMI.

This is the main reason that I will not distribute v2 executables,
instead, I will distribute v1 produced executables.  I though that I
might be able to get rid of v1 by distributing distribute CWSDPMI.exe;
however, I am unable to run 16 bit apps from the application subshell
if DPMI is provided by CWSDPMI.

-- 
John E. Davis                   Center for Space Research/AXAF Science Center
617-258-8119                    MIT 37-662c, Cambridge, MA 02139
http://space.mit.edu/~davis

- Raw text -