From: Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Building CWSDPMI.EXE into my program
Date: 7 Apr 2000 15:37:16 GMT
Organization: Aachen University of Technology (RWTH)
Lines: 14
Message-ID: <8ckvbc$dmj$1@nets3.rz.RWTH-Aachen.DE>
References: <8ckq17$ujl$1 AT newsg4 DOT svr DOT pol DOT co DOT uk>
NNTP-Posting-Host: acp3bf.physik.rwth-aachen.de
X-Trace: nets3.rz.RWTH-Aachen.DE 955121836 14035 137.226.32.75 (7 Apr 2000 15:37:16 GMT)
X-Complaints-To: abuse AT rwth-aachen DOT de
NNTP-Posting-Date: 7 Apr 2000 15:37:16 GMT
Originator: broeker@
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Ben Davis <ben AT vjpoole DOT freeserve DOT co DOT uk> wrote:
> Is there any way of building CWSDPMI.EXE into my installation program so
> that plain DOS users don't need to get it separately?

No. Unless you count distributing a ZIP self-extractor containing your
installer and cwsdpmi.exe as a solution.

One of the alternatives to CWSDPMI, Pmode/DJ can be integrated into
the archive, if memory serves. But it has other drawbacks.

For details, see the FAQ, issue 9.6 
-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.