Slice is glad to present a new EFI bootloader. CLOVER Now version 2 rEFIt based.
It is open source based on different projects: Chameleon, rEFIt, XNU, VirtualBox. The main is EDK2 latest revision. I also want to thank all who help Slice with the development. Credits and copyrights remain in the sources. http://cloverefiboot.sourceforge.net/
If you have a question please provide outputs from DarwinDumper (formed from Trauma tool). Thanks Trauma! Continued by blackosx and STLVNUB.
How to do UEFI boot
How to use - common words
Calculator for Automatic DSDT fix
Instructions for GraphicsInjector
Any kexts patching with some Samples
Hiding unnecessary menu entries
Instruction for DSDT corrections to do DeviceInjection works
About kexts injection
Instructions for P- and C-states generator
Patching DSDT to get Sleep working
CPU settings and geekbench
ACPI tables loading
How to make orange icons to be metallic
How to make software RAID (by Magnifico)
How to modify InstallESD.dmg (by shiecldk)
Using extra kexts and skipping kernelcache
Choosing EFI drivers
Automatic config.plist creating
Custom DSDT patches
How to do sleep/wake working with UEFI BOOT
DeviceID substitution (FakeID)
Using Custom OS Icons
Error allocating pages while starting OS
So at boot you will have two options: boot macOS Mojave or Windows 10
STEP 2 - Using a drive without Windows 10 installed
Disconnect system drive that contains your macOS Mojave install from computer ( This is so that Windows does not overwrite existing macOS Mojave boot loader )
Proceed with a Windows 10 UEFI install.
After installation reconnect macOS Mojave Drive, the Windows installation should now be detected and usable in Clover.
If Windows 10 is not detected or able to boot, then verify you installed Windows 10 as UEFI and not MBR ----> ( Read step 2 - For a drive with Windows 10 installed )
STEP 2 - Using a drive with Windows 10 already installed
Verify your Windows install is GPT / UEFI or MBR / Legacy BIOS.
If Windows install is GPT UEFI then Windows 10 install is ready to use at Clover boot menu, you should be able to boot into Windows directly from Clover boot screen.
But if Windows drive is detected at Clover boot screen, but when booting Windows you get a black screen with a cursor on the top left,
then this is most likely because Windows drive is MBR ( Legacy BIOS ). You can easily convert MBR to GPT using Windows MBR2GPT tool ( this saves hours work having to reinstall Windows 10 and setting up all your applications again )
If Windows 10 install is MBR / Legacy BIOS then simply convert to GPT / UEFI following instructions below ( read video summary and view video )
** To use Windows 10 MBR2GPT tool you must have Windows 10 version 1703 ( creators update ) or later and less than 3 partitions on
the Windows 10 drive **
Confirm Windows 10 drive is MBR Legacy BIOS ( in Windows Disk Management )
Reboot into Windows PE ( Advanced Startup )
Convert from MBR Legacy BIOS to GPT UEFI ( using commands below )
Verify Windows 10 drive has changed to GPT UEFI ( in Windows Disk Management )
After conversion Windows 10 is ready to use at the Clover boot menu
STEP 3 - Stop Windows Boot manager from overriding Clover boot manager
How to stop Windows boot manager from overriding your Hackintosh Clover boot manager when using dual booting between macOS and Windows
OK, I've searching for days trying to gather up the tools to make my current install work correctly. I'm well on my way. But all the links to the things I currently must have were apparently nuked "during a forum upgrade". :(
As far as EFI Studio goes; I can find many links to it. But for Insanelymac, they're broken (due to the upgrade), or for the Netkas site, they're links to either Rapidshare, or Mediafire that also no linger exist. I see many users here indicating that they used it to tweak their DSDT. But the web (google/duckduckgo), Instanelymac, and Netkas seem to have no idea where it's gone.
Could some kind soul please share a copy, or a link? I'm a loooong time hacker, and would love to bring it back to life. In fact, I'd love to improve it -- or at least bring it up to current times. If only I knew where it was.
Thank you for all your time, and consideration.
Use this thread to link / talk about of the future Nvidia Web Driver updates for macOS Sierra.
Nvidia Web Driver - 378.05.05.25f16 --> build 16G2016 (thanks to Cyberdevs) New!
Nvidia Web Driver - 378.05.05.25f15 --> build 16G1918 (thanks to BreBo)
Nvidia Web Driver - 378.05.05.25f14 --> build 16G1917 (thanks to BreBo)
Nvidia Web Driver - 378.05.05.25f13 --> build 16G1815 (thanks to flowrider)
Nvidia Web Driver - 378.05.05.25f12 --> build 16G1710 (thanks to BreBo)
Nvidia Web Driver - 378.05.05.25f11 --> build 16G1618 (thanks to Frank Nitty)
Nvidia Web Driver - 378.05.05.25f10 --> build 16G1510 (thanks to BreBo)
Nvidia Web Driver - 378.05.05.25f09 --> build 16G1408 (thanks to BreBo)
Nvidia Web Driver - 378.05.05.25f08 --> build 16G1314 (thanks to BreBo)
Nvidia Web Driver - 378.05.05.25f07 --> build 16G1314 (thanks to haring)
Nvidia Web Driver - 378.05.05.25f06 --> build 16G1212 (thanks to WeBeRiO)
Nvidia Web Driver - 378.05.05.25f04 --> build 16G1114 (thanks to lukazm)
Nvidia Web Driver - 378.05.05.25f03 --> build 16G1036 (thanks to Gradou)
Nvidia Web Driver - 378.05.05.25f01 --> build 16G29 (thanks to Badruzeus)
Nvidia Web Driver - 378.05.05.15f01 --> build 16F73 (see this post)
Nvidia Web Driver - 378.05.05.05f02 --> build 16E195(thanks to crachmaster4999)
Nvidia Web Driver - 378.05.05.05f01 --> build 16E195 (thanks to Moviemakergr) Pascal support!!!
Nvidia Web Driver - 3184.108.40.206f01 --> build 16E195 (thanks to Lanc)
Nvidia Web Driver - 3220.127.116.11f01 --> build 16D32 (thanks to shatterhenner)
Nvidia Web Driver - 318.104.22.168f02 --> build 16C68 (see this post)
Nvidia Web Driver - 322.214.171.124f01 --> build 16C67 (see this post)
Nvidia Web Driver - 3126.96.36.199b06 --> build 16C60b/16C63a (see this post)
Nvidia Web Driver - 3188.8.131.52f03 --> build 16B2657/16B2659 (thanks to Moviemakergr).
Nvidia Web Driver - 3184.108.40.206f01 --> build 16B2555 (thanks to Moviemakergr)
Nvidia Web Driver - 367.15.10.05f01 --> build 16A323 (thanks to phi777)
Nvidia Web Driver - 367.10.10.05b01 --> build 16A323 (same driver since DP4/PB3)
Nvidia Web Driver - 367.10.10.05b01 --> build 16A322 (see this post)
Nvidia Web Driver - 367.10.10.05b01 --> build 16A320 (see this post)
Nvidia Web Driver - 367.10.10.05b01 --> build 16A313a (DP8 & PB7) (see this post)
Nvidia Web Driver - 367.10.10.05b01 --> build 16A304a (DP7 & PB6) (see this post)
Nvidia Web Driver - 367.10.10.05b01 --> build 16A294a (DP6 & PB5) (see this post)
Nvidia Web Driver - 367.10.10.05b01 --> build 16A286a (DP5 & PB4) (see this post)
Nvidia Web Driver - 367.10.10.05b01 --> build 16A270f (DP4 & PB3) (thanks to TheRacerMaster)
Nvidia Web Driver - 367.05.10.05b07 --> build 16A254g (DP3 & PB2) (see this post)
Nvidia Web Driver - 367.05.10.05b07 --> build 16A238m (PB1) (thanks to Faun)
Nvidia Web Driver - 367.05.10.05b07 --> build 16A239j (DP2) (thanks to Faun)
Nvidia Web Driver - 367.05.10.05b03 --> build 16A201w (DP1) (thanks to Xmedik)