Apply install not updating new files

[EpicorRelease]

I have a base install 9.05.600 that I would like to patch to 9.05.601, 602, 603, ect. The base version was created with a very old Wise script so convential methods of patching won't apply until 602.

The new single file executable is suppose to deliver permanent files and then delete any trace of itself from the registry. The problem is it will not deliver any files if they exist or are newer than the ones in the executable. If they are missing no problem. I don't want to have to delete my install every time I need to patch something.

I am a newbie and probably missing something obvious. I have played with patch mode, version number and product numbers with out luck. This was suppose to be done last week, so I am under a bit of a time crunch.

Any assistence would be greatly appreciated. Thanks!

[mills]

Please consider this post:
http://installaware.com/forum/viewtopic ... 248#p21248

Then you may have a better understanding of how you need to develop your InstallAware setup for your first "upgrade" from the wise-installed product.

It might be most simple to just uninstall the old and install a fresh copy.

[EpicorRelease]

Great suggestion that I have explored. The uninstall made a mess of the target machines. The move to IA was because of issues like unruly uninstalls. Aside from not installing the files, the new IA script totally rocks the house.

It may be weird file permission bug? For example, file application1.r with file date 6/17/10 is not replaced with a file dated 8/19/10 on initial run of the patch executable. The user that executes the script deletes the file manually and then same version added back. The patch executable is run again by the same user and the executable replaces the file with the correct version.

Of course, it would be easy to delete all files with the Run Program As feature. cmd /C "del /f/q/s "$targetdir\*.r"" The hurdle is some of our customers have custom code mixed with the delivered code.

I don't know if there is a solution for this particular issue. I have tried a "reset file date" plug in, running as administrator, "attrib"ing the files, renaming, following the patch white papers, and a host of other things. Any more suggestions are totally appreciated.

Thanks for the reply!

[mills]

If you know what files you are "patching" you could delete them specifically instead of using a wildcard.

There is also a "delete files" MSIcode command as well. This command takes effect immediately. By the way, the pink (microsoft installer commands) will not take affect until Apply Install.

If you can more clearly define your problem, then we may be able to provide a better solution.