Switch between DEBUG and RELEASE versions of OC modules.Auto-run ocvalidate to sanitize existing config and updates.Absorb an existing drive ESP/EFI into the work area,.Download OC+modules to a local config work area.The OCAT README presents a workflow that's more oriented to experienced OC developers management the steady releases of OC plus key kexts/ACPI (OC+modules) than being a vehicle for canned configs.Ĭlearly, being able to quickly create an original EFI from boilerplate is enormously helpful and there are several major timesavers in this OCAT approach, such as: It greatly shifts user emphasis of work to create and maintain configs away from myriad details of Dortania, towards a more canned approach.īut it's maybe less targeted towards new builders than this above into makes it seem. This looks a like nifty tool with great upsides. 5T33Z0 used his Intel base configs as a starting point for creating the Intel config templates you will find in the database. Gabriel Luchina originally created the EFI repo. This post will cover what you need to get started. Why ? Because your hackintosh doesn't contain the exact same hardware that a real Mac does.Īt first glance, how to use the OCAT app may not seem obvious. It would likely create a mess of your EFI folder and make the system unbootable. I wouldn't attempt to use it to update OpenCore. OCLP is only used on hacks for a few specific use cases: When you need root patching for Broadcom Wifi/BT cards or unsupported graphics. If you do need a standalone plist editor, I'd suggest using: Ĭan I use OpenCore Legacy Patcher to do the same things ? It will probably cause problems and errors. The Dortania guide suggests using ProperTree and other apps, which are ok to use with each other. You can use Hackintool for making that kext and for gathering other system info that you'll need.ĭon't use multiple apps to edit your EFI folder. You can now do nearly everything, except making your custom USBPorts kext, with the OCAT app. When you start fresh with a new EFI folder generated with OCAT this won't be a problem. You need to make sure any app you use is for the same release version of OC that your ist was made with. I've heard that configurator apps can corrupt my ist. This app has made a lot of progress over the past few months and is now ready for use by everyone in the greater hackintosh community. When the time comes to upgrade your version of OpenCore, OCAT will make that a routine process that only takes a small amount of effort to accomplish. See post #2 for more info in the OpenCore documentation. This requires research on your part to know what to do. You will still have to make plist edits, add certain kexts and drivers to make your USB installer bootable with no kernel panics. It's not like copy/pasting a perfectly configured EFI folder from a Golden Build. View a video demo of this in Post #4 of this thread.Īs you will see in the video, OCAT doesn't do all the work for you. You will edit the ist, add kexts and drivers etc. You will still need to have a basic understanding of how OpenCore works to have success with OCAT. You'll produce your own custom EFI in just a few minutes and then modify it to work with your specific hardware. Now that anyone can download and use this app, there is no reason for beginners to copy and paste someone else's outdated EFI folder. ![]() It greatly reduces the amount of time it takes to produce a custom, working EFI folder. It's primary advantage over manual EFI creation is that it gives beginners a graphical user interface that is easy to navigate. OCAT is an app like Hackintool that serves various functions to help you build, edit and maintain your OpenCore EFI folder. ![]() OCAuxiliary Tools will be shortened to OCAT. In this thread, Open Core bootloader will be referred to as OC. Building a CustoMac Hackintosh: Buyer's Guide
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |