Apple core mod что это

AppleCore [1.12.2] [1.12.1] [1.12] [1.10] [1.7.10]

Описание

Скриншоты

Видео

Как установить AppleCore

  1. Скачай и установи Minecraft Forge
  2. Скачай мод
  3. Не распаковывая, скопируй в .minecraft\mods
  4. Готово

Скачать AppleCore

Версия Ссылка Загрузок Размер Дата
Все версии Скачать 300 000 2.3 МБ 09 декабря 2021
Для 1.12.2 Скачать 1 0.1 Мб 31 мая 2020
Для 1.12.1 Скачать 0 0.1 Мб 20 января 2018
Для 1.12 Скачать 0 0.1 Мб 20 января 2018
Для 1.11.2 Скачать 0 0.1 Мб 18 июня 2019
Для 1.10.2 Скачать 0 0.1 Мб 13 июня 2018
Для 1.10 Скачать 0 0.1 Мб 21 августа 2016
Для 1.9.4 Скачать 0 0.1 Мб 06 марта 2018
Для 1.8.9 Скачать 0 0.1 Мб 06 марта 2018
Для 1.7.10 Скачать 0 0.1 Мб 06 марта 2018
  1. Нажми на клавиатуре сочетание клавиш Win + R
  2. Введи в открывшемся окне %APPDATA%\.minecraft и нажми кнопку OK
    Папка находится в домашней директории пользователя

