OpenCore General Discussion

[SavageAUS]

If using OC does windows “have” to be reinstalled via boot camp to work correctly? Eg blue screens or instant reboots when selecting windows from OC picker? 
In my laptop I have 2 x nvme drives and an ssd. Nvme 1 has windows 10, nvme 2 has Catalina, ssd will have linux when I decide which one or ones. Nvme 2 with Catalina with my OC EFI folder and upon booting to OC I can boot macOS perfectly but windows will either blue screen “acpi error” or I just get some text on the top left of my screen, not sure what it says as it’s quick then instant reboot. If using BCA to install windows can BCA install windows to a seperate drive?

[MacNB]

12 hours ago, Download-Fritz said:

@MacNB I think your boot entry "issue" is "by design" with the newly introduced boot policy. BlessOverride at all times was the prefered way to add options, custom entries are more or less only for the case of multiple OSes per partition, which is not a thing at all in Apple land. So to say, an extension of ours to what Apple gave us to work with. To rename an option, you can just use the .contenDetails file as described in the PDF fine with no need for a custom entry.

 

Thanks for the info.

 

I added .contentDetails text file to the folder /EFI/Microsoft/Boot with the words "Windows 10 Pro" and the boot picker now displays that name. 

 

But I still thinks there are problems:

1. With Misc->Entries, if we cannot add an entry that works then what is the point of allowing a Custom entry that is not bootable ? Can you please give an example of "multiple OSes per partition" ?
2. There's another problem with the "by design" boot policy now. I could only get the Windows OS displayed in the boot picker if I enable the bit OC_SCAN_ALLOW_FS_ESP in the ScanPolicy setting. If I unset that bit and instead set OC_SCAN_ALLOW_FS_NTFS, then Windows drive is NOT displayed (I did not expect it but I thought I try it).
3. The side-effect of setting bit OC_SCAN_ALLOW_FS_ESP now also displays EFI harddisk icon (I don't know for which of my 3 drives but I assume OC drive). I am setting scanPolicy value to 0x010F0503.The HideSelf setting has now been removed from OC 0.5.9 is that the problem ?.
4. The OC boot log now shows "Invalid file system policy (200/10F0503) for BB94DA98". Here's a snapshot"

   
   07:077 00:005 OCB: Adding fs BBBACE98 (E:0|L:1|P:Success) - PciRoot(0x0)/Pci(0x1,0x1)/Pci(0x0,0x0)/NVMe(0x1,36-39-28-51-29-A7-79-64)/HD(1,GPT,48FD2EC1-C3AE-4458-B959-BDBEED7D2ABE,0x28,0x64000)
   07:079 00:002 OCB: Adding fs BB983B18 (E:0|L:0|P:Success) - PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0xFFFF,0x0)/HD(1,GPT,B23BFB37-1721-48BA-823F-76152B5DC630,0x28,0x64000)
   07:082 00:002 OCB: Adding fs BB95DB18 (E:0|L:0|P:Success) - PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x1,0xFFFF,0x0)/HD(1,GPT,A4CE4F1A-43C6-492D-BB16-2DD6EABCE4EF,0x28,0x64000)
   07:083 00:001 OCPI: Located cached partition entries
   07:085 00:001 OCB: Invalid file system policy (200/10F0503) for BB94DA98
   07:087 00:001 OCB: Adding fs BB94DA98 (E:0|L:0|P:Security Violation) - PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x1,0xFFFF,0x0)/HD(7,GPT,8B191946-A4A6-4CDF-8D18-F0E28B417C68,0x574107A8,0x135F20)
   07:088 00:001 OCPI: Located cached partition entries

    

Here's boot picker screenshot now:

 

[MacNB]

2 hours ago, insanefrancis said:

 

UPDATE:

Sure enough the solution is on the Docs, set AdviseWindows=YES

 

Glad you got it working.

 

Interesting.

I have AdviseWindows=NO and I do not have any problems selecting Windows on Startup Disk.

 

In my config, I have:

    PlatformInfo->PlatformNVRAM->FirmwareFeatures = FD8FF53E 

    PlatformInfo->PlatformNVRAM->FirmwareFeaturesMask = FF9FFF3F 

 

