Support for Sandy Bridge CPUs.
VID based power consumption estimates for the newer CPUs.
Improved log file formatting.
Added a single system tray icon that reports the maximum core temperature.
RealTemp GT updated for the 6 core Sandy Bridge E CPUs.
i7 Turbo GT 1.30 multiplier monitoring tool.
Download Real Temp 3.70 | techPowerUp
A Guy
There seem to be an issue with running this software automatically via task scheduler in Windows 7 in my case, and I hope that someone can help me out here.
Situation:
• Windows7 set up with an admin account (password protected) + a non admin user account (password protected)
• On boot, my computer is set to boot directly into the non-admin user account automatically without prompting for any password (as expected)
Task scheduler setup (non admin user account)
• Create basic task
• Trigger, When I log on
• Action, Start a program
• D:\Software\RealTemp_370\RealTemp.exe
• Finish
And then..
• Switch to the admin account
• Edit the new task in Task scheduler
• Enable the ticker for "run with highest privileges"
• Voila
• Reboot
But then..
• Machine boots into the non admin user account as expected, but user is then prompted with the admin password to start Real Temp
• Shake fist at screen
So the issue for me is really that the promp for my admin password on login (non admin user account) is annoying and I wish there was a way to not have Windows prompt for it on every log in.
If there is a sensible solution to my problem then somebody might know about it, or if there is a certain limitation I hope this information will help me as well.
Additional info: The OS is located on C: while the executable for Real Temp is located on a different harddrive as indicated above.
Could my issue with all of this be related to lack of rights for running batch files somehow?
Last edited by Decoman; 27 Jan 2012 at 15:15.
Have you tried setting run whether logged on or not while in the adminsistrator account?
Under the General Tab near the bottom.
I see it.
Somehow I now had to create the task with the admin account and then change the useraccount name to that other account name in "properties" for that task.
If I use the option "run whether logged on or not" while having changed the user account in the properties, I am not allowed to continue. What happens is that I am immediately prompted for the password of that other non-admin account, but entering this leads to an error stating that such an account does not have "batch job rights".
Hm, not 100% sure that I did things correctly. Maybe someone could try this out for themselves and see if they can get it to work, given that they a) use windows 7, b) autolog into non-admin account on boot.
Quote