Jump to content
484 posts in this topic

Recommended Posts

8 hours ago, 5T33Z0 said:

Please write your own documentation for the app!

I may not be able to do this for a while, as my personal time is very limited.
Although OCAT is designed to be so simple and clear that all users can use it almost without documentation, there are already enthusiastic users who are writing documentation for OCAT, such as 5T33Z0 from Germany, and we welcome more enthusiastic users to join in, thank you.
Please believe that in the future, OCAT will become more and more simple and smart.
Thank you for your feedback and more suggestions or questions are welcome.

  • Like 1
6 hours ago, ic005k said:

"[…] there are already enthusiastic users who are writing documentation for OCAT, such as 5T33Z0 from Germany, and we welcome more enthusiastic users to join in, thank you."
 

 

Yeah, well… that's me… I think you should take a rest…

2 hours ago, 5T33Z0 said:

Yeah, well… that's me… I think you should take a rest…

Oh, oh, I just answered the user's question in a hurry without paying attention to the author of the question, please forgive my rudeness and sorry again, please don't mind.
Generally, I'm just interested in the question itself and rarely pay attention to the author who asked the question, which is probably not a good habit, sorry.
Finally, thank you for your concern, I probably really do need a break, and as always, you are welcome to contribute to OCAT, thank you.
Also, I may not come here much in the future because I'm really busy, so if you have any questions, please post them directly to GitHub, please understand.

 

  • Like 1
  • 3 weeks later...

@ic005k

 

Feature suggestion: Add preset menus for:

  • ACPI > Quirks
  • Booter > Quirks
  • Kernel > Quirks

With a preset menu for each section, it would be easy to create and share presets for various CPU models. This way, building a working config would become so easy.

Edited by 5T33Z0

Feature suggestion: please use a different identifier for the EFI disks rather than the Device name reported by the Firmware/BIOS.

 

OCAT:

927968623_Bildschirmfoto2021-12-09um18_54_55.png.ba6e7037adbd996de9144bcbf7df07f0.png

Clover Configurator:

 

1065537835_Bildschirmfoto2021-12-09um18_58_45.thumb.png.92813837f02f15d536c5a95b23b07f1c.png

In Clover Configurator I can easily see which EFI to mount because it shows the used macOS version as well.

 

Thanks

Edited by 5T33Z0
  • 2 weeks later...
  • 2 weeks later...

I guess I am confused as how this is supposed to operate. According to the readme:

Quote

How to upgrade OC automatically? (Very simple, only two steps)

  • Drag and drop the configuration file onto the OCAT interface and click "Save" on the toolbar.
  • Then click "Upgrade OC Main Program" on the toolbar, a "Synchronize OC" interface will appear, Click the "Start Sync" button below to finish the OC upgrade.

I may be blind, but I don't see 

"Upgrade OC Main Program" on the toolbar

If I copy my existing config file to a brand new OC directory and open it from there synchronize activates, but then it cannot find half of the kexts online. If I open the config file within my original OC folder synchronize does not activate. Am I missing something?

 

Edit: I think I got it. It needs the whole EFI structure not just the OC folder

Edited by startergo
1 hour ago, 5T33Z0 said:

@startergo Sync is only available if the ESP is mounted and the config.plist inside its EFI folder is opened.

It is not necessary for the ESP to be mounted. What is important is to keep the EFI structure. In fact I operated with the EFI folder copied to My Documents.

45 minutes ago, eSaF said:

I am sorry but this is wrong, as stated the ESP must be mounted to enable OCAT to scan the files, that way you can see at a glance any misalignments in the config.plist using the builtin OCValidate plus using the synchronising tab will also enable you to see what Drivers and kexts may need updating.

What I said is that the contents of the ESP can be copied elsewhere and it can be set as a working directory and later pasted back to the ESP. There is no nececity to work directly on the ESP therefore it is not necessary to be mounted during the update. 

@startergo What you said was "Sync is not available".

 

  1. It's true that you can download an EFI Folder from somewhere and then open the config in OCAT and sync it because you have access to the files, since they are accessible on the disc. Or you can copy the EFI folder from the ESP to the desktop or elsewhere and update it this way and sync will be available
  2. What's not true is your 2nd statement: "There is no nececity [sic!] to work directly on the ESP therefore it is not necessary to be mounted during the update."  This deductions is completely wrong and illogical. You cannot update something if you don't have access to the files you want to update. And you don't have access to the files if you don't mount the ESP to make the files accessible to the system, specifically OCAT. In other words: No mount = no access to the files = no sync function. Simple as that.

 

 

 

6 hours ago, 5T33Z0 said:

@startergo What you said was "Sync is not available".

 

  1. It's true that you can download an EFI Folder from somewhere and then open the config in OCAT and sync it because you have access to the files, since they are accessible on the disc. Or you can copy the EFI folder from the ESP to the desktop or elsewhere and update it this way and sync will be available
  2. What's not true is your 2nd statement: "There is no nececity [sic!] to work directly on the ESP therefore it is not necessary to be mounted during the update."  This deductions is completely wrong and illogical. You cannot update something if you don't have access to the files you want to update. And you don't have access to the files if you don't mount the ESP to make the files accessible to the system, specifically OCAT. In other words: No mount = no access to the files = no sync function. Simple as that.

 

 

 

Why would someone assume that he can update the ESP partition without mounting the ESP folder? This is completely off topic. The topic is the OpenCore update/upgrade program. 

  • 2 weeks later...

Tried it yesterday for the first time and it really does a great job. From 0.7.4 to a booting 0.7.6 configuration with the newest kext files. Great work! 

@ic005k New Settings/Keys for UEFI > Audio in latest nightly build:

 

        <key>Audio</key>
        <dict>
            <key>AudioCodec</key>
            <integer>0</integer>
            <key>AudioDevice</key>
            <string>PciRoot(0x0)/Pci(0x1b,0x0)</string>
            <key>AudioOutMask</key>
            <integer>1</integer>
            <key>AudioSupport</key>
            <false/>
            <key>DisconnectHda</key>
            <false/>
            <key>MaximumGain</key>
            <integer>-15</integer>
            <key>MinimumAssistGain</key>
            <integer>-30</integer>
            <key>MinimumAudibleGain</key>
            <integer>-55</integer>
            <key>PlayChime</key>
            <string>Auto</string>
            <key>ResetTrafficClass</key>
            <false/>
            <key>SetupDelay</key>
            <integer>0</integer>
        </dict>

 

Edited by 5T33Z0
  • 3 weeks later...

Hi,

Just a notice:

Windows Defender found  '@OCAT.exe' as a potentially unwanted application.

I'm pretty sure it's false but you might want to look into it so this msg won't appear in the future.

 

Spoiler

image.thumb.png.62f103648af3329600bb4afc6f305a56.png

 

1 hour ago, kushwavez said:

Windows Defender found  '@OCAT.exe' as a potentially unwanted application.

For more information on this issue, please see here: https://github.com/ic005k/QtOpenCoreConfig/issues/106

  • Like 1
×
×
  • Create New...