Thanks W1zzard.
-X-hellfire: I just remembered that there is one time when RealTemp will try to connect to the internet. Your warning would only make sense if you opened up the About... box in RealTemp and clicked on the TechPowerUp logo. That would then try to open up your default browser, Firefox, and open up the RealTemp home page at TechPowerUp. That's the only time RealTemp tries to connect to the internet and it
doesn't send your latest Visa statement or anything else to TechPowerUp. It should just open up that page and that's it.
Here's the C++ code:
Code:
// Close the About window and head to the TechPowerUp website
void CAboutDlg::OnTechbutton() '
{
ShellExecute( NULL, _T("open"), _T("http://www.techpowerup.com/realtemp/"),NULL, NULL, SW_SHOWNORMAL );
SendMessage(WM_CLOSE,0,0);
}
I'm not sure about using SendMessage to close the About dialog after someone clicks on it but it seems to work so I left it. If anyone knows a better way to accomplish the same thing then let me know. Maybe I'll eliminate the automatic closing of this window so I won't have to send any of these suspicious messages.
Now if you have a virus on your computer and it is infecting your .exe files like RealTemp then there isn't much I can do about that. If RealTemp is taking 30 seconds to start showing you temperature data then it sounds like there is something wrong with your computer. It always takes less than a second to show temp data on my computer when I start RT.
As I mentioned before, some nanny software might consider reading temperature data directly from a processor to be suspicious activity. If you push deny and RealTemp doesn't read temps anymore then you have two choices. Tell ZoneAlarm to allow RealTemp to go crazy or you can remove RealTemp and try a different solution. I use an older version of ZoneAlarm and love it. Luckily it doesn't have any of the new "Suspicious Behavior" code in it.
Your cores are numbered from 0 to 3. Core2 reading 36 is likely stuck and the other pair sitting nicely at 32 might be stuck as well but they might just need a calibration adjustment. You can't assume anything but it's certainly not unusual for 3 of your 4 cores to be stuck. All of these sensors seem to get stuck at some point. The lucky ones have processors with sensors that stick at a temperature lower than their normal operating temperature. You should do that quick Prime test I mentioned before to see if the data looks suspicious and then try running the Calibration test as outlined in the docs. My best initial guess is that core3 is probably reading too low and will need to be calibrated upward and I wouldn't do anything with core2 if it is stuck.
Originally Posted by unclewebb
Reply With Quote
Bookmarks