Have to shut down and start again....

[Ryssen]

When I start the computer I only get core temp to show up,I have set the cpu frekv,and cpu load to show up,to get them to show up to,I have to shut the program down and start it gain,then all show.
Is this a bug?

[The Coolest]

Do you mean the taskbar icons that you set in the "Systemtray" tab?
If so then this is a bug, Core Temp saves 1 one file with the settings, but when it starts automatically it loads a different file.
This problem will be fixed in the next release.
As a workaround, copy "Core Temp.ini" to your Windows\System32 folder and overwrite the existing file there. It should solve this issue with the current version.

[Correon]

i think they are hidden icons - so you have to press the arrow pointing up and mark them as not hidden icons - (correct me if i´m wrong)

[The Coolest]

The frequency and load icons are not on by default, you have to enable them from the program's settings.
But when the settings file it uses at startup is not the same where the settings were saved will cause this problem to occur.

[1tsbr0ken]

Confirming this bug still exists in 1.0 RC2.

Have set Coretemp(64) to start on Windows (7) startup, have set it to show processor frequency in system tray, in addition to highest temperature.
But upon each system restart, frequency display is missing from system tray.

Funny enough, frequency display comes back if I open the settings, and press 'cancel' without changing anything.
(did this to see if the checkmark had gone - but it was still checked)

So yeah, I'd be very happy if finally the autostart would work correctly in Win7 (it has been annoying the heck out of me for the last 6 months, to be frank!)

Nonetheless, thank you for picking up development again; aside from the buggy Win7 autostart, it's a nice, small, and helpful app!


Core i7-870 and Intel DP55KG here, btw.

[The Coolest]

Thanks for letting me know. I'll look into it again.

[1tsbr0ken]

Well...

this morning, I did a major PC cleanup run, because I'm going to install NativeInstruments Komplete 8, and I needed more free space on the system partition.
So, I uninstalled some stuff and deleted some more stuff.

After I'd finished, I did a reboot, and guess what: the frequency display came back!
I did some more restarts, and yes, it is now working as expected.

What is this - some race condition on system startup?

The stuff I uninstalled was games, 3D demos and the likes, mostly stuff one would think does not change anything regarding Windows startup.

The two things that stick out though: I applied a small Acronis TrueImage hotfix (though, for some seemingly unrelated bug), and I uninstalled Oracle's Virtualbox.
Could one of those be responsible for the changed behaviour of CoreTemp autostart? (as both of those start services on system startup)


Anyway, case closed for me, for now at least.

[The Coolest]

Just to let you know, I've tracked the bug down and fixed it. Next release should not have this problem anymore