Maybe FirmwareFeatures value is allowing me to successfully select Windows.

That is, FW_FEATURE_SUPPORTS_UEFI_WINDOWS_BOOT bit set in my FirmwareFeatures value.

 

UPDATE:

From sources:
#define FW_FEATURE_SUPPORTS_CSM_LEGACY_MODE 0x00000001U //  bit 0

#define FW_FEATURE_SUPPORTS_UEFI_WINDOWS_BOOT 0x20000000U // bit 29

 

So in my case, FW_FEATURE_SUPPORTS_UEFI_WINDOWS_BOOT bit is set and FW_FEATURE_SUPPORTS_CSM_LEGACY_MODE bit is NOT set.

Therefore, no dot need AdviseWindows=Yes.

 

Check yours in terminal:

nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:FirmwareFeatures

 

 

 

Edited May 21, 2020 by MacNB

[arsradu]

5 minutes ago, MacNB said:

 

Glad you got it working.

 

Interesting.

I have AdviseWindows=NO and I do not have any problems selecting Windows on Startup Disk.

 

In my config, I have:

    PlatformInfo->PlatformNVRAM->FirmwareFeatures = FD8FF53E 

    PlatformInfo->PlatformNVRAM->FirmwareFeaturesMask = FF9FFF3F 

 

Maybe FirmwareFeatures value is allowing me to successfully select Windows.

That is, FW_FEATURE_SUPPORTS_UEFI_WINDOWS_BOOT bit set in my FirmwareFeatures value.

 

 

I'm thinking the same, since I also have it set to NO, as you know. And no problems either selecting BootCamp Windows or booting to/from it.

[MacNB]

1 hour ago, SavageAUS said:

If using OC does windows “have” to be reinstalled via boot camp to work correctly? Eg blue screens or instant reboots when selecting windows from OC picker? 
In my laptop I have 2 x nvme drives and an ssd. Nvme 1 has windows 10, nvme 2 has Catalina, ssd will have linux when I decide which one or ones. Nvme 2 with Catalina with my OC EFI folder and upon booting to OC I can boot macOS perfectly but windows will either blue screen “acpi error” or I just get some text on the top left of my screen, not sure what it says as it’s quick then instant reboot. If using BCA to install windows can BCA install windows to a seperate drive?

 

No Windows does not have to be reinstalled via Bootcamp.

The ACPI errors seems "normal" if you have your own custom DSDT and SSDT's with "extensive" mods that you use/need for macOS.

When OC "passes control" to Windows boot loader, that ACPI "environment" is passed Windows and windows can't handle.

 

I now do NOT use my DSDT.

I use simple OC ACPI patch capabilities such as renaming EHC1 to EH0, etc.

There's one SSDT-EC.aml that has the required OS check in there (_OSI) to allows for non macOS's.

and that's it. Windows boots fine.

[arsradu]

1 hour ago, SavageAUS said:

If using OC does windows “have” to be reinstalled via boot camp to work correctly? Eg blue screens or instant reboots when selecting windows from OC picker? 
In my laptop I have 2 x nvme drives and an ssd. Nvme 1 has windows 10, nvme 2 has Catalina, ssd will have linux when I decide which one or ones. Nvme 2 with Catalina with my OC EFI folder and upon booting to OC I can boot macOS perfectly but windows will either blue screen “acpi error” or I just get some text on the top left of my screen, not sure what it says as it’s quick then instant reboot. If using BCA to install windows can BCA install windows to a seperate drive?

 

You can install it via whatever you want. In fact, installing it via BCA has its own issues, as you can see in my previous post here. :))

 

But yes, with some "help" from certain SMBIOSes, you can install it on a different drive, as well, via BootCamp. But...it would probably be easier to just make a USB drive in Windows, or using UnetBootin on MacOS, boot into it, install it and be done with it. Still, since you are using multiple drives, you can expect some errors (at least I had plenty of those) during Windows installation. Not related to BootCamp or anything. Just Windows being Windows. And, although it might not be the case for you, you might need to unplug some of your drives in order to complete the installation successfully. You can see some of my previous (bad) experiences here.

 

So...I don't think the problem is that it's not installed via BootCamp... I had Windows installed before, and it wasn't via BootCamp. So...I feel like it's probably something else. Have you tried booting with Clover (just for comparison)? Does that work? Cause if it does, since it's the same Windows installation, it might be something specific to OC then. But personally I haven't had any issues.

Edited May 21, 2020 by arsradu

[SavageAUS]

12 minutes ago, arsradu said:

 

You can install it via whatever you want. In fact, installing it via BCA has its own issues, as you can see in my previous post here. :))

 

But yes, with some "help" from certain SMBIOSes, you can install it on a different drive, as well, via BootCamp. But...it would probably be easier to just make a USB drive in Windows, or using UnetBootin on MacOS, boot into it, install it and be done with it. Still, since you are using multiple drives, you can expect some errors (at least I had plenty of those) during Windows installation. Not related to BootCamp or anything. Just Windows being Windows. And, although it might not be the case for you, you might need to unplug some of your drives in order to complete the installation successfully. You can see some of my previous (bad) experiences here.

 

So...I don't think the problem is that it's not installed via BootCamp... I had Windows installed before, and it wasn't via BootCamp. So...I feel like it's probably something else. Have you tried booting with Clover (just for comparison)? Does that work? Cause if it does, since it's the same Windows installation, it might be something specific to OC then. But personally I haven't had any issues.

The windows install works 100% with Clover. I remember OC used to have a setting that wouldn’t pass its specifics to windows but that’s since been removed.

I guess I’ll have to work out how to implement the _OSI checks to my SSDT’s so they don’t get passed through to windows. 

[MacNB]

18 minutes ago, SavageAUS said:

The windows install works 100% with Clover. I remember OC used to have a setting that wouldn’t pass its specifics to windows but that’s since been removed.

I guess I’ll have to work out how to implement the _OSI checks to my SSDT’s so they don’t get passed through to windows. 

 

I am new to OC (new since 0.5.5) so don't know if OC had a feature before 0.5.5 to bypass ACPI mods but you may be thinking of @n.d.k's fork of OC that has that feature.

 

I think Clover does not pass on the ACPI mods/patches to Windows but only macOS.

 

If you do make to _OSI edits to your SSDT's (not all SSDT's need them BTW), then it would be good to share them here 

Edited May 21, 2020 by MacNB

[arsradu]

18 minutes ago, SavageAUS said:

The windows install works 100% with Clover. I remember OC used to have a setting that wouldn’t pass its specifics to windows but that’s since been removed.

I guess I’ll have to work out how to implement the _OSI checks to my SSDT’s so they don’t get passed through to windows. 

 

Probably.. I'm not using a custom DSDT... So..if that's what's causing it, I can't confirm that. I'm only using some pretty generic SSDT for CPU and USB and all that. So nothing fancy. And didn't have to add any _OSI checks. But since we're using different hardware, I expect that to have something to do with it. So...yeah, I hope that fixes it for you.  

 

I feel like Haswell might be the best platform to build a hackintosh on right now. :))) You have so very few things to patch/adjust it's almost seamless. :)))

Edited May 21, 2020 by arsradu

[Andrey1970]

1 hour ago, MacNB said:

 

Thanks for the info.

 

I added .contentDetails text file to the folder /EFI/Microsoft/Boot with the words "Windows 10 Pro" and the boot picker now displays that name. 

 

But I still thinks there are problems:

