Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
MP 1,1-5,1 Manually Configured OpenCore on the Mac Pro
- Thread starter cdf
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
Nope, you install with a cd copy of windows by pressing ALT at startup (the official boot screen)
Nice!Yes ! I didn't try that because I was afraid to kill the OC EFI boot, but yes ! Finally it's workingThanks a looooot ******* !
In what respect? Both RP and OC run there.
Edit: you ask about BS I presume ? Than not yet.
Maybe someone can help me:
I can't get the OpenCore Label of my Mojave disks renamed.
I once had the name "blade" and do ccc copies. Now all my copies have the name "blade" in the OC selection list.
Volume Name is not "blade" no more of course.
I used oc disklabel command to add the tags to both Coreservices directories of Preboot and System APFS Volume.
even checked .disk_label.contentDetails, file was correctly written
where does OpenCore gets the name in the selection list from?
Just use text mode if that counts.
And PickerAttributes set to 2.
I can't get the OpenCore Label of my Mojave disks renamed.
I once had the name "blade" and do ccc copies. Now all my copies have the name "blade" in the OC selection list.
Volume Name is not "blade" no more of course.
I used oc disklabel command to add the tags to both Coreservices directories of Preboot and System APFS Volume.
even checked .disk_label.contentDetails, file was correctly written
where does OpenCore gets the name in the selection list from?
Just use text mode if that counts.
And PickerAttributes set to 2.
Last edited:
11.3 Beta 20e5210c has "nice" glitches:
won't install with a Kepler Card, I popped a GT120 in.
after installation put the Kepler back in everything works regarding GPU.
Won't boot if an Apple AHCI Blade is in. Buddy told same with a NVMe.
Ya, I think the final release date should be announced tomorrow, probably with iOS 14.5.
I just made a new install to a spinner booted from Mojave.
Problem is even without OC just with -no_compat_check set, btw
I'm thinking about setting up a Windows10 boot partition on my OpenCore 5,1 and could appreciate pointers in the right direction to make sure I stay out of trouble.
First, what are the pros and cons of booting with a so called "legacy" windows install (and boot without OpenCore I guess?), vs what is described in CDF's guide by using OpenCore to protect the UEFI, and avoid "legacy" mode, whatever that is?
Any recommendations for partitioning a place for Windows in order to avoid messing up an existing Catalina, Mojave or Big Sur boot partition on the same physical drive? One spare place I have with some room for windows is on the drive where I have Mojave.
ps - I also use RefindPlus, so I am able boot Windows with or without OpenCore...doesn't matter to me which way I set it up, but want to understand the pros and cons of doing it through OpenCore vs legacy mode or whatever...
First, what are the pros and cons of booting with a so called "legacy" windows install (and boot without OpenCore I guess?), vs what is described in CDF's guide by using OpenCore to protect the UEFI, and avoid "legacy" mode, whatever that is?
Any recommendations for partitioning a place for Windows in order to avoid messing up an existing Catalina, Mojave or Big Sur boot partition on the same physical drive? One spare place I have with some room for windows is on the drive where I have Mojave.
ps - I also use RefindPlus, so I am able boot Windows with or without OpenCore...doesn't matter to me which way I set it up, but want to understand the pros and cons of doing it through OpenCore vs legacy mode or whatever...
if you don't really need Uefi Windows (because of running it from a NVMe for example) I'd avoid the risks and run it in legacy.
As you do (and me) you can run it thru RefindPlus or
thru OpenCore with chainloaded Refind. I tried both.
As you do (and me) you can run it thru RefindPlus or
thru OpenCore with chainloaded Refind. I tried both.
Big Sur 20e5210c is a kinda freaking mess, crashes 2 out of 3 times due to IONVMEFamily.cpp but the one time does decide on booting zero issues in Mac OS even when running from an NVME.
I recommend to use a different drive, not a partition.
H.265 (VideoToolBox) is HEVC hardware encoding option.
N.B. the decoding part (from source video) still handle by CPU, no option for that in Handbrake.
A second way to confirm is by installing VideoProc. That application provides a visual confirmation that hardware encoding and decoding is available if everything is configured correctly.
Apart from that, iStat menu will also show GPU info such as load when the GPU is tasked with encoding or decoding source media.
FF-Works can also utilize Videotoolbox for encoding/decoding if you need advanced encoder/decoder software that
uses ffmpeg and has more advanced features then handbrake.
