Thks everybody for your assistance in getting me on the right track. I have progressed
considerably thanks to all your inputs.
Clover is currently running on my EFI partition formatted to HFS and not FAT32 ESP as
the UEFI specification recommends. Both formatting types work equally well.
I use the Apple format for the EFI pertition because Apple is deliberately deviating with its own hardware from the UEFI spec. I think Apple considers it's HFS formatting scheme superior and more robust than FAT32 ESP. I somehow agree however on such a small sized partition I would assume the advantages of HFS over FAT32 ESP are negligible. But I want to build an "Apple"
hence my choice to go for HFS in EFI.
Clover had no problems installing itself on my HFS EFI partition.
I did migrate from a working Yosemite 10.10.1 Uni/Multibeast Chameleon installation to
Clover, starting at point 4 of tonymac86's guide. Everything was working one shot.
Sound, networking sleep you name it, except Face Time and iMessage, which I have never attempted to get working before my excursion into Clover.
That I will however tackle next, using the MacPro5.1 system definition, which appears
pretty close to what we are using in terms of our mobos.
I still have quite a bit of reading to do before I make my hands too dirty in trying to get
iMessage and Face Time working, although I don't think it will take me ages to accomplish, as Clover is stable and functional.
At the moment I would like to cleanup Clover's boot screen, preferably booting straight
into Yosemite bypassing that screen altogether. I use multiple operating systems with only data disks installed inside the machine. ALL opsyses I use are dedicated external HDDs which slide into a kind of slipway, on top of my case, on an as and when required basis.
This eliminates all the complexities of multibooting into different opsyses. My main data storage is provided by a NFS configured Linux NAS server. With Yosemite, Windows 8.1 Enterprise, Win 7 Ultimate and Linux desktop all supporting NFS well.
In Windows I was able to disable all the funny Microsoft protocols that just consume
Network bandwidth. The only protocol that is active is TCP/IP nothing more. Netbios over TCP/IP and all others are gone and as expected the CPU loading and thus temps on my Windows opsyses have gone down considerably.
If anybody can provide advice as to how to bypass the Clover bootscreen it will be most appreciated. I guess doing some more reading on my part will also help me in accomplishing that.