Real Temp - New temp program for Intel Core processors

[RealTelstar]

Thanks guys for your quick testing. I just did a major upgrade of the software development kit (SDK) I'm using from 1998 to 2004. The rounded buttons look a little more this century. The transition looks very smooth so far. Just making sure that I didn't create some issue somewhere.

Randomly the app do NOT start minimized for me (vista x64) in 2,70.

[Talonman]

Looking good...

So far, no issues.

[RejZoR]

It happened to me also. It usually happens when you just log off and on, not when you do a full reboot.

[unclewebb]

Randomly the app do NOT start minimized for me (vista x64) in 2,70.

Are you using Task Scheduler in Vista? Approximately what percentage of the time doesn't it start minimized. I built some delay into RealTemp but I might need to slow it down some more for better compatibility. Try downloading the latest beta since there was a major change in the libraries, etc. that RT uses.

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

Version 2.72 has the smallest change ever. The cryptic PROCHOT# has been replaced by Thermal Status.

[gbeans99]

Hey Unc!

Just loaded up 2.71 yesterday as I was anxious to test the date/time logging. (I'm the one suggested it over @ [H] "nomad8u"). Everything works great except the log. I love the fonts and ProcHot change.

Maybe this log issue I see is by design IDK.

8/14/2008	23:18:00	49	47	46	43
8/14/2008	23:21:00	47	47	46	44
8/14/2008	23:24:00	49	46	46	43
8/14/2008	23:27:00	47	46	46	43
8/14/2008	23:30:00	45	46	44	42
23:18:00	47	47	46	43	
23:21:00	46	47	46	43	
23:24:00	47	47	46	43	
23:27:00	50	46	49	43	
23:30:00	47	46	45	43	
8/14/2008	23:33:00	47	47	46	43
8/14/2008	23:36:00	50	46	47	43
8/14/2008	23:39:00	49	47	46	43
8/14/2008	23:42:00	49	47	46	44
8/14/2008	23:45:00	47	46	46	43
23:33:00	47	47	46	43	
23:36:00	49	46	46	44	
23:39:00	50	47	47	43	
23:42:00	49	47	46	43	
23:45:00	50	47	47	43	
8/14/2008	23:48:00	49	47	46	44
8/14/2008	23:51:00	49	46	46	43
8/14/2008	23:54:00	47	47	46	43
8/14/2008	23:57:00	47	47	46	44
8/15/2008	0:00:00	46	46	42	42
23:48:00	49	47	46	44	
23:51:00	49	46	46	44	
23:54:00	46	47	46	43	
23:57:00	49	47	46	43	
0:00:00	46	46	42	42	
8/15/2008	0:00:00	47	46	45	43
0:00:00	49	47	46	43

This is how it's logging for me. It looks to be doing 5 date/time logs (set for 180 sec) and then re-logs the same data using just time? I just copied the last several entries out of the log. I shut down Rt and renamed the log and restarted it. It is doing the same thin on this go around.

Other than that it's looking good! Thought I'd jump over here and post this after you're agg with posting links and crap over there. Sorry to see you had issues with the forum there. I do appreciate you stopping by there though and answering questions...

Cheers,
gbeans99
nomad8u

[unclewebb]

gbeans99: Thanks for bringing that to my attention. Is it possible that you were running both version 2.70 and 2.71 at the same time in the same directory? If they were both running from the same directory and logging to the same file then your log file would look like a mess!

I'll go have a look at the code for this to see if I can find a problem on my side.

[RejZoR]

This app is really shaping well. What about "More" or "More..." text on button next to the CPU frequency?

Also it happened quiet few times that both core trey icons were split apart by some other icon. Is there any possibility to always force them together when using 2 or more cores? It's a very minor thing but may bother some (like me :P ).

[unclewebb]

RejZoR: The way I look at it, anyone that is computer literate enough to be interested in the core temperature of their processor is not going to be too scared to go and give that little button in the top right corner of RealTemp a poke to see what happens. Especially if they've seen a screen shot or two with other information being displayed there. At your suggestion, I made it a little bigger and I think it looks great and is reasonably intuitive. No long term users of RealTemp have ever approached me and said, "Well holy s-h-i-t, I had no idea what that little button did." I like the present cleaned up look.

I've also noticed when booting up that the System Tray icons can get spread apart but that's more of a Windows / multi core processor issue / bug. The only thing I can think of doing with RealTemp is put in a user selectable delay feature so their system would have more time to boot up before RealTemp tried to add its system tray temperature icons.

A quick fix is to open up RealTemp when this happens, click on the Settings button and then cycle one of your displayed cores off and back on to get the tray icons lined up properly. You could also go get a nice new Quad core processor. Throwing money at a problem is always a good idea.

Can you not use Task Scheduler to add a small amount of delay before RealTemp starts or can it not be adjusted to a small enough amount of delay time?

gbeans99: I did a similar test to yours where I had the logging feature at 180 seconds / 3 minutes and my log looks fine. The date is on each line as it is supposed to be now.

08/14/08 23:27:00 35 35 35 35
08/14/08 23:30:00 36 36 36 36
08/14/08 23:33:00 36 36 36 35
08/14/08 23:36:00 36 36 36 35
08/14/08 23:39:00 36 36 36 36
08/14/08 23:42:00 36 36 36 36
08/14/08 23:45:00 36 36 36 36
08/14/08 23:48:00 36 36 36 35
08/14/08 23:51:00 36 36 36 36
08/14/08 23:54:00 36 36 36 35
08/14/08 23:57:00 36 36 36 35
08/15/08 00:00:00 36 36 36 35
08/15/08 00:03:00 36 36 36 36
08/15/08 00:06:00 36 36 36 37
08/15/08 00:09:00 36 36 36 36
08/15/08 00:12:00 36 36 36 36
08/15/08 00:15:00 36 36 36 36

Always wanted an excuse to use those code tags!

You can see that a person really needs a Quad core processor to surf the net. Core3 touched like 37C.

[RejZoR]

Well i still think "More..." text on that button would look nicer than button without anything... Or even maybe minimalistic "->" or ">" arrow. Empty buttons just look weird. Always.

[nuclearjock]

unclewebb,

Just saw This on anandtech. So by the 18th, we'll know TjMax for sure???

[RealTelstar]

Are you using Task Scheduler in Vista? Approximately what percentage of the time doesn't it start minimized. I built some delay into RealTemp but I might need to slow it down some more for better compatibility. Try downloading the latest beta since there was a major change in the libraries, etc. that RT uses.

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

Version 2.72 has the smallest change ever. The cryptic PROCHOT# has been replaced by Thermal Status.

No, always in startup folder.
I tried to download 2.71 but the zip was the old one.

OK i got 2.72 now

[JohnLoph]

I try to read 11 of 79 pages (very tried >_<")
but i can't find the answer that the E8400's tjmax is 95'C or 105'C

anyone can confirm that?

sry, for newbie question

and THANK YOU for your answer

[jas420221]

95c

[unclewebb]

I guess we'll find out next week what TjMax really is when Intel finally comes clean. It's very interesting that they plan to use RealTemp in their presentation to finally explain everything there is to know about these sensors.

Is RealTemp right or is RealTemp out to lunch?
The anticipation is killing me!

Here's my E8400 TjMax test:
http://www.xtremesystems.org/forums/...&postcount=573

RealTelstar: If you're using Vista it seems that Task Scheduler works best.

[skinnee]

Let us know the outcome of their preso, good or bad!

[loonym]

Either way it's great that you've brought this type of attention. Great work

looking good on vista in this shot.

[BeastNotro]

I can't for the life of me figure out all those steps to calibrate the idle.

Can anyone simplify it.

[WoZZeR999]

Undervolt vcore as low as it will go, underclock FSB to 266, change multi to 6x. Boot windows, turn fan to max speed. Get ambient temp around the cpu (or the fins if you can). Adjust calibration for cores so that they are around 6-7C above the ambient temp.

[unclewebb]

loonym: That's how I see it. If it wasn't for RealTemp pushing this subject we might not have ever found out.

BeastNotro: You might want to attend the IDF. I heard they might be bringing that subject up there.

[BeastNotro]

Where is it at Unclewebb?

Also ...... i ain't lower my stable OC clock and all that ... to get idle calibration .... Idle between cores are this 32-31-27-29 ... so it ain't that far off..

There must be a away to do so with OC idle.

Sure i can offset it to match my lowest idle core, but would that be correct?

[WoZZeR999]

Does the P5Q allow OC profiles? My P5K when I still had it allowed OC profiles. You can save your profile, and then undervolt. Calibrate and load OC profile.

[BeastNotro]

Yeah it has 2 spots for such a thing, but i don't like loading back from profiles as before i tried that and my RIG seemed to run slower, chuggier.

I may try it, but we will see as like i said it is not that far off .. my room temp is around 24C... so if you look at what my OC idle temps were in my above post .. they are like 5-6C above room temp.

So can calibration be done on OC idle temps ..... question is ... why not?

[JohnLoph]

95c

I guess we'll find out next week what TjMax really is when Intel finally comes clean. It's very interesting that they plan to use RealTemp in their presentation to finally explain everything there is to know about these sensors.

Is RealTemp right or is RealTemp out to lunch?
The anticipation is killing me!

Here's my E8400 TjMax test:
http://www.xtremesystems.org/forums/...&postcount=573

RealTelstar: If you're using Vista it seems that Task Scheduler works best.

Great THANK, that very useful. I will look forward to next week

[unclewebb]

The reason I recommend low MHz and low voltage is so users have a common baseline to the testing I've done. There are so many variables including things like case air flow that it's very difficult to say what your core temperature is when you are overclocked by just looking at your idle numbers. For me going into the bios and turning on C1E so the multi drops to 6.0 at idle and setting the MHz and core voltage to the lowest amount is not a big deal. I don't have to play with any of the other settings and it's easy to re-boot and go back to my overclocked settings later on.

If you want the easy way then take your previous idle temps and equalize them to about 32C or 34C with the case open and you'll probably be pretty close.

Intel IDF is in San Francisco. I haven't received my invitation yet to ride down on the company jet!

[gbeans99]

gbeans99: I did a similar test to yours where I had the logging feature at 180 seconds / 3 minutes and my log looks fine. The date is on each line as it is supposed to be now.

Always wanted an excuse to use those code tags!

Hey Unc!

Thought I'd finally report back. Sorry it took so long but I'm in the middle of a 6 out of 7 day work week and 13 hr days just don't leave me enough time to keep up with the folding farm and figure out what I fraked up trying to beta software.

I'm gonna have to chalk this one up to user error LOL... The way I did the "drop in" upgrade was to stop/kill 2.60, rename the exe and unzip the new files in the working directory. I fired up 2.71 and did my folding @ home updates and then checked my logs before I posted. My guess is what happened (I think you were right on the mark) was that with all four cores folding, the processor didn't give up the 2.60 version when I stopped it before I got the 2.71 version restarted. Probably 2 minutes elapsed between me stopping/renaming 2.60 and restarting 2.71.

Either way, the log today looks all good, so I hope you didn't spend much time looking for my "ghost" user induced problem...

Yeah.. code tags are . Takes up a lot less room on the page.

Lovin the new version!

gbeans99