Search results

I agree that there are compatibility issues in some applications in HS that could be a reason to stick with sierra. I have also read that some users have a better experience with the nvidia drivers in Sierra? Not to mention if you still want to use legacy 32-bit applications such as final cut 7...

Ah, that explains it. After running som real world tests I realised I have openGL support. Didn't occur to me that cinebench removed the GPU benchmark. Thank you.

So I finally seem to have a working system with high sierra. But I seem to be missing openCL support? I have cuda and nvidia drivers installed but running cinebench I only get the option to run a cpu test? Am I missing something or is openCL support not available with the current drivers?

Hi @kgp I am also trying the workaround method for installing 10.12. Do you think the working 10.12 system must be specifically from another x299 system? Correct me if I'm wrong but I am thinking that the critical part of a working hackintosh happens during boot right? In my case I tried to...

How did you get past the runtime and plus sign errors? I'm losing my mind here :(

So after a couple of months I decided to give it a shot again. After hours of reading various guides I can never get past either the runtime error or the plus sign error :( It's so frustrating!

What did I miss or do wrong if I get the "stop sign" when trying to do a fresh install? I did all the steps on creating a bootable high sierra :( EDIT: This is of course AFTER the clover bootloader screen and after I have chosen "install mac OS high sierra"

Today I tried deleting all the kexts in the EFI folder and I got the allocate runtime area error again. So to sum it up: -I need to have all the default kexts created with unibeast in place -and use the OsxAptioFix2Drv-free2000.efi only then do I get past the allocate runtime area error but...

Hi This is my second hackintosh build. After reading that some x299 users have got it working I thought I'd give it a go. I have done some troubleshooting and trial and error but I am stuck at this point. My build: Motherboard: MSI X299 Tomahawk CPU: Intel Core i9-7920X (12 Core) RAM: Corsair...

If anyone ever find themselves in my position, needing to install yosemite but are unable to create a usb using unibeast, the clover 10.10 guide WILL work! http://www.tonymacx86.com/yosemite-desktop-guides/144426-how-install-os-x-yosemite-using-clover.html After successful install you can...

I decided to finally flash the bios to UEFI, it now works like a charm :)

I have successfully been running Mountain Lion for some time now and I thought it was time to update. Did some test with clover and el capitan but I don't think I will ever get it working 100%, maybe with Multibeast 8 but not even sure about that. Anyway, I decided Yosemite would be the best...

I also came across this problem. But even after adding manual entries and turning off the scan in the config.plist, it never even gets to the clover screen, just reboots when the raid drives are plugged in. If I unplug the raid, it works. I don't know if it matters but I'm using legacy bios...

Don't know if I missed something, but it feels like I tried everything. 1. No audio codec under 10.11. Working fine in 10.8.5 with Multibeast ALC889 2. OS X 10.11, GA-Z68X-UD3H-B3, BIOS F10, I7 2700K, ASUS GTX 660 Ti 2Gb 3. cloverALC-110 4. Attached 5. Attached 6. N/A 7. N/A 8...

Yes the system is 12,2 under About this Mac, the problem is it will not boot from the system drive as soon as I apply that definition in clover configurator. 3,1 definition gets me a cpu error.

I guess what I am asking plain and simple is, is it not weird that the system is working without a system definition?

Do I need smbios definition? I got my system working without adding a system definition in clover, does this matter? I am on a GA-Z68X-UD3H-B3 using legacy bios and have been using chimera up until now. My complete system is in my user profile. El capitan identified my system as iMac12,2...

I also have this issue and I have actually posted a thread on it as well. There are what I could find 3 posts on this issue, mine included. I find it fascinating that no one has a fix for this. I find it even more fascinating about all the people answering pure rubbish like "cable is too...

I wouldn't say it's a hit or miss. It should definately work on a real Mac, in fact I tried it on 4 different Macs at work, both macbooks and Mac Pros and it worked on all. But I would really like to get to the bottom of why this doesn't work on a hackintosh. As some of you stated there is in...

Thank you for your replies. This DOES work on a real mac that's why I'm confused to why it doesn't work on my hackintosh. Do Mac computers have a higher usb power output than pc? I would like to point out that yes my devices work just fine when I plug them directly to the motherboard. EDIT...