even if the use of HFSPlus.efi driver is KINDA depricated since I THINK (someone need to check) Clover already gives the hfs driver when installing, and you still need to give more reasons for "Why UEFI/GPT?" (And optionally show what's UEFI and GPT) GOOD WORK
HFSPlus.efi was taken out of CloverEFI's "boot" file after r2986 (for licensing/distribution reasons since copyright belongs to Apple) and replaced with VBoxHfs-64.efi. For Clover r3042+, you can add HFSPlus.efi in /EFI/CLOVER/drivers64 to over-ride the inbuilt VBox driver.
If you compile Clover yourself with CloverGrowerPro, you can also specify the "boot" file to include HFSPlus.efi instead of the default VBoxHfs-64.efi.
Advantages of VBoxHfs-64.efi - Open source, supports sym links and aliases but slow
Advantages of HFSPlus.efi - faster boot performance
making a os x install guide will just gather bees around ya, and as you know, noobs are noobs, they need to flood you with questions, that's why I referred to this guide, so no one will have any question since this guide is so complete just make sure to tell them to skip the bootloader part OR to fuse them both
Hahahaha...LOL...Very true @midi. They'll just say "it doesn't work!!" and NOT provide details of what they actually did....
I alluded to some of the advantages of GPT and why install UEFI Windows when using Clover in post #344.
Congratulations and great to see your guide coming along .
One problem with Clover on legacy BIOS machines can be the long delay in booting to the Clover Menu. You can greatly speed up the boot process by using the "BiosBlock IO" install option (speeds the process of initialising USB) if your BIOS is compatible.
Also you don't have to install any drivers in EFI/CLOVER/drivers64UEFI (these are for UEFI booting). When I first converted from Chameleon to Clover, I followed BatcOuntrY's Non UEFI guide which mentioned installing EmuVariableUefi-64.efi in EFI/CLOVER/drivers64UEFI. I've since discovered this is not necessary for legacy BIOS booting .