Title says it all. Please do not use this driver, like ever. It was meant to test a bug on a specific platform and for some reason is now being used as if it was not just completely freeing a ton of memory that is probably needed for your system to actually function correctly. This driver can cause your mobo to be bricked or even damage components. If you must use this driver to get functioning system I would suggest that you try to use one of the other newer drivers (OsxAptioFix3Drv or AptioMemoryFix), build a different system, or at least know that I am sorry for all the pain I have inflicted upon your poor hack... Rest in peace, poor little machines. You were a good boi and I just let these jackals tear you to shreds.
EDIT: Because many have asked about this, there is always a probability that you can damage your hardware no matter what by hacking. This probability is extremely small and based more on your own actions than anything. However, this driver basically ensures that eventually, your hardware will be damaged regardless of your actions.
EDIT2: You should try using fix drivers in this order, AptioMemoryFix, OsxAptioFix3Drv, OsxAptioFix2Drv, OsxAptioFixDrv. The first three try without and with slide calculation, the last always uses slide=0 (and must to work) so no need to provide slide. Most likely you only need to calculate the slide once as the largest available region is always the largest available region. How to calculate your slide from my comment below.
EDIT3: I'm glad I'm seeing people who thought that this was there only solution getting their system working using one of the other drivers. I've never felt more proud of you guys... Dang onion ninjas....
EDIT4: You can almost always change your firmware settings to disable stuff you don't need or to delay devices allocating memory until needed (fast boot) and get a better memory map for booting. There may be downsides to this though so just be aware that you indeed do not need something.
楼主: 夜雨声烦丶薇
