I
il barbi
I have an external HD (Western Digital My Book 1 terabyte) connected via
firewire, following its specifications after 10' of inactivity it must enter
standby status by stopping rotation, in the contrary often I realize it goes
on spinning even if I don't access it and surely it becomes more and more
hot. WD says it never will be a damage and the 10' timeout has been foreseen
not to avoid overheating, but to save energy.
Now I carried out some tests with Filemon utility and rather surprisingly
saw a "Query information" command is issued to My Book when I open a
directory on my INTERNAL HD, so since I often work with explorer.exe the 10'
timeout will never expire.
I reported this to WD which obviously said at this point the fault was not
of themselves.
Now this is unsatisfactory and I can't understand why Windows behaves this
way, I just think this is a misbehaviour
any ideas?
il barbi
firewire, following its specifications after 10' of inactivity it must enter
standby status by stopping rotation, in the contrary often I realize it goes
on spinning even if I don't access it and surely it becomes more and more
hot. WD says it never will be a damage and the 10' timeout has been foreseen
not to avoid overheating, but to save energy.
Now I carried out some tests with Filemon utility and rather surprisingly
saw a "Query information" command is issued to My Book when I open a
directory on my INTERNAL HD, so since I often work with explorer.exe the 10'
timeout will never expire.
I reported this to WD which obviously said at this point the fault was not
of themselves.
Now this is unsatisfactory and I can't understand why Windows behaves this
way, I just think this is a misbehaviour
any ideas?
il barbi