Don't uninstall, instead just install another instance

[5aclockshadow]

When I run my setup on a new PC the first time it will install everything, everytime after that it either uninstalls / reinstalls or asks me if I want to modify, repair, or uninstall.

I don't want it to unistall ... I want to be able to run the setup on the same PC several times and just install new instances (user will manually change path each time) and leave the old instances alone.

Is it possible to turn off uninstall?

If not, what is the best way to be able to keep installing new instances on the same PC? Could be hundreds...

Example:
C:\Program Files\Program001
C:\Program Files\Program002
C:\Program Files\Program003, etc.


Thanks for any help.

[giaviv]

Dear 5aclockshadow,

What you are trying to achieve is definitely possible with InstallAware - please refer to this recent thread:
http://www.installaware.com/forums/view ... f=2&t=6267

[5aclockshadow]

This seemed to work great, thanks!

Not crazy about the TITLE including date & time ... wonder if I can put a textbox somewhere to allow the user to type in something to append to the title? But then I have to worry about it being unique ... any other ideas to generate a unique title? Even automatically appending a number and incrementing it would work for me (ex: MyProgram - 01, MyProgram - 02, MyProgram - 03, etc.).

Thanks again!

[5aclockshadow]

Spoke a little too soon...

I keep getting a box stating:

"The feature you are trying to use is on a network resource that is unavailable.

Click OK to try again, or enter an alternate path to a folder containing the installation package 'Setup.msi' in the box below.

Use source:
C:\Users\<username>\AppData\Local\Temp\miaD3F2.tmp\data\"

Originally I thought it was because we generate a new revision code each time we build the setup. But now I have tested both ways; generating a new revision code before building and not.

Either way, it does the same thing.

So it appears this only works with the same exact setup.exe? Even if I make the most minor change and have to build a new setup, the users will see this message? One more note, we always change the Product Version value each time we build a setup so we know which setup was ran (ex: 02.00.01, 02.00.02, etc.) ... could that come into play?

Btw, even though I see this message, it does appear to install all the files.

[5aclockshadow]

Another update.

Tried building the setup and not changing the Product Version, still got the Setup.msi message, so that is not the problem.

I noticed that I have to click cancel on the Setup.msi message box for as many previous instances are installed ... last time had to click cancel 3 times, now 4 times, etc.

Not sure if that info helps or not...


Thanks for any help!

[5aclockshadow]

Any help?

Does Multiple Instances only work when the same exact setup is ran?

[giaviv]

Dear 5aclockshadow,

Multiple instances do indeed refer to the <b>same</b> instance installed multiple times. What is your status with the problems exactly?

[5aclockshadow]

Thanks for the response.

Well I was hoping that if someone ran a setup & installed our product that if they run another setup for the same product it would allow them to install another instance without any errors.

Right now it will error unless it is the same setup. User will see the following when they run the second setup:

"The feature you are trying to use is on a network resource that is unavailable.
Click OK to try again, or enter an alternate path to a folder containing the installation package 'Setup.msi' in the box below.
Use source:
C:\Users\<username>\AppData\Local\Temp\miaD3F2.tmp\data\"

It does appear to install all the files but I do not see the new instance in add/remove programs.

Is it possible to install multiple instances if the setups used are not the exact same ones?

[giaviv]

Dear 5aclockshadow,

What exactly are you trying to achieve here? Maybe we can find you a different solution. Note that the transform instance mechanism will work if you make changes to your setup but maintain the same product code - could it be that you are experiencing problems because of the specifics of your installer?