WTF is "FAT formatter"?
There is more to an EFI partition than just "200 MB FAT32". Read up here: https://apple.stackexchange.com/questions/57597/how-to-fix-broken-efi-partition/58892#58892
BTW OCLP might not pick FAT16.
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
There is more to an EFI partition than just "200 MB FAT32". Read up here: https://apple.stackexchange.com/questions/57597/how-to-fix-broken-efi-partition/58892#58892
BTW OCLP might not pick FAT16.
Love your ways to ask questions. 🤣
I would ask the opencore legacy patcher discord. This thread is for the diy opencore solution. You will get more help in the discord
Edit : I also agree with @hwojtek that OCLP may not see a FAT16 drive since FAT16 is not common on macOS and was probably not kept in mind when the OCLP devs were making their app
Just curious, how does the above installation work? Are people running it more or less without problems once they patch in all the older drivers?
It's more a curiosity, not even DRM works. No one in the right mind would use Ventura as is right now with non-AVX Macs.
question, I renamed my boot volume, using Finder... When I reboot the computer, the OC boot picker still shows the old volume name. its not showing the new name as I renamed it in Finder. Is this cached somewhere or what do I need to change so that the name of the boot volume will be the same as what I see in OC boot picker...or visa versa...??
I also did notice already that when I changed the name of the boot volume in Finder, Finder did not change the name of the "nnn - Data" volume, so I renamed that one also using Disk Utility... But same difference, shows up in OC boot picker as the previous name.
I also did notice already that when I changed the name of the boot volume in Finder, Finder did not change the name of the "nnn - Data" volume, so I renamed that one also using Disk Utility... But same difference, shows up in OC boot picker as the previous name.
where are those? Its picking up the names automatically. So why would it be picking up the wrong names? In any case, if those files are something I can use to hard code names of my own choosing, I will look into that, but I'd also like to know how or why OC is automatically detecting the wrong, older names.
BTW - I am not using the Canopy stuff...I'm just talking about the built in terminal disk picker in OC.
BTW - I am not using the Canopy stuff...I'm just talking about the built in terminal disk picker in OC.
Last edited:
As far as I know, this is the customary way of doing it without resorting to OC or any other solutions. Go to System Preferences/Startup Disk, unlock the panel if necessary and select the startup volume whose name just changed. More likely than not, the old name will be displayed. Select or reselect it as the startup disk. You should see the updated name the next time your computer reboots. This won't destroy the blessing of the OC EFI volume.
This has been discussed a lot. Try searching for .disk_label in this thread. I have not done this myself yet, but try following this: https://forums.macrumors.com/thread....2207814/page-257?post=29565692#post-29565692
Sounds like a possible band aid but does anyone have any idea why OC is displaying the wrong name to begin with?
I took a look at your config and noticed that you are not using LauncherOption. When using Windows, it’s best to set LauncherOption=Full to protect the OC boot entry.
It’s also a good idea to verify that the only BOOTx64.efi file present on all EFI partitions is the OC one. Such files can be created and overwritten during Windows updates. You can verify whether the file is the OC one by opening it with a text editor; you’ll see “OpenCore Bootloader” at the top.
Try my step-by-step method to rename the .disk_label.contentDetails , .disk_label_2x or .disk_label files.
Thanks. I reinstalled MacOS already which fixed the problem. Since then I read up how these are in the Preboot area, and so forth and I just decided I didn't want to mess with it. Apparantly the next OS update would have also refreshed the PreBoot at that time and fixed the problem also most likely. Running the installer also fixed it.
Kind of a pain in the butt that Apple's various tools which can be used to rename the volumes including Finder, Disk Utility, Get Info, etc...don't also update the disk_label stuff in preboot, but then on the other hand I guess its supposed to read-only area...so....
That's a great link though with explanation for how to do it manually...maybe next time I will try that first.
Kind of a pain in the butt that Apple's various tools which can be used to rename the volumes including Finder, Disk Utility, Get Info, etc...don't also update the disk_label stuff in preboot, but then on the other hand I guess its supposed to read-only area...so....
That's a great link though with explanation for how to do it manually...maybe next time I will try that first.
Hi all
I'm trying to install Windows 11 on my 5,1 macpro. I've been following the instructions n page one up to the poiny i need to type:dism /apply-image /imagefile:install:wim /index:6 /applydir:C:\/compact /EA
Upon pressing return I get a "specified path not found" error.
(error persists with all index numbers
Any ideas?
Thanks
I'm trying to install Windows 11 on my 5,1 macpro. I've been following the instructions n page one up to the poiny i need to type:dism /apply-image /imagefile:install:wim /index:6 /applydir:C:\/compact /EA
Upon pressing return I get a "specified path not found" error.
(error persists with all index numbers
Any ideas?
Thanks
:wim should be .wim and you need a space between the path C:\ and the argument /compatdism /apply-image /imagefile:install.wim /index:6 /applydir:C:\ /compact /EA
Thanks! Also is it OK to install windows on the same drive where opencore efi sits?