Recent content by bryonhowley

Do not think so. I can't see Apple putting support for it in 10.8.5 just to remove it in 10.9.x.

For me sleep on my Hackintosh is working for the first time ever. That is after updating to OS X 10.9.2. Before that if I let the system sleep it would lock up forcing a reset or forced shutdown. Now with 10.9.2 everything works great very happy with it so far.

Article: Update Your Mavericks App to 10.9.2 I updated to 10.9.2 from the App Store. Was surprised to see that Sleep works just fine now. I found out by accident because I forgot to turn it off and left the PC running and when I came home it was sleeping. Any time it did this before this update...

It sounds like you do not have the correct boot drive selected in the BIOS/UEFI. Does your motherboard offer a boot menu where you can select what drive you want to boot from? Is Mavericks on a drive of its own or are you using a multipartition drive?

Would be really really nice but from what I read before the devs will not even consider something like that. It would be nice to know there reasons other than "Won't do it".

That would be the best way for one you would own OS X legally. You would us iBoot to boot the original Snow Leopard DVD and then you can use MultiBeast to make that install bootable and update to Mavericks from there. I always prefer the legal way of doing it plus there is no chance of the DVD...

Instead of trying to use two GPU's why not just use the GTX650TI Boost? It can handle both monitors with no problems. I have 3 Asus 27" monitors and my Panasonic 50" 3D Plasma connected to my GTX 670 SLI and it handles all 4 with no problems at all. I do not even have my igpu enabled in the...

That would be from the PC itself NOT the boot disk. Since the BIOS did not find a boot disk it is trying to boot from the Network Card. That is what all those lines are for... Realtek PCIe GBE Family Controller series CLIENT MAC ADDR: ..... GUID : ...... DHCP...- PXE-E53 : no boot filename...

Would have done that if it had worked. For me it resulted in a Kernel Panic after reboot. That is why I used the one I was using with 10.8.4-10.8.5 and why I post what I did. If MultiBeast 6.0 had worked I would have suggested that instead.

1-2 You may not have a UEFI BIOS so that would not apply to you. 3. Wrong if your drive is formatted as a MBR instead of GPT you will not be able to install OS X even if you split the drive into two partitions. It has to formatted correctly and that means GPT or OS X will not boot. As...

I would second the recommendation for paragon software. I use it with OS X and Windows and it works great. If I am in Windows I have full access to my OS X drives and visa versa.

If you are getting a Kernel Panic on AppleIntelCPUPowerManagement.kext you need to replace that .kext with a patched one. Search these forums for one. I am still using the same one I did with 10.8.4 and it works fine. As for the Audio I had to use install the ALC 892 drivers from MultiBeast 6...

As stated in the MultiBeast Configuration of my post I used the UserDSDT option for MultiBeast. I choose the UserDSDT option because I use a DSDT to get the HDMI Audio working on my Gigabyte GTX 670's. Then I installed the Audio for my ALC892 and Intel Networking. I got the replacement...

To boot Windows 7 you will want to select the System Reserved that is the partition that has the Windows 7 boot loader on it. Doing that and you should boot into Windows 7 just fine. My rig is the same way to boot into Windows 8.1 I select System Reserved and it boots right into Windows 8.1.

Boot up with the -v flag and see where you are getting a kernel panic. That will help narrow down the problem.