6 replies to this topic

[HeikoFolkerts]

Hi,
I have created a patch using the patchdesign view. The Paths to the previous setup are setup as absolute paths such as c:\installer\... The patchcreation reports no erros and no warnings. But the patch doesN't patch any files.
In the patchcreation.log I find entries that the source files are missing the desired path to the file looks like
c:\installer\.\program files\application...
So installshield put a dot between the relative part and the absolute part of my previous installer.
How can I prevent installshield from using theese wrong filepaths?

[Glytzhkof]

The first thing I would check is that the source and target installations have the same media layout. That is dont use compressed files for one setup and uncompressed files for the other.

[HeikoFolkerts]

Hi,
It seems that it was a mistake by me. What irritated me was the notation of the path with the dots. Andyour tip may be right. Maybe I setup to use the compressed releasetype instead of uncompressed as in the old one.
thanks!
Regards
Heiko

[Glytzhkof]

If you have used compressed files, you need to create admin images of your setup to be able to create a patch. I prefer using compressed files and then use the admin image for patching rather than creating setups with uncompressed files. That's just a matter of personal preference though.

[HeikoFolkerts]

Hi,
what do you mean by making admin images? How can they be made?
Regards
Heiko

[Glytzhkof]

From a command line:

setup.exe /a

or

msiexec /a InstallFile.msi

If supported by the setup this will uncompress all CAB files inside the compressed setup and give you a "network image" of the files.

[HeikoFolkerts]

Hi,
OK thanks for the help