1 reply to this topic

[dGabay]

Hi,
We have a couple of versions of a CD media type setup in the field which are working well. If a customer installs the later version, a minor upgrade occurs and the app works fine.

For our latest release, we have created a custom bootstrapper using VB6 which taps into the API to fire off the MSIs silently. The bootstrapper and MSIs are on a CD. They are supposed to do a minor upgrade if the user has a previous version. In that case, we are using REINSTALL=ALL and REINSTALLMODE=vomu;

Now a few customers are having issues. When attempting to upgrade from the new cd, they are being asked for disk 1. If the new disk is removed and the old disk is inserted, they are still being asked for disk1.

If we try to uninstall the old version first, they are asked for disk1. If the original disk is inserted, the uninstall still asks for disk1. If we avoid the bootstrapper and use the setup directly - same problem. These customers are stuck - even though they have both the old and the new disks. What could be happening? Any workarounds?
Thanks

[Stefan Krueger]

First you need to amke sure that the Volume Label of your CDs never change.
The CD request upon uninstall sounds strange. Did you double check that it really requests the CD for your application, and not some other CD (like MS Office)? Sometimes MSI activitiy triggers a repair for a third party application which then requests the respective CD.
Also a log file might give additional information.