Hackintool VS SSDTTime

AIO display may be using a different display connector (probably LVDS which is mostly uses in laptops). Could have a look at hackintool and check what connectors need patching. Hope it helps.

Easiest way I've found to mounting it is with Hackintool from the Disks tab, you'll want to use that tool either way if you're fiddling around with a Hack.

The USB mapping method using Hackintool explained in the post here worked perfectly for me.

Yes. Download hackintool and go to section Boot - then you can see it.

Download Hackintool to confirm your ports are working properly. This is also a handy tool to see all of your active kexts, check for updates etc. I often use it to update my kexts.

A quick thought: Something similar (many) already exist. One is https://www.sl-soft.de/en/kext-updater/, another is https://github.com/ic005k/OCAuxiliaryTools, another is https://github.com/headkaze/Hackintool. Does yours offer something different?

First we need to download these three Applications: Hackintool, AWEDIDEditor and HexFiend

1: Make sure your OpenCore is updated to at least 0.8.2, you can check what version of OpenCore you have using Hackintool under the boot section.

Build SSDT-EC, SSDT-USBX, SSDT-XOSI, SSDT-PLUG, and SSDT-HPET from SSDTTime instead of manually https://github.com/corpnewt/SSDTTime

I'm trying to do a fresh install of Ventura. I tried using SSDTTime from my Catalina at first, only to discover that the option to dump DSDT is disabled by design because that'll not give me the unadulterated DSDT which makes sense.

Precisely, I went through the guide once more, discovered some new tools (like USBToolBox for example) then I did USB mapping + SSDTs (using SSDTTime) by hand (I was not sure that I did them properly in the first place, 3 years ago). Then with those clean SSDTs & kext, I used my old EFI and OCAT to merge everything together. Double checked everything at the end just to be sure that I did not forget a thing and that OCAT did not mess up anything.

I couldn't get past this point in mine without running https://github.com/corpnewt/SSDTTime and enabling `SetupVirtualMap` in Booter Quirks

It's a must though. Every PC is different, even 2 identical models might not have the same ACPI tables.. I would Start here.. There's only a few things you'll really need, especially on these machines. While there's many methods, a clean install of windows NOT booted through OpenCore, using SSDTime is the easiest for most.

I built my own SSDTs using SSDTTime.

OpenCore 0.8.7 / Dumping DSDT use SSDTTime for generate ACPI Tables / Use genSMBIOS for generate MLB (Board Serial), ROM (Mac Address), SystemSerialNumber (Serial), SystemUUID (SmUUID)

[1]: https://www.youtube.com/watch?v=DhN35HNsYDg [2]: https://dortania.github.io/Getting-Started-With-ACPI/ssdt-methods/ssdt-long.html [3]: https://dortania.github.io/Getting-Started-With-ACPI/ssdt-methods/ssdt-easy.html [4]: https://dortania.github.io/Getting-Started-With-ACPI/ssdt-methods/ssdt-easy.html#running-ssdttime [5]: https://github.com/corpnewt/SSDTTime [6]: https://dortania.github.io/Getting-Started-With-ACPI/Universal/ec-methods/manual.html#pnp0c09-already-has-an-sta-method

try mapping usb drive on windows first using USBToolBox as USBInjectAll isn't fully working anymore on Monterey. Also I suggest creating your own SSDT/acpi patches via SSDTTime.

If so, switch back to AppleALC and add SSDT-HPET.aml with the patches in the patches.plist generated in SSDTTime (https://github.com/corpnewt/SSDTTime).