7zip WEB-Media block archive is not compatible with installer built on other machine.

[Yuriy Svichenskiy]

I created an installer using InstallAware. I used WEB-media blocks feature to reduce size of installer. I was using it without problems until I reinstalled my OS and InstallAware(as result). Now, newly built installer does not work with old 7zip archive(Unable to unpack or something like that). I found that newly built 7zip and old 7zip have different subfolders. Is there a way to control the way how InstallAware creates 7zip archives for WEB-media blocks so I'll be able to make all my installer-versions compatible with same 7zip archive?

[FrancescoT]

Web Media Blocks are "dependent" on the "source files" path specified with each installation command.

So to make Web Media Blocks compatible when building from different machines, the source file path specified with each installation command, it must resolve to the same identical "full path to source files" when compiling from the respective build environments.

[Edhy]

Hi Francesco,

So to make Web Media Blocks compatible when building from different machines, the source file path specified with each installation command, it must resolve to the same identical "full path to source files" when compiling from the respective build environments.

In my case, I upgraded from X7 to X12, so any Web Media Blocks created with X7 will not work with my updated setup in X12, right?

I use 4-5 custom Web Media Blocks, and they all reside in the IA folder "C:\Program Files (x86)\InstallAware X7\runtimes" when upgrading to X12, I simply copied my runtimes to "C:\Program Files (x86)\InstallAware X12\runtimes", is there a way I can relocate my runtimes to a common path that when upgrading to X13, I don't have to re-build the Web Media Blocks?

Note: the problem with this issue is that prior version of my setup files will fail when downloading the same Web Media Blocks files created on X12 with the same names as the previous one.

Thanks!

[FrancescoT]

You may use an unique and dedicated custom path (ex: x:\MyRtm) to store your custom runtimes. In this way regardless of any IA update that you will install, your dedicated custom path will remain identical.

Hope this helps you.

[Edhy]

Hi Francesco,

Sorry for my ignorance, but how do I tell IA to use a custom path (x:\MyRuntimes) instead of "C:\Program Files (x86)\InstallAware X12\runtimes" folder?

Thanks!

[FrancescoT]

You should specify such path in your custom runtime script code.

[Edhy]

Hi Francesco,
Thanks for the reply, I will investigate how to do this so when installing X13 and future updates, does not break my distributed setups for those common runtimes I use.