ALCPU Forums

I dl the program by itself with out the installer. Seems like a great little program btw. When I select the box start core temp when windows starts. Nothing happens. I even rebooted. I am using a limited account under windows 7 for security purposes. Could that be the problem? If so. How can I get it to start up under my limited account?

The answer is in the FAQ.
It is impossible to auto-start Core Temp on a limited account.

Thank you. That is a real bummer.

Well there is one way, but you'd have to enter the administrator password each time manually.
You have to go to task manager, double click on the Core Temp Autostart task and change the user under security options to the "Users" group.
This way Core Temp will start up automatically for each account on the system (except Guest) but limited users would have to enter the admin password for Core Temp to start.

Can you set it like that to just 1 user limited account? Or does it have to be for all?

You can, you need to dig some into the Triggers tab.

I don't know how limited your account is, but I managed to get Core Temp running in my regular W7 64-bit Pro install with the help of this site:

http://blogs.techrepublic.com.com/windo ... l;post-635

Basically you go to Task Scheduler, create a new task to "run with highest privileges", make it start at logon, and point its way to the CoreTemp.exe.
It managed to solve some other software startup trouble I had. Though I'm new to the Windows 7 thingies, there might still be some checkbox somewhere that would have solved it in one click.

In the latest Core Temp version simply checking start with windows box does the same already, but in non-administrator users it doesn't work.

What a pita to go through all of that. Not the programs fault though. I wish there was a simple and easy way around it. Think I will just dl the standalone 64 bit version and run it manually every time.

hi guys, got a similar problem on W7/64. I first installed coretemp, set it to start with windows, and it worked. For some reason unrelated here I had to create a new Windows account, and since then, coretemp refuses to start with Windows, even with a shortcut pasted in startup/all users. I even uninstalled and reinstalled coretemp and there's no change.The old account was an admin account and the new one too. Thanks.

Go to Scheduled Tasks and delete Core Temp Autostart task from there.
Then enable "Start with Windows" again from the settings.
This solution apparently works on a per account basis. In a later version, Core Temp will create a task with the name of the account, that way, each user can separately configure whether he wants Core Temp to startup automatically or not

The Coolest wrote:Go to Scheduled Tasks and delete Core Temp Autostart task from there.
Then enable "Start with Windows" again from the settings.
This solution apparently works on a per account basis. In a later version, Core Temp will create a task with the name of the account, that way, each user can separately configure whether he wants Core Temp to startup automatically or not

okay thanks I will try this and report back

alright worked fantastic, unchecked "start with Windows", deleted the task manually, reactivated the setting in coretemp which recreated the task, rebooted and it just worked. Thanks again

ps: and yes I see now in the task details that it works on a per account basis.

Wouldnt a service solve the problem?
Why not detacthing the core from GUI, make the core a service and the GUI could access it from anywhere? That way, permissions can be given to a "normal" user to start up a given service and solve all user privileges issues while the service itself able access the underlying hardware.

A service would solve that issue, but it will make the application much more complex, and less flexible. Right now you can just run the exe from just about anywhere and it will work.

Then why not installing the driver permanently instead of loading it at runtime every time? Because the problem is the OpenSCManager, whose generated handle according to MSDN can only be called by Administrator users to create a new service.
If the driver service was installed permanently then "normal" user can gain start_stop rights by the use of SetACL.

EDIT: Or at least give the option to install it permanently.

There are a few additional parts of code that require admin rights, so installing the drivers permanently would still not do the trick.

If I may disagree, I dont know the code you are talking about but here is proof that it can be done.

Loading coretemp as admin, let it startup the driver, "crash" coretemp so it wont unload it, start coretemp as normal user, it will start no problem.

Notice in the image below, DeviceTree started as admin that shows that the driver stayed (coz I "crashed" the software so it wouldnt unload)
then i started coretemp as my normal user and it works, even the gadgets work.

EDIT open the image link in another page to see the whole pic

I managed to workaround by copying driver to a different location and using the Osr Driver Loader to create an ALsysIO automatic load driver entry from that position. Rebooted and set coretemp to startup from Automatic startup menu of my limited user account and it works flawlessy. Obviously starting coretemp as admin after applying the workaround breaks the workaround as it reset the ALsysIO driver entry in the registry.

The driver is not the only thing in Core Temp that requires admin rights. There are some other parts of code, designed to maintain system stability and accuracy of the application when used in conjunction with other monitoring software.
So the solution of separating the driver and installing it permanently won't solve this issue.
The only real solution will probably be to run Core Temp as a service, which at this point is not the way I want to go with.

Well, you wrote the code so you know, but for the purpose of running the basic coretemp on a limited user account and interact with the gadgets this is more than enough. Who is going to overclock from a limited user account anyway?

Hrulgios wrote:I don't know how limited your account is, but I managed to get Core Temp running in my regular W7 64-bit Pro install with the help of this site:

http://blogs.techrepublic.com.com/windo ... l;post-635

Basically you go to Task Scheduler, create a new task to "run with highest privileges", make it start at logon, and point its way to the CoreTemp.exe.
It managed to solve some other software startup trouble I had. Though I'm new to the Windows 7 thingies, there might still be some checkbox somewhere that would have solved it in one click.

If you set "Start Core Temp with Windows" in the options, there is already a task to run it at login. You can see the properties of this task by typing:

schtasks | find /i "core temp"

in a command window created with Administrator privileges. The description will look like:

Core Temp Autostart <username> N/A Running

You can modify this task to run at the highest account privilege by typing:

schtasks /change /tn "Core Temp Autostart <username>" /rl highest

This ensures that Core Temp will start with Windows on an account with Administrator privileges. It would be nice if a future release set the run level automatically when creating the task.