Problems with patch

[SteveDude]

Checked this and it looks like I followed the tips to the tee, but after creating a patch I end up with a 6MB file and when I run the EXE right when the files start to copy I am presented with a Browse for folder dialog asking me to select the orginal setup sources.

This was the same installer as the original with a couple of files changed and one added. Any ideas?

[evoX]

I have the same problem

[Tinus]

Steve,
you should have used a web based setup to avoid this problem. The patch needs access to the original setup sources. A web based setup caches the sources locally on your machine.

Patching fails if you used a compressed, single file setup (because the sources are not expanded at time of patching).

If you used an uncompressed setup (CD/DVD setup) try to located the original sources.

[SteveDude]

Thanks, got it figured out. Just had to make note to add cached file sizes to installation requirements in the manual for required free disk space.

[evoX]

Steve how you solved the problem ? I need to use single file compressed setup.

[SteveDude]

Pretty much as Martin said, doing a web deploy build instead of single EXE. The result is pretty much the same as you end up with a single EXE, but the 7Zip files are cached on the users drive during the install, so you need to compensate in your manual/documentation for required free disk space since the files will stay on the users drive and not be removed like a single EXE build.

[evoX]

that's not a very good solution, because there are many windows cleaners which removes the cached MSI installer files and then the patch will not work.

[SteveDude]

I'm not really sure what else can be done as that is I believe part of the Windows Installer Technology and not IA (Correct me if I am wrong). I think the only difference is the format that IA stores the files in.

The workaround in that case I believe, would be a true web based install and then if the files are gone they would be redownloaded.

Personally I have never found a good Windows cleaner/repair utility that has not trashed something that it shouldn't of.

[evoX]

Then how the installaware registration patch works ? When you buy installaware you get a registration patch which does not require the original setup files.

[SteveDude]

I update my software not using the patch technology but by manipulating the prereq's and maintainance mode. You can really make it work however you want.

I read the TARGETDIR from the registry, that I set in the original installation.

I am also using the same technique to update software written with other installers.

The scripting is very easy to manipulate, just play around with it.

I have one installer that updates the same software distributed by different Vendors and the software is the same, but has 3 different names by changing the $TITLE$...

I use this in the Shortcut Path - $DISTRIBUTOR$\\$TITLE2$ under project properties. The scripting is very flexible. I also use different varibles in Dialogs.

[evoX]

but if I use the prereq/maintenance it removes all other files and installs the new files.

[SteveDude]

You can completely stop it from removing any of the old files and make it ignore any of the prereq's if you want and still not have it affect the desired uninstall procedure. Just peak at the script and comment out what you don't want or just reset some varibles.

The files I want removed I just delete or move to a backup folder.