Xref: news2.mv.net comp.os.msdos.djgpp:5021 From: Charles Sandmann Newsgroups: comp.os.msdos.djgpp Subject: Re: Installer Date: Sat, 15 Jun 1996 10:49:02 CDT Organization: Rice University, Houston, Texas Lines: 23 Message-ID: <31c2db6e.sandmann@clio.rice.edu> References: <11578 DOT 9606141351 AT ws-ai5 DOT dur DOT ac DOT uk> 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 Let me give you my vision and design with respect to multiple copies of CWSDPMI out there. I would expect that there would be one in each distribution, and no real need to remove/consolidate them. For one, it only takes around 25K of disk space. Second, the way the stub works, it looks for CWSDPMI in the same directory as the DJGPP image first. This allows for custom tuning parameters (or even a custom DPMI) for the distribution. If the user wants to delete multiple CWSDPMIs, or update them all to a future release, that's fine, but I would leave that up to the knowledgable user. This was set up so V2 djgpp images could run without any environment variables, or without CWSDPMI even being in the path. Let's suppose that CWS breaks something big time in release 2 of CWSDPMI. You tested your game inside out with R1 and it works great. If you don't put CWSDPMI in the distribution directory, maybe you get the buggy cwsdpmi, your game crashes, and users hate you. Same for uninstalls - if by default there is one per distribution, it's easy to know you can delete the one in your directory. Even if QDPMI or Windows was present at install time, why not put cwsdpmi in the directory anyway, just in case they change configurations? Trying to do anything sophisticated to save 30K of disk space is really pretty silly. If you are worried about name conflicts, rename cwsdpmi.exe to xyzzy42_.exe and stubedit your distribution to look for that instead. Any way you slice it, 32K of disk space is worth less than a penny.