\.minecraft.

  • Так как в linux нет единой инструкции как открыть папку, используй универсальный способ.
    1. Открой Finder
    2. Нажми на клавиатуре сочетание клавиш Cmd + Shift + G
    3. Введи в открывшемся окне

    /Library/Application Support/Minecraft/

  • Нажми кнопку Перейти
  • Источник

    Apple core mod что это

    Apple Core – очередной замечательный мод для игры Майнкрафт. Он славится тем, что предусматривает новую механику еды и голода. Помимо этого, владелец AplleCore сможет полностью ознакомиться с полезной информацией, касающейся определенной разновидности еды. Большой частью, мод AppleCore является вспомогательным.

    Помимо вышеперечисленных возможностей, AppleCore представляет возможность изменения функционала еды и голода. Но, не следует самостоятельно его изменять, если вы не разобрались с этим модов. Ведь это может привести к неполной работоспособности самого мода.

    Также автор мода предвидел тот факт, что большая часть игроков пользуется ресурс-паками и другими модами. Поэтому он и сделал полную оптимизацию. Теперь вы сможете пользоваться не только этим модом, но и совмещать его с другими.

    Измененные индикаторы еды и голода

    Как было упомянуто ранее, с помощью этого мода, игровой функционал еды и голода станет более удобным, чем был раньше.

    • Во время зажатия кнопки «Shift», игроки смогут увидеть питательную ценность определенной разновидности еды. С помощью этой возможности, можно точно рассчитать, сколько и какой еды нужно съесть для полного утоления голода. Это особенно важно в режиме «Хардкор», на начальных стадиях игры;

    • Теперь, чтобы узнать, насколько будет полезна вам еда, хватит навести на нее курсором. После этого вы увидите, что начнут мигать индикаторы голода. И с помощью этого, вы узнаете, сколько «голода» вам восстановит определенный продукт;

    • Помимо этого, вы будете наблюдать за тем, как ваш персонаж голодает. Индикаторы также будут мигать, и полностью покажут вам, когда вы проголодаетесь. Иными словами, вы сможете рассчитать, сколько времени продержится ваш персонаж без пищи.

    Но, в первую очередь вам придется убедиться, что вы пользуетесь именно версией игры 1.7.10. Ведь этот мод представлен только для единственной версии. Если же попытаться установить его на более новую, или же наоборот, старую, версию игры, то вы заметите, что AppleCore не будет полноценно работать. Поэтому обратите на этот факт внимание! Это важно!

    А для новичков специально написан небольшой гайд, который ответит на вопрос: «Как установить мод». Это очень просто!

    Установка мода Apple Core

    • В первую очередь, для полной установки вам нужен Minecraft Forge;
    • Если он есть, то займитесь скачиванием мода AppleCore для Minecraft 1.7.10;
    • После того, как он оказался на вашем компьютере, скопируйте целостный архив и поместите в папку .minecraft/mods. Готово! Перезапустите лаунчер и заходите в игру!

    Источник

    AppleCore – GUI Mod For Minecraft 1.10.2, 1.9.4, 1.8.9, 1.7.10


    This small modification contains only two great features. First, this is a secondary core that needs some modifications. And secondly, it has a lot of informative hints about food and hidden parameters. This is mainly useful for beginners who do not know how much a particular food restores health points.

    Screenshots

    Review

    How to install AppleCore

    1. Download and install Forge
    2. Make sure that you have the “Java” application installed.
    3. Download the “Zip” archive from our website.
    4. Inside this is a “Jar” mod. It can also contain old and new builds.
    5. Select the latest version of the “Jar” file that matches the game version.
    6. Please note that some releases may contain bugs, incompatibilities with other modifications, and in some cases may cause conflicts within Forge or Fabric. You can try installing the previous build to fix this.
    7. Move the “Jar” file to the “Mods” folder.
    8. This folder is located at the following path:

    Mac OS X:
    /Users/Your Profile Name/Library/Application Support/minecraft/
    Quick way to get there: Click on the desktop and then press the combination of “Command+Shift+G” keys at the same time.
    Type

    /Library and press the “Enter” key.
    Open the Application Support folder and then Minecraft

    Windows 11, 10, 8, 7:
    C:\Users\Your Profile Name\AppData\Roaming\.minecraft\
    Quick way to get there: Press the “Windows” key and the “R” key at the same time.
    Type %appdata% and press “Enter” key or click OK.

  • The “Mods” folder is created automatically when you install Forge or Fabric, but you can always create it manually.
  • Open the launcher and select the desired modloader.
  • Launch the game and enjoy the new gameplay.
  • Ready!
  • Источник

    # Desktop Haswell and Broadwell

    Support Version
    Initial macOS Support OS X 10.8, Mountain Lion

    # Starting Point

    So making a config.plist may seem hard, it’s not. It just takes some time but this guide will tell you how to configure everything, you won’t be left in the cold. This also means if you have issues, review your config settings to make sure they’re correct. Main things to note with OpenCore:

    • All properties must be defined, there are no default OpenCore will fall back on so do not delete sections unless told explicitly so. If the guide doesn’t mention the option, leave it at default.
    • The Sample.plist cannot be used As-Is, you must configure it to your system
    • DO NOT USE CONFIGURATORS, these rarely respect OpenCore’s configuration and even some like Mackie’s will add Clover properties and corrupt plists!

    Now with all that, a quick reminder of the tools we need

    And read this guide more than once before setting up OpenCore and make sure you have it set up correctly. Do note that images will not always be the most up-to-date so please read the text below them, if nothing’s mentioned then leave as default.

    This is where you’ll add SSDTs for your system, these are very important to booting macOS and have many uses like USB maps

    (opens new window) , disabling unsupported GPUs and such. And with our system, it’s even required to boot. Guide on making them found here: Getting started with ACPI

    For us we’ll need a couple of SSDTs to bring back functionality that Clover provided:

    Required SSDTs Description
    SSDT-PLUG

    (opens new window)

    Allows for native CPU power management on Haswell and newer, see Getting Started With ACPI Guide

    (opens new window) for more details.

    SSDT-EC

    (opens new window)

    Fixes the embedded controller, see Getting Started With ACPI Guide

    (opens new window) for more details.

    Note that you should not add your generated DSDT.aml here, it is already in your firmware. So if present, remove the entry for it in your config.plist and under EFI/OC/ACPI.

    For those wanting a deeper dive into dumping your DSDT, how to make these SSDTs, and compiling them, please see the Getting started with ACPI

    (opens new window) page. Compiled SSDTs have a .aml extension(Assembled) and will go into the EFI/OC/ACPI folder and must be specified in your config under ACPI -> Add as well.

    # Delete

    This blocks certain ACPI tables from loading, for us we can ignore this.

    # Patch

    This section allows us to dynamically modify parts of the ACPI (DSDT, SSDT, etc.) via OpenCore. For us, our patches are handled by our SSDTs. This is a much cleaner solution as this will allow us to boot Windows and other OSes with OpenCore

    # Quirks

    Settings relating to ACPI, leave everything here as default as we have no use for these quirks.

    # Booter

    This section is dedicated to quirks relating to boot.efi patching with OpenRuntime, the replacement for AptioMemoryFix.efi

    # MmioWhitelist

    This section is allowing spaces to be passthrough to macOS that are generally ignored, useful when paired with DevirtualiseMmio

    # Quirks

    Settings relating to boot.efi patching and firmware fixes, for us, we leave it as default

    # DeviceProperties

    Sets device properties from a map.

    This section is set up via WhateverGreen’s Framebuffer Patching Guide

    (opens new window) and is used for setting important iGPU properties.

    AAPL,ig-platform-id is what macOS uses to determine how the iGPU drivers interact with our system, and the two values choose between are as follows:

    AAPL,ig-platform-id Comment
    0300220D Used when the Desktop Haswell iGPU is used to drive a display
    04001204 Used when the Desktop Haswell iGPU is only used for computing tasks and doesn’t drive a display
    07002216 Used when the Desktop Broadwell iGPU

    I added another portion as well that shows a device-id fake in case you have an HD 4400 which is unsupported in macOS.

    The device-id fake is set up like so:

    • 12040000 — this is the device id for HD 4600 which does have support in macOS

    We also add 3 more properties, framebuffer-patch-enable , framebuffer-stolenmem and framebuffer-fbmem . The first enables patching via WhateverGreen.kext, the second sets the min stolen memory to 19MB and third sets the framebuffer memory to 9MB. This is usually unnecessary, as this can be configured in BIOS(64MB recommended) but required when not available.

    • Note: Headless framebuffers(where the dGPU is the display out) do not need framebuffer-patch-enable , framebuffer-stolenmem and framebuffer-fbmem
    Key Type Value
    AAPL,ig-platform-id Data 0300220D
    framebuffer-patch-enable Data 01000000
    framebuffer-stolenmem Data 00003001
    framebuffer-fbmem Data 00009000
    device-id Data 12040000

    (This is an example for a desktop HD 4400 without a dGPU and no BIOS options for iGPU memory)

    Key Type Value
    AAPL,ig-platform-id Data 07002216
    framebuffer-patch-enable Data 01000000
    framebuffer-stolenmem Data 00003001
    framebuffer-fbmem Data 00009000

    (This is an example for a desktop Iris Pro 6200 and no BIOS options for iGPU memory)

      Applies AppleALC audio injection, you’ll need to do your own research on which codec your motherboard has and match it with AppleALC’s layout. AppleALC Supported Codecs

    (opens new window) .

  • You can delete this property outright as it’s unused for us at this time
  • For us, we’ll be using the boot-arg alcid=xxx instead to accomplish this. alcid will override all other layout-IDs present. More info on this is covered in the Post-Install Page

    # Delete

    Removes device properties from the map, for us we can ignore this

    # Kernel

    Here’s where we specify which kexts to load, in what specific order to load, and what architectures each kext is meant for. By default we recommend leaving what ProperTree has done, however for 32-bit CPUs please see below:

    More in-depth Info

    The main thing you need to keep in mind is:

    • Load order
      • Remember that any plugins should load after its dependencies
      • This means kexts like Lilu must come before VirtualSMC, AppleALC, WhateverGreen, etc

    A reminder that ProperTree

    (opens new window) users can run Cmd/Ctrl + Shift + R to add all their kexts in the correct order without manually typing each kext out.

    • Arch
      • Architectures supported by this kext
      • Currently supported values are Any , i386 (32-bit), and x86_64 (64-bit)
    • BundlePath
      • Name of the kext
      • ex: Lilu.kext
    • Enabled
      • Self-explanatory, either enables or disables the kext
    • ExecutablePath
      • Path to the actual executable is hidden within the kext, you can see what path your kext has by right-clicking and selecting Show Package Contents . Generally, they’ll be Contents/MacOS/Kext but some have kexts hidden within under Plugin folder. Do note that plist only kexts do not need this filled in.
      • ex: Contents/MacOS/Lilu
    • MinKernel
      • Lowest kernel version your kext will be injected into, see below table for possible values
      • ex. 12.00.00 for OS X 10.8
    • MaxKernel
      • Highest kernel version your kext will be injected into, see below table for possible values
      • ex. 11.99.99 for OS X 10.7
    • PlistPath
      • Path to the info.plist hidden within the kext
      • ex: Contents/Info.plist

    Kernel Support Table

    OS X Version MinKernel MaxKernel
    10.4 8.0.0 8.99.99
    10.5 9.0.0 9.99.99
    10.6 10.0.0 10.99.99
    10.7 11.0.0 11.99.99
    10.8 12.0.0 12.99.99
    10.9 13.0.0 13.99.99
    10.10 14.0.0 14.99.99
    10.11 15.0.0 15.99.99
    10.12 16.0.0 16.99.99
    10.13 17.0.0 17.99.99
    10.14 18.0.0 18.99.99
    10.15 19.0.0 19.99.99
    11 20.0.0 20.99.99

    # Emulate

    Needed for spoofing unsupported CPUs like Pentiums and Celerons

    • Cpuid1Mask: Leave this blank
    • Cpuid1Data: Leave this blank

    # Force

    Used for loading kexts off system volume, only relevant for older operating systems where certain kexts are not present in the cache(ie. IONetworkingFamily in 10.6).

    For us, we can ignore.

    # Block

    Blocks certain kexts from loading. Not relevant for us.

    # Patch

    Patches both the kernel and kexts.

    # Quirks

    Settings relating to the kernel, for us we’ll be enabling the following:

    Quirk Enabled Comment
    AppleCpuPmCfgLock NO Need if running 10.10 or older and cannot disable CFG-Lock in the BIOS
    AppleXcpmCfgLock YES Not needed if CFG-Lock is disabled in the BIOS
    DisableIoMapper YES Not needed if VT-D is disabled in the BIOS
    LapicKernelPanic NO HP Machines will require this quirk
    PanicNoKextDump YES
    PowerTimeoutKernelPanic YES
    XhciPortLimit YES Disable if running macOS 11.3+

    (opens new window) We recommend users either disable this quirk and map before upgrading or map from Windows

    (opens new window) . You may also install macOS 11.2.3 or older.

    The reason being is that UsbInjectAll reimplements builtin macOS functionality without proper current tuning. It is much cleaner to just describe your ports in a single plist-only kext, which will not waste runtime memory and such

    # Scheme

    Settings related to legacy booting(ie. 10.4-10.6), for majority you can skip however for those planning to boot legacy OSes you can see below:

    More in-depth Info

    FuzzyMatch: True

    • Used for ignoring checksums with kernelcache, instead opting for the latest cache available. Can help improve boot performance on many machines in 10.6

    KernelArch: x86_64

    • Set the kernel’s arch type, you can choose between Auto , i386 (32-bit), and x86_64 (64-bit).
    • If you’re booting older OSes which require a 32-bit kernel(ie. 10.4 and 10.5) we recommend to set this to Auto and let macOS decide based on your SMBIOS. See below table for supported values:
      • 10.4-10.5 — x86_64 , i386 or i386-user32
        • i386-user32 refers 32-bit userspace, so 32-bit CPUs must use this(or CPUs missing SSSE3)
        • x86_64 will still have a 32-bit kernelspace however will ensure 64-bit userspace in 10.4/5
      • 10.6 — i386 , i386-user32 , or x86_64
      • 10.7 — i386 or x86_64
      • 10.8 or newer — x86_64

    KernelCache: Auto

    • Set kernel cache type, mainly useful for debugging and so we recommend Auto for best support

    Settings for boot screen (Leave everything as default).

    # Debug

    Helpful for debugging OpenCore boot issues(We’ll be changing everything but DisplayDelay ):

    Quirk Enabled
    AppleDebug YES
    ApplePanic YES
    DisableWatchDog YES
    Target 67

    These values are based of those calculated in OpenCore debugging

    # Security

    Security is pretty self-explanatory, do not skip. We’ll be changing the following:

    Quirk Enabled Comment
    AllowNvramReset YES
    AllowSetDefault YES
    BlacklistAppleUpdate YES
    ScanPolicy 0
    SecureBootModel Default Leave this as Default if running macOS Big Sur or newer. The next page goes into more detail about this setting.
    Vault Optional This is a word, it is not optional to omit this setting. You will regret it if you don’t set it to Optional, note that it is case-sensitive

    AllowNvramReset: YES

    • Allows for NVRAM reset both in the boot picker and when pressing Cmd+Opt+P+R

    AllowSetDefault: YES

    • Allow CTRL+Enter and CTRL+Index to set default boot device in the picker

    ApECID: 0

    • Used for netting personalized secure-boot identifiers, currently this quirk is unreliable due to a bug in the macOS installer so we highly encourage you to leave this as default.

    AuthRestart: NO

    • Enables Authenticated restart for FileVault 2 so password is not required on reboot. Can be considered a security risk so optional

    BlacklistAppleUpdate: YES

    • Used for blocking firmware updates, used as extra level of protection as macOS Big Sur no longer uses run-efi-updater variable

    DmgLoading: Signed

    • Ensures only signed DMGs load

    ExposeSensitiveData: 6

    • Shows more debug information, requires debug version of OpenCore

    Vault: Optional

    • We won’t be dealing vaulting so we can ignore, you won’t boot with this set to Secure
    • This is a word, it is not optional to omit this setting. You will regret it if you don’t set it to Optional , note that it is case-sensitive

    ScanPolicy: 0

      0 allows you to see all drives available, please refer to Security

    (opens new window) section for further details. Will not boot USB devices with this set to default

    SecureBootModel: Disabled

      Controls Apple’s secure boot functionality in macOS, please refer to Security

    (opens new window) section for further details.

  • Note: Users may find upgrading OpenCore on an already installed system can result in early boot failures. To resolve this, see here: Stuck on OCB: LoadImage failed — Security Violation
  • # Tools

    Used for running OC debugging tools like the shell, ProperTree’s snapshot function will add these for you.

    # Entries

    Used for specifying irregular boot paths that can’t be found naturally with OpenCore.

    Won’t be covered here, see 8.6 of Configuration.pdf

    # NVRAM

    Used for OpenCore’s UI scaling, default will work for us. See in-depth section for more info

    Booter Path, mainly used for UI Scaling

    UIScale:

    • 01 : Standard resolution
    • 02 : HiDPI (generally required for FileVault to function correctly on smaller displays)

    DefaultBackgroundColor: Background color used by boot.efi

    • 00000000 : Syrah Black
    • BFBFBF00 : Light Gray

    OpenCore’s NVRAM GUID, mainly relevant for RTCMemoryFixup users

    System Integrity Protection bitmask

    • General Purpose boot-args:
    boot-args Description
    -v This enables verbose mode, which shows all the behind-the-scenes text that scrolls by as you’re booting instead of the Apple logo and progress bar. It’s invaluable to any Hackintosher, as it gives you an inside look at the boot process, and can help you identify issues, problem kexts, etc.
    debug=0x100 This disables macOS’s watchdog which helps prevents a reboot on a kernel panic. That way you can hopefully glean some useful info and follow the breadcrumbs to get past the issues.
    keepsyms=1 This is a companion setting to debug=0x100 that tells the OS to also print the symbols on a kernel panic. That can give some more helpful insight as to what’s causing the panic itself.
    alcid=1 Used for setting layout-id for AppleALC, see supported codecs

    (opens new window) to figure out which layout to use for your specific system. More info on this is covered in the Post-Install Page

    (opens new window)

    • GPU-Specific boot-args:
    boot-args Description
    agdpmod=pikera Used for disabling board ID checks on Navi GPUs (RX 5000 & 6000 series), without this you’ll get a black screen. Don’t use if you don’t have Navi (ie. Polaris and Vega cards shouldn’t use this)
    nvda_drv_vrl=1 Used for enabling Nvidia’s Web Drivers on Maxwell and Pascal cards in Sierra and High Sierra
    -wegnoegpu Used for disabling all other GPUs than the integrated Intel iGPU, useful for those wanting to run newer versions of macOS where their dGPU isn’t supported

      csr-active-config: 00000000

      • Settings for ‘System Integrity Protection’ (SIP). It is generally recommended to change this with csrutil via the recovery partition.
      • csr-active-config by default is set to 00000000 which enables System Integrity Protection. You can choose a number of different values but overall we recommend keeping this enabled for best security practices. More info can be found in our troubleshooting page: Disabling SIP

      run-efi-updater: No

      • This is used to prevent Apple’s firmware update packages from installing and breaking boot order; this is important as these firmware updates (meant for Macs) will not work.

      prev-lang:kbd: <>

      • Needed for non-latin keyboards in the format of lang-COUNTRY:keyboard , recommended to keep blank though you can specify it(Default in Sample config is Russian):
      • American: en-US:0 ( 656e2d55533a30 in HEX)
      • Full list can be found in AppleKeyboardLayouts.txt

      (opens new window)

    • Hint: prev-lang:kbd can be changed into a String so you can input en-US:0 directly instead of converting to HEX
    Key Type Value
    prev-lang:kbd String en-US:0

    # Delete

    Forcibly rewrites NVRAM variables, do note that Add will not overwrite values already present in NVRAM so values like boot-args should be left alone. For us, we’ll be changing the following:

    Quirk Enabled
    WriteFlash YES

    LegacyEnable: NO

    • Allows for NVRAM to be stored on nvram.plist, needed for systems without native NVRAM

    LegacyOverwrite: NO

    • Permits overwriting firmware variables from nvram.plist, only needed for systems without native NVRAM

    LegacySchema

    • Used for assigning NVRAM variables, used with LegacyEnable set to YES

    WriteFlash: YES

    • Enables writing to flash memory for all added variables.

    # PlatformInfo

    For setting up the SMBIOS info, we’ll use CorpNewt’s GenSMBIOS

    For this Haswell example, we chose the iMac15,1 SMBIOS. The typical breakdown is as follows:

    SMBIOS Hardware
    iMac14,4 Haswell with only iGPU
    iMac15,1 Haswell with dGPU
    iMac16,2 Broadwell

    Note: The following SMBIOS are only supported up-to macOS 11, Big Sur. For cases where you must boot Monterey, see below:

    Monterey SMBIOS table

    Note choosing a SMBIOS from the list below for Big Sur or older is not recommended, as Power Management and such can break when using unoptimized SMBIOS.

    SMBIOS Hardware
    iMac16,2 Broadwell with only iGPU
    iMac17,1 Broadwell with dGPU

    Run GenSMBIOS, pick option 1 for downloading MacSerial and Option 3 for selecting out SMBIOS. This will give us an output similar to the following:

    The Type part gets copied to Generic -> SystemProductName.

    The Serial part gets copied to Generic -> SystemSerialNumber.

    The Board Serial part gets copied to Generic -> MLB.

    The SmUUID part gets copied to Generic -> SystemUUID.

    We set Generic -> ROM to either an Apple ROM (dumped from a real Mac), your NIC MAC address, or any random MAC address (could be just 6 random bytes, for this guide we’ll use 11223300 0000 . After install follow the Fixing iServices

    (opens new window) page on how to find your real MAC Address)

    Reminder that you want either an invalid serial or valid serial numbers but those not in use, you want to get a message back like: «Invalid Serial» or «Purchase Date not Validated»

    Automatic: YES

    • Generates PlatformInfo based on Generic section instead of DataHub, NVRAM, and SMBIOS sections

    # Generic

    AdviseFeatures: NO

    • Used for when the EFI partition isn’t first on the Windows drive

    MaxBIOSVersion: NO

    • Sets BIOS version to Max to avoid firmware updates in Big Sur+, mainly applicable for genuine Macs.

    ProcessorType: 0

      Set to 0 for automatic type detection, however this value can be overridden if desired. See AppleSmBios.h

    SpoofVendor: YES

    • Swaps vendor field for Acidanthera, generally not safe to use Apple as a vendor in most case

    SystemMemoryStatus: Auto

    • Sets whether memory is soldered or not in SMBIOS info, purely cosmetic and so we recommend Auto

    UpdateDataHub: YES

    • Update Data Hub fields

    UpdateNVRAM: YES

    UpdateSMBIOS: YES

    UpdateSMBIOSMode: Create

    • Replace the tables with newly allocated EfiReservedMemoryType, use Custom on Dell laptops requiring CustomSMBIOSGuid quirk
    • Setting to Custom with CustomSMBIOSGuid quirk enabled can also disable SMBIOS injection into «non-Apple» OSes however we do not endorse this method as it breaks Bootcamp compatibility. Use at your own risk

    ConnectDrivers: YES

    • Forces .efi drivers, change to NO will automatically connect added UEFI drivers. This can make booting slightly faster, but not all drivers connect themselves. E.g. certain file system drivers may not load.

    # Drivers

    Add your .efi drivers here.

    Only drivers present here should be:

    By default, OpenCore only loads APFS drivers from macOS Big Sur and newer. If you are booting macOS Catalina or earlier, you may need to set a new minimum version/date. Not setting this can result in OpenCore not finding your macOS partition!

    macOS Sierra and earlier use HFS instead of APFS. You can skip this section if booting older versions of macOS.

    Both MinVersion and MinDate need to be set if changing the minimum version.

    macOS Version Min Version Min Date
    High Sierra ( 10.13.6 ) 748077008000000 20180621
    Mojave ( 10.14.6 ) 945275007000000 20190820
    Catalina ( 10.15.4 ) 1412101001000000 20200306
    No restriction -1 -1

    # Audio

    Related to AudioDxe settings, for us we’ll be ignoring(leave as default). This is unrelated to audio support in macOS.

      For further use of AudioDxe and the Audio section, please see the Post Install page: Add GUI and Boot-chime

    # Input

    Related to boot.efi keyboard passthrough used for FileVault and Hotkey support, leave everything here as default as we have no use for these quirks. See here for more details: Security and FileVault

    # Output

    Relating to OpenCore’s visual output, leave everything here as default as we have no use for these quirks.

    # ProtocolOverrides

    Mainly relevant for Virtual machines, legacy macs and FileVault users. See here for more details: Security and FileVault

    # Quirks

    Relating to quirks with the UEFI environment, for us we’ll be changing the following:

    Quirk Enabled Comment
    IgnoreInvalidFlexRatio YES
    UnblockFsConnect NO Needed mainly by HP motherboards

    IgnoreInvalidFlexRatio: YES

    • Fix for when MSR_FLEX_RATIO (0x194) can’t be disabled in the BIOS, required for all pre-Skylake based systems

    DisableSecurityPolicy: NO

    • Disables platform security policy in firmware, recommended for buggy firmwares where disabling Secure Boot does not allow 3rd party firmware drivers to load.
    • If running a Microsoft Surface device, recommended to enable this option

    RequestBootVarRouting: YES

    • Redirects AptioMemoryFix from EFI_GLOBAL_VARIABLE_GUID to OC_VENDOR_VARIABLE_GUID . Needed for when firmware tries to delete boot entries and is recommended to be enabled on all systems for correct update installation, Startup Disk control panel functioning, etc.

    UnblockFsConnect: NO

    • Some firmware block partition handles by opening them in By Driver mode, which results in File System protocols being unable to install. Mainly relevant for HP systems when no drives are listed

    # ReservedMemory

    Used for exempting certain memory regions from OSes to use, mainly relevant for Sandy Bridge iGPUs or systems with faulty memory. Use of this quirk is not covered in this guide

    # Cleaning up

    And now you’re ready to save and place it into your EFI under EFI/OC.

    For those having booting issues, please make sure to read the Troubleshooting section first and if your questions are still unanswered we have plenty of resources at your disposal:

    # Intel BIOS settings

    • Note: Most of these options may not be present in your firmware, we recommend matching up as closely as possible but don’t be too concerned if many of these options are not available in your BIOS

    # Disable

    • Fast Boot
    • Secure Boot
    • Serial/COM Port
    • Parallel Port
    • VT-d (can be enabled if you set DisableIoMapper to YES)
    • CSM
    • Thunderbolt(For initial install, as Thunderbolt can cause issues if not setup correctly)
    • Intel SGX
    • Intel Platform Trust
    • CFG Lock (MSR 0xE2 write protection)(This must be off, if you can’t find the option then enable AppleXcpmCfgLock under Kernel -> Quirks. Your hack will not boot with CFG-Lock enabled)
      • For 10.10 and older, you’ll need to enable AppleCpuPmCfgLock as well

    # Enable

    • VT-x
    • Above 4G decoding
    • Hyper-Threading
    • Execute Disable Bit
    • EHCI/XHCI Hand-off
    • OS type: Windows 8.1/10 UEFI Mode
    • DVMT Pre-Allocated(iGPU Memory): 64MB
    • SATA Mode: AHCI

    # Once done here, we need to edit a couple extra values. Head to the Apple Secure Boot Page

    Источник

    Читайте также:  Айфон 11 pro space grey
    Оцените статью