Open source cross-platform OpenCore Auxiliary Tools（OCAT)

[eSaF]

5 hours ago, fuzzylogic said:

for now if i pick dev in the drop down ocat changes to 82, if i pick debug it goes back to 78, 

deleted oc hidden folder as per instruction, not sure why 78 seems so prev but at least with Edit opencore dev it changes

ironically i have opencore version 83 and beta kext so not sure why ocat aux tools does not reflect the actual opencore efi folder with opencore version 83 

thanks for helping out

 

 

Hi, sorry to interrupt but it's strange the latest version reverts to an older one. Just as a matter of interest, have you maybe got more than one OS X versions running in a multi-boot setup with an older OCAT version somewhere there? Because if you followed the advice @5T33Z0 offered in his post by cleaning the troublesome version from your system and then installing the latest version, then you should have no problem unless it is picking up old OCAT data stored elsewhere on the machine.

[Guest 5T33Z0]

@fuzzylogic Well, that's becaus the DEBUG version of OpenCoere stored in your DATABASE is still on Version 078! You need to update that as well. SAME INSTRUCTIONS (STEPS 9 to 11) apply!

 

OCAT can download and install 4 variants of OpenCore:

 

Release (has its own version)

Release Debug (has its own version)

Dev (has its own version)

Dev Debug (has its own version)

 

ALL these VARIANTS have to be downloaded and present in the DATABASE so the correct and latest version is displayed – there is an error message displayed it it is not present.

 

And if you would have read my guide on github you would know all this!

[fuzzylogic]

Thankyou for your help, i have both monterey and ventura on one nvme but both use the same EFI folder. I have loaded up Monterey and checked for hidden files and folders OCAT was never installed on Monterey in order to boot Ventura the EFI file and kext had to be updated to EFI 83 with Beta kext otherwise Ventura would not install. I am sure over time I will figure out what is going on, its not the case that version 78 of opencore exist, as Ventura would not install or run

thankyou once again it is very much appreciated

[Guest 5T33Z0]

It doesn't matter, if you use the same EFI folder or not. This is NOT ABUT THE EFI FOLDER, ITS ABOUT THE APP, more specifically: its DATABASE. It can store 4 different variants of OpenCore (as explained already). And this Database is installed somewhere on your system, if you ever downloaded an OpenCore update through OCAT.

 

If OCAT was never installed on the Monterey disk, why did you look for hidden OCAT folder on that drive in the first place– it makes absolutely no sense to do that…

 

Since you have 083 installed, you need to switch the App to DEV mode and download the latest build so it's in the DATABASE, SO that the correct version is displayed. I don't know what's so hard to understand about it

[fuzzylogic]

Hi and thankyou for taking the time to reply, I had big sur and Monterey on one nvme, I removed big sur and installed ventura I assumed that becaue Big sur was the startup because this was the first os installed, then monterey and formating big sur would remove all traces of Big Sur, so I now have ventura and Monterey on one nvme, I checked and did find a hidden folder for ocat but thought it may well have been the new ocat considering big sur partition was wiped .

I manually downloaded opencore 83 and beta kext and replaced the EFI folder, when I went to check the EFI folder due to a change in one Kext I found I was stuck on ocat version 78 no matter what i did i could only update to version 78. I then tried dev and get opencore latest and now the ocat reports version 82, but i know that version 83 beta is installed as I have a backup on the desktop, anyway at least i now seem to have ocat report version 82 which technically is incorrect given that the installed version is 83, I am happy enough that it no longer shows ocat 78.

I appreciate your help at least now it reports 82, it would have been a nice touch if opencore displayed the boot version

[Guest ricoc90]

@fuzzylogic The version number is not reflecting the version of OpenCore on your EFI, but the github repo OCAT is using. It is showing 0.8.2 because you haven't selected Dev:

Edited July 23, 2022 by ricoc90

[Guest 5T33Z0]

@ricoc90 Don't waste your time, I already explained this to him at least 5 times already… I even added it to my OpenCore updade guide.

Edited July 23, 2022 by 5T33Z0

[Guest 5T33Z0]

There's currently a bug in OCAT where disabling "LoadEarly" settings are not applied to the config.plist (although it looks like it). Should be set to "false" when unchecked.

 

[Guest 5T33Z0]