1. With Misc->Entries, if we cannot add an entry that works then what is the point of allowing a Custom entry that is not bootable ? Can you please give an example of "multiple OSes per partition" ?
2. There's another problem with the "by design" boot policy now. I could only get the Windows OS displayed in the boot picker if I enable the bit OC_SCAN_ALLOW_FS_ESP in the ScanPolicy setting. If I unset that bit and instead set OC_SCAN_ALLOW_FS_NTFS, then Windows drive is NOT displayed (I did not expect it but I thought I try it).
3. The side-effect of setting bit OC_SCAN_ALLOW_FS_ESP now also displays EFI harddisk icon (I don't know for which of my 3 drives but I assume OC drive). I am setting scanPolicy value to 0x010F0503.The HideSelf setting has now been removed from OC 0.5.9 is that the problem ?.
4. The OC boot log now shows "Invalid file system policy (200/10F0503) for BB94DA98". Here's a snapshot"

   
   
   07:077 00:005 OCB: Adding fs BBBACE98 (E:0|L:1|P:Success) - PciRoot(0x0)/Pci(0x1,0x1)/Pci(0x0,0x0)/NVMe(0x1,36-39-28-51-29-A7-79-64)/HD(1,GPT,48FD2EC1-C3AE-4458-B959-BDBEED7D2ABE,0x28,0x64000)
   07:079 00:002 OCB: Adding fs BB983B18 (E:0|L:0|P:Success) - PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0xFFFF,0x0)/HD(1,GPT,B23BFB37-1721-48BA-823F-76152B5DC630,0x28,0x64000)
   07:082 00:002 OCB: Adding fs BB95DB18 (E:0|L:0|P:Success) - PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x1,0xFFFF,0x0)/HD(1,GPT,A4CE4F1A-43C6-492D-BB16-2DD6EABCE4EF,0x28,0x64000)
   07:083 00:001 OCPI: Located cached partition entries
   07:085 00:001 OCB: Invalid file system policy (200/10F0503) for BB94DA98
   07:087 00:001 OCB: Adding fs BB94DA98 (E:0|L:0|P:Security Violation) - PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x1,0xFFFF,0x0)/HD(7,GPT,8B191946-A4A6-4CDF-8D18-F0E28B417C68,0x574107A8,0x135F20)
   07:088 00:001 OCPI: Located cached partition entries

    

Here's boot picker screenshot now:

 

 

The UEFI Windows bootloader is located on ESP FAT32.

OC_SCAN_ALLOW_FS_NTFS - it is useless for UEFI Windows.

[insanefrancis]

1 hour ago, MacNB said:

Check yours in terminal:

nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:FirmwareFeatures

 

 

 

 

Do I just run this in terminal?

This is the output.

4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:FirmwareFeatures	w%f5%8f%fd

 

Quote

In my config, I have:

    PlatformInfo->PlatformNVRAM->FirmwareFeatures = FD8FF53E 

    PlatformInfo->PlatformNVRAM->FirmwareFeaturesMask = FF9FFF3F 

 

I also don't have these in my config.

[SavageAUS]

59 minutes ago, MacNB said:

 

I am new to OC (new since 0.5.5) so don't know if OC had a feature before 0.5.5 to bypass ACPI mods but you may be thinking of @n.d.k's fork of OC that has that feature.

 

I think Clover does not pass on the ACPI mods/patches to Windows but only macOS.

 

If you do make to _OSI edits to your SSDT's (not all SSDT's need them BTW), then it would be good to share them here 

I’ll definitely share what I come up with when it works. If anyone has advice on how to implement the _OSI patch into SSDT’s I’m all ears. I will also share my config at a later point in case it’s a config issue. 

Edited May 21, 2020 by SavageAUS

[MacNB]

 

36 minutes ago, Andrey1970 said:

 

The UEFI Windows bootloader is located on ESP FAT32.

OC_SCAN_ALLOW_FS_NTFS - it is useless for UEFI Windows.

 

Yes I know it does not work that's why I said "(I did not expect it but I thought I try it)" thinking there's a problem with the new boot policy.

What's your comment on the 4 issues ?

[Andrey1970]

8 minutes ago, insanefrancis said:

I also don't have these in my config.

For Automatic = Yes, need only Generic.

[Andrey1970]

13 minutes ago, MacNB said:

 

 

Yes I know it does not work that's why I said "(I did not expect it but I thought I try it)" thinking there's a problem with the new boot policy.

What's your comment on the 4 issues ?

You shall enable 0x00000200 (bit 9) — OC_SCAN_ALLOW_FS_HFS, allows scanning of HFS file system.

It is necessary for macOS install and Recovery.

[MacNB]

23 minutes ago, insanefrancis said:

 

Do I just run this in terminal?

This is the output.

