From:	Charles Sandmann <sandmann AT clio DOT rice DOT edu>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: cwsdpmi
Date:	Sun, 24 Aug 2003 20:23:46 CDT
Organization:	Rice University, Houston, TX
Lines:	17
Message-ID:	<3f496522.sandmann@clio.rice.edu>
References:	<20030824165917 DOT 08383 DOT 00000649 AT mb-m27 DOT aol DOT com>
NNTP-Posting-Host:	clio.rice.edu
X-Trace:	joe.rice.edu 1061774901 3228 128.42.105.3 (25 Aug 2003 01:28:21 GMT)
X-Complaints-To:	abuse AT rice DOT edu
NNTP-Posting-Date:	Mon, 25 Aug 2003 01:28:21 +0000 (UTC)
X-NewsEditor:	ED-1.5.9
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

> I want that my program tests, whether cwsdpmi or others
> are installed. If not, it shall install cwsdpmi ,
> run the program, and uninstall cwsdpmi after terminating.

This is exactly what the stub prepended to each DJGPP image 
already does.  It first checks to see if DPMI is present,
and if not it searches for CWSDPMI.EXE in the directory the
image is located in (does not need to be in path, so you
can run by name with full path) - then checks the path, and
finally checks the current directory if all other locations
failed.

It then EXECs CWSDPMI, then continues.  CWSDPMI will 
automatically unload itself on the image exit.

If you need something custom that the stub doesn't do, then
the source and tools to build it are in djdev203.zip

- Raw text -