|
MARTINK "No one needs to fry anything here. Be sure to check out:..." Yes, I did. Still, 2 words of caution: - values that have reportedly worked for others may NOT work for you. I've found a report about a Tibook 400Mhz like mine going OK at 140 percent CPU speed (using ATIcc 102). The same type of machine sitting on my desktop freaks out at speeds higher than 121,43 percent (127,50 Mhz). When I had set ATIcc CPU value to 140 percent, then right after restart the CPU value showed minus!100 percent, and the respective value in the plist was something in a galactical range that I've simply forgotten it by now. So maybe it's been me stretching things too far. Yet by now I believe that it also might be a problem at least with the current version of ATIcc that it may not always calculate and/or write proper settings to its preference file. -- See also next word of caution... - While YOU may be cautious about setting the values, ATIcc may not always, at least not the current version. Couple of days ago I've ATIcc'ed an iMac (with Range 128 Pro) using fairly conservative values and without any further experimenting. The machine worked well every day since until this morningafter auto-start it sat there with screen looking like a piece of some sort of computer science art. And again, ATIcc's CPU value stood at minus100 percent and the respective value in the plist file is way higher than I had set it. And I can just *guarantee* that between yesterday and today *no one* has changed *any* system related prefs incl ATIcc's settings. I cannot see it other than that out of the clear blue, ATIcc has messed up it's own pref file. I love this program. It definitely speeds OS-X on aging machines. It's worth trying it, and I'll even keep using it. By the same token, it also deserves more hard work to improve it's engineering in addition to all the hard work that may have already gone into it. My2cents. (Version 1.0.6) |