OK, I did a little bit of experimentation for several hours today, here is what I found:
1.) The Fan, at the lowest possible power usage of the CPU @ 800MHz, comes on around 44-46 Degrees. This doesn't seem to be rate dependent.
2.)The Fan spool up rate depends on the rate of increase of temperature. If there is a large increase, around 0.3~0.5 Degrees/Second, it seemsas if the Fan spools up to Maximum, then comes down...for what I can hear, 5 different levels. It can stay here for awhile, sometimes, I get mine to turn off
by switching to a *perfectly identical* minimal setting...I.e. Ultra Battery Life 1 and Ultra Battery Life 2...the Fan will spool up a bit, then spin down to its off state. This is when it came down from 45 Degrees, but I have done the same thing at higher temperatures. Also, NHC should pop up a ballon window telling you that a power management profile has changed. As far as I have done this, it always shuts the fan off for 30~45 Minutes and can be repeated. For me, the fan being off is not much different from Level 1 or 2, but lasts, at maximum, for one hour. This does indeed imply that the fan can be indirectly and temporarily controlled by use of the Power Manager and NHC. Also, if you pay close attention in the Power Manager, you will see that the Fan cannot go below two "Green Bars" as it were. These bars jibe with the levels of noise I can pick out of the Fan when it cycles through RPMs.
3.) You can plug into AC Power, then off, to reinitialize the system...as long as it stays on the same power manager profile.
Theoretically, it should be possible to write a little program/script that updates the registry values associated with the Power Manager...As these seem to be the only things that change when I viewed them before and after with the Administrative Tools and Regedit. I don't know how difficult that would be, but from all my programming experience, it isn't too difficult at all to update the registry. The only Problem here is, for it to be fully automated, it requires some input as to what the temperature is so it can compare it to the user set thresholds that the user had entered into a little config file for the program beforehand. I assume that, since NHC can get the temperature via the Microsoft .NET Framework, this little program can too. If that proves to be too difficult, it could always be on a little timer that the user, again, configures in a little file for the program telling it at what times it should "Cycle" the Registry Entries. Just a thought; tell me what you think
