Installation on E: drive - Why does Installaware insist on .

[Seán]

Hi there,

I've just installed an update to my X2 install and TOLD it to install on E: drive so imagine my surprise when I see Installaware insisted on installing more than 2GB on my C: drive under C:\user\AppData\ProgramData.

My C: is full - I never want Installaware installed on it...

So why is Installaware installing on C: when I specifically said E:?

I need to delete this directory any problems?

Thanks and regards
Seán

[FrancescoT]

Dear Seán,

the C:\user\AppData\ProgramData contains the setup source files used by the IA installer, if these are not there, you will be asked to locate them when you will run the IA installer in maintenance mode (Repair\Remove\Add-Change Features).

You should keep those files!

Regards

[Seán]

Thanks Franco,

but I think you're missing my point.

As you noted these are Setup Source installer files, and they can be placed anywhere. They do not have to go to C:. I remember in the previous version we were asked where to store the installer files so when updating it was not necessary to download everything again.

I run all my installs from my NAS, as I'm sure many others do, this can be saved in a config file rather than forcing the use of C: exclusively. Because of this Installer file requirement I simply cannot download the full product, which basically means I can't fully utilize it. For now I've had to drop all SQL servers and all IE (except for the latest).

OK, it's my bad for only having 120GB SSD (RAID-5) drives as my C; drive, but they are expensive where I live and IMHO it should not be necessary to store Setup Source installer files on C:.

I have 18TB of NAS where I would love all installer files to go, why insist on going to C:? Source Installers do not get used that often, they should be on low cost secondary storage, not expensive front end storage...

I hope you see my point of view and future updates will take consideration of Source Installer location, ask the user where they want them like before. C: would be my last location for any installer files, they simply does not belong on C:

best regards
Seán

[FrancescoT]

Dear Seán,

I remember in the previous version we were asked where to store the installer files so when updating it was not necessary to download everything again.

This is still true ...
... you could try to install IA from command line using the OVERRIDECACHE pre-defined variable.
"Overriding the value of the OVERRIDECACHE variable allows changing the installer cache location".

This should solve your problem.

Let me know

Regards

[Seán]

I could as you say try

using the OVERRIDECACHE pre-defined variable

.

But why should I?

Isn't Installaware the best installer that can be used? That's why I purchased it for our company, a very good choice by the way . But why not just ask this simple question in the installer bootstrap?

On the machine we have it installed on we get the toolbar popup that says there is an update available for X2. We click update...we're not going anywhere near the command line, and we don't want to.

We think the best and most flexible Installer system should be able to do this one thing, Ask, remember it for future updates and just get on with it. And all without resorting to command line options etc.

I must admit, Microsoft doesn't make it easy either with its Windows/Installer folder taking up 16GB. So you're not the only one at issue on space on C:.

My simple request is add a dialog box to ask people where they would like the Installer cache location to be with a small explanation of the impact (i.e. on C:\user\AppData if default is taken). Then people can make their own decision...

Is it too much to ask for a cleaner leaner C: drive?

I appreciate your time and thoughts on this and look forward to the next update asking me where I want to place the Installer cache.

With kindest regards
Seán

[FrancescoT]

But why should I?

That's simple, it's not safe to assign such variable after any features have been defined, persistent variable values have been assigned, and so forth.
Consequently, it's more appropriate to pass it from command line.

Maybe I am wrong, but I don't believe other tools allow this kind of customization .

Regards