Welcome to the New Edition
The newest edition of Building a Hackintosh features newer content that covers new technologies, updated content on updated software, more photos, better writing, and more.
UPDATE 2020/9/22
I thought I would be able to go back on Amazon and change the book info suggesting that readers not pay for the book at all due to the age and simply go here, and even get the info from Reddit. But apparently I can't save my changes to reflect that. I guess Amazon isn't rich enough and won't allow for free advertising elsewhere. But if you're able to go back and get your money back, please do so.
I haven't been in the hobby for a while, but I sure need to be. I'm aware of OpenCore, but my first few attempts with it were unsuccessful. I'm still learning stuff with Clover, but I have my AMD Hackintosh since last year and my previous i5-6500 system that I use for music production. Still, I'd like to stay ahead of the game. Because of coronavirus I've had to keep going from temp job to temp job to stay afloat. So far I've been working at a hospital in their IT department, so that keeps things stabilized for a while. Enough about my boring self though. For the most complete and ongoing news on Hackintosh, I recommend going to www.reddit.com/r/hackintosh.
I haven't been in the hobby for a while, but I sure need to be. I'm aware of OpenCore, but my first few attempts with it were unsuccessful. I'm still learning stuff with Clover, but I have my AMD Hackintosh since last year and my previous i5-6500 system that I use for music production. Still, I'd like to stay ahead of the game. Because of coronavirus I've had to keep going from temp job to temp job to stay afloat. So far I've been working at a hospital in their IT department, so that keeps things stabilized for a while. Enough about my boring self though. For the most complete and ongoing news on Hackintosh, I recommend going to www.reddit.com/r/hackintosh.
A Short, Meaningful Mediocre Review (and my Rebuttal)
The second edition has been available since 2015, well out-of-date at the moment. UK Reviewer Mark G had this to say:
Pretty much out of date now. Plus it tells you how to build a PC. If you're building a Hackintosh you'd assume you already know how to build a PC. Too much fluff and doesn't go deep enough on the nitty gritty.
Mark summed it up semi-correctly. Granted any bad review hurts a bit, but like the first version, it just drove me to do a better job. So it's status of being out-of-date for so long, the changing times and technologies of the Hackintosh hobby, and the desire to provide updates quickly and easily inspired me to rewrite this book and provide it for free on my website. I started rewriting this in mid-January while the review itself was posted as far back as August (which I never bothered to check).
"If you're building a Hackintosh you'd assume you already know how to build a PC." - That's where he's incorrect. I came in to the hobby knowing only of Macintosh hardware from tower systems, the Mac Mini, the 90's Mac Classic (all-in-one) and PowerBook laptops. So when I got into it, I had to do a lot of research on my own learning the differences between newer and older PC technology (that still was being used) in addition to the Mac-compatible hardware and the Hackintosh software utilized to get everything working. In addition, I like having restrictions, then finding ways to perform tricks and hacks to overcome those restrictions, and finally exploiting those same techniques and sharing them with others. Why not help others try to overcome the same issues? Why not explain the mistakes I made in the process and advise others how to avoid time-consuming and costly mistakes and setbacks? Even the introduction states that if anything, the reader will now have the knowledge on how to build a PC. Besides, if I knew how to build a shed, does that mean I'm qualified to know how to build a house? We all come into this world not knowing anything, and that includes you Mark. I'm attempting to educate readers using a centralized point rather than having them scurry around the Internet.
"Too much fluff and doesn't go deep enough on the nitty gritty." - This is true that I did add a lot of fluff. The original version explained the benefits of using additional tools/parts and the cost and benefit to each one, along with pros/cons to doing things differently. I also explained ways that the macOS does things compared to the way they are done using Windows, which is important to note for those who only know Windows but are curious to know more about the more secure operating system? Ejecting a DVD in Windows by pressing the eject button on the drive doesn't work the same way under macOS, which does nothing. Control + Alt + Delete in Windows does nothing under macOS either, but pressing Command (Alt) + Option (Windows key) + Escape does bring up the macOS equivalent of Task Manager. Should the buyer of the eBook assume they already know macOS and purchased the book for a cheaper hardware alternative, where the techniques I just listed would be common knowledge to a Mac user?
My goal in writing was to provide a solution for those who already knew how to build a PC, those who had a PC and wanted macOS (then known as OS X), those already familiar with Macs and wanted a cheaper alternative (my reason for explaining PC parts and assembly and dedicating an entire chapter on it), and those who knew nothing about computer hardware. In my line of IT work and technical writing (or any writing for that matter), there has to be a lowest common denominator. It's assumed the reader knows what a computer is, that Windows and Mac look and operate slightly different from each other, that they know how to operate a keyboard and mouse. The challenge is finding that common denominator when explaining anything technical. Even Haynes and Chilton car/truck repair manuals know that the people who buy their manuals want to do their own mechanical and body work, so there's no need to point out to readers where the engine is and where the brakes are. But those manuals provide diagrams showing where specific parts are located and the name of each part regarding specific vehicles. Talk technical to someone non-technical and there's an off-putting, possibly intimidating communication barrier. Talk too remedial to someone and they may feel insulted or that the level of help they need can be acquired elsewhere, or they may feel they know more than you do.
As far as the nitty-gritty, I have neither the time nor the budget to show every piece of code for every time of CPU, motherboard, and system. But that's just an excuse. At the time I was using the now-lamented UniBeast and MultiBeast tools from tonymacx86.com. Since that time I've followed the Vanilla guide from the Hackintosh subreddit on Reddit.com and built a friendship with heroic Hackintosh staple CorpNewt, both having expanded my knowledge on the creation and stabilization of a Hackintosh system. While it's impossible for me to get details and fixes for every system and parts combination possible, I understand how Mark feels that my book doesn't get into the nitty-gritty. On one hand I wanted to go over any potential roadblocks the average reader may encounter, but not go too in-depth with technical terms and techniques that the user may be unfamiliar with, or blatantly guide them to a different website to resolve the remainder of their issues. I fully understand how getting into the small details sometimes can make or break a system, which can please or displease a builder.
Too often I may Google an issue, see forum posts with the same or similar questions, and replies from people simply guiding them elsewhere or coming down on them for not knowing the answer themselves. To this day I still see replies guiding the user to a different website for their answer, but this is sometimes a blessing in disguise. If the site simply provides text and photos explaining how to do things, how to resolve the issue; then that's great. Other times it may provide more information regarding what can/does happen if done differently, the benefit of using a different part or technique. Eventually I'll find some sites that provide information into a glimpse of a larger world, like the first time I discovered Reddit.
So Mark, your criticism is noted and I will take that into account from now on when I update the book. It will provide a challenge, perhaps a roadblock, for diving into various levels regarding technical details where readers can go at their own pace, perhaps even seeking their answer elsewhere if I explain at a level too advanced for them. If my book hasn't helped you build a Hackintosh to your liking, I sincerely hope you were able to get assistance elsewhere and build a powerful machine that exceeds your needs.
"If you're building a Hackintosh you'd assume you already know how to build a PC." - That's where he's incorrect. I came in to the hobby knowing only of Macintosh hardware from tower systems, the Mac Mini, the 90's Mac Classic (all-in-one) and PowerBook laptops. So when I got into it, I had to do a lot of research on my own learning the differences between newer and older PC technology (that still was being used) in addition to the Mac-compatible hardware and the Hackintosh software utilized to get everything working. In addition, I like having restrictions, then finding ways to perform tricks and hacks to overcome those restrictions, and finally exploiting those same techniques and sharing them with others. Why not help others try to overcome the same issues? Why not explain the mistakes I made in the process and advise others how to avoid time-consuming and costly mistakes and setbacks? Even the introduction states that if anything, the reader will now have the knowledge on how to build a PC. Besides, if I knew how to build a shed, does that mean I'm qualified to know how to build a house? We all come into this world not knowing anything, and that includes you Mark. I'm attempting to educate readers using a centralized point rather than having them scurry around the Internet.
"Too much fluff and doesn't go deep enough on the nitty gritty." - This is true that I did add a lot of fluff. The original version explained the benefits of using additional tools/parts and the cost and benefit to each one, along with pros/cons to doing things differently. I also explained ways that the macOS does things compared to the way they are done using Windows, which is important to note for those who only know Windows but are curious to know more about the more secure operating system? Ejecting a DVD in Windows by pressing the eject button on the drive doesn't work the same way under macOS, which does nothing. Control + Alt + Delete in Windows does nothing under macOS either, but pressing Command (Alt) + Option (Windows key) + Escape does bring up the macOS equivalent of Task Manager. Should the buyer of the eBook assume they already know macOS and purchased the book for a cheaper hardware alternative, where the techniques I just listed would be common knowledge to a Mac user?
My goal in writing was to provide a solution for those who already knew how to build a PC, those who had a PC and wanted macOS (then known as OS X), those already familiar with Macs and wanted a cheaper alternative (my reason for explaining PC parts and assembly and dedicating an entire chapter on it), and those who knew nothing about computer hardware. In my line of IT work and technical writing (or any writing for that matter), there has to be a lowest common denominator. It's assumed the reader knows what a computer is, that Windows and Mac look and operate slightly different from each other, that they know how to operate a keyboard and mouse. The challenge is finding that common denominator when explaining anything technical. Even Haynes and Chilton car/truck repair manuals know that the people who buy their manuals want to do their own mechanical and body work, so there's no need to point out to readers where the engine is and where the brakes are. But those manuals provide diagrams showing where specific parts are located and the name of each part regarding specific vehicles. Talk technical to someone non-technical and there's an off-putting, possibly intimidating communication barrier. Talk too remedial to someone and they may feel insulted or that the level of help they need can be acquired elsewhere, or they may feel they know more than you do.
As far as the nitty-gritty, I have neither the time nor the budget to show every piece of code for every time of CPU, motherboard, and system. But that's just an excuse. At the time I was using the now-lamented UniBeast and MultiBeast tools from tonymacx86.com. Since that time I've followed the Vanilla guide from the Hackintosh subreddit on Reddit.com and built a friendship with heroic Hackintosh staple CorpNewt, both having expanded my knowledge on the creation and stabilization of a Hackintosh system. While it's impossible for me to get details and fixes for every system and parts combination possible, I understand how Mark feels that my book doesn't get into the nitty-gritty. On one hand I wanted to go over any potential roadblocks the average reader may encounter, but not go too in-depth with technical terms and techniques that the user may be unfamiliar with, or blatantly guide them to a different website to resolve the remainder of their issues. I fully understand how getting into the small details sometimes can make or break a system, which can please or displease a builder.
Too often I may Google an issue, see forum posts with the same or similar questions, and replies from people simply guiding them elsewhere or coming down on them for not knowing the answer themselves. To this day I still see replies guiding the user to a different website for their answer, but this is sometimes a blessing in disguise. If the site simply provides text and photos explaining how to do things, how to resolve the issue; then that's great. Other times it may provide more information regarding what can/does happen if done differently, the benefit of using a different part or technique. Eventually I'll find some sites that provide information into a glimpse of a larger world, like the first time I discovered Reddit.
So Mark, your criticism is noted and I will take that into account from now on when I update the book. It will provide a challenge, perhaps a roadblock, for diving into various levels regarding technical details where readers can go at their own pace, perhaps even seeking their answer elsewhere if I explain at a level too advanced for them. If my book hasn't helped you build a Hackintosh to your liking, I sincerely hope you were able to get assistance elsewhere and build a powerful machine that exceeds your needs.
Microsoft Boot Issues - Don't Install With a Mac Drive Already There
I first installed Catalina on a 256 GB m.2 drive on my older i5-6500. Months later I decided to put an older solid state drive in and install Windows 10 to it. It worked, but I had issues afterwards.
After I installed Windows I had issues booting to Catalina, and going into the BIOS wasn't much help. Instead of showing both the normal SATA drive port of "Port 0: Kingston 256 GB" and the UEFI version for macOS which is "Port 0: UEFI 256 GB Kingston", it was displaying "Port 0: Windows Boot Manager" even though I installed Windows to a separate solid state drive. I removed the m.2 drive and put it in an external case, then connected it via USB to my Ryzentosh, it still showed up as Catalina. But I went a step further by using Clover Configurator to mount the EFI partition, and found the culprit.
In addition to the CLOVER and BOOT folder, there was another folder labeled "Microsoft". That had to be it! So I deleted it, trashed it, then removed the USB drive from my Ryzentosh and connect it to my i5-6500. I booted it back up to BIOS and THEN it returned as "Port 0: UEFI 256 GB Kingston". Booting externally took longer but it got back to the MacOS Desktop, so I knew I was safe. After removing it from the external case and remounting it to my i5-6500 board and booting again, all was good.
Lesson learned: Disconnect the SATA power and data cables, or in my case the m.2 drive, before installing Windows.
After I installed Windows I had issues booting to Catalina, and going into the BIOS wasn't much help. Instead of showing both the normal SATA drive port of "Port 0: Kingston 256 GB" and the UEFI version for macOS which is "Port 0: UEFI 256 GB Kingston", it was displaying "Port 0: Windows Boot Manager" even though I installed Windows to a separate solid state drive. I removed the m.2 drive and put it in an external case, then connected it via USB to my Ryzentosh, it still showed up as Catalina. But I went a step further by using Clover Configurator to mount the EFI partition, and found the culprit.
In addition to the CLOVER and BOOT folder, there was another folder labeled "Microsoft". That had to be it! So I deleted it, trashed it, then removed the USB drive from my Ryzentosh and connect it to my i5-6500. I booted it back up to BIOS and THEN it returned as "Port 0: UEFI 256 GB Kingston". Booting externally took longer but it got back to the MacOS Desktop, so I knew I was safe. After removing it from the external case and remounting it to my i5-6500 board and booting again, all was good.
Lesson learned: Disconnect the SATA power and data cables, or in my case the m.2 drive, before installing Windows.
I GOT IT ON AN AMD RYZEN! (2019/12/1)
A HUGE THANK YOU to Hackintosh guru and community staple CorpNewt for his excellent help on getting my system going. The guide I followed was from the amd-osx.com site here (vanilla.amd-osx.com/). The most beneficial parts are that one no longer needs access to a Mac in order to get macOS itself, and that you can pay even less now with Ryzen CPUs and get better performance than their Intel counterparts.
The way it works is you download a set of free files on a Windows PC. The installer is a recovery installer, so you will need an Ethernet connection to get it going. Then you use a program to format the flash drive properly, then loads the recovery installer on it. There was an initial problem with formatting the USB drive in the guide under "Creating the macOS Install USB", and the issue was that the program was using the latest version of Clover, which cuts off Ethernet access during install. Thankfully CorpNewt pointed out that users have to use version r5092 of Clover in order to get it to load properly.
The way it works is you download a set of free files on a Windows PC. The installer is a recovery installer, so you will need an Ethernet connection to get it going. Then you use a program to format the flash drive properly, then loads the recovery installer on it. There was an initial problem with formatting the USB drive in the guide under "Creating the macOS Install USB", and the issue was that the program was using the latest version of Clover, which cuts off Ethernet access during install. Thankfully CorpNewt pointed out that users have to use version r5092 of Clover in order to get it to load properly.
In the above screenshot, after the warning, any available drives are listed including the connected flash drives. In this example i have no flash drives connected, only my HP SSD which already has Mojave on it., and I definitely don't want to start over with that. Before what I was doing was selecting the flash drive, then pressing enter. If you look at the line with the red arrow you'll see the fix for this. What CorpNewt instructed me to do was type the number of the flash drive. then type in the letter "C" because I already had the macOS recovery on the flash drive, followed by typing in "r", then typing in the Clover version number, in this case 5092. After this is completed, the next step is to select the macOS Recovery version you downloaded in a previous step in the guide.
Now if you do the same thing just starting out, not having already put the recovery on the flash drive, what you'll need to do is type in the number corresponding to the flash drive for Mojave or Catalina, then "r" and the Clover version. So if your flash drive shows up as 3 for a SanDisk 32GB, you would type in:
3 r5092
Then hit return, and follow the rest of the instructions. I was having issues getting Catalina installed, but with this recent fix I will try another flash drive and another SSD to attempt to get it working. I hope this helps you as it has helped me!
Now if you do the same thing just starting out, not having already put the recovery on the flash drive, what you'll need to do is type in the number corresponding to the flash drive for Mojave or Catalina, then "r" and the Clover version. So if your flash drive shows up as 3 for a SanDisk 32GB, you would type in:
3 r5092
Then hit return, and follow the rest of the instructions. I was having issues getting Catalina installed, but with this recent fix I will try another flash drive and another SSD to attempt to get it working. I hope this helps you as it has helped me!
New Updates
Switching Video Teams (for real this time. i mean it!) - Lack of Nvidia and Apple getting together means delayed drivers for Mojave users with Nvidia cards.
New Laptop and HD4600 Mixups - I bought another laptop but had conflicting info regarding its settings.
DPCI Manager - Thanks to Reddit user and new friend CorpNewt, I was introduced to a new tool to help identify internal hardware when motherboard manufacturer's don't provide such information.
NEW BOARD, NEW PROBLEMS - It was about time for me to upgrade, so I decided on a more-compatible Skylake i5-6500 than a newer Kaby Lake i5-7500. I also got an MSI H110M Gaming board (instead of a Gigabyte board). Using my old hard drive and switching things around proved more complex than simply reinstalling from scratch, but it does have it's delightful surprises. More to follow.
LOUIE'S MOTHERBOARD GUIDE - If you're just starting out and need help learning about motherboards and their components, or an experienced builder in need of narrowing down your choices, check out Louie's Motherboard Guide.
AMD OSX Forum - Here's a handy forum for users attempting to run OS X using AMD cards. The site has a few downloads as well. Be aware that you'll need to sign up in order to see forum replies.
NVIDIA 1XXX-SERIES DRIVERS (Link) from TonymacX86.com - As of 4/11 newer Nvidia 1xxx series cards (GTX 1050, etc) are now available to enable these cards working in OS X Sierra.
2017/3/8 - Added info for Chapters 5, 6, and 8.
2017/3/7 - Completed changes for Chapters 6 and 7. Adding info for Chapter 8.
2017/3/6 - Completed Chapter 5, now adding things for Chapter 6
2017/3/5 - Added info to Chapter 5 Changes. more info and screenshots are coming soon including a better guide to formatting and installation.
New Laptop and HD4600 Mixups - I bought another laptop but had conflicting info regarding its settings.
DPCI Manager - Thanks to Reddit user and new friend CorpNewt, I was introduced to a new tool to help identify internal hardware when motherboard manufacturer's don't provide such information.
NEW BOARD, NEW PROBLEMS - It was about time for me to upgrade, so I decided on a more-compatible Skylake i5-6500 than a newer Kaby Lake i5-7500. I also got an MSI H110M Gaming board (instead of a Gigabyte board). Using my old hard drive and switching things around proved more complex than simply reinstalling from scratch, but it does have it's delightful surprises. More to follow.
LOUIE'S MOTHERBOARD GUIDE - If you're just starting out and need help learning about motherboards and their components, or an experienced builder in need of narrowing down your choices, check out Louie's Motherboard Guide.
AMD OSX Forum - Here's a handy forum for users attempting to run OS X using AMD cards. The site has a few downloads as well. Be aware that you'll need to sign up in order to see forum replies.
NVIDIA 1XXX-SERIES DRIVERS (Link) from TonymacX86.com - As of 4/11 newer Nvidia 1xxx series cards (GTX 1050, etc) are now available to enable these cards working in OS X Sierra.
2017/3/8 - Added info for Chapters 5, 6, and 8.
2017/3/7 - Completed changes for Chapters 6 and 7. Adding info for Chapter 8.
2017/3/6 - Completed Chapter 5, now adding things for Chapter 6
2017/3/5 - Added info to Chapter 5 Changes. more info and screenshots are coming soon including a better guide to formatting and installation.
Are there errors, corrections, or things you'd like to see in the new update? Email me at [email protected].
Helpful Links
Tips and Tricks - Here you'll find helpful articles showing you how to get the most from your machine, hardware setup, and more.
Files / Websites - Web links to needed sites and helpful files.
Contact - Find a mistake or something that needs corrected? Let me know!
Updating to Sierra - Apple's newest version of OS X and much easier to work with!
Switching (Video) Teams?
Files / Websites - Web links to needed sites and helpful files.
Contact - Find a mistake or something that needs corrected? Let me know!
Updating to Sierra - Apple's newest version of OS X and much easier to work with!
Switching (Video) Teams?
Last Updated 2019/2/25