Mac Pro 5,1 with the original Radeon 5770, to be replaced with Sapphire Pulse RX580 8GB, two SSDs in optical SATA, four HDDs in the HDD bays set up as RAID5.
Installed Mojave on a SATA SSD
Created a Windows install USB on another Mac
Installed Win 10 on a separate SATA SSD, drivers installed mostly automatically, bootcamp panel, that was easy
Windows works, restarting from Windows into MacOS using the toolbar menu works. msinfo32 explicitly says EFI mode, not Legacy/BIOS.
Restarting into Windows by changing the startup disk in MacOS SysPref panel results in an error. But does work using Apple's own Option-boot, with the Windows disk shown as EFI SECTOR.
Installed Open Core 0.5.7 NdkBootPicker like this:
Opened the EFI folder on the macOS drive, made a backup copy of its contents, namely these folders
APPLE (contains EXTENSIONS folder with just one file)
Boot (contains just one file - bootx64.efi)
Microsoft (a whole bunch of files and folders)
The 0.5.7 package included two folders
OC (lots of files), and
BOOT (all CAPS in case it matters) containing BOOT64x.efi
macOS asked whether to replace the original 'Boot' folder with the OC 'BOOT' one. Pressed replace.
The included bless script did not return any errors.
Reinstalled the RX580, restarted the mac with the following results:
Mojave h/w acceleration per VideoProc - YES
The OC Bootpicker only shows Mojave and Recovery, no Windows
Trying to boot into Windows using the old card and Apple's Option-boot (have to reinstall the old GPU, obviously) shows EFI SECTOR but results in immediate BSOD.
Removing OC files/restoring the original Boot folder in the EFI allows to Option-boot into Windows without errors as before.
There's no EFI partition on the Windows SSD, Clover does not show any EFI on that drive, and diskutil shows just one named BOOTCAMP, while showing four for the macOS drive.
Numerous 'secure" strings in the romtool dump (this one is really scary).
So, the questions are:
Is there a short way out for me by making the OC bootpicker 'see' the Windows already installed? (without there being a visible EFI partition - is this even normal?)
Is it safe to run Windows at all since it was installed BEFORE OC, which says will protect NVRAM from Microsoft's certificates or whatever?
If not, I am more than willing to reformat the Windows SSD and DO IT RIGHT this time around. Do I have to use the Virtual Box procedure described in one of the threads to make OC see the Windows partition and avoid corrupting NVRAM?
I would very very much appreciate some tips from the gurus.
Thank you
Installed Mojave on a SATA SSD
Created a Windows install USB on another Mac
Installed Win 10 on a separate SATA SSD, drivers installed mostly automatically, bootcamp panel, that was easy
Windows works, restarting from Windows into MacOS using the toolbar menu works. msinfo32 explicitly says EFI mode, not Legacy/BIOS.
Restarting into Windows by changing the startup disk in MacOS SysPref panel results in an error. But does work using Apple's own Option-boot, with the Windows disk shown as EFI SECTOR.
Installed Open Core 0.5.7 NdkBootPicker like this:
Opened the EFI folder on the macOS drive, made a backup copy of its contents, namely these folders
APPLE (contains EXTENSIONS folder with just one file)
Boot (contains just one file - bootx64.efi)
Microsoft (a whole bunch of files and folders)
The 0.5.7 package included two folders
OC (lots of files), and
BOOT (all CAPS in case it matters) containing BOOT64x.efi
macOS asked whether to replace the original 'Boot' folder with the OC 'BOOT' one. Pressed replace.
The included bless script did not return any errors.
Reinstalled the RX580, restarted the mac with the following results:
Mojave h/w acceleration per VideoProc - YES
The OC Bootpicker only shows Mojave and Recovery, no Windows
Trying to boot into Windows using the old card and Apple's Option-boot (have to reinstall the old GPU, obviously) shows EFI SECTOR but results in immediate BSOD.
Removing OC files/restoring the original Boot folder in the EFI allows to Option-boot into Windows without errors as before.
There's no EFI partition on the Windows SSD, Clover does not show any EFI on that drive, and diskutil shows just one named BOOTCAMP, while showing four for the macOS drive.
Numerous 'secure" strings in the romtool dump (this one is really scary).
So, the questions are:
Is there a short way out for me by making the OC bootpicker 'see' the Windows already installed? (without there being a visible EFI partition - is this even normal?)
Is it safe to run Windows at all since it was installed BEFORE OC, which says will protect NVRAM from Microsoft's certificates or whatever?
If not, I am more than willing to reformat the Windows SSD and DO IT RIGHT this time around. Do I have to use the Virtual Box procedure described in one of the threads to make OC see the Windows partition and avoid corrupting NVRAM?
I would very very much appreciate some tips from the gurus.
Thank you
Last edited:
