Page 1 of 1

Problem applying patch

Posted: Tue Aug 11, 2009 9:20 am
by MortSkil
I am trying to create a patch to one of our setup projects, using the patch whitepaper as a pattern.

I run into three problems:

1) When adding a second version to the patch references, the build ends with
Error during build: Unable to create patch database [TargetImages.Target = 'TARGET2': PackageCode {thecode} is not unique.]
I thought only the revision code had to be unique?

2) With only one reference, I try to apply a patch built with no warnings or errors to a system that was installed from a single file setup. I was unable to locate the original setup as indicated in the whitepaper; the .tmp folder was deleted upon successful installation of the product.

3) Upgrading a CD/DVD setup, I successfully indicated a original source folder. This time, I got the following error message:
The file 'MMCFor7e17cMMCFormsShim.' cannot be installed because the file cannot be found in cabinet file 'PCW_CAB_B7F786DC'. This could indicate a network error, an error reading from the CD-ROM, or a problem with this package.
Do anyone have any idea what I might have done wrong, or misunderstood?

Thanks,

MortSkil

Posted: Tue Aug 11, 2009 5:57 pm
by MichaelNesmith
If you are on InstallAware 9, set the compiler variable NOHARDLINKS to TRUE and see if that helps.

Posted: Wed Aug 12, 2009 11:14 am
by MortSkil
Thank you, Michael, for quick response!

That definately changed things - now I get the following error message when compiling the script:
WARNING!

No files matching wildcard pattern \\Installers\\Common\\Sentinel\\*.msi
This happens while building a plug-in action where I include any MSI file in the indicated folder in order to prepare for installing Sentinel drivers.

Should the original setup have been compiled with NOHARDLINKS too, or is this only important for the setup being built?

How do I apply a patch to a product installed from a single file installer?

Posted: Wed Aug 12, 2009 11:15 am
by MortSkil
Also, I think I should read through the Patching chapter in the User's guide.

I have changed the product name between the versions (name including version info), so this might also cause problems wrt patch execution.