Seems we have to check for both the apple value and for the UEFI value if we #error "Can not determine the default boot file name for unknown processor type!"Īpple seems to have a different EFI_REMOVABLE_MEDIA_FILE_NAME value, so it #define EFI_REMOVABLE_MEDIA_FILE_NAME L"\\EFI\\BOOT\\BOOTEBC.EFI" and IPF processor, so need define boot file name for EBC architecture here. Uefi specification only defines the default boot file name for IA32, X64
#CLOVER EFI BOOTLOADER WONT INSTALL ON MOJAVE CODE#
From the source code ( /src/VBox/Devices/EFI/Firmware/IntelFrameworkModulePkg/Library/GenericBdsLib/InternalBdsLib.h):Ĭode: Select all Expand view Collapse view #if !defined (EFI_REMOVABLE_MEDIA_FILE_NAME)
But, as with all things Apple, they had to make it " different". You can read it and get the "appropriate" boot file. The EFI partition in a typical OSX installation (and I think for everything EFI), is a 200 MB, FAT32 partition with the "boot" and "ESP" (EFI System Partition) flags. The filesystem is browseable all right, that part is done. Mpack wrote:You have to support whatever filesystem is used by the boot partition (which is separate from the OS main partition) Readonly VM_DIR="$" $(printf "::%s" EXIT & main Posts: 10 Joined: 12. Readonly DST_DMG="$DST_DIR/macOS-Mojave.dmg" Readonly INST_BIN="/Applications/$INST_VER.app/Contents/Resources/createinstallmedia" Readonly INST_VER="Install macOS 10.14 Beta" Simple script to test:Ĭode: Select all Expand view Collapse view #!/usr/bin/env bash
I can confirm that using macOS 10.14 Mojave as a guest doesn't work due to missing APFS support.
0 kommentar(er)
