Oh...before i forget..this program requires you to have ACPICPUThrottle.kext (writtin by Niall Douglas) installed and working on your system. Grab a copy from his website: http://www.nedprod.c...CPICPUThrottle/
and please make sure to follow all instructions to get the kext working! I will not be supporting people with problems loading the kext...since i think Niall has that quite covered.
Lastly, I wanted to thank all the people who have made this project possible. It started with keithpk posting a information gathering thread. phb then took over the reigns with a enhancedspeedstep.kext. And finally, thanks to Niall for getting the ACPI throttling to work. This app would be absolutly useless (I probably never would have even thought to make it) without these three guys. And i wanted to thank Mashugly for setting up this great community and these new X-Labs! SO, THANKS KEITHPK, PHB, NIALL, and MASH! you guys rock....'nuff said.
EDIT: WORKAROUND FOR AUTHORIZATION TIMEOUT
currently, CPUThrottler2 prompts you for your password every 5 minutes...this is a security feature of osx and i am working on finding a more elegant work around. However, until I do, the following instructions will fix this problem...
1. navigate to /etc "cd /etc"
2. open the file authorization with a text editor(i use nano): "sudo nano authorization"
3. scroll down until you see the following rule:
<string>Used by AuthorizationExecuteWithPrivileges(...)
AuthorizationExecuteWithPrivileges is used by programs requesting
to run a tool as root (ie. some installers).
Credentials remain valid 5 minutes after they've been obtained.
An acquired credential isn't shared with other clients.
Clients running as root will be granted this right automatically.
4.Delete the following
5. Save and exit....CPUThrottler2 should no longer prompt you for your password every 5 minutes.
I realize this is not a very elegant way of doing things. As long as you do not mess around with any other values in the authorization file you should not have any problems, but I dont assume any risk. By deleting the timeout value you are essentially setting the timeout to infinity. I hope this helps...im honestly tired of looking at authorization code, so I am going to concentrate on the NSStatusItem for the moment and put this on the backburner. If anyone has any experience with creating rights in the policy database, please contact me. Hope this helps some people out....