delorie.com/archives/browse.cgi | search |
Xref: | news2.mv.net comp.os.msdos.djgpp:6752 |
From: | Charles Sandmann <sandmann AT clio DOT rice DOT edu> |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | Re: Binding CWSDPMI |
Date: | Wed, 31 Jul 1996 15:12:45 CDT |
Organization: | Rice University, Houston, Texas |
Lines: | 9 |
Message-ID: | <31ffbe3d.sandmann@clio.rice.edu> |
References: | <4tlvhp$9b8 AT eis DOT wfunet DOT wfu DOT edu> |
Reply-To: | sandmann AT clio DOT rice DOT edu |
NNTP-Posting-Host: | clio.rice.edu |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
> 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. Alternate answer - look at pmode10b.zip where you got cwsdpmi - it does allow you to imbed an alternate DPMI server in the stub.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |