|
|
Right now I need for some tester to run the latest beta under WinXP. |
|
|
I would like to test, I have a Core 2 Duo E6600 on a GA-965P-DQ6. dogus at free.fr |
|
|
I liked to test, too Several Asus montherboards with E6600 and XEON 5100 |
|
|
I would also like to test this with my Core 2 Duo T7200 (Merom). |
|
|
Me too, please... I have a Core 2 Duo E6300 and Asus P5LD2 SE renierx at seznam.cz |
|
|
I can test with E6600 on a Asus P5B Deluxe ondra_novak(at)seznam(dot)cz |
|
|
I have an e6600 and a Gigabyte DQ6 running XP SP2. I wanted to mention that for the RMClock 2.2 "RC1", the author has started applying a -15C offset to the "core" temperatures - so instead of the typical 58-60 (C), I see 43-45. Since I am not using any of the control features of RMClock, it will be nice when SpeedFan is able to display the core temps (note that these are *per CPU*) in addition to the surface temp. Of course, I would be happy to test a new version - I use your betas when you offer them. |
|
|
Progress update: I seem to be very close to be able to support DTS. Right now I'm working to fix an odd issue that I discovered. Basically, it looks like my routines are working fine under Win2K, but the very same routines can't access both cores on WinXP. I need to rewrite some code that I added long ago. The odd part is that the offending instruction is RegQueryValueEx(HKEY_PERFORMANCE_DATA,'238',nil,nil,data,@len) As soon as I execute it under WinXP, I can no longer set the affinity mask, even if SetProcessAffinityMask returns success. |
|
|
Ok. I should publish a beta tomorrow. I worked for some 40 hours to fix the main issue and now it seems to be working fine. ABOROS: please, contact me by email as I would like you to test the beta before releasing it. |
|
|
ABOROS, I sent a beta to you. |
|
|
SpeedFan 4.32 beta is online! |
|
|
The new readings on my C2D e6600 seem to be reasonable - and the old stuff still works too! One thing I wanted to clear up - I mentioned in a previous entry in this thread that RMClock is going to a 15C offset - I looked at their thread again and the number is 16. Sigh. So, other than their readings being 1C below SpeedFan's... I will keep an eye on the new CPU usage display behavior. Thanks for all the work, Alfredo! :) |
|
|
I derived all the internally used offsets by reading almost every available datasheet. At present I was told that my readings are consistent with the ones from other tools. |
|
|
As I said previously, the [new] core temps on my C2D e6600 seem to be working fine. Also, the CPU usage reports appear to behave reasonably too - at least they track quite closely with the Sysinternals Process Explorer. :) OTOH, the +12/-12 voltage displays are still not working, with the +12 always showing ZERO, and the -12 always showing "-16.97V"... this is on a Gigabyte DQ6 running XP SP2. |
|
|
I have a Core 2 Duo 6300 with a Gigabyte ga-965g-ds3 motherboard. Speedfan reports the CPU temp to be beteween 38-39C, yet the Core 0: is at 50, Core 1: is at 48C. Which temperature is it detecting incorrectly? I find this a bit bizarre. |
|
|
Presumably *none* of the temps is incorrect... :) This beta of SpeedFan is reporting values from new (with C2D) sensors that are embedded in each core that are "closer to the action", and so naturally reflect higher temps. Other monitoring S/W like "RMClock" and "Core Temp" also report the values from these new sensors - but SpeedFan now shows all of your temps in one interface. |
|
|
I noticed that under 100% load environments, the internal core temperature readings on Speedfan 4.32 Beta 4 read 2-3 |
|
|
4.32 works perfect with Asus P 5 deluxe same core temps reported by everest and Core Temp 0.9 nice |
|
|
Speedfan 4.32 beta 8 gives both core temperatures with an E6600 on an MSI P965 Platinum (ICH8R chipset). Thanks Almico! |
|
|
Jonk, Please tell if you are able to see e fans using speedfan on your MSI P965 platinum .. I can't :(!!!! |
|
|
FYI: On a P5B Deluxe WiFi / C2D 6600 Speedfan 4.32 beta 8 gives me same readings as Coretemp and Intel's TAT which are assumed to be correct. |
|
|
The readings of the Core 2 Duo E4300 core temperatures are wrong, about 15C lower. (maybe wrong Tjunction/Tjmax reading???? C2D L2 rev. Tjunction/Tjmax is 100C not 85C) |
|
2007-03-18 22:18
|
sptat32.jpg (102,013 bytes) |
|
|
Alfredo, What did you do to fix the RegQueryValueEx(HKEY_PERFORMANCE_DATA,'238',nil,nil,data,@len) problem? Mike |
- Anonymous