4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:FirmwareFeatures	w%f5%8f%fd

 

 

 

Your value is FD8FF577 which means FW_FEATURE_SUPPORTS_CSM_LEGACY_MODE bit set.

That means you should not need AdviseWindows=YES.

Hmmm...not sure why you need it.

 

But at least you can now boot Windows from Startup disk 

[MacNB]

24 minutes ago, Andrey1970 said:

You shall enable 0x00000200 (bit 9) — OC_SCAN_ALLOW_FS_HFS, allows scanning of HFS file system.

It is necessary for macOS install and Recovery.

 

Thanks for the tip but that's not the current problem with Windows & EFI partitions.

 

Which means there's a bug with log or code: "Invalid file system policy (200/10F0503) for BB94DA98"

Also, if Bit 9 is necessary for macOS install & Recovery, then I suggest that it should set for Failsafe (by default) and Configuration.pdf changed accordingly.

Currently failsafe = 0x10F0103

I recommend failsafe = 0x10F0303

[arsradu]

Hi guys!

 

Hope you're all doing fantastic!

 

So, I was trying to get a better understanding of how we're supposed to add values like Audio Codec and Audio Out to config. I took a look at the Configuration PDF and I think I finally understood how to set it up.  

 

Still, interestingly enough, in my case at least, I have a boot chime with both Audio Out 0 and 2. I haven't tried the rest of them (from 0 to 4, since I've got 5 output ports, so N-1=5-1=4), but 0 and 2 seemed to work fine. I'm guessing that's probably normal...?

 

Anyway, what I wanted to suggest is if you could maybe update the font of the pdf, because bold text on that font is almost the same as regular which is not good when the bold text is actually what you're looking for. Here's an example of what it looks like in Preview (the default app for PDFs) and Typora.

 

If you can tell me which part is bolded in the first screenshot, without looking at the second one, I'll give you a beer. And not Corona. :))

 

 

And here's from Typora. Same text, just copy-pasted in another app. Literally night and day difference.

 

Edited May 21, 2020 by arsradu

[mhaeuser]

3 hours ago, MacNB said:

With Misc->Entries, if we cannot add an entry that works then what is the point of allowing a Custom entry that is not bootable ? Can you please give an example of "multiple OSes per partition" ?

You nowhere said it was unbootable, only that it was not accepted as default entry from macOS Startup Disk. macOS Startup Disk, as it uses said Apple boot policy, does not have the concept of multiple OSes per partition. It stores only the partition (not file) information into NVRAM and then lets the firmware (Apple EFI, here accounted for by OpenCore) decide which file is bootable on the partition - this happens by an algorithm detailed in the PDF. Without BlessOverride, bootmgfw can never be the determined boot file from this partition node, this is the whole reason we have BlessOverride in the first place, and that is exactly what you are seeing. Previously, we adhered to one OS per partition (enforcing Apple rules and our extensions) and when scanning did not yield any entry for this partition (e.g. BlessOverride does not contain the necessary file), custom entries were chosen by partition matching. Now, we support e.g. arbitrary Boot#### entries and such, hence partition matching is no longer utilised - this is what breaks this behaviour for you. However, that was never "supported/recommended" in the first place, that was just what happened to be the implementation.

 

Multiple OSes on a partition refers to the amount of non-alternative (e.g. macOS Recovery can be alternative on FileVault setups) booters on one partition. OpenCore and Windows sharing an ESP does count as "multiple OSes".

[insanefrancis]

1 hour ago, MacNB said:

 

Your value is FD8FF577 which means FW_FEATURE_SUPPORTS_CSM_LEGACY_MODE bit set.

That means you should not need AdviseWindows=YES.

Hmmm...not sure why you need it.

 

But at least you can now boot Windows from Startup disk 

 

I might be wrong but I'm thinking OC sets these values accordingly depending on your partition schemes, whether EFI is first partition or not, when you have AdviseWindows=YES. I don't remember setting any of these values on my config manually. I might try clearing NVRAM to remove these values, set AdviseWindows=NO then check again if OC will set something. I'll probably not, I have it already working. But I may if no one validate or invalidate my theory.

