Hi Cosmin
In order to avoid this behavior you must create a new Advanced Installer project for each installation package. Also, you need to make sure that any two packages don't use the same installation path.
I have created three different installers for the three different programs. I may have been unspecific in my original post, so allow me to elaborate. I depend on three (old Win95) programs that all assume they are installed in a *specific directory* (e.g. C:/MYDIR). All data files created by these programs are stored in this directory and read from here.
If the folder exists then another application is installed in it. If you install another application then the original one will be overwritten. In order to avoid this you should install each application into a different sub-folder of the "C:\APP" folder.
Installing the programs in subfolders within this folder is therefore out of the question, cause they WON'T WORK.
We don't want to pay the cost of a programmer to modify these programs to exhibit more directory-agnostic behaviour (i.e. so they can be installed in other directories), but rather want to distribute them as-is.
I have already created a combo installer that installs alle three programs in the same installation path and this works perfectly. Because some customers only may want one or two of these programs, I created stand-alone installer projects for separate distribution.
Installing any two of these programs does NOT work, however, because the installation procedure erases whatever program is already installed in the C:\MYAPP directory, deleting valuable user data etc. in the process. This can be disastrous for the customer.
I find it strange that an Advanced Installer project defaults to overwrite whatever is installed in its installation path. As it can keep track of program versions and overwrite older with new, I see this "kill 'em all" attitude as a bit of a mystery. I was therefore wondering whether this was not "set in stone", but could be changed.
So to rephrase my original question:
Is there a setting somewhere in Advanced Installer (folder attributes etc.) that can change the installer's behaviour to just install the app in the specified directory without touching whatever may be stored in that path already?
FOLLOW US
Get the latest news in Application Packaging