/* Class = "NSPopUpButton"; ibShadowedToolTip = "Type: plist string\nFailsafe: None\nDescription: Hibernation detection mode. The following modes are supported:\n• None — Avoid hibernation (Recommended).\n• Auto — Use RTC and NVRAM detection.\n• RTC — Use RTC detection.\n• NVRAM — Use NVRAM detection."; ObjectID = "wPi-6s-R0s"; */
/* Class = "NSButtonCell"; title = "Enable display of additional timing and debug information, in Builtin picker in DEBUG and NOOPT builds only."; ObjectID = "xjK-fm-3ud"; */
"xjK-fm-3ud.title" = "Enable display of additional timing and debug information, in Builtin picker in DEBUG and NOOPT builds only.";
/* Class = "NSTextFieldCell"; title = "TakeoffDelay"; ObjectID = "yDl-hK-Eml"; */
/* Class = "NSButton"; ibShadowedToolTip = "Type: plist boolean\nFailsafe: false\nDescription: Some types of firmware may not succeed in booting the operating system quickly, especially in debug mode, which results the watchdog timer aborting the process. This option turns off the watchdog timer."; ObjectID = "LCd-qL-7KC"; */
/* Class = "NSComboBox"; ibShadowedToolTip = "Type: plist string\nFailsafe: Auto\nDescription: Choose specific icon set to be used for boot management.\n\nThe following values are supported:\n• Auto — Automatically select one set of icons based on the DefaultBackground colour.\n• Default — Normal icon set (without prefix).\n• Old — Vintage icon set (Old filename prefix).\n• Modern — Nouveau icon set (Modern filename prefix).\n• Other value — Custom icon set if supported by installed resources."; ObjectID = "M7r-QM-SNm"; */
"M7r-QM-SNm.ibShadowedToolTip" = "Type: plist string\nFailsafe: Auto\nDescription: Choose specific icon set to be used for boot management.\n\nThe following values are supported:\n• Auto — Automatically select one set of icons based on the DefaultBackground colour.\n• Default — Normal icon set (without prefix).\n• Old — Vintage icon set (Old filename prefix).\n• Modern — Nouveau icon set (Modern filename prefix).\n• Other value — Custom icon set if supported by installed resources.";
/* Class = "NSTextField"; ibShadowedToolTip = "Type: plist data 64 bytes\nFailsafe: all zero\nDescription: Password hash used when EnabledPassword is set."; ObjectID = "NCW-lH-X8S"; */
/* Class = "NSButton"; ibShadowedToolTip = "Type: plist boolean\nFailsafe: false\nDescription: Ignore boot options trying to update Apple peripheral firmware (e.g. MultiUpdater.EFI).\n\nNote: This option exists due to some operating systems, namely macOS Big Sur, being incapable of disabling firmware updates with the NVRAM variable (run-EFI-updater)."; ObjectID = "Nph-Bb-8b6"; */
"Nph-Bb-8b6.ibShadowedToolTip" = "忽略嘗試更新Apple外設韌體的引導選項 (例如MultiUpdater.EFI).\n\n注意: 由於某些操作系统（即macOS Big Sur）無法使用NVRAM變量（run-EFI-updater）停用韌體更新，因此存在此選項.";
/* Class = "NSTextFieldCell"; title = "BootProtect"; ObjectID = "OeD-Mz-a2a"; */
"OeD-Mz-a2a.title" = "BootProtect";
/* Class = "NSButton"; ibShadowedToolTip = "Type: plist boolean\nFailsafe: false\nDescription: Enable screen reader by default in boot picker.\nFor macOS bootloader screen reader preference is set in preferences.EFIres archive in isVOEnabled.int32 file and is controlled by the operating system. For OpenCore screen reader support this option is an independent equivalent. Toggling screen reader support in both OpenCore boot picker and macOS bootloader FileVault 2 login window can also be done with Command + F5 key combination.\nNote: screen reader requires working audio support, see UEFI Audio Properties section for more details."; ObjectID = "PDS-bo-Qx8"; */
/* Class = "NSPopUpButton"; ibShadowedToolTip = "Type: plist string\nFailsafe: Auto\nDescription: Choose specific icon set used for boot management.\n\nThe following values are supported:\n• Auto — Automatically select one set of icons based on DefaultBackground colour.\n• Default — Normal icon set (without prEFIx).\n• Old — Vintage icon set (Old filename prEFIx).\n• Modern — Nouveau icon set (Modern filename prEFIx).\n• Other value — Custom icon set if supported by the resources."; ObjectID = "vsq-vB-3zg"; */
"vsq-vB-3zg.ibShadowedToolTip" = "選擇用於OC引導選單的指定圖示主題。\n\n支援以下值:\n• Auto — 根據預設背景顏色自動選擇一組圖示。\n• Default — (預設主題（所有圖示文件無前缀名稱，比如Apple.icns、Background.icns)。\n• Old — Old主題(此為官方樣板主題,所有圖示文件名前缀為Old,比如OldApple.icns、OldBackground.icns)。\n• Modern — Modern主題(所有圖示文件名前缀為Modern,比如ModernApple.icns、ModernBackground.icns)。\n• 其他值 — 可以自訂自己的主題風格,所有圖示文件名加自己的前缀,比如MyApple.icns、MyBackground.icns,那麼自訂的主題值就填寫My。\n\n注意事項:\n選擇任意一個主題,包括自訂主題的圖示文件路徑必須在EFI/OC/Resources/Image下有對應格式的文件名圖示,對於0.6.6以上版本，必須有包含Left.icns和Right.icns的圖示文件名，否則會變為文字模式選單";
/* Class = "NSButton"; ibShadowedToolTip = "Type: plist boolean\nFailsafe: false\nDescription: Enable modifier hotkey handling in boot picker.\nIn addition to action hotkeys, which are partially described in UsePicker section and are normally handled by Apple BDS, there exist modifier keys, which are handled by operating system bootloader, namely boot.EFI. These keys allow to change operating system behaviour by providing different boot modes.\n\nOn types of firmware, it may be problematic to use modifier keys due to driver incompatibilities. To workaround this problem this option allows registering select hotkeys in a more permissive manner from within boot picker. Such extensions include the support of tapping on keys in addition to holding and pressing Shift along with other keys instead of just Shift alone, which is not detectable on many PS/2 keyboards. This list of known modifier hotkeys includes:\n• CMD+C+MINUS — disable board compatibility checking.\n• CMD+K — boot release kernel, similar to kcsuffix=release.\n• CMD+S — single user mode.\n• CMD+S+MINUS — disable KASLR slide, requires disabled SIP.\n• CMD+V — verbose mode.\n• Shift — safe mode."; ObjectID = "vvg-w7-KxC"; */
/* Class = "NSPopUpButton"; ibShadowedToolTip = "Type: plist string\nFailsafe: None\nDescription: Hibernation detection mode. The following modes are supported:\n• None — Avoid hibernation (Recommended).\n• Auto — Use RTC and NVRAM detection.\n• RTC — Use RTC detection.\n• NVRAM — Use NVRAM detection."; ObjectID = "wPi-6s-R0s"; */
/* Class = "NSPopUpButton"; ibShadowedToolTip = "Type: plist string\nFailsafe: None\nDescription: Attempt to provide bootloader persistence.\nValid values:\n• None — do nothing.\n• Bootstrap — create or update top-priority \\EFI\\OC\\Bootstrap\\Bootstrap.EFI boot option in UEFI variable storage at bootloader startup. For this option to work RequestBootVarRouting is required to be enabled.\n• BootstrapShort — create a short boot option instead of a complete one, otherwise equivalent to Bootstrap.\n\nThis variant is useful for some older firmwares, Insyde in particular, but possibly others, which cannot handle full device paths.\nThis option provides integration with third-party operating system installation and upgrade at the times they overwrite \\EFI\\BOOT\\BOOTx64.EFI file. By creating a custom option in Bootstrap mode this file path becomes no longer used for bootstrapping OpenCore.\n\nNote 1: Some types of firmware may have faulty NVRAM, no boot option support, or other incompatibilities. While unlikely, the use of this option may even cause boot failures. This option should be used without any warranty exclusively on the boards known to be compatible.\n\nNote 2: Be aware that while NVRAM reset executed from OpenCore should not erase the boot option created in Bootstrap, executing NVRAM reset prior to loading OpenCore will remove it. For significant implementation updates (e.g. in OpenCore 0.6.4) make sure to perform NVRAM reset with Bootstrap disabled before reenabling."; ObjectID = "xNT-zI-wd8"; */
/* Class = "NSButtonCell"; title = "Enable display of additional timing and debug information, in Builtin picker in DEBUG and NOOPT builds only."; ObjectID = "xjK-fm-3ud"; */
"xjK-fm-3ud.title" = "Enable display of additional timing and debug information, in Builtin picker in DEBUG and NOOPT builds only.";
/* Class = "NSTextFieldCell"; title = "TakeoffDelay"; ObjectID = "yDl-hK-Eml"; */
/* Class = "NSTextFieldCell"; title = "KernelArch"; ObjectID = "Edd-Fj-thV"; */
"Edd-Fj-thV.title" = "KernelArch";
/* Class = "NSButton"; ibShadowedToolTip = "Type: plist boolean\nFailsafe: false\nRequirement: 10.4\nDescription: Disables PKG_CST_CONFIG_CONTROL (0xE2) MSR modification in AppleIntelCPUPowerManage- ment.kext, commonly causing early kernel panic, when it is locked from writing.\n\nSome types of firmware lock the PKG_CST_CONFIG_CONTROL MSR register and the bundled VerifyMsrE2 tool can be used to check its state. Note that some types of firmware only have this register locked on some cores.\nAs modern firmware provide a CFG Lock setting that allows configuring the PKG_CST_CONFIG_CONTROL MSR register lock, this option should be avoided whenever possible. On APTIO firmware that do not provide a CFG Lock setting in the GUI, it is possible to access the option directly:\n(a) Download UEFITool and IFR-Extractor.\n(b) Open the firmware image in UEFITool and find CFG Lock unicode string. If it is not present, the firmware may not have this option and the process should therefore be discontinued.\n(c) Extract the Setup.bin PE32 Image Section (the UEFITool found) through the Extract Body menu option.\n(d) Run IFR-Extractor on the extracted file (e.g. ./ifrextract Setup.bin Setup.txt).\n(e) Find CFG Lock, VarStoreInfo (VarOffset/VarName): in Setup.txt and remember the offset right after it (e.g. 0x123).\n(f) Download and run Modified GRUB Shell compiled by brainsucker or use a newer version by datasone.\n(g) Enter setup_var 0x123 0x00 command, where 0x123 should be replaced by the actual offset, and reboot.\n\nWarning: Variable offsets are unique not only to each motherboard but even to its firmware version. Never ever try to use an offset without checking."; ObjectID = "FUx-RJ-QTK"; */
"FUx-RJ-QTK.ibShadowedToolTip" = "Type: plist boolean\nFailsafe: false\nRequirement: 10.4\nDescription: Disables PKG_CST_CONFIG_CONTROL (0xE2) MSR modification in AppleIntelCPUPowerManage- ment.kext, commonly causing early kernel panic, when it is locked from writing.\n\nSome types of firmware lock the PKG_CST_CONFIG_CONTROL MSR register and the bundled VerifyMsrE2 tool can be used to check its state. Note that some types of firmware only have this register locked on some cores.\nAs modern firmware provide a CFG Lock setting that allows configuring the PKG_CST_CONFIG_CONTROL MSR register lock, this option should be avoided whenever possible. On APTIO firmware that do not provide a CFG Lock setting in the GUI, it is possible to access the option directly:\n(a) Download UEFITool and IFR-Extractor.\n(b) Open the firmware image in UEFITool and find CFG Lock unicode string. If it is not present, the firmware may not have this option and the process should therefore be discontinued.\n(c) Extract the Setup.bin PE32 Image Section (the UEFITool found) through the Extract Body menu option.\n(d) Run IFR-Extractor on the extracted file (e.g. ./ifrextract Setup.bin Setup.txt).\n(e) Find CFG Lock, VarStoreInfo (VarOffset/VarName): in Setup.txt and remember the offset right after it (e.g. 0x123).\n(f) Download and run Modified GRUB Shell compiled by brainsucker or use a newer version by datasone.\n(g) Enter setup_var 0x123 0x00 command, where 0x123 should be replaced by the actual offset, and reboot.\n\nWarning: Variable offsets are unique not only to each motherboard but even to its firmware version. Never ever try to use an offset without checking.";
/* Class = "NSButton"; ibShadowedToolTip = "Type: plist boolean\nFailsafe: false\nRequirement: 10.4\nDescription: Disables PKG_CST_CONFIG_CONTROL (0xE2) MSR modification in AppleIntelCPUPowerManage- ment.kext, commonly causing early kernel panic, when it is locked from writing.\n\nSome types of firmware lock the PKG_CST_CONFIG_CONTROL MSR register and the bundled ControlMsrE2 tool can be used to check its state. Note that some types of firmware only have this register locked on some cores. As modern firmware provide a CFG Lock setting that allows configuring the PKG_CST_CONFIG_CONTROL MSR register lock, this option should be avoided whenever possible.\n\nOn APTIO firmware that do not provide a CFG Lock setting in the GUI, it is possible to access the option directly:\n(a) Download UEFITool and IFR-Extractor.\n(b) Open the firmware image in UEFITool and find CFG Lock unicode string. If it is not present, the firmware may not have this option and the process should therefore be discontinued.\n(c) Extract the Setup.bin PE32 Image Section (the UEFITool found) through the Extract Body menu option.\n(d) Run IFR-Extractor on the extracted file (e.g. ./ifrextract Setup.bin Setup.txt).\n(e) Find CFG Lock, VarStoreInfo (VarOffset/VarName): in Setup.txt and remember the offset right after it (e.g. 0x123).\n(f) Download and run Modified GRUB Shell compiled by brainsucker or use a newer version by datasone.\n(g) Enter setup_var 0x123 0x00 command, where 0x123 should be replaced by the actual offset, and reboot.\n\nWarning: Variable offsets are unique not only to each motherboard but even to its firmware version. Never ever try to use an offset without checking.\n\nOn selected platforms, the ControlMsrE2 tool can also change such hidden options. Pass desired argument: lock,\nunlock for CFG Lock. Or pass interactive to find and modify other hidden options.\n\nAs a last resort, consider patching the BIOS (for advanced users only)."; ObjectID = "FUx-RJ-QTK"; */
"FUx-RJ-QTK.ibShadowedToolTip" = "Type: plist boolean\nFailsafe: false\nRequirement: 10.4\nDescription: Disables PKG_CST_CONFIG_CONTROL (0xE2) MSR modification in AppleIntelCPUPowerManage- ment.kext, commonly causing early kernel panic, when it is locked from writing.\n\nSome types of firmware lock the PKG_CST_CONFIG_CONTROL MSR register and the bundled ControlMsrE2 tool can be used to check its state. Note that some types of firmware only have this register locked on some cores. As modern firmware provide a CFG Lock setting that allows configuring the PKG_CST_CONFIG_CONTROL MSR register lock, this option should be avoided whenever possible.\n\nOn APTIO firmware that do not provide a CFG Lock setting in the GUI, it is possible to access the option directly:\n(a) Download UEFITool and IFR-Extractor.\n(b) Open the firmware image in UEFITool and find CFG Lock unicode string. If it is not present, the firmware may not have this option and the process should therefore be discontinued.\n(c) Extract the Setup.bin PE32 Image Section (the UEFITool found) through the Extract Body menu option.\n(d) Run IFR-Extractor on the extracted file (e.g. ./ifrextract Setup.bin Setup.txt).\n(e) Find CFG Lock, VarStoreInfo (VarOffset/VarName): in Setup.txt and remember the offset right after it (e.g. 0x123).\n(f) Download and run Modified GRUB Shell compiled by brainsucker or use a newer version by datasone.\n(g) Enter setup_var 0x123 0x00 command, where 0x123 should be replaced by the actual offset, and reboot.\n\nWarning: Variable offsets are unique not only to each motherboard but even to its firmware version. Never ever try to use an offset without checking.\n\nOn selected platforms, the ControlMsrE2 tool can also change such hidden options. Pass desired argument: lock,\nunlock for CFG Lock. Or pass interactive to find and modify other hidden options.\n\nAs a last resort, consider patching the BIOS (for advanced users only).";
/* Class = "NSTextFieldCell"; title = "ExitBootServicesDelay"; ObjectID = "wxD-TC-lrQ"; */
"wxD-TC-lrQ.title" = "ExitBootServicesDelay";
/* Class = "NSTextField"; ibShadowedToolTip = "Type: plist integer\nFailsafe: 0\nDescription: Remove key unless it was submitted during this timeout in 10 ms units.\n\nAppleKeyMapAggregator protocol is supposed to contain a fixed length buffer of currently pressed keys. However, the majority of the drivers only report key presses as interrupts and pressing and holding the key on the keyboard results in subsequent submissions of this key with some defined time interval. As a result we use a timeout to remove once pressed keys from the buffer once the timeout expires and no new submission of this key happened.\n\nThis option allows setting this timeout based on the platform. The recommended value for the majority of platforms is 5 (50 milliseconds). For reference, holding one key on VMware will repeat it roughly every 20 milliseconds and the same value for APTIO V is 30-40 milliseconds. Thus, it is possible to set a slightly lower value on faster platforms and a slightly higher value on slower platforms for more responsive input.\n\nPressing keys one after the other results in delays of at least 60 and 100 milliseconds for the same platforms.\n\nNote: Some platforms may require different values, which may be higher or lower. For example, when detecting key misses in OpenCanopy, try increasing this value (e.g. to 10), and when detecting key stall, try decreasing this value. Since every platform is different, it may be prudent to check every value from 1 to 25 (10 to 250 milliseconds)."; ObjectID = "xNH-9V-3kd"; */
"xNH-9V-3kd.ibShadowedToolTip" = "Type: plist integer\nFailsafe: 0\nDescription: Remove key unless it was submitted during this timeout in 10 ms units.\n\nAppleKeyMapAggregator protocol is supposed to contain a fixed length buffer of currently pressed keys. However, the majority of the drivers only report key presses as interrupts and pressing and holding the key on the keyboard results in subsequent submissions of this key with some defined time interval. As a result we use a timeout to remove once pressed keys from the buffer once the timeout expires and no new submission of this key happened.\n\nThis option allows setting this timeout based on the platform. The recommended value for the majority of platforms is 5 (50 milliseconds). For reference, holding one key on VMware will repeat it roughly every 20 milliseconds and the same value for APTIO V is 30-40 milliseconds. Thus, it is possible to set a slightly lower value on faster platforms and a slightly higher value on slower platforms for more responsive input.\n\nPressing keys one after the other results in delays of at least 60 and 100 milliseconds for the same platforms.\n\nNote: Some platforms may require different values, which may be higher or lower. For example, when detecting key misses in OpenCanopy, try increasing this value (e.g. to 10), and when detecting key stall, try decreasing this value. Since every platform is different, it may be prudent to check every value from 1 to 25 (10 to 250 milliseconds).";
/* Class = "NSTextField"; ibShadowedToolTip = "Type: plist integer\nFailsafe: 0\nDescription: Treat duplicate key presses as held keys if they arrive during this timeout, in 10 ms units. Only applies to systems using KeySupport.\n\nAppleKeyMapAggregator protocol is supposed to contain a fixed length buffer of currently pressed keys. However, the majority of the drivers which require KeySupport report key presses as interrupts, with automatically generated key repeat behaviour with some defined initial and subsequent delay. As a result, to emulate the raw key behaviour required by several Apple boot systems, we use a timeout to merge multiple repeated keys which are submitted within a small timeout window\n\nThis option allows setting this timeout based on the platform. The recommended value for the majority of platforms is from 5 (50 milliseconds) to 7 (70 milliseconds), although values up to 9 (90 milliseconds) have been observed to be required on some PS/2 systems.For reference, holding a key on VMware will repeat roughly every 20 milliseconds and the equivalent value for APTIO V is 30-40 milliseconds. KeyForgetThreshold should be configured to be longer than this. Thus, it is possible to configure a lower KeyForgetThreshold value on platforms with a faster native driver key repeat rate, for more responsive input, and it is required to set a higher value on slower platforms.\n\nPressing keys one after the other results in delays of at least 60 and 100 milliseconds for the same platforms. Ideally, KeyForgetThreshold should remain lower than this value, to avoid merging real key presses.\n\nNote}: If you wish to fine tune this value, a good heuristic is to use the 'set default' indicator within either OpenCanopy or the builtin picker. When KeyForgetThreshold is configured correctly, this indicator should flicker once, when first pressing and holding the CTRL key, and then after a further very brief interval should go on and stay on. (The initial flicker is an unavoidable artefact of using KeySupport to emulate raw keyboard data.) If KeyForgetThreshold is configured too low for the system, then the 'set default' indicator will continue to flicker while CTRL is held. Configure the lowest value which causes this indicator to go on and stay on after the first initial flicker."; ObjectID = "xNH-9V-3kd"; */
"xNH-9V-3kd.ibShadowedToolTip" = "Type: plist integer\nFailsafe: 0\nDescription: Treat duplicate key presses as held keys if they arrive during this timeout, in 10 ms units. Only applies to systems using KeySupport.\n\nAppleKeyMapAggregator protocol is supposed to contain a fixed length buffer of currently pressed keys. However, the majority of the drivers which require KeySupport report key presses as interrupts, with automatically generated key repeat behaviour with some defined initial and subsequent delay. As a result, to emulate the raw key behaviour required by several Apple boot systems, we use a timeout to merge multiple repeated keys which are submitted within a small timeout window\n\nThis option allows setting this timeout based on the platform. The recommended value for the majority of platforms is from 5 (50 milliseconds) to 7 (70 milliseconds), although values up to 9 (90 milliseconds) have been observed to be required on some PS/2 systems.For reference, holding a key on VMware will repeat roughly every 20 milliseconds and the equivalent value for APTIO V is 30-40 milliseconds. KeyForgetThreshold should be configured to be longer than this. Thus, it is possible to configure a lower KeyForgetThreshold value on platforms with a faster native driver key repeat rate, for more responsive input, and it is required to set a higher value on slower platforms.\n\nPressing keys one after the other results in delays of at least 60 and 100 milliseconds for the same platforms. Ideally, KeyForgetThreshold should remain lower than this value, to avoid merging real key presses.\n\nNote}: If you wish to fine tune this value, a good heuristic is to use the 'set default' indicator within either OpenCanopy or the builtin picker. When KeyForgetThreshold is configured correctly, this indicator should flicker once, when first pressing and holding the CTRL key, and then after a further very brief interval should go on and stay on. (The initial flicker is an unavoidable artefact of using KeySupport to emulate raw keyboard data.) If KeyForgetThreshold is configured too low for the system, then the 'set default' indicator will continue to flicker while CTRL is held. Configure the lowest value which causes this indicator to go on and stay on after the first initial flicker.";
/* Class = "NSTextField"; ibShadowedToolTip = "Type: plist integer\nFailsafe: 0\nDescription: Adds delay in microseconds after EXIT_BOOT_SERVICES event.\n\nThis is a very rough workaround to circumvent the Still waiting for root device message on some APTIO IV firmware (ASUS Z87-Pro) particularly when using FileVault 2. It appears that for some reason, they execute code in parallel to EXIT_BOOT_SERVICES, which results in the SATA controller being inaccessible from macOS. A better approach is required and Acidanthera is open to suggestions. Expect 3 to 5 seconds to be adequate when this quirk is needed."; ObjectID = "yXm-Kd-A6O"; */
"yXm-Kd-A6O.ibShadowedToolTip" = "Type: plist integer\nFailsafe: 0\nDescription: Adds delay in microseconds after EXIT_BOOT_SERVICES event.\n\nThis is a very rough workaround to circumvent the Still waiting for root device message on some APTIO IV firmware (ASUS Z87-Pro) particularly when using FileVault 2. It appears that for some reason, they execute code in parallel to EXIT_BOOT_SERVICES, which results in the SATA controller being inaccessible from macOS. A better approach is required and Acidanthera is open to suggestions. Expect 3 to 5 seconds to be adequate when this quirk is needed.";
/* Class = "NSTextFieldCell"; title = "PickerVariant"; ObjectID = "4Mc-Dm-vYw"; */
"4Mc-Dm-vYw.title" = "PickerVariant";
/* Class = "NSPopUpButton"; ibShadowedToolTip = "Type: plist string\nFailsafe: Builtin\nDescription: Choose boot picker used for boot management.\nPicker describes underlying boot management with an optional user interface responsible for handling boot\noptions. The following values are supported:\n• Builtin — boot management is handled by OpenCore, a simple text only user interface is used.\n• External — an external boot management protocol is used if available. Otherwise Builtin mode is used.\n• Apple — Apple boot management is used if available. Otherwise Builtin mode is used.\n\nUpon success External mode will entirely disable all boot management in OpenCore except policy enforcement. See OpenCanopy plugin for an example of a custom user interface.\nOpenCore built-in boot picker contains a set of actions chosen during the boot process. The list of supported actions is similar to Apple BDS and in general can be accessed by holding action hotkeys during boot process. Currently the following actions are considered:\n• Default — this is the default option, and it lets OpenCore built-in boot picker to loads the default boot option as specified in Startup Disk preference pane.\n• ShowPicker — this option forces picker to show. Normally it can be achieved by holding OPT key during boot. Setting ShowPicker to true will make ShowPicker the default option.\n• ResetNvram — this option performs select UEFI variable erase and is normally achieved by holding CMD+OPT+P+R key combination during boot. Another way to erase UEFI variables is to choose Reset NVRAM in the picker. This option requires AllowNvramReset to be set to true.\n• BootApple — this options performs booting to the first found Apple operating system unless the default chosen operating system is already made by Apple. Hold X key to choose this option.\n• BootAppleRecovery — this option performs booting to Apple operating system recovery. Either the one related to the default chosen operating system, or first found in case default chosen operating system is not made by Apple or has no recovery. Hold CMD+R key combination to choose this option.\n\nNote 1: Activated KeySupport, OpenUsbKbDxe, or similar driver is required for key handling to work. On several types of firmware, it is not possible to get all the key functions.\n\nNote 2: In addition to OPT OpenCore supports Escape key to display picker when ShowPicker is disabled. This key exists for Apple picker mode and for firmware with PS/2 keyboards that fail to report held OPT keys and requiring continual presses of the Escape key to access the boot menu.\n\nNote 3: On Macs with problematic GOP, it may be difficult to access the Apple BootPicker. The BootKicker utility can be blessed to workaround this problem even without loading OpenCore. On some Macs however, the BootKicker utility cannot be run from OpenCore."; ObjectID = "5Or-M0-hZS"; */
"5Or-M0-hZS.ibShadowedToolTip" = "Sélectionnez un sélecteur de démarrage pour la gestion du démarrage \nSupporte les valeurs suivantes: \nBuiltin (par défaut) - La gestion du démarrage est gérée par OpenCore, à l'aide d'une interface utilisateur en texte brut. \n • Protocole de gestion de démarrage externe à usage externe (si disponible), sinon, le mode intégré sera utilisé. \n • Apple-Use Apple Boot Management (si disponible), sinon, le mode intégré sera utilisé.";
...
...
@@ -116,6 +119,9 @@
/* Class = "NSButtonCell"; title = "OC_SCAN_ALLOW_DEVICE_PCI"; ObjectID = "I0K-dq-ofU"; */
"I0K-dq-ofU.title" = "OC_SCAN_ALLOW_DEVICE_PCI";
/* Class = "NSPopUpButton"; ibShadowedToolTip = "Type: plist string\nFailsafe: Disabled\nDescription: Register the launcher option in the firmware preferences for persistence.\n\nValid values:\n• Disabled — do nothing.\n• Full — create or update the top priority boot option in UEFI variable storage at bootloader startup.\n\t– For this option to work, RequestBootVarRouting is required to be enabled.\n• Short — create a short boot option instead of a complete one.\n\t– This variant is useful for some older types of firmware, typically from Insyde, that are unable to manage full device paths.\n• System — create no boot option but assume specified custom option is blessed.\n\t– This variant is useful when relying on ForceBooterSignature quirk and OpenCore launcher path management happens through bless utilities without involving OpenCore.\n\nThis option allows integration with third-party operating system installation and upgrades (which may overwrite the \\EFI\\BOOT\\BOOTx64.efi file). The BOOTx64.efi file is no longer used for bootstrapping OpenCore if a custom option is created. The custom path used for bootstrapping can be specified by using the LauncherPath option.\n\nNote 1: Some types of firmware may have NVRAM implementation flaws, no boot option support, or other incompatibilities. While unlikely, the use of this option may result in boot failures and should only be used exclusively on the boards known to be compatible. Refer to acidanthera/bugtracker#1222 for some known issues affecting Haswell and other boards.\n\nNote 2: While NVRAM resets executed from OpenCore would not typically erase the boot option created in Bootstrap, executing NVRAM resets prior to loading OpenCore will erase the boot option. Therefore, for significant implementation updates, such as was the case with OpenCore 0.6.4, an NVRAM reset should be executed with Bootstrap disabled after which it can be re-enabled."; ObjectID = "IqM-FZ-Tdv"; */
"IqM-FZ-Tdv.ibShadowedToolTip" = "Type: plist string\nFailsafe: Disabled\nDescription: Register the launcher option in the firmware preferences for persistence.\n\nValid values:\n• Disabled — do nothing.\n• Full — create or update the top priority boot option in UEFI variable storage at bootloader startup.\n\t– For this option to work, RequestBootVarRouting is required to be enabled.\n• Short — create a short boot option instead of a complete one.\n\t– This variant is useful for some older types of firmware, typically from Insyde, that are unable to manage full device paths.\n• System — create no boot option but assume specified custom option is blessed.\n\t– This variant is useful when relying on ForceBooterSignature quirk and OpenCore launcher path management happens through bless utilities without involving OpenCore.\n\nThis option allows integration with third-party operating system installation and upgrades (which may overwrite the \\EFI\\BOOT\\BOOTx64.efi file). The BOOTx64.efi file is no longer used for bootstrapping OpenCore if a custom option is created. The custom path used for bootstrapping can be specified by using the LauncherPath option.\n\nNote 1: Some types of firmware may have NVRAM implementation flaws, no boot option support, or other incompatibilities. While unlikely, the use of this option may result in boot failures and should only be used exclusively on the boards known to be compatible. Refer to acidanthera/bugtracker#1222 for some known issues affecting Haswell and other boards.\n\nNote 2: While NVRAM resets executed from OpenCore would not typically erase the boot option created in Bootstrap, executing NVRAM resets prior to loading OpenCore will erase the boot option. Therefore, for significant implementation updates, such as was the case with OpenCore 0.6.4, an NVRAM reset should be executed with Bootstrap disabled after which it can be re-enabled.";
/* Class = "NSButtonCell"; title = "AllowNvramReset"; ObjectID = "Jpe-QB-x2r"; */
"Jpe-QB-x2r.title" = "AllowNvramReset";
...
...
@@ -131,6 +137,9 @@
/* Class = "NSButton"; ibShadowedToolTip = "Type: plist boolean\nFailsafe: false\nDescription: Some types of firmware may not succeed in booting the operating system quickly, especially in debug mode, which results the watchdog timer aborting the process. This option turns off the watchdog timer."; ObjectID = "LCd-qL-7KC"; */
"LCd-qL-7KC.ibShadowedToolTip" = "Si macOS se bloque à certains endroits au démarrage, il peut être nécessaire de le régler sur OUI, ce qui est généralement utilisé pour éliminer l'erreur";
/* Class = "NSComboBox"; ibShadowedToolTip = "Type: plist string\nFailsafe: Auto\nDescription: Choose specific icon set to be used for boot management.\n\nThe following values are supported:\n• Auto — Automatically select one set of icons based on the DefaultBackground colour.\n• Default — Normal icon set (without prefix).\n• Old — Vintage icon set (Old filename prefix).\n• Modern — Nouveau icon set (Modern filename prefix).\n• Other value — Custom icon set if supported by installed resources."; ObjectID = "M7r-QM-SNm"; */
"M7r-QM-SNm.ibShadowedToolTip" = "Type: plist string\nFailsafe: Auto\nDescription: Choose specific icon set to be used for boot management.\n\nThe following values are supported:\n• Auto — Automatically select one set of icons based on the DefaultBackground colour.\n• Default — Normal icon set (without prefix).\n• Old — Vintage icon set (Old filename prefix).\n• Modern — Nouveau icon set (Modern filename prefix).\n• Other value — Custom icon set if supported by installed resources.";
/* Class = "NSTextField"; ibShadowedToolTip = "Type: plist data 64 bytes\nFailsafe: all zero\nDescription: Password hash used when EnabledPassword is set."; ObjectID = "NCW-lH-X8S"; */
"NCW-lH-X8S.ibShadowedToolTip" = "Type: plist data 64 bytes\nFailsafe: all zero\nDescription: Password hash used when EnabledPassword is set.";
...
...
@@ -143,9 +152,6 @@
/* Class = "NSButton"; ibShadowedToolTip = "Type: plist boolean\nFailsafe: false\nDescription: Ignore boot options trying to update Apple peripheral firmware (e.g. MultiUpdater.efi).\n\nNote: This option exists due to some operating systems, namely macOS Big Sur, being incapable of disabling firmware updates with the NVRAM variable (run-efi-updater)."; ObjectID = "Nph-Bb-8b6"; */
"Nph-Bb-8b6.ibShadowedToolTip" = "Type: plist boolean\nFailsafe: false\nDescription: Ignore boot options trying to update Apple peripheral firmware (e.g. MultiUpdater.efi).\n\nNote: This option exists due to some operating systems, namely macOS Big Sur, being incapable of disabling firmware updates with the NVRAM variable (run-efi-updater).";
/* Class = "NSTextFieldCell"; title = "BootProtect"; ObjectID = "OeD-Mz-a2a"; */
"OeD-Mz-a2a.title" = "BootProtect";
/* Class = "NSButton"; ibShadowedToolTip = "Type: plist boolean\nFailsafe: false\nDescription: Enable screen reader by default in boot picker.\nFor macOS bootloader screen reader preference is set in preferences.efires archive in isVOEnabled.int32 file and is controlled by the operating system. For OpenCore screen reader support this option is an independent equivalent. Toggling screen reader support in both OpenCore boot picker and macOS bootloader FileVault 2 login window can also be done with Command + F5 key combination.\nNote: screen reader requires working audio support, see UEFI Audio Properties section for more details."; ObjectID = "PDS-bo-Qx8"; */
"PDS-bo-Qx8.ibShadowedToolTip" = "Activez la fonction d'écran assistant vocal dans le sélecteur de démarrage. \nVous pouvez également utiliser la combinaison de touches Commande + F5 pour changer la fonction d’assistant vocal de l’écran dans le sélecteur de démarrage OpenCore et la fenêtre de connexion FileVault 2 du chargeur de démarrage macOS. \nRemarque: le pilote audio AudioDxe.ef doit être chargé pour la fonction d'assistance vocale à l'écran.";
...
...
@@ -194,6 +200,9 @@
/* Class = "NSTextFieldCell"; title = "Hibernate Mode"; ObjectID = "TmR-t7-bmq"; */
/* Class = "NSTextField"; ibShadowedToolTip = "Type: plist string\nFailsafe: Default\nDescription: Launch path for the LauncherOption property.\n\nDefault points to OpenCore.efi. User specified paths, e.g. \\EFI\\SomeLauncher.efi, can be used to provide custom loaders, which are supposed to load OpenCore.efi themselves."; ObjectID = "Uqn-Ww-mAH"; */
"Uqn-Ww-mAH.ibShadowedToolTip" = "Type: plist string\nFailsafe: Default\nDescription: Launch path for the LauncherOption property.\n\nDefault points to OpenCore.efi. User specified paths, e.g. \\EFI\\SomeLauncher.efi, can be used to provide custom loaders, which are supposed to load OpenCore.efi themselves.";
/* Class = "NSButtonCell"; title = "Enable logging to file"; ObjectID = "Uz7-yL-WDQ"; */
"Uz7-yL-WDQ.title" = "Activer la journalisation dans un fichier";
...
...
@@ -296,6 +305,9 @@
/* Class = "NSButtonCell"; title = "OC_SCAN_ALLOW_DEVICE_ATAPI"; ObjectID = "i2m-65-2vq"; */
/* Class = "NSTextFieldCell"; title = "LauncherOption"; ObjectID = "i5B-oK-z1D"; */
"i5B-oK-z1D.title" = "LauncherOption";
/* Class = "NSButtonCell"; title = "Download/Update tools"; ObjectID = "i6P-Lb-eX2"; */
"i6P-Lb-eX2.title" = "Download/Update tools";
...
...
@@ -347,6 +359,9 @@
/* Class = "NSButtonCell"; title = "AllowSetDefault"; ObjectID = "qpq-Le-cti"; */
"qpq-Le-cti.title" = "AllowSetDefault";
/* Class = "NSButtonCell"; title = "Enable pointer control in the picker when available"; ObjectID = "r8W-nu-W4X"; */
"r8W-nu-W4X.title" = "Enable pointer control in the picker when available";
/* Class = "NSButton"; ibShadowedToolTip = "Type: plist boolean\nFailsafe: false\nDescription: Allow CTRL+Enter and CTRL+Index handling to set the default boot option in boot picker."; ObjectID = "rQF-20-vFl"; */
"rQF-20-vFl.ibShadowedToolTip" = "Autorisez CTRL + Entrée ou CTRL + Index (numéro d'élément du menu de démarrage) pour définir l'option de démarrage par défaut suivante dans le menu de démarrage.";
...
...
@@ -401,6 +416,9 @@
/* Class = "NSButtonCell"; title = "ApplePanic"; ObjectID = "yaU-Lw-vco"; */
"yaU-Lw-vco.title" = "ApplePanic";
/* Class = "NSTextFieldCell"; title = "LauncherPath"; ObjectID = "ykx-r5-I09"; */
"ykx-r5-I09.title" = "LauncherPath";
/* Class = "NSButtonCell"; title = "Expose printable booter path as an UEFI variable."; ObjectID = "z6D-gM-UDa"; */
"z6D-gM-UDa.title" = "Exposez le chemin de démarrage imprimable en tant que variable UEFI.";
