http://www.fileden.com/files/2008/3/...alTempBeta.zip

I've added the ability to run a file when the RealTemp alarm is triggered.

I haven't decided yet if I'm going to add a file picker into the Settings GUI or keep it hidden. At the moment you can try this feature out by adding a new line to the RealTemp.INI configuration settings file like this:

AlarmFile="C:\Program Files\IrfanView\i_view32.exe"

You can probably think of something better than running IrfanView when you're computer is getting ready to go nuclear!

The AlarmFile will only be run once when an alarm occurs. If you want RealTemp to run it again then you'll have to restart RealTemp. A person could also write a .bat file for an orderly shut down or whatever they want their computer to do during a high temp alarm. Any suggestions about improvements or additional options for this feature are appreciated.

I'm in the middle of adjusting the Start Minimized feature in RealTemp for better Vista x64 compatibility. If that part of RealTemp 2.78 is working worse than before in Vista then don't be surprised. It's a work in progress. If I can't make it better then I'll at least go back to the old way. Version 2.78 is for users that want the AlarmFile feature right NOW!

genec57: I know a little bit about sticking core digital thermal sensors but my experience with a sticking CPU sensor is the same as yours. Zilch!

With any sensor, if you know it is sticking, even sometimes, then you can't rely on it to give you accurate and usable information below that sticking point. The Intel on chip sensors are consistent and usually fine when the temperature goes above the "bottoming out" point.

Same goes for you radaja. The RealTemp calibration feature is not designed to give you usable information out of a stuck sensor. If the sensor isn't moving at low temps then low temperature information coming from this sensor is useless.

I might be able to understand your situation better if you send me some data. Turn on the RealTemp logging feature and set the interval to 1 second. Let your computer sit idle for a minute, then run Prime95 small FFTs for about 2 minutes and then stop that and return your computer to idle for a minute. Take the log file and either e-mail it to me at the address in the About... box of RealTemp or copy and PM it to me here at XS. I can't guarantee you any miracles but I've seen enough messed up data that I might be able to help.