InstallAware

Hi,
I learned about the advantages of a web-based created setup. But now I realized the disadvantage: Too much data is cashed under ...\\All Users\\Application Data\\{..}
With our application I have to provide three huge setups - all about 4 GB in total uncompressed mode; compressed about 1.5 GB.
Many system administrators at the target site don't accept that huge sizes on Drive C: just in order to cache the setup when a patch comes. Just to have the advantage that the reference of the basis version is stored.
Or can you give me a different idea how could I manage it? Did I miss s.th. until now?
Anyway, the worse solution for our clients would be that every time a update patch will be delivered that they have to click on the reference (basis) setup first. I think its a bit bothersome. But it avoids at leaset much disk space. Can somebody give me another brilliant idea??

Eddy

If you release patches and the installation was downloadeded or a CD is not handy this is the only thing I know what do, create a web based setup.

I did find an elegant solution, but unfortunately it required the use of a product from a different vendor.

Technically if you create a web based install for intention of using the current IA patching technology in the future then you should increase the disk space requirements to compensate for the cached files. Not real pretty.

I'm having the same problem. Our software is 3GB and we'll only create web-based setup. The current way InstallAware works it requires almost triple the disk space than an actual installation and most of them on C:.

Here is why it requires almost triple disk space:
First, it saves the downloaded files to “Temporary Internet Files” directory (usually on C:)
Then, it caches the entire installation at C:\\Document and Settings\\All Users\\Application Data (on C:)
Then the actual installation in target location.

So it requires the user has at least 5GB on C: drive. which is quite unacceptable.

Has anyone found a good solution for this?

Thanks.