Jump to content



Member Since 21 Jun 2009
Offline Last Active 53 minutes ago

Posts I've Made

In Topic: AptioMemoryFix

54 minutes ago

I refactored RTShims.nasm in Clover r4390 so the shim code only appears once.  It's attached if you want to use it.

In Topic: Clover General discussion

Today, 11:34 AM

@Sherlocks, STLVNUB:
Problem fixed in r4387.  You can return to same setup and driver names you were using < r4384.
The priority is

Use the highest that works.
If you don't need nvram access from OS/X and don't want the extra overhead, delete the first two from the list.

In Topic: Clover problems report & features request

Yesterday, 11:12 AM

Before 4385, if you had both OsxAptioFixDrv and OsxAptioFix2Drv in drivers64UEFI, it would pick up the one that occurs first in the FAT32 directory iteration.  After 4385 there is a prioritisation, so OsxAptioFix2Drv is picked up first.  I suggest you keep just the one that works for use in drivers64UEFI and move the others to drivers-Off/drivers64UEFI.


Had to change OsxAptioFixDrv2 to  OsxAptioFixDrv for 4385  :thumbsup_anim:

In Topic: Clover problems report & features request

18 January 2018 - 05:02 PM

Try r4385


Anybody tried 4384, don't work here, had to revert to 4380

In Topic: Clover General discussion

07 January 2018 - 04:56 PM

There is a fix for bug introduced by AMI UEFI BIOS.
As well whole AptioFix was developed to fight with AMI AllocateMemory() stupid function while EDK2 AllocateMemory is good. See legacy Clover == CloverEFI doesn't need AptioFix.

I have AMI firmware, and it needs either of the AptioFixDrv to work. I don't know which "Aptio" it is because there's no indication. It's made by MB manufacturer. Is there any way to identify the "Aptio" version?
© 2017 InsanelyMac  |   News  |   Forum  |   Downloads  |   OSx86 Wiki  |   Designed by Ed Gain  |   Logo by irfan  |   Privacy Policy