KSP 0.9 startup requests all hardrives in system to awake from sleep

[perk]

- I have a couple of older harddrives for data storage in my system.

- KSP 0.9 is downloaded and unzipped into a folder on my primary ssd.

- System is a 64 bit Windows 7

- In usual operation of my system all my harddrives are idle and not moving. When i start KSP they all start up spinning, which (due to their age) takes a while, and not only prolongs the starting process of KSP unneccessarily (as it waits until all hdds are spun up) but it also puts strain on those drives i don't want.

So my questions are: is that call from KSP to the operating system, that causes the spin up of all hard drives, really necessary for the way the startup process is currently coded or can you change it?

[vexx32]

Hard to say... where's KSP installed to, exactly?

[sal_vager]

Not heard of this one before, it may be a Unity3D thing but even so, it seems very strange, as Vxx says it'd help to know where you have KSP installed and it'd also help to see your logs, the sticky threads have info on where to find these and how to post the contents

[perk]

It is not really installed, it came as a zip package from the site, i unzipped it to C:\Program Files (x86)\ksp0.9

so the executable resides in C:\Program Files (x86)\ksp0.9\KSP_win

the output_log: https://www.dropbox.com/s/frayixg13qjhoh2/output_log.txt

as you can see nothing in that log happens on any other partition let alone harddrive than C:\, still it always starts them all :/

[Technical Ben]

Not heard of this one before, it may be a Unity3D thing but even so, it seems very strange, as Vxx says it'd help to know where you have KSP installed and it'd also help to see your logs, the sticky threads have info on where to find these and how to post the contents

I get it with all sorts of things. Sometimes the (mainly never used) DVD drive kicks into life, it's usually a program being opened somewhere.

[vexx32]

Having KSP under Program Files like that can produce some unwanted results, as Windows may at times deny it read/write access to its own directory, because it lacks the registry entries most installed programs will create when placing files into the Program Files folder(s). I've not heard of it producing this exact problem before, but it's not unlikely to be the cause.

I'd recommend unzipping a new copy to C:\KSP and running that; see if that causes the same issue.