Do you want to use InstallShield® to install multiple products in a single directory, but are afraid (or know for sure) that the UnInstallShield® will remove shared files? Here's a program that will fix that. When you do your install, add UnInst1d.Exe to that single directory and run it. Then whenever you install another product in that directory using InstallShield® run UnInst1d.Exe again.
What running UnInst1d.Exe does is add its own name to the front of the UninstallString key at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Current Version\Uninstall\<AppName> where <AppName> was set by the entry in the Application Name field of the Application Information dialog in InstallShield®. Then when the uninstall is run from the ControlPanel/AddRemovePrograms dialog box, UnInst1d.Exe is called with a command line of UnInstallShield® command. UnInst1d.Exe makes all *.dll, *.txt and *.isr files read-only; spawns the UnInstallShield® command; then marks all *.dll, *.txt and *.isr files as read-write again after InstallShield® finishes.
If there are other files besides *.dll, *.txt and *.isr that you need to prevent from being prematurely uninstalled, create a file named Uninst1d.txt that contains a single ANSI text line with each filename (they can include * and ?) separated by one space. Maximum additional filenames is 30 using no more than 500 bytes. Add this Uninst1d.txt file to the directory along with Uninst1d.Exe.
If there is only one package left in the directory, when it is uninstalled, Uninst1d.Exe does nothing except spawn UnInstallShield® and immediately exit so all files are removed including itself.
If you distribute Uninst1d.Exe as part of a commercial package, please read the note that can be seen in the Windows Explorer File/Properties dialog box for Uninst1d.Exe in the Version tab at the Legal Trademarks entry and pay the appropriate fee.
Note: UnInst1d.Exe only works with InstallShield® and UnInstallShield®
| Back to Leigh's Home Page | Site Map | Site Search |
/ Revised 01 Jan 11