3.1.0 Installation error

posted on March 21st, 2010, 4:05 pm

Hi folks,
when trying to install 3.1.0 to drive d:, where free space is absolutely sufficient, the installer stops with an error due to drive c: running out of space. Obviously the Nullsoft Installer caches installation data on drive c:. Is there any possibility to change this ?
I do not want to workaround this by expanding drive c:.
Operation System is WinXP x64 SP2.

Thanks for any hints.

posted on March 21st, 2010, 4:25 pm

easy option: clean out space on drive c

harder option: make a virtual machine on free space in drive d. intsall fleetops inside that virtual machine, then copy the installation directory back out to the host computer. i think this will work, i dont think fleetops requires registry entries, so moving an installed director from one "computer" to another should be fine.

EDIT: i just checked that fleet ops installs reg data, but i dont know how it uses it, you can try it anyway and see if it works, it wont hurt your comp.

posted on March 21st, 2010, 4:37 pm

easy option: clean out space on drive c

harder option: make a virtual machine on free space in drive d. intsall fleetops inside that virtual machine, then copy the installation directory back out to the host computer. i think this will work, i dont think fleetops requires registry entries, so moving an installed director from one "computer" to another should be fine.

This will work, but I consider it's a huge amount of effort and another workaround.

EDIT: i just checked that fleet ops installs reg data, but i dont know how it uses it, you can try it anyway and see if it works, it wont hurt your comp.

FleetOps does indeed write registration data, but after the installation. Thus they won't influence the caching issue due to the Nullsoft Installer.

Preferred Solution: Turning off Caching in the Nullsoft Installer. Any way to do so ?

Nevertheless thanks for advise, myleswolfers !

posted on March 21st, 2010, 4:47 pm

i wasnt worried about the reg data affecting the install, i was worried about the reg data preventing just copying the install dir over. 

i dont know if the nullsoft installer is easy to configure like that

[DOCa Cola]

posted on March 23rd, 2010, 12:51 pm

Last edited by DOCa Cola on March 23rd, 2010, 12:56 pm, edited 1 time in total.

a command line option for the nsis installer to change the location of it's temporary directory does not exist. the best way really would be to free space on your system drive. i assume it is not the first time you get a problem with an installer because of this or atleast it won't be the last time.
if you really have no other choice then you may have luck by using sandboxie for example. with it you could 'sandbox' the installer and let it 'think' that your windows temporary directory is in another location. should be possible with sandboxie though i haven't tried that.
again, freeing up space on your system drive should be clearly the better alternative

posted on March 23rd, 2010, 4:50 pm

If D: has plenty of space, why not just uninstall 1 or 2 things from C: and reinstall onto D:  Shouldn't be too hard to free up a few hundred MBs.