Open source cross-platform OpenCore Auxiliary Tools（OCAT)

[Guest 5T33Z0]

@ic005k OCAT killed my config. I forgot to close the app after saving. Then I rebooted and the config was corrupted:

 

Beginning of file:

>> Header is ****ed.

 

Then I tried fixing it and noticed that it had been after the End of the file:

Anyway, I couldn't reconstruct the plist. Luckily, I had a backup. But this is a serious issue.

 

[ic005k]

13 minutes ago, 5T33Z0 said:

OCAT killed my config. I forgot to close the app after saving. Then I rebooted and the config was corrupted

This problem will never happen, whether you save or not, OCAT will not damage your profile without turning it off. You can test it again.
There is a possibility that your configuration file is being opened by other software at the same time, which may cause your configuration file to be corrupted.
In any case, I will keep an eye on this issue and appreciate the feedback.

[ic005k]

@5T33Z0 

In terms of design principles, because OCAT does not have a write operation at any other time unless you save it, the configuration file corruption is 100% not caused by OCAT.

You can test it repeatedly.

[ic005k]

@5T33Z0 OCAT is very reliable in the underlying design. You are very welcome to conduct high-intensity tests.

[junaed.rx]

Hello @ic005k,

 

I found there is no boolean class in NVRAM varaible. Could you please add that variable class. Now we have to use string with YES or NO value. I don't know if it has any difference.

 

regards

Junaed

 

[ic005k]

8 hours ago, junaed.rx said:

Now we have to use string with YES or NO value.

Although the value is "YES" or "NO", its data type is still "string", so it is not a Boolean type.
But I am not sure if it is necessary to add a boolean data type, if it is necessary, I will add it, it is very simple.

[Guest 5T33Z0]

19 hours ago, ic005k said:

Although the value is "YES" or "NO", its data type is still "string", so it is not a Boolean type.
But I am not sure if it is necessary to add a boolean data type, if it is necessary, I will add it, it is very simple.

 

So far, I haven't seen any keys in Boolean in the NVRAM Section. And I don't know if OpenCore could interpret the value of a key if you switched it to boolean – even if it's just about "true" or "false".

[junaed.rx]

6 minutes ago, 5T33Z0 said:

So far, I haven't seen any keys in Boolean in the NVRAM Section. And I don't know if OpenCore could interpret the value of a key if you switched it to boolean – even if it's just about "true" or "false".

Actually I also don't care about it that much. I noticed it when I tried to set NVRAM variable of HibernationFixup.kext per it's documentaion. Where it mentioned bunch of NVRAM variables with boolean type. That's why I thought, for the sake of fine tuning of OCAT, this could be included. Nothing more. Here is the link: HibernationFixup. See NVRAM Options section. 

[ic005k]

2 hours ago, junaed.rx said:

Here is the link: HibernationFixup. See NVRAM Options section. 

It looks like the boolean type is needed and I will add it.

[Guest 5T33Z0]

OCAT killed config again. Can someone help me to fix it?

 

config.plist

[ic005k]

@5T33Z0Hi, for safety reasons, please suspend the use of OCAT or wait until you find the cause before you start using it. I will analyze this file you provided and find the reason together, thanks.

[ic005k]

@5T33Z0Can you tell me your country or region, I would like to know the local text encoding in your region, please.
OCAT writes files in UTF-8 text encoding.

[Guest 5T33Z0]

Region in System Settings is set to German. I think this issue only occurs after saving the file and then rebooting without quitting the app.

[ic005k]

@5T33Z0Did you have your config.plist file open in another text editor without closing it when you rebooted the system? Thanks.

[ic005k]

18 hours ago, 5T33Z0 said:

I think this issue only occurs after saving the file and then rebooting without quitting the app.

I think this problem has something to do with config.plist being opened by some text editor. Please recall carefully if your config.plist was opened by a text editor when this problem occurred.

[ic005k]

@5T33Z0In terms of technical principles, if this problem was created by OCAT, then it would have been a problem to begin with, that is, as soon as the config.plist is saved, it would destroy that config.plist.
Although I am interested in this issue, I still can't figure it out at the moment and I will continue to analyze it.

[niknod]

I had same problem I updated using ocat than when opened with proper tree and sync and saved it destroyed my config.plist wouldn't boot.

[ic005k]

1 hour ago, niknod said:

I had same problem I updated using ocat than when opened with proper tree and sync and saved it destroyed my config.plist wouldn't boot.

The corruption we are talking about is that the file is corrupted and cannot be opened, for example, when you open this config.plist with a text editor, it shows a mess of codes, not that the OC is not set correctly and cannot be booted.
Please provide your corrupted config.plist file and I will analyze it on my side, thanks.

[niknod]

Also if I sync and save with OCAT and I use sanity checker it shows as uefi drivers openruntime and OpenHfsPlus disabled. but in OCAT UEFI Drivers shows Enabled

[ic005k]

@niknod

Also, if you need to use OCAT's Sync OC feature, you need to save your config.plist and upgrade it to the latest version at the same time.

If you just synchronize the OC without upgrading the config.plist (save it in OCAT), the OC may not boot properly.

11 minutes ago, niknod said:

I use sanity checker

What is this software? Is it officially provided by OC? Otherwise, please ignore it.
All the tools used by OCAT are officially provided by OC, please refer to OC official.

[Guest 5T33Z0]

2 hours ago, ic005k said:

@niknod

What is this software? Is it officially provided by OC? Otherwise, please ignore it.

All the tools used by OCAT are officially provided by OC, please refer to OC official.

 

It's a website which uses data from the install guide to compare it with the settings in the config.plist to check if you have the correct settings for the selected cpu family. It is no longer maintained.

 

https://opencore.slowgeek.com/ 

[ic005k]

@5T33Z0I recommend that you only use OCAT for now and suspend the other editors, or upgrade the other editors to the latest version and see what happens. If you use OCAT alone, I believe there will be no problem.
As always, you are welcome to suggest improvements or ask any questions about OCAT. Thank you.

[Guest 5T33Z0]

@ic005k Okay. One thing I wish would be different is the behavior of the "Generate"  function in the ProductInfo Section. As of now, it auto-generates new SMBIOS Data as soon as you change the model. If I change the SystemProductName from MacBookPro10,1 to MacBookPro11,4 (which I need to do for installing macOS Monterey Updates), it generates new SMBIOS data automatically. It would be good if it wouldn't do that automatically. Otherwise I have to edit the file in a plist editor. So, changing the generate options from auto to manual would be useful.

Edited October 10, 2021 by 5T33Z0

[ic005k]

1 hour ago, 5T33Z0 said:

changing the generate options from auto to manual would be useful.

Ok, the next release will implement it.

[Guest 5T33Z0]

@ic005k When updating OpenCore and Resources, it puts .icns files where they don't belong.

 

"Image" folder structure in original OcBinaryData:

 

Image folder after updating with OCAT: