Feel free to ask as here as wellĪs discussed in this post ( ) darkwake boot-flag values affect how our system sleeps. This is a very detailed wiki on all the features and possible configurations of Clover. If you wish to learn more about Clover than what I have discussed in this guide, you can head here. Finish your Windows installation and you are done! Remember to format the HFS+ partition to NTFS (you will catch this up, Windows won't let you install to the partition the first time)Īfter the first restart, you should already have the Windows entry read by Clover. Windows should load up, you can continue the installation process normally. Press the spacebar on every entry to see it's details, until you find one named "boot圆4.efi" or "bootmgrfw.efi". If you let Clover load the boot options, there will be more than one. You have two options: either boot directly to the Windows installation from the NUC boot options or let Clover pick up the entry and boot the Windows installer. In OS X, create a partition for Windows and format it as HFS+ Journaled (NOT MS-DOS) REMEMBER: Only 64-bit installations, 32-bit installations will not show up on our UEFI boot options! If you have an USB optical drive or already have your installation on a USB, then go on ahead. I have copied my Windows 7 copy to a USB since we don't have an optical drive. I will give an example of installing Windows alongside an already installed OS X. By doing this, Disk Utility creates a Hybrid MBR in the GPT we don't want that to happen! Delete an existing OS with less possibility of breaking our system.ĭo NOT format a partition on your HDD/SSD in Disk Utility as MS-DOS (FAT). This will stop the error messages from appearing.Ĭlover makes easy the possibility to install other OS into the NUC alongside OS X, because we will be able to use all the advantages of GPT (GUID Partition Table).Ģ. Just grab the AppleHDAIDT kext prepared by minihack on this post attachments, install it to /System/Library/Extensions and it's done.Īfter you boot with Clover, you will have two means of configuring it:Īfter it's installation, you'll find it here: By using a injector kext, we will make AppleHDA to load only the layouts needed for our audio Clover will patch the binary for us, so we will be ready to go! Thanks to minihack (posts below) we have a way of patching AppleHDA on-the-fly. We are done with the required things in the ist file, save and close it and boot up your system with Clover! In the GUI section, you can specify a theme for Clover boot screen and manage other boot entries, in case you are doing a multi-boot setup. Some of the sections in the config are empty (like Cpu), this configurations are generated at boot time automatically by Clover, we do not need to specify them. Clover will just patch the in-memory copy of the files specified in the section, so any patch you remove from this section will stop having effect at next boot. ![]() Note: The actual kernel and kext files will not be patched. There are patches already for the kernel, the framebuffer connectors, AppleHDA patches and TRIM Enabler patch. You can also fill up your RAM information as well, although they should be detected.Īfter this change, you could add more patches in the Kernel and Kext patches section if you need. With the wand icon you will be able to generate the serial number for your build. If your EFI partition is not mount, use Command+E to mount it, like this: Get the latest version from the developer page located here: Īfter we have the app, it's time to load our config file. We will be using the Clover Configurator app, which let's us easily modify our ist through a GUI. I have uploaded in this post a ist file with all the necessary configurations for the NUC you have to copy that file to the location EFI/CLOVER/ ![]() Once Clover is installed, we must do a few steps to set it up nicely.įirst, the DSDT and SSDT files must be placed in the location EFI/CLOVER/ACPI/Patched, in order for Clover to pick up their configurations at boot time.Īdditionaly, a ist file must be defined. (Also deselect this option if installing Clover to a USB). The Clover preference pane is a easy way to do Clover maintenance. (Deselect this option if you are installing to a USB) Install RC scripts on target volume records an rc.shutdown script required by Clover to work. The OSxAptioFix driver fixes memory issues in UEFI firmware. The EmuVariableUEFI driver allows OS X to use NVRAM variables. The CSMVideoDXE driver helps us to have correct resolutions while on Clover boot menu and while OS X is booting. ![]() This will install Clover to the EFI partition by default. UEFI only booting, since our board supports UEFI. Building a CustoMac Hackintosh: Buyer's GuideĪll the selections are required in order to boot OS X successfully!
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |