Clover Efi Bootloader Iso Download
Clover EFI Bootloader is a free and lightweight application which gives you the possibility to boot Linus, Mac OS X and MS Windows on machines having BIOS of UEFI firmware. The application is capable of booting UEFI directly, but UEFI firmware emulation can be performed as well. Apr 11, 2018 Clover Bootloader is a great boot loader, it supports both UEFI and Legacy. This article will guide you how to install Clover Bootloader on USB from Windows and Linux. Download Clover Bootloader ISO here. Its ISO file was compressed into a file named CloverISO-4428.tar.lzma. This is a 64-bit version, the 32-bit version has been discontinued.
This tutorial was updated on 2019-06-05 to fetch the installer directly from Apple’s servers instead of getting it from the app storeThis tutorial for installing macOS Mojave has been adapted for Proxmox 5.4 from. There is more documentation there which will help out with enabling extra features and diagnosing problems! RequirementsI’ll assume you already have installed. You also need a real Mac available in order to fetch the OSK key.Your Proxmox host computer’s CPU must support SSE 4.2, so for Intel your CPU must be at least as new as Nehalem, which was the first CPU generation to bear the “Core” i5/i7 branding. Older CPUs will cause the finder to repeatedly crash after installation completes (with an Illegal Instruction exception in the graphics code).Apparently modern AMD CPUs also support SSE 4.2 and can be used with this guide without any modification (maybe Bulldozer and certainly Ryzen), but I haven’t tested this myself.First step: Create an installation ISOOn a Mac machine, download and run in a terminal to download the Mojave recovery image from the Apple software distribution server:This results in a 460MB “BaseSystem.dmg” file in the current directory. Convert that dmg into an “iso” like so: hdiutil convert BaseSystem.dmg -format RdWr -o Mojave-installer.isomv Mojave-installer.iso.img Mojave-installer.isoThis is actually a raw disk image, not a true ISO, but Proxmox has better tools for picking and re-using ISO images than disk images. Upload the “ISO” to your Proxmox server’s ISO store (typically /var/lib/vz/template/iso).It is possible to run this download script on Linux instead.
In that case, you need to install the “dmg2img” package on your system, and replace the “hdiutil” command invocation with: dmg2img BaseSystem.dmg Mojave-installer.iso Prepare a Clover imageWe’ll be using Clover as a bootloader for Mojave.(that I built using from ), unpack it, and upload it to Proxmox’s ISO store at /var/lib/vz/template/iso. Although it has a.iso file extension, this is actually a hard disk image. Fetch the OSK authentication keymacOS checks that it is running on real Mac hardware, and refuses to boot on third-party hardware. You can get around this by reading an authentication key out of your real Mac hardware (the OSK key).
Run the first bit of (you’ll need XCode installed) and it’ll print out the 64 character OSK for you. Make a note of it.Every Mac uses the same OSK, so don’t be surprised if it doesn’t look like a random string! Create the VMFrom the Proxmox web UI, create a new virtual machine as shown below. Keep a note of your VM’s ID. Select the Clover ISO you uploaded and set OS type to “Other”.
Set graphics to “VMWare Compatible”, set BIOS to OVMF (UEFI), set Machine to Q35, Tick Add EFI Disk, set SCSI to Default. Set the size of the hard disk (I chose 64GB). Attach it to SATA0. Set the number of cores for the VM, I chose 4 (note that some core counts seem to be troublesome, try 4 first).
Clover Efi Bootloader Iso Download Free
Set the CPU to Penryn. I chose a fixed memory of 8192MB. Disable ballooning because there is no balloon driver available for macOS. Choose VMWare vmxnet3 for the network modelIn the Options page for the VM, ensure that “use tablet for pointer” is set to “Yes”.In the Hardware page for the VM, add a second DVD drive at IDE0, set it to use your Mojave-installer.iso.Don’t try to start the VM just yet. First, SSH into your Proxmox server so we can make some edits to the configuration files.Edit /etc/pve/qemu-server/YOUR-VM-ID-HERE.conf (with nano or vim). Shame on me: to dumb for copy/paste!12x model name: Intel(R) Xeon(R) CPU X5670 @ 2.93GHzflags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constanttsc archperfmon pebs bts repgood nopl xtopology nonstoptsc cpuid aperfmperf pni pclmulqdq dtes64 monitor dscpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid dca sse41 sse42 popcnt aes lahflm pti tprshadow vnmi flexpriority ept vpid dtherm ida arat everything there.Please ignore my stupid response.
Diving straight in as a new Proxmox user I decided to follow this guide and install the now launched Mojave. Having checked my working twice now I can’t find any mistakes but find myself stuck on the apple logo right at the stage of selecting boot macOS install from clover. Seems to sit there indefinitely – longer than I have patience for! With no errors visible.
First, thanks take the time writing these up. I’d used your guide to install High Sierra before with great luck before (on a different Proxmox host machine).I’m having trouble with Mojave, however, running into an issue with a boot loop. This is the error message I’m getting:Start ProcessOptionsEnd ProcessOptionsRegisterRestartDataProtocol: called. Ox7dI4ad9ORestartnata protocol installed successfully.Start SetConsoleModeEnd SetConsoleModeStart ReadllernelCacheEnd ReadllernelCacheStart UncompressllernelCacheEnd UncompressllernelCacheStart CalculateAdler32End CalculateAdler32Start LoadllernelFromStreamEnd LoadllernelFromStreamStart InitBootStructroot device uuid is ‘ACB39C20-0C7B-3B0C-OB03-79EAOBBE3302.End InitBootStructStart LoadRAMDiskEnd LoadRAMDiskStart FinalizeBootStructStart RandomSeedEnd RandomSeedSome searching seems to suggest it might be a ram issue? I’m really not sure though, or how to fix it. If you had any suggestions, I’d appreciate it.
Great set of instructions! Thank you for taking the time.2 questions / problems that I’m having if you can help.1. Do you need to set the OVMF resolution at boot-up everytime or is there a way to make this configuration permanent?– I’m able to set it to 1024×768 and press reset to avoid scrambled display but I need to do this every time starting the VM. Can this be set?– Also is this is the only way to increase resolution beyond 1024×768?2. I’m experiecning a VM lock-up / hang many times after the VM has been running for a bit. No crash but a complete lock with no mouse/keyboard input possible.
Any ideas?Thanks again! I’m having the same issue getting stuck after “End RandomSeed”. I have the most recent version of Clover that you had attached, with a fresh install of Proxmox 5.2. I have it configured for 64G RAM and dual 6 core CPUs (running as sole guest on a dual 6 core xeon machine).
I’ve checked and my cpus support SSE4.1. Yes is was the right one:pve-edk2-firmware 1.20180612-1Args addedbios: ovmfboot: cdbootdisk: ide2cores: 2cpu: Penrynefidisk0: local-lvm:vm-114-disk-1,size=128Kide0: local:iso/Mojave.iso,size=8000M,media=cdromide2: local:iso/Clover.iso,cache=unsafe,size=13050Kmachine: pc-q35-2.11memory: 4096name: macOS-Mojavenet0: e1000-82545em=A2:61:00:E7:92:80,bridge=vmbr0numa: 0ostype: othersata0: local-lvm:vm-114-disk-0,cache=unsafe,size=50Gscsihw: virtio-scsi-pcismbios1 uuid sockets: 1vga: stdHard to find the mistake.thanks. Root@proxmox:/var/lib/vz/template/iso# file Mojave.isoMojave.iso: Apple Driver Map, blocksize 512, blockcount 12582912, devtype 0, devid 0, driver count 0, contains@0x200: Apple Partition Map, map block count 3, start block 1, block count 63, name Apple, type Applepartitionmap, valid, allocated, contains@0x400: Apple Partition Map, map block count 3, start block 64, block count 262144, type AppleFree, contains@0x600: Apple Partition Map, map block count 3, start block 262208, block count 12320704, name disk image, type AppleHFS, valid, allocated, readable, writable, mount at startup. Hi, thank you for this awesome article. I’m having a problem initially starting the VM. I do have a Proxmox subscription, but it basically just releases some high priority patches sooner (and my setup has been working for ages, those patches are definitely in the community version).What’s your QEMU version(dpkg -l pve-qemu-kvm)?
Mine’s 2.12.1-1. If your QEMU is old (predating Proxmox 5.2) then it might not know q35-2.11, and fallback to something else.Maybe post your VM’s configuration file here too so I can check that out. Something is triggering your QEMU to use a whole different architecture. I have the same QEMU version. When looking at the machine configs for QEMU (qemu-system-x8664 -machine help) it looks like q35 is just an alias for a later version q35 (pc-q35-2.12). Sorry, I’ve never really used a mac before. I believe I read that movie trailers in the itunes store are drm protected?Been researching this all day, and so far I’ve found a few things.-It’s been reported that the 10.14.1 breaks something and people have had success downgrading AppleGVA to the 10.14 version.-Lilu/WhateverGreen is likely required.
I’ve simply put them in /efi/clover/kexts/other but I believe they may require additional setup to work with mojave.-I’ve used Clover Configurator to try a few different smbios settings, and MacPro6,1 seems the most promising. With the downgraded AppleGVA, I’m able to get an error (Netflix in Safari) instead of being immediately redirected to the unsupported page (MacPro5,1 and the default unconfigured smbios).-I’ve read that working imessages etc is a prerequisite to getting working drm, so I’m looking into that now.Otherwise, the vm seems to be working reasonably well. Metal is shown as supported. I can switch back and forth between macos and windows vms without any issues (had to switch to the 2nd dvi port for macos to reliably display on boot).Took a snapshot before I started monkeying around so I can go back easily 🙂Thanks again for the guide. Wow thanks for trying all that!I completely forgot about the bitmovin demo.
Alas, it does not work for me either.I saw Conrad’s post here:which worked to mark en0 as builtin. With that and MacPro6,1 smbios, I get the cannot sign in to imessages on this mac at this time / contact support message. That’s a good sign as far as I understand it (assuming I don’t care about imessages.).I tested all the macpro smbioses 3,1 and up, and 6,1 is the only one that doesn’t redirect netflix to the requirements page. The imacpro smbios works as well. I haven’t tried any other configurations.
I suspect this would fix safari netflix for you since the bitmovin demo is working.Unfortunately, my only goal for setting up a hackintosh is to have a testbed for fairplay drm. It’s pretty remarkable how well everything else is working.Your 280x is the same generation gcn as my 7850, so I suspect our results should/could be similar. I’m going to try your iMac 14,2 setting now.Are you on 10.14.1 as well? And without swapping in the older 10.14 AppleGVA? “inject ati” unticked as well?Thanks so much your testing. Yeah, I’m on 10.14.1, AppleGVA is completely untouched, and InjectATI isn’t ticked.About Macs, Netflix says “Supported on all 2012 or later models and select 2011 models”, which should include the Late 2013 iMac 14,2, but I’m guessing they’re doing VM-detection.
Kholia reverse-engineered some VM detection in the macOS standard libraries the other day:There are a ton of ways of detecting VMs, so Fairplay may or may not be using this method.The Bitmovin demo does work for me, and chooses Fairplay in Safari. In Chrome it chooses Widevine which also works. Ha this issue has me tearing my hair out. Gave High Sierra a try with the same results.Meanwhile, it looks like setting the hard drive to IDE is the best solution (assuming there’s no performance penalty, although I haven’t tested) to having it be internal. It’s still shown as a SATA device in macos.Also, looking at the cpu flags:smbios type=2 -cpu Penryn,kvm=on,vendor=GenuineIntel,+invtsc,vmware-cpuid-freq=on,+pcid,+ssse3,+sse4.2,+popcnt,+avx,+aes,+xsave,+xsaveopt,checkI don’t believe vendor and +ssse3 are necessary (they should be included by the Penryn setting). Jeez, it’s working. I had a theory a few days ago that videos weren’t playing because I had no audio device.
Figured it was a pretty ridiculous idea so I didn’t explore it.Now that I have inject kexts enabled, I added applealc and tried a TV via HDMI again. Lo and behold, itunes/netflix/bitmovin fairplay demo all work. Don’t even need WhateverGreen.Time to figure out how to get applealc to work with the default q35 intel hda. Just needs to be a dummy device really.Thanks again for all your help. Going for a netflix trial was really aboveboard and is truly appreciated. Thank you for a great write-up! I’m new to Proxmox, relative novice w/ VM’s (last played w/ Xen @5 yrs ago), but I have built Hackintosh’s for the last several releases.
Learned a lot following your guide. Everything worked as described for Proxmox 5.3-6 on i4770k/z87-pro. Even did the Mojave OS update to 10.14.2, though that required manually restarting the update installer from Clover. Easy to fix.Only minor issue atm is msr warnings in syslog specific to the Mojave VM: 8028.414375 kvmgetmsrcommon: 26 callbacks suppressed 8028.414377 kvm 6752: vcpu1, guest rIP: 0xffffff8004b5ad75 ignored rdmsr: 0x60d (9 more lines from 2 rIP addrs for rdmsr’s 0x3f8,9,a, 0x630,1,2, 0x619,d, 0x621 every 480s)root@pve:# cat /etc/modprobe.d/kvm.confoptions kvm ignoremsrs=Yroot@pve:# cat /sys/module/kvm/parameters/ignoremsrsYroot@pve:# pveversionpve-manager/5.3-6/37b3c8df (running kernel: 4.15.18-9-pve)It boots, so only question is whether these syslog messages are expected or not? I’m guessing the “ignored” warning is actually correct behavior?I have lots of rereading/learning, testing, adding disks and passthrough devices and whatnot to go, but thank you for the tremendous head start!
Hey guys, I’m running Proxmox 5.3 with latest updates and trying to install Mojave but hitting a kernel panic when trying to boot the installer. I just did this some weeks ago on another system and it went swimmingly, so I’m fairly confident I’m following instructions correctly. Hey Nick!thanx again for terrific guide!!!even I’m still on h.sierra and not figured out how to properly tune nv106 card (distorted dbl apple screen, black screen then, probably drivers issue) but using r9 280x perfectly fine, I’m posting here my completely different question as it’s more future proof version LOL:what about clustering 2 hosts used as desktop located in 2 different locations over VPN?
Live VM migration on Proxmox (true clustering support) is disabled for VMs that have passthrough hardware enabled. However you can probably use the Ceph clustered storage engine to share a VM disk image between two nodes (so that you can shut it down at one location and start it up at the other location with minimal waiting time). I haven’t tried Ceph myself.The absolute minimum for passthrough is the graphics card, otherwise the performance is godawful. Everything else can be emulated with fair success. Sorry at the first, for my english (not my native) and for my blind (perhaps) eyes – i don’t understand how to work graphic card in mac os?
Is there full acceleration? Which hardware is support (whats the better Nvidia or AMD for the best build) and can i use 4k display connected in my graphic card with 4k2k resolution (60hz)?
Clover Efi Bootloader Iso Download Torrent
Another one – can i use the iCloud and imessage in MacOs? I’m asking because in this moment just interesting for using Proxmox for MacOs and want try to select hardware (exception Display – already have) for best using. Thanks for answer and advice. Getting graphics acceleration requires you to pass through a graphics card. There are currently no drivers available for modern Nvidia cards in Mojave (and there may never be), so you should definitely use AMD. I’m not sure what the best choice of AMD card is, you will need to research it in Hackintosh and VFIO (passthrough) communities.
4k 60Hz displays work great through DisplayPort, my monitor is 4k 60Hz. Please check out this post of mine to learn more about how passthrough is set up:iCloud and the App Store definitely work. Getting iMessage to work requires a bunch of messing around with setting serial numbers in Clover, and many people never get this to work. There are a lot of tutorials available for this on the ‘net if you search.
I tried using iMessage today and it doesn’t work for me (I can log in, but can’t send or receive messages). Real madrid font download. After many head scratching hours I managed to make it though.One thing I wanted to point out: my system was not initially outputting video properly after selecting the OSX installer from clover. Turns out it wasn’t handing off the resolution properly, so it was totally scrambled and impossible to read.I can’t remember verbatim what the menus were called, but I think this is close:The fix was to go into clover settings, then Graphics, then load Vbios or force vbios. Don’t remember what it was called exactly, but it will have EDID display options above, then the last option will be VBIOS related. Enable it by using the arrow keys to navigate to it, then pressing space on it. So, I have found two dmg installers for High Sierra and Mojave on torrent. People write in the comments that the installer is working.After downloading I’ve converted dmg to iso through dmg2img tool for linux.
As I know uncompressed img is same to iso. Finally, clover do not see mojave or high sierra iso. Could you help to find the reason.P.S. I have some doubt about Installing the fixed OVMF.Here is the output of dpkg -l pve-edk2-firmware, is it OK?Desired=Unknown/Install/Remove/Purge/Hold Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend / Err?=(none)/Reinst-required (Status,Err: uppercase=bad) / Name Version Architecture Description-ii pve-edk2-firmware 1.20190312-1 all edk2 based firmware modules for virtual machines. Hi,I tried proxmox 5.4 with mojave on a Fujitsu Primergy RX300 S8 (2x E5-2650v2, 256 GB Ram) server and I can start the vm and install mojave without problems.But within the final mojave, after some seconds of mouse movement, the mouse and also the keyboard stop working.I opened the activity monitor quickly after reboot and I can see everything working as expected. Unfortunately the input devices are gone completely after some seconds.I already tried the args: -device usb-kbd,bus=ehci.0,port=2and also to set thedevice “keyboard1”driver = “usb-kbd”bus = “ehci.0”port = “2”part.
But without luck 🙁Can you help me with that? Thanks so much for your guide, it has proved invaluable.
I have had some interesting effects when attempting your Mojave install on my hardware:Everything works perfectly up untill after the installer restarts for the first time. Then the Apple logo appears with the progress bar below and this continues until there are 14 minutes remaining. Then the PC hangs, the lights on my keyboard go off, and a minute or so later everyone else that is connected to our switch (which is a cheap Asus 4-port wireless router of some sort that’s plugged into our cable modem) loses access to the internet.
Well, more like they have no bandwith. Pages don’t load, YouTube video’s freeze, their wifi connections still work however and this “no bandwith effect” immediately ceases when I hit the “reset” switch on my PC case. When the PC restarts I am warned that the bios is corrupt and that it’s being restored from a backup. This happens every single time! In the end I installed High Sierra and this works just fine.This is my hardware:Gigabyte X79 UP5-Wifi motherboard with F4 bios32GB Corsair Vengeance 1666mhz DDR3Intel Sandy Bridge i7-E 3820Gigabyte Geforce GTX 670 OC 4GB (I have an AMD RX 570 for passthrough)Kingston 120gb SSDAgain, thank you for your efforts. This isn’t necessarily something that needs to be investigated, just an amusing tale of X79/C606 ownership. I do wonder if anyone else has experienced something similar?
Hi Nick,Thanks for the great instructions. I’m using the latest version of ProxMox but seem to be getting stuck with the system failing to boot past:Initialized /dev/rdisk5 as a 5 MB case-insensitive HFS Plus volumeFurther research shows that this is due to the machine being unable to boot off a USB 3.0 drive and requires Clover and the BIOS to be set down to USB 2.0 (initially at least).Have you any thoughts on this? Could you rebuild the Clover ISO with the latest version for me to test? I was working through your.sh file for it but must admit, I didn’t really know where to start! I actually upgrade proxmox from 5.1-? To 5.4-6 and the OSX VM with 10.3.4 does not start anymore, it seems to kernel panic during starting CLOVER image, then clover appears, and when I load macOS on disk macOS, I just see an Apple and nothing happens and this is a static screen, okay, not much else than a running OSX, but hey, this is about getting an OS and not a backside photo of an iPhone 🙂 Any thoughts, ideas, how to fix my VM or shall I just dump it and install Mojave on 5.4 now?
I have no real data there, nothing important. Installing Mojave now on my Proxmox 5.4 because noone reacted on my post before, even not the moderator so I ran into an issue:During installation (about 4 Minutes remaining of progress bar, installing ISO to External APFS Drive) I get the error: “a server with the specified hostname is not found. Please try again later, I tried now in 1-2 hours already again, even with new MAC address”. And if I retry to install MacOS without reboot of the VM I get the other error: “can’t install macOS because it requires downloading important content which can’t be downloaded.” Any thoughts/experiences?I have logs of the issue that are more accurate.
I have the same issue with only the macOS Base System disk showing in Clover.However if I open the OVMF boot manager during boot (F2) and choose to boot from the first alternative called UEFI QEMU HARDDISK QM00003, I can see all the other disks in Clover.What’s weird here is even though this boot option is supposedly the first option during normal boot, it still only shows the Base System disk, unless I specifically open the boot manager and chose this disk.Not sure whats causing this or how to fix so normal boot works. Interesting, good find!First double check that your Options - Boot Order setting in Proxmox points to the Clover disk and try again.If that doesn’t work, in Clover, please try navigating to the “Clover Boot Options” menu (second from the left), then select Remove all Clover boot options, then reopen the Clover Boot Option menu and select “Add Clover boot options for all entries”. Then try stopping the guest and re-starting it and see what it boots!You can also use the guest UEFI “Boot Maintenance Manager” to manually re-order the boot order and delete unwanted entries.
My OVMF resolution setting has no deleterious effect with my passthrough R9 280X video card – even if it doesn’t match Clover, macOS sorts itself out with no crash once it initialises the graphics system (at about the 80% mark on the progress bar).Check your config.plist in your Clover EFI partition to see what resolution Clover is configured for (you can do this from Clover’s built-in shell), then set OVMF to match. The Clover image I provide here has the resolution set to 1920×1080, but you may have modified this in the course of updating your SMBIOS settings. The setting appears in GUI - ScreenResolution.Note that you may need to select Reset when the Clover menu first appears in order to have the resolution you chose in OVMF applied successfully (you can tell that this is going to happen when the “Proxmox” logo appears to be the wrong size too big during boot). Since it even affects the Proxmox logo, this appears to be an OVMF/Proxmox bug.EDIT: Oh I nearly forgot, try adding the Lilu and WhateverGreen kexts to your Clover setup, I can’t remember if my setup worked correctly without these.
Manually install Clover for UEFI booting and configure boot priority with EasyUEFI in WindowsThis tutorial will show how to manually install Clover in the EFI system partition of a pre-existing install of UEFI Windows. In the process, you will also learn how to mount the EFI partition and add Clover as a UEFI boot option (using the EasyUEFI program) in Windows.Prerequisites1. CloverISO from.2. For Windows3.4. Existing UEFI install of Windows X64 (7,8,8.1 or 10)Obtain Clover1. Download the CloverISO.tar.lzma file from Sourceforge and open the file with 7-Zip.2.
Extract the Clover subfolder to your Downloads with 7-Zip.3. Copy the Clover folder by right clicking on its icon in Windows File Explorer.Mounting the EFI System Partition and installing Clover1. Open an administrative command prompt by clicking the Windows start button, typing cmd and right clicking on the search result as shown below.2. Type the following commands, followed by after each line:diskpartlist diskselect disk # (where # is the disk number of the disk with UEFI Windows)list partitionselect partition x (where x is the partition number of the EFI system partition. By default, it is usually the 100MB second partition)assign letter=sexit3. Open Windows Task Manager as administrator by clicking the Windows start button, typing taskmgr and right clicking on the search result as shown below.4. Click Run new task5.
Click Browse and in the Browse window, navigate to the EFI folder in the System Partition (which is mapped to drive S:) and also select 'All files' from the drop down menu.6. Right click inside the EFI folder to 'paste' the Clover folder we downloaded earlier. If necessary, you can make edits to Clover's default config.plist with Wordpad or add OSX kexts like FakeSMC into the kextsother folder while still in the Task Manager browse window.
For UEFI booting into OSX, you will most likely need the OsxAptioFix2Drv-64.efi or OsxAptioFixDrv-64.efi driver in EFICLOVERdrivers64UEFI (copy from the CLOVERdrivers-Offdrivers64UEFI folder).7. Quit Task Manager.Add Clover as a UEFI Boot Option using the EasyUEFI Program1. Open EasyUEFI and click on the small icon with the plus sign (second from top) to add a new entry.2. In the Create Boot Entry Window, choose 'Linux or other OS' as the entry type, click to select the EFI System partition as the target and browse to the CLOVERX64.efi file (file path EFICLOVERCLOVERX64.efi) as shown below.3.
Type Clover in the Description field then the OK button.4. You will now see the new Clover entry on the main GUI of EasyUEFI. Click on the entry and then click the small up arrow icon to move Clover to the top so it will get priority over the Windows Boot Manager on boot up. Note on this screen, you can also delete/edit/disable boot entries or move them down the boot order.5. Click the power menu and select reboot to restart your system ( use your system's boot device selection key to choose the drive with CLOVER installed if necessary eg F12 for Gigabyte motherboards, F8 for ASUS motherboards, F11 for ASrock motherboards) - will now be presented with the Clover Main Menu GUI to boot Windows (or OSX).Enjoy and Good Hack!
Microsoft Windows Version 10.0.10586© 2015 Microsoft Corporation. Nice work fusion71au!I am looking for solution for dualboot, but first, short explanation what i have done till now:My HW Specs:HP Z800 Workstation BIOS V.3.602 x Intel® Xeon® processor X5650 2.66 GHz, 12MB cache 1333 MHz memory, 6-Core24GB DDR3 RAMGFX: Nvidia QUADRO 6000Windows 10 on RAID0 LSILogic RAID SAS 1068E Controller ( 3 x 420GB SAS HD)Backup SAS HD 1TB on LSILogic RAID SAS 1068E ControllerSierra on Kingston 120GB SSDNow on SATA port 1First installed Win10 on RAID0 (LUN0).
The Apple Xserves, possibly the Mac Pro RAID Card, use the LSI SAS1068E controller chip as well.Second installed OS-X Sierra on SSD with Clover. Aplied EFI to Windows EFI Systempartition, but cannot boot in to the Windows!Analyzing my system, I noticed that under the system information Sierra recognizes LSILogic RAID controller and single HD 1TB connected on it, but does not recognize the Windows partition on raid0. Which leads to the conclusion that clover does not recognize Raid0. Making a High Sierra USB Installer Entirely From Scratch in WindowsThis is a proof of concept tutorial, to show it's possible to create a vanilla High Sierra installer, entirely from scratch, in Windows (even without App Store downloaded 'Install macOS High Sierra.app' from a real Mac ).