Leaderboard

@rramon Is it possible to rewrite config.plist with an XML editor (such as plistEDplus)? Then, can I download and unzip CloverV2-5134.zip from the release 5134 web page? CloverV2-5134.zip has Sample.plist, which can be used as a reference to correct the plist. (You can search with an XML editor and use it as a reference.) Open it in your config.plist (after making a duplicate) by XML editor. The item skipped by Clover is an item that you don't need, so you can search it with an XML editor and delete the line. Also, "Clover wants boolean to be true", so I think that part should be

Good. When typing into console, you have completion. So for me a long name isn't a problem. But I like ccpv too. I don't we'll ever confuse with "Club Canin du Périgord Vert" , so it's ok by me. Does everyone prefer ccpv ? Sure, yes.

scheme referred to the one into buildpkg to integrate ccpv, not when building CloverConfigPlistValidator itself... Oh yes, forgot to mention as requested ccpv, will be named after the actual clover build. this one will generate CloverConfigPlistValidator_5134 /usr/local/bin? This could be the best solution, and the easiest way to use the tool from terminal even for beginners. Proposition: if we agree to this solution, what about renaming the tool (only the one installed in /usr/local/bin) ccpv (obviously i will also add all informations into the installer locat

@Jief_Machak Just my modest opinion: validator is already provided in Github release. End users can download it along with Clover, if they need to. It seems to me the easiest solution. Advanced users can compile it manually quite easily: with instructions in a readme.file, if they wish.

I just wanted to let you know that I updated the prebuilt binary in the download section to version 2.4.2. Have fun! Mieze

@MifJpn Already in the process of doing that. I‘m down to unknown keys in custom entries - checking that right now. Edit: seemed to be the „Ignore“ key that was ignored. How ignorant^^

Open your config.plist with an editor and: - /ACPI/DSDT/DropOEM_DSM:12 delete it - /GUI/Mouse/DoubleClick:266 delete it - /KernelAndKextPatches/KernelCPU:322 delete it They are ignored now, some of them are from old config.plist or probably added in a wrong way by Clover Configurator app.

Use this Kext Droplet tool from Chris1111 there's nothing simpler than this. I am serious. Just install like any other app. This automatically drops into /L/E/ There is nothing more simpler than this. Fully GUI and does work perfectly. To set SiP in Clover or OC Configurator 0x867 from 0x67 << you know where to do this in GUI? RtVariables section. Surfs Up Kext-Droplet-V2.dmg.zip OC configurator if you do not have time get there OpenCore Configurator.zip

it does, in fact, if that was your question...

Is anyone here using apps that require SIP to be disabled? (for example AdGuard, Navicat and a few others?) I wonder if there is a way in OpenCore to set SIP in such way that it won't disabled SIP completely so that the apps could work but also the systems update could also as it is kind of pain in the ass to enable SIP, reboot, run software update, then reboot, then disable sip and then reboot again... In OpenCore website they state "Enabling CSR_ALLOW_UNAUTHENTICATED_ROOT and CSR_ALLOW_APPLE_INTERNAL are common options that can break OS updates for users", but I can't

Yes, that's true. But now it's possible to keep many Clover folder with any name, and inside each folder many clover efi file with any name, that means a user might need to keep different validator versions. So installing it by default in a small efi partition might not be a so good idea. Well spotted @MifJpn. How do we resolve that ? Is it possible that installer ask where to put it, like a save panel ?

Thank you @Mieze for also updating Git Hub releases, got a notification! Vielen Dank

Well fact is, it already builds into CloverPackage, what i find awkward is to have the installer install the tool onto the same directory already containing it. So to be clear as it seems to be a lot of misunderstandings: 1) it already builds into CloverPackage 2) does it still need to be added into the buildpkg (*see point 3 ) and if so where should it be pointed for installation? (since it builds before the pkg, its already present inside CloverPackage (1) ) 3) please correct me if i'm wrong. The release installer from https://github.com/CloverHackyColor/CloverBoo

Ideally, yes, for neatness and peace of mind. Your system booted fine before and it's very likely there was no problem caused by the global rename. But now the ability exists to target it, it's cleanest to do so.

The reason to apply the _DSM -> XDSM patch is because you have already added SSDTs that are trying to add _DSM sections, and they are conflicting with a _DSM in the same Device(s) in your system DSDT. So yes, there would be an SSDT adding a _DSM for each specific _DSM ACPI patch, but not a new SSDT - the one you were already adding. And if you don't have any SSDTs that include a _DSM and are resulting in an AE_ALREADY_EXISTS error, there's no reason to rename _DSM. Before ACPI -> Base was added to OpenCore, we used to have to rename _DSM to XDSM globally, affecti

new OpenCore has "Base" option for ACPI patches, so you can rename only some _DSM's if it is really needed

BTW i am keepin g updating the github repo of the driver, in the PPC experimental section: https://github.com/ITzTravelInTime/kx-audio-driver/tree/PPC_Experimental

I managed to build a version of the driver that loads and has features working on PPC macs, sadly playback still doesn't work, but i am working on figuring out that.

About the PPC port project i have opened a dedicated thread: https://forums.macrumors.com/threads/kx-audio-driver-sound-blaster-live-and-audigy-series-driver-os-x-ppc-porting-project.2287424/

So i have announced i am working on a powerpc kext, but what i didn't tell you is the fact that most likely the kext could also work on apple silicon using almost the exact same code, so if apple will ever release an apple silicon machine featuring pcie slots i think we can get something like the audigy rx working on those machines. All of this depends on if i am able to get it working on power pc, since both shares pretty similar models for pci device usage, that said porting this kext on other platforms i very complicated due to the huge ammount of x86-specific stuff present insi

Just an update, i have started working on a fork for PowerPc macs, this fork whould maintain x86 compatibility but it will be focused on getting the driver to work on PowerPC macs running OS X 10.5.x Here is the github branch link: https://github.com/ITzTravelInTime/kx-audio-driver/tree/PPC_Experimental Edit: This fork is currently broken, it can't work on PowerPc macs at the time of writing, because it misses support for the implemen tation of the pci I/O ports on PowerPc, as far as i know it should just work on x86 for now, with the main difference being the fact that

Hi everyone, @Jief_Machak and @Slice I have a bug to report for r5134 that is not there in r5133 unless the structure of config.plist changed. No I am getting the mouse pointer in the bootloader UI main screen in r5134 despite having it disabled (setting is respected in r5133): <key>GUI</key> <dict> <key>EmbeddedThemeType</key> <string>Dark</string> <key>Hide</key> <array> <string>Preboot</string> <string>Recovery</string> </array> <key>Mouse</key> <dict>