Edited May 21, 2020 by insanefrancis

[arsradu]

 

Thanks, @vit9696  

[MacNB]

3 hours ago, Download-Fritz said:

You nowhere said it was unbootable, only that it was not accepted as default entry from macOS Startup Disk. macOS Startup Disk, as it uses said Apple boot policy, does not have the concept of multiple OSes per partition. It stores only the partition (not file) information into NVRAM and then lets the firmware (Apple EFI, here accounted for by OpenCore) decide which file is bootable on the partition - this happens by an algorithm detailed in the PDF. Without BlessOverride, bootmgfw can never be the determined boot file from this partition node, this is the whole reason we have BlessOverride in the first place, and that is exactly what you are seeing. Previously, we adhered to one OS per partition (enforcing Apple rules and our extensions) and when scanning did not yield any entry for this partition (e.g. BlessOverride does not contain the necessary file), custom entries were chosen by partition matching. Now, we support e.g. arbitrary Boot#### entries and such, hence partition matching is no longer utilised - this is what breaks this behaviour for you. However, that was never "supported/recommended" in the first place, that was just what happened to be the implementation.

 

Multiple OSes on a partition refers to the amount of non-alternative (e.g. macOS Recovery can be alternative on FileVault setups) booters on one partition. OpenCore and Windows sharing an ESP does count as "multiple OSes".

 

Thanks @Download-Fritz for the explanation on how the new boot method is meant to work.

 

To get around the fact that Windows is not accepted as default, I used ScanPolicy of 0x010F0503.

That allows the Windows drive to be selected in Startup Disks and macOS restarts.

On restart the boot picker now displays TWO windows drives: (a) the UN-Blessed one (labeled "Windows") that it finds in the ESP and (b) the Custom Entry I had put in (named "Windows 10 Pro"). BUT the default one selected is the (a) and NOT (b) and when hitting Enter, of course (a) cannot boot. As soon as I provide BlessedOverride, then OC boots Windows perfectly.

Recommendation: now that OC support e.g. arbitrary Boot#### entries and such, hence partition matching is no longer utilised - this is what breaks the Custom Entries behaviour, should be documented in the ScanPolicy section. That is, avoid Custom Entries AND BlessOverride for the same OS.

 

Earlier, I list the problems :

1. With Misc->Entries, if we cannot add an entry that works then what is the point of allowing a Custom entry that is not bootable ? Can you please give an example of "multiple OSes per partition" ?
2. There's another problem with the "by design" boot policy now. I could only get the Windows OS displayed in the boot picker if I enable the bit OC_SCAN_ALLOW_FS_ESP in the ScanPolicy setting. If I unset that bit and instead set OC_SCAN_ALLOW_FS_NTFS, then Windows drive is NOT displayed (I did not expect it but I thought I try it).
3. The side-effect of setting bit OC_SCAN_ALLOW_FS_ESP now also displays EFI harddisk icon (I don't know for which of my 3 drives but I assume OC drive). I am setting scanPolicy value to 0x010F0503.The HideSelf setting has now been removed from OC 0.5.9 is that the problem ?.
4. The OC boot log now shows "Invalid file system policy (200/10F0503) for BB94DA98". Here's a snapshot"

   
   07:077 00:005 OCB: Adding fs BBBACE98 (E:0|L:1|P:Success) - PciRoot(0x0)/Pci(0x1,0x1)/Pci(0x0,0x0)/NVMe(0x1,36-39-28-51-29-A7-79-64)/HD(1,GPT,48FD2EC1-C3AE-4458-B959-BDBEED7D2ABE,0x28,0x64000)
   07:079 00:002 OCB: Adding fs BB983B18 (E:0|L:0|P:Success) - PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0xFFFF,0x0)/HD(1,GPT,B23BFB37-1721-48BA-823F-76152B5DC630,0x28,0x64000)
   07:082 00:002 OCB: Adding fs BB95DB18 (E:0|L:0|P:Success) - PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x1,0xFFFF,0x0)/HD(1,GPT,A4CE4F1A-43C6-492D-BB16-2DD6EABCE4EF,0x28,0x64000)
   07:083 00:001 OCPI: Located cached partition entries
   07:085 00:001 OCB: Invalid file system policy (200/10F0503) for BB94DA98
   07:087 00:001 OCB: Adding fs BB94DA98 (E:0|L:0|P:Security Violation) - PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x1,0xFFFF,0x0)/HD(7,GPT,8B191946-A4A6-4CDF-8D18-F0E28B417C68,0x574107A8,0x135F20)
   07:088 00:001 OCPI: Located cached partition entries

    

 