The "LoadEarly" issue has been fixed in the latest update (20220229)

 

I've check the manual: the LoadEarly feature is only required for emulated n NVRAM, which requires "OpenVariableRuntimeDxe.efi". In this case you have to enable "LoadEarly" for this as well as for "OpenRuntime.efi"

[eSaF]

1 hour ago, 5T33Z0 said:

The "LoadEarly" issue has been fixed in the latest update (20220229)

Yea the last version caused me a non-boot before I figured what was happening, usually I do a manual cross check after a OC update with PlistEdit Pro but on this occasion I didn't and OCAT let me down. All is well now after the bug fix.

[deeveedee]

I don't use OCAT (just my preference), but I am occasionally debugging config.plists that have been generated with OCAT. Does OCAT include an option to export a "sanitized" config.plist that excludes PlatformInfo > Generic > MLB, ROM, etc. so that it can be shared in a public forum?  If not, maybe it should?

[PippoX0]

Nice tool

[Olroy]

It's normal ? The version I use in windows 10 (20220236) tells me a threat (virus?). Windows Defendeur refuses and deletes it!

[makk]

5 hours ago, Olroy said:

It's normal ? The version I use in windows 10 (20220236) tells me a threat (virus?). Windows Defendeur refuses and deletes it!

Turn off that idiot Virus Protection nothing but troubles, run two firewalls one with all the trimmings and the other to protect from outside intrusion such as ping monster, double packer, so forth. 

Microsoft micro manager system is junk ruins your privacy.  

Edited November 17, 2022 by makk

[Drovosek]

Hello.

 

Anybody tell me, please, is it normal that the program shows the version of OpenCore 0.78 at the top left at the first launch, although now the latest version is 0.87?

 

I seem to have figured out how to change this, I am interested in exactly what is displayed at the first launches of the program without applying any settings

 

[eSaF]

1 hour ago, Drovosek said:

Anybody tell me, please, is it normal that the program shows the version of OpenCore 0.78 at the top left at the first launch, although now the latest version is 0.87?

I think that's normal until the data base within is updated to the latest OC version.

[pkdesign]

On 12/8/2022 at 11:32 AM, Drovosek said:

Hello.

 

Anybody tell me, please, is it normal that the program shows the version of OpenCore 0.78 at the top left at the first launch, although now the latest version is 0.87?

 

I seem to have figured out how to change this, I am interested in exactly what is displayed at the first launches of the program without applying any settings

 

[jlrycm]

@ic005k The OCAT is really great, so far the best I've seen to manage OC config.plist files. I do have a question: how can I edit the config file in OCAT without OCAT erasing the "EnableForAll" entries that I add in ACPI and Booter Quirks when I'm using the OpenCore MOD version?

[Anto65]

Of course you have to use the Mod version https://github.com/wjz304/OpenCore_NO_ACPI_Build/releases/tag/0.8.8_7eaedb9 ... the official version will restore the plist by deleting "EnableForAll" 

 

You can import the zip.( mode ) in the OCAT database switch first to Dev

 

 

 

 

 

 

 

Edited December 21, 2022 by antuneddu

[SavageAUS]

Can OCAT create a UEFI secure bootable OC?
Surely I cannot be the only one who would like this feature.


Sent from my iPhone using Tapatalk

[Matgen84]

Hi @ic005k

Thank your for your tool.

 

Is it possible to add number commit to Opencore zip: for example, Opencore-0-9-0_ba22024_RELEASE.zip instead of Opencore-0-9-0-RELEASE.zip 😊 in this way we can identify each build

[Andy Vandijck]

I have ported OCAT to Qt 6

https://github.com/andyvand/OCAuxiliaryTools

 

[Andy Vandijck]

Built binaries using Qt 6.

- ARM64 and X86_64 macOS

- X86 Windows (Win32)

- AMD64 Windows (Win64)

- ARM64 Windows (WinARM64)

 

Download:

https://github.com/andyvand/OCAuxiliaryTools/releases/tag/20240002

Edited February 5 by Andy Vandijck

[pkdesign]

I'm confused. How is this different from the original app and why do I need it?

[Anto65]

Out of curiosity I tried it and received this at startup

 

Spoiler

 

I don't know if it was my mistake but by reinstalling the official version, it started correctly

Edited February 5 by Antonuccio