*coughs LOUD* Geez guys, haven't you figured it out yet?<font face="Verdana, Arial" size="2">Originally posted by Prey521:
CPUIdle works with Win2K. I'm about to run down to the corner and buy some, *cough* crack *cough*
</font>
[edit: damn, I'm blind, freckmoto knew it]IT'S FRIGGIN' INCLUDED IN WIN2K!!!
What that program does (like EVERY OTHER sort of program that tries to cool your CPU by the way) is issuing the so called "HLT" commands to those parts of the CPU which aren't in use. Instead of those parts running an idle cycle, no energy will flow through them. No energy=no heat. Win2k automatically issues the HLT command instead of running idle-cycles by default. That's why you don't NEED such a proggy under Win2k. To my knowledge, it was also included in NT4 (but you had to turn it on, I think).
One more reason why Win2k rocks!
If you use 100% CPU power, the program won't do anything. Since there are no idle parts to cut the power off of. But what it can do is reduce the temperature (really fast too) when you're not using 100% CPU power. Try running CPUidle together with SETI@home, and you won't see a noticable difference. Why? Because SETI@home takes all the idle processes and uses them for itself.
If you don't believe me, get a mobomonitor that graphs the temperature, set it to update every 5 seconds, play two levels of Q3, and then look at the graph. While you were playing it was at about the normal temperature, where you'd be without Win2k/rain/cpuidle/whatever. But as soon as you stopped playing, the temperature drops really fast. Then when it's nice and cool, turn on SETI@home. Back to about max. temperature.
Cheers,
Ronald
[This message has been edited by SeedOfChaos (edited 01-16-2001).]
