ALCPU Forums

Iks there a way to delay the sidebar core temp gadget from starting until the running taks has completed it's initialization process? It seems our gadget initializes faster than the 'feeder' task causing an error message on the gadget itself. Error is "unable to obtain clock..." Seems like a race condition of sorts.

thx

Hello,

You could try using Soluto - http://www.soluto.com/, you can set phases for when things will start up, and also speed up your Windows desktop boot times!

Triton,

I'm not quite sure what you are talking about.
Which gadget?
Where do you see "unable to obtain clock"?

To be more clear -

When the PC boots the sidebar gadget that actually displays the core temps initializes with the following message: "Unable to get value of clock". I know the core temp service process is functioning as the are temps displayed in the taskbar. So I'm assuming the 'display' gadget initializes prior to the running service and a race condition exits. I have proved this to be the case by delaying the start-up of the actual sidebar by 10 seconds using "start-up delayer" (a program that can delay application start times). It works every time when I add that delay. Problem with that solution is windows insists on replacing the sidebar to autorun after every reboot negating the delay we have added. I'm working on that solution as well.

Heliosicle

Thanks for the suggestion. I have "Startup Delayer' installed to test this whole thing out.
http://www.r2.com.au

It works great and is easy to use. But as I noted in another post Windows will overwrite the 'delayed' entry with a new sidebar entry - negating (after the first reboot) the delayed entry. So one might think taking the sidebar entry out of the 'run' line using msconfig would do the trick??? Apparently windows shoves it right back as a start-up service. We're working that as well. I'm sure a little digging might provide a solution.

Problem Solved - enabling core temp to "start with Windows" has the display gadget wait for the process to start w/o displaying an error message.. I was running core temp in the start-up folder.

Glad to hear that you got it sorted out