Terc

I'm actually overclocked (but not as much as my sig shows - I added more RAM - filled the slots, and we all know what that does to core2 quads). Anyhow, I just clocked back down to stock settings with 1.13vcore and I now have a delta between my heatsink and cores of 20C (reporting 57C for 3/4 cores and 37C for cpu at idle). It's clear that the Tjmax is 10 or 15C lower, and I'm just trying to find out how to change it in the kext. Even if I'm wrong, couldn't someone else want to do this? Also, I had the vdroop fix enabled in bios when I took that screenshot. I'm quite familiar with core2 architecture and I am totally comfortable with the voltages I use for overclocking. You're right though, that sure would be a lot to run at stock speeds. Not to get off topic, but what CPU are you running? I'd love to hit 4Ghz stable on this chip, but it's just not going to happen. 3.92 was great though (while I was water cooled). Nowdays, I'm totally happy with 3.6, it's more than enough for the work I do. And the extra 400Mhz per core doesn't make a huge difference in encoding or virtualization. For anyone just joining this thread, oldnapalm posted earlier that you should head over to http://redirectingat.com/?id=292X457&x...8081%26st%3D160 for new updates on this project.

Erm... Looking at those charts, I don't know if the Q8000 and Q9000 series blanket applies to my chip. (it's a 45nm quad core core2 based chip) and has been discontinued (possibly before the release of those charts). I can tell you that I'm not at 67C when idle. I have a good heatsink and I'm certain it's seated properly. Under the 45nm Xeon quad cores, you'll see that the X54xx series is listed as 85C. The xeon equivalent of the Q9450 is the E5430, so my 85C Tjmax makes a lot of sense I think. Here's a screen of everything working - while my system is under load (doing a Handbreak encode) http://cl.ly/8e88afc78358d3cb1b2d The heatsink (tjunction) is reported as 58C (This seems accurate and believable for a full load with my cooling equipment) But those per core temps.... I'd think I would have some stability issues. But here I am, typing away with no problems at all while the encode continues. Anyhow, does it really matter? I set 85 and there was no difference in reported temps. I'd just like to know how to change my Tjmax setting with this set of kexts, what I attempted doesn't seem to work.

First off, this is some great work! I love having all the extra info. Here's my problem though. I use a Q9450, which has a TJmax of 85. The TJmax setting was moved from the FakeSMC plist. I _think_ I found the new location (inside the plugins folder, in FakeSMCIntelThermal.kext) However, when I modified this plist and rebooted, I still see the same high temps. Here's a screenshot with VoodooMonitor using the Tjmax override option in the preferences (I know it says CPU-i Preferences, it's still VoodooMonitor though). Anyway, is it possible that the Tjmax value is not being read properly yet? I'm guessing it's just not included in this version since the default value was 0. http://cl.ly/b67c214cd71a3ee22d11 If it's just a work in progress, no worries! I'd really like to see the ability to fix this though, seeing 61C in my menu bar is a little unsettling. I can deal with it for now though, just wanted to confirm I'm not missing something. I'd like to post this over at projectosx, but for some reason it's saying I don't have permission to reply to that topic... Edit: Hey! I just noticed we've both been around here since '05 How's it going old timer?

First off, it's working great. Thanks for a job well done. But, I'm wondering if I could get my Core Duo (not Core 2 Duo) reported properly. What number would I use? Core Duos were used in at least the first Intel Mac Mini (I actually own one, so if you need me to check something on that computer to determine how to properly report Core Duo processors, I would be glad to)

I've done the update on my UD3P board... all is well except sound. I should have that up and running tonight. My guess - the driver version is now higher, so the one in Extra is getting overwritten by the new one in S/L/E.

Anyone care to post a diff? Maybe just a diff for the kexts (lists all modified kexts) ?

Windows or Linux!

STOP USING iPC!! For that matter, stop using any modified "distro" (pre-hacked iso of OSX). Almost all the noobs that come around asking for help need it because they've used a torrented iso and now can't figure out why ____ doesn't work after the latest update. Just go buy retail, and install using a boot cd to load up your extensions before loading the install dvd. There are tutorials all over for how to do this. If you still think that pirating some pre-hacked disk is the best way to do this, then go for it. But polluting helpful threads like this one with what power supply you have that kinda sorta works with whatever torrent you last downloaded, and how many things are not working yet, and what quirks you're still going to have to work out is a waste of everyone's time. So STOP!

I'm using it enabled, with 5 hard drives installed (and one SATA DVD drive) Boot time is 31 seconds. I think you were having some other issue.

No, you need to go BUY Leopard. Do that, and I'll walk you through installing it directly from the disk that comes from the Apple store. Downloading OSX is illegal. Hacking it my way is just a violation of their Terms of Service. Not something that they'd have much luck (or would even try) taking you to court over.

omfg

I use the EVGA 9400 GT 512 MB with dual monitors using efi strings in the com.apple.Boot.plist. Granted, it has a fan, but I absolutely cannot hear it at all. http://www.newegg.com/Product/Product.aspx...N82E16814130389 It'll give you reasonable performance, and at a tough price to beat.

EVGA 9400 512 MB I'm using it with dual DVI and two 19" 1280x1024 monitors. Should handle dual 24" monitors fine. Also, it's the new "standard" video card in a real Mac, so it'll be very similar to a real mac experience. Use EFI strings in your com.apple.Boot.plist to get it working after installing at least the 10.5.2 update (I know it works after 10.5.4, but I think it may work starting at 10.5.2)

:Mumbles something about kids these days:

Did you give up? I'll check back in a few