- Joined
- Dec 10, 2010
- Messages
- 1,378
- Motherboard
- Gigabyte Z390 Aorus Elite
- CPU
- i9-9900K
- Graphics
- RX 6600 XT
- Mobile Phone
Which error message? None?Seems I got past OC 0.6.9 validation
Security fail at boot.
Which error message? None?Seems I got past OC 0.6.9 validation
Security fail at boot.
set Vault to OptionalView attachment 518925
This is the error I’m getting.
@Feartech vault is set to Optional.set Vault to Optional
XCode is nice, especially for binary values, but heavy, and I sometimes had issues opening with ProperTree a file which had been edited by XCode. So now I tend to only use ProperTree (and live with byte swapping binary data…) or TextEdit for editing.Could someone expand on what the most consistent methods of updating your config.plist would be.
Golden advice Removing unnecessary quirks improves your hack—and sometimes opens the road to full success!- hit 7 "Compare": this will display the differences, now it's up to you to use whatever editor to add new keys, etc. Note that you certainly have additional keys specific to your build in your config.plist, so of course don't delete them... But it's a good time to check if they're really needed or have become obsolete.
AFAICT, you can skip all the errors marked "skipped" but you'll have to change the type from String to Data for the setting in config.plist -> NVRAM -> Add -> 7C436110-AB2A-4BBB-A880-FE41995C9F82 -> prev-lang:kbdI installed OS X Monterey Beta with OC 0.7.1. I would like to get some assistance in finding out the reason why I am getting this error message just before the picker displays; ocs: Failed to calculate size of array field containing <empty> as type data, context <Patch>. I have tried using OCConfigcompare, and the result is attached. I cannot quite figure out what the error message is telling me.
Thank you for your help in advance.
As for the "skipped" messages, they only appeared with the last version(s?) of OCConfigcompare: with the same config.plist, I first checked with an old one (from April, I believe) and they didn't show up, then I had the idea to update OCConfigcompare and had the same as you. Here, everything is working ok without caring for those issues (might be a bug in OCConfigcompare, who knows...)@Nodarkthings,
Thank you for your quick response.
According to the picture below;
View attachment 524321
it appears that it can be either way. However, I did change it as you suggested though.
As to the error message, there are three <Patch>es; ACPI, Booter, and Kernel. I compared them with the Sample.plist line-by-line, they are all agreed with each other. Still trying to decipher the error........ when I use ocvalidate, this is the message;View attachment 524323
Not sure if there is any way related.....