1. above you explained. 2/3. OC now lists EFI drive as bootable now that there's no HideSelf setting. How do we stop EFI drive being listed ?

4. With ScanPolicy of 0x010F0503, the OC log file shows (a warning ?) : "Invalid file system policy (200/10F0503)" @Andrey1970 explained that's because I did not enable the bit 9 (OC_SCAN_ALLOW_FS_HFS) which is needed for macOS Recovery. Recommendation: this should be documented and FailSafe value should be changed to 0x010F0303 (to avoid the error/warning in the OC log).

I now set the ScanPolicy to 0x010F0703 and this "warning" disappears from the OC log.

 

Thanks for all your work and continuous improvements all you Devs are making to this great project. 

[Synapsis]

@vit9696please use a utf8 capable typeface font, if I may suggest a freely available superior fonts:

Input Its superior to other rip-off of it (fontbureau actually knows their s**t)

 

https://input.fontbureau.com/download

https://www.jetbrains.com/de-de/lp/mono

https://fonts.google.com/specimen/IBM+Plex+Mono

 

Jetbrains mono (allthough I dont know if it can be used that way, allthough its a heavily "inspired" by FontBurea Input.

 

For sans-serif typeface (aka copytext), you can use Input Sans which is also quite nice, but I suggest IBM Plex Serif, for all

copy/headlines textes and Input for code listing

 

Please, don't use any half-as*ed fonts like MS Consolas or MS Cascadia, it seems they werer "designed" by people not yet

fully aware the 21st century arrived some time ago and they missed stuff like HIDPI devices, preper hinting and ligatures.

Edited May 21, 2020 by Synapsis
double

[arsradu]

42 minutes ago, Synapsis said:

@vit9696please use a utf8 capable typeface font, if I may suggest a freely available superior fonts:

Input Its superior to other rip-off of it (fontbureau actually knows their s**t)

 

https://input.fontbureau.com/download

https://www.jetbrains.com/de-de/lp/mono

https://fonts.google.com/specimen/IBM+Plex+Mono

 

Jetbrains mono (allthough I dont know if it can be used that way, allthough its a heavily "inspired" by FontBurea Input.

 

For sans-serif typeface (aka copytext), you can use Input Sans which is also quite nice, but I suggest IBM Plex Serif, for all

copy/headlines textes and Input for code listing

 

Please, don't use any half-as*ed fonts like MS Consolas or MS Cascadia, it seems they werer "designed" by people not yet

fully aware the 21st century arrived some time ago and they missed stuff like HIDPI devices, preper hinting and ligatures.

 

Speaking of fonts, I also liked this one from Google Font Directory. Probably less interesting than the IBM Plex (really nice one, by the way). Still very nice and simple. And it seems to have glyphs for other languages, too (including Russian, some special characters for French, I think I saw some Polish ones as well, a few Romanian ones, too, but not all, and probably others, too). So yeah, not bad.

 

You can probably tell I'm not any kind of expert in fonts and stuff like that. :)) I just analyse them mostly on a "visual" basis, and that's about it. I mean, I know the point is to be easy to read. And, you have to have (at least for the language they're meant to be used for) a complete set of glyphs, otherwise you're probably gonna have fonts from different families which is gonna look like garbage, but...specific stuff about them...I leave that to the people with more experience. :))

 

There are a ton of beautiful fonts out there. And the ones from Google if I'm not mistaken are also free to do anything with them, except selling them as your own, of course. Cause that wouldn't be fair to the author(s). But otherwise...yeah, free to use.

Edited May 21, 2020 by arsradu

[pkdesign]

Source Code Pro is another great font. Lots of variation.