Contribute
Register

[HOW TO] OpenCore 0.8.7 > 0.8.8 differences

Status
Not open for further replies.
@Nodarkthings @oli.mathieu

Can you please try this? Put the attached miscController.strings file inside the
/OpenCore Configurator.app/Contents/Resources/fr.lproj
folder replacing the existing one.
With French language, ATAPI has now 0x100000 value, as in the English UI? I have tried it and both UI are now the same.
There was a few mistakes in the French file. The ScanPolicy list was different to the English file:
  • LINUX items (3) were missing.
  • EXT item must not be present.
  • And the Object-Id were changed from one to the other.
Imo, what happens is that the original language of the app is English, volunteers help to translate it but they don't always update the translations when a new version of the app is released, so the added languages are becoming obsolete except when the translator and the developer collaborate to publish an updated translation at the same time as the complete app.
It is different when the developer has its own translators, for example macOS, in this case the new versions usually have the updated translations.
It's a problem not easy to solve in one person apps like mackie100's OCC and CCC.
 

Attachments

  • miscController.strings.zip
    4.2 KB · Views: 26
Last edited:
@Nodarkthings @oli.mathieu

Can you please try this? Put the attached miscController.strings file inside the
/OpenCore Configurator.app/Contents/Resources/fr.lproj
folder replacing the existing one.
With French language, ATAPI has now 0x100000 value, as in the English UI? I have tried it and both UI are now the same.
There was a few mistakes in the French file. The ScanPolicy list was different to the English file:
  • LINUX items (3) were missing.
  • EXT item must not be present.
  • And the Object-Id were changed from one to the other.
Fixed! :thumbup: I've verified each and every bit one by one.
I'm happy I have contributed to find that long standing issue. :headbang:
Thanks for your involvement!
 
Well, for whatever reason, when I went to check my ScanPolicy setting in OCAT, it was set to zero. I then thought I'd set it to one but after saving and rebooting, the OC Bootpicker only showed my Windows 11 (which disappeared after the first boot), Reset NVRAM, and Toggle SIP partitions but NO macOS or Recovery partitions! Fortunately, I have a bootable Ventura backup NVMe on a PCIe card and used that to boot with its own OpenCore which got me back into my normal Ventura partition and EFI. But even after numerous tries at setting all sorts of different combinations of scan policy numbers, I STILL could NOT boot from that EFI - only the backup - even after setting it all back to zero. I still don't know what got borked but I ended up replacing my main EFI with the backup and that's what finally worked. So my definitely NON-empirical testing leads me to decide that using a .contentVisibilty file AND setting the scan policy to anything other than zero is what most likely caused the issue.
Now that I've put my nose in ScanPolicy again, here is the things to know to customise it to your needs:
- the first bits (OC_SCAN_FILE_SYSTEM_LOCK and OC_SCAN_DEVICE_LOCK) are mandatory
- then you have to check both the filesystems AND the interfaces.
 
@Nodarkthings @oli.mathieu

I guess that the ScanPolicy list can be wrong in all non English languages if the translators haven't update them after the changes made last months in the ScanPolicy list.
May be mine was already correct because OCC is configured with English (OCC prefs) on French MacOS with French keyboard layout ?
 
@oli.mathieu
Yes, the system language doesn’t matter, it’s the app language selected in the settings. English is fine because is the native language and the developer works on it. But translations can be outdated.
 
May be mine was already correct because OCC is configured with English (OCC prefs) on French MacOS with French keyboard layout ?
Indeed! As I'm not using it, I never noticed there was this language setting in the prefs! :lol:
 
Drivers has been updated to support "write xor execute".
A fresh install from USB using OpenCore 0.8.8 will not load the old driver.
 
Last edited:
After upgrading to Opencore 0.8.8, in the booting picker screen, has a new Drive selection "EFI" and it becomes the first drive booter, and the booter is defaulted to select it, so when I disable the boot drive picker, can't boot the correct drive (it will be booted by "EFI").
I rolled back to Opencore 0.8.7, no this issue.

Could anyone help to figure out what the issue is and how to solve it?

Thanks.
 
Last edited:
After upgrading to Opencore 0.8.8, in the booting picker screen, has a new Drive selection "EFI" and it becomes the first drive booter, and the booter is defaulted to select it, so when I disable the boot drive picker, can't boot the correct drive (it will be booted by "EFI").
I rolled back to Opencore 0.8.7, no this issue.

Could anyone help to figure out what the issue is and how to solve it?

Thanks.
In order to hide the EFI partiton, you now have to add a hidden file called ".contentVisibilty" (No, that's not a typo, it needs to have that preceding dot in the file name) in the efi/efi/Boot folder (with Bootx64.efi) as noted at the bottom of post #1. Others have stated that you can also alter the "scanpolicy" setting in the "config.plist". You'll have to search through the previous comments in this post for more info on doing that.
 
Status
Not open for further replies.
Back
Top