InstallAware

I've had the following problems:

- My Drive C: has 9G free (after uninstalling version 8 ). After the version 9 installer expands all its files, of course there is LESS than the required 5G available, however the screen that tells me this allows me to proceed, despite showing a -1G deficit. Its not until partway through the install that it discovers the problem (I assumed that if it let me through it was because it realised the space was being used by the installer's own temp files, and it might clean up after itself during the installation)

- Is There is a way to make the installer expand its files on another drive (the std command line options for MSI installers aren't available??).

Yes, I believe what you are looking for is the pre-defined variable OVERRIDECACHE=<path>

MichaelNesmith wrote:Yes, I believe what you are looking for is the pre-defined variable OVERRIDECACHE=<path>

I'm afraid that

installaware_9.02_with_runtimes OVERRIDECACHE=D:\\TEMP

doesn't do anything - it still tries to expand in the default temp folder on C:. Or have I got the syntax wrong here? Can you give me a specific example?

Note that

installaware_9.02_with_runtimes /?

also doesn't do anything, which is unusual - even std MSI installers offer a screen with their commandline options when queried using this std param. Is this omission accidental or deliberate? IAC, this is a side issue to the main problem above.

If you are talking about the initial self extractor, then the only way to change its folder is to redirect your %TMP% folder elsewhere, or to manually extract it using a 7zip extraction tool.

My tip applies to the setup engine itself and where it caches its setup files for a web build scenario.

MichaelNesmith wrote:If you are talking about the initial self extractor, then the only way to change its folder is to redirect your %TMP% folder elsewhere, or to manually extract it using a 7zip extraction tool.

Ahh, that seems to be working now. Thanks

You might want to add that gem (manual extraction) to an FAQ or something, the master installer is now big enough that this will be an increasing problem on systems - and for those of us outside the US, installing over the web isn't a practical option.