zip file downloaded to your system with everything you need to install OpenCore on your Classic Mac Pro. Pick and download the latest one (0.7.1 at this time of writing) – Martin Lo’s preconfigured OpenCore for the cMP package.įor that package, go to this page, scroll down until you see all the attachments. – 144.0.0.0.0 Boot ROM (You get this by running the Mojave installer and just doing the firmware update that is a part of it) Most of the text in this guide is simply explaining stuff, so don’t let the fact you see a bunch of text scare you off, this really is a simple process. This guide may have steps in it that are not needed for most people, but I include them so that the guide can work for anyone that reads it. This post is the quick and easy guide that should have anyone up and running with OpenCore on the cMac Pros in minutes. I have no experience (yet) with other versions of OpenCore, such as the Legacy patcher, but I fully intend to explore that as well at some point. If you don’t know what OpenCore is, read about some of its benefits here. This seems weird, but maybe good because the target drive is Drive 0 from its point of view.OpenCore is, for lack of a better word, amazing. But Win10 installer thinks that m.2_2 is disk 0 and m.2_1 is disk 1. When I start the Win10 installer boot, the only storage devices are (a) the usb stick, (b) the target SSD m.2_2, (c) the macOS boot SSD m.2_1. In any case, I've discovered that my BIOS allows me to disable all SATA devices with one click. But my m.2_2 is not in the special NVME slot but in a PCIe adapter card. But I think I have devices on SATA 4, 5, 6 that are working despite m.2_2 being live. If you also use m.2_2, I think you then lose SATA 5 and 6 even if it's PCIe, unless you choke it down to x2 which sort of defeats the purpose of SSD that is what I have read in ASUS forum anyway. On my mobo use of m.2_1 disables SATA port 1 for some reason (not 0, dunno why) but ONLY if you have it set up as a SATA drive if it's configured as per default (PCIe) then apparently SATA 1 remains usable. That’s thanks, from what I have googled (NB I don't say understood, just read) this is the scoop: To install the driver follow this path EFI > CLOVER > drivers64. ![]() Now you need to put additional driver called NTFS X64 driver on the EFI partition. When installing clover finished, it will automatically mount the EFI partition. Source: Clover installer]Ĭontinue with click on ‘ CloverEFI‘ menu dropdown and select ‘ CloverEFI 64-bits SATA‘Ĭheck also ‘ Install RC script on target volume‘ ![]() ![]() This choice will NOT set the partition status byte to active in the MBR. This bootloader is a good choice when you have Windows installed on the same disk because Windows wants to have its partition active. If no partition is found it will try to boot the active partition defined in MBR. [ boot0ss (boot0 Signature Scanning) bootloader tries to boot the first EFI/FAT32/HFS partition (defined in the MBR and then the GPT) with a valid PBR signature. In ‘ Bootloader section‘ check for’ Install boot0ss in MBR this option will be used for BIOS booting on BIOS motherboards. Inside ‘ Custom Install‘ Check for ‘ Install Clover in ESP‘ When you installing Clover, on ‘Installation Type’ Instead click on ‘Install’ choose to click ‘Customize’ see screenshot below. ![]() "this is how I settings the clover bootloader for my hackintosh that dual boot with Windows 10. Building a CustoMac Hackintosh: Buyer's Guide
0 Comments
Leave a Reply. |