Just checked from op #1314, it downloads just fine. The url you’ve posted ist not the same though, the final 7 numbers are different. Try again from there.The link https://forums.macrumors.com/attachments/opencore-1-0-0-zip.2381502/ for Martin's latest version appears to be broken.
Thanks for the report, the link in that post is now updated.The link https://forums.macrumors.com/attachments/opencore-1-0-0-zip.2381502/ for Martin's latest version appears to be broken.
Are your mouse and keyboard plugged into native USB 2.0 and not a PCIe card? If plugged into PCIe card, they will not work until OS is loaded.I have installed Martin Lo's OC pkg and it works great - except that my mouse and keyboard both freeze at the boot picker, so I can't choose a different OS. Is there a way to fix this? Been looking all over here but no luck. Also, is there a way to remove the boot picker timeout so it doesn't just load whichever OS it's set to after 10 seconds? Maybe a config file that can be edited? Any help appreciated.
Ok, now for some reason the mouse and kyb don't work in the USB 2.0 slots on the back of the 5,1 cMP. Plugged in a USB 2.0 adapter which got them working, but I remember reading about an issue (Monterey installation?) where the system loses the USB 2.0 kexts in Monterey and only works as 1.1. Sorry if I'm mixing things up, but it's been a while. Is this an issue with Martin Lo's pkg?
Can, testedI'm planning to only have Windows 10 installed on my MacPro5,1 (at the moment I have Windows 10 and Monterey).
Should be okay to install newer versions of @h9826790's OpenCore package from within Windows as long as I can mount the EFI partition, right?
Sorry, follow up question: can I move OpenCore onto the EFI partition of my NVMe drive that I have in the PCIe enclosure in my MacPro5,1 (it's currently on a SATA drive) or is that problematic? Think I remember something about it being that.Can, tested
The problem is not PCIe. I forget, does MacPro5,1 have NVMe EFI driver built-in? If not, then you have to put it in the firmware or have it get loaded from a SATA drive using a boot loader or Driver#### NVRAM variables.Sorry, follow up question: can I move OpenCore onto the EFI partition of my NVMe drive that I have in the PCIe enclosure in my MacPro5,1 (it's currently on a SATA drive) or is that problematic? Think I remember something about it being that.
Aha, because PCIe drivers aren't "initialized" so early in the startup process perhaps?
Firmware 144.0.0.0.0 includes NVMe bootable driver.I forget, does MacPro5,1 have NVMe EFI driver built-in?
You can move the EFI folder to the NVMe EFI partition.Sorry, follow up question: can I move OpenCore onto the EFI partition of my NVMe drive that I have in the PCIe enclosure in my MacPro5,1 (it's currently on a SATA drive) or is that problematic? Think I remember something about it being that.
Aha, because PCIe drivers aren't "initialized" so early in the startup process perhaps?
That’s a great piece of info if someone is tied to boot times. Thanks, I may try this just for fun.If you still have any SATA drive installed as data storage, you can actually put an extra OpenCore copy onto that drive, bless it accordingly, to speed up the boot process.
Thanks for the info!You can move the EFI folder to the NVMe EFI partition.
Three points to notes:
1) The cMP must have BootROM 140.0.0.0.0 or above (ideally 144.0.0.0.0)
2) You better bless the NVMe EFI partition when you still have macOS installed. Technically, if you remove your existing drive that contain OpenCore, the cMP will automatically search the remanning drive, and locate the EFI folder. However, there is no guarantee it will happen.
If you have boot screen, either by Mac EFI UGA, or UEFI GOP (e.g. EnableGop), even you've already removed the macOS drive, you can always hold Option key to boot, then manually select (and bless) the OpenCore in the Apple start up manger.
3) Booting OpenCore from NVMe usually much slower than in any SATA drive (even a very slow ancient HDD). This has nothing to do with the drive's performance, but how the cMP initial its storage. If you still have any SATA drive installed as data storage, you can actually put an extra OpenCore copy onto that drive, bless it accordingly, to speed up the boot process.
I do prefer to have two identical copies installed on to two bootable drives indeed.Or do you think it's good to have an EFI partition with OpenCore in two places (two different drives) just in case something goes wrong with one of them?
You may have just leftover Windows ESPs. Those are also critical, when it comes to unprotected UEFI Windows boots.If someone has an fix for why "Windows" comes up as three entries in the OpenCore boot picker when I only have one physical Windows 10 installation, I'd be happy to get help on that
It used to be two entries (one more than there should) but after doing some command suggested by LLM/AI (used a "bcdboot" command in Windows command prompt to rebuild the boot configuration) I now have three entries instead. 😂
I'm thinking part of the confusion is that I cloned Windows 10 over from one drive to another and the other drive is still "stuck" in OpenCore in some way. Now, why the bcdboot made yet another "Windows" entry show up in the OpenCore boot picker, I have no idea.