InstallAware

Greetings:
We are evaluating IA 9, and created a setup for one of our products, using "Compressed Single Self-Installing EXE" and caching sources, Best compression (final size 154 Mb).
When we initialize our setup, it takes a while loading the package (so far, so good), but when it finishes, the UI dissapear for a minute or even 1 minute and a half.
During that time no UI is shown, thus the user thinks setup failed and starts it again, but in fact it continues working and when it finishes what seems to be a second decompression, the first UI dialog appears (welcome UI).

I searched the forums and only found that this problem was in version 8, but we are testing on IA 9 and the problem is still there.
If we un-check "Always cache Setup Sources" this problem does not happen, but we are unable to uninstall our product, due to the lack of sources.

Could you give some advice on how to solve this?

Thanks in advance

Show a non-modal progress dialog which reads like "preparing to install" on the first line of your MSIcode script, and this problem will vanish.

MichaelNesmith wrote:Show a non-modal progress dialog which reads like "preparing to install" on the first line of your MSIcode script, and this problem will vanish.

It did the trick, thank you for the fast reply!!

I had to use the same trick, but that's exactly what it is: a trick
It's three minutes now that my setup is showing my "progress dialog", but I do not actually know what it is doing, and it's way too long time to wait for a customer, even if he has a cute dialog to watch.
If this is related to caching, is there any chance I can control WHAT is going to be cached? My 300 Mbs setup actually includes 250 Mbs of runtimes and I can live without caching them.
Thanks

Sorry to bring this one up again but it's really a problem here (actually, it's the only problem left then I can say my setup is ready!).
Can I cache only the program files? Or at least cache only the files I really need (no prereqs for example)?
Thanks!

It's possible that the delay you're noticing is being caused by VC++ runtimes scanning system subfolders for MFC files. You could try excluding the VC++ runtimes to see if that make a noticeable difference.

Have you considered web deployment? This way, you can check the system for required updates and download only those required.

I also noticed this post. Are you using logged execution?