Jump to content
InsanelyMac Forum

Recommended Posts

Manually install Clover for UEFI booting and configure boot priority with EasyUEFI in Windows

 

This 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.

 

Prerequisites
1.  CloverISO from Sourceforge.
2.  7-Zip for Windows
3.  EasyUEFI
4.  Existing UEFI install of Windows X64 (7,8,8.1 or 10)

Obtain Clover
1.  Download the CloverISO.tar.lzma file from Sourceforge and open the file with 7-Zip.

 

post-846696-0-43352700-1451035731_thumb.png

2.  Extract the Clover subfolder to your \Downloads with 7-Zip.

 

post-846696-0-24546100-1451035750_thumb.png

3.  Copy the Clover folder by right clicking on its icon in Windows File Explorer.

 

post-846696-0-33202600-1451035779_thumb.png

Mounting the EFI System Partition and installing Clover
1.  Open an administrative command prompt by clicking the Windows start button, typing cmd and right clicking on the search result as shown below...

 

post-846696-0-80106900-1451035804_thumb.png

2.  Type the following commands, followed by <Enter> after each line:

diskpart
list disk
select disk # (where # is the disk number of the disk with UEFI Windows)
list partition
select partition x (where x is the partition number of the EFI system partition.  By default, it is usually the 100MB second partition)
assign letter=s
exit

post-846696-0-42695000-1451035849_thumb.png

3.  Open Windows Task Manager as administrator by clicking the Windows start button, typing taskmgr and right clicking on the search result as shown below...

 

post-846696-0-98469900-1451035903_thumb.png

4.  Click Run new task

 

post-846696-0-53196700-1451035929_thumb.png

5.  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...

 

post-846696-0-92956500-1451035973_thumb.png

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 \kexts\other 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 EFI\CLOVER\drivers64UEFI (copy from the \CLOVER\drivers-Off\drivers64UEFI folder).

 

post-846696-0-56017700-1451036024_thumb.png

 

7.  Quit Task Manager.

 

Add Clover as a UEFI Boot Option using the EasyUEFI Program
1.  Open EasyUEFI and click on the small icon with the plus sign (second from top) to add a new entry.

 

post-846696-0-22133300-1451036124_thumb.png

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 \EFI\CLOVER\CLOVERX64.efi) as shown below...

 

post-846696-0-33853800-1451036154_thumb.png

post-846696-0-82792200-1451036173_thumb.png

3.  Type Clover in the Description field then the OK button.

 

post-846696-0-25737000-1451036230_thumb.png

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.

 

post-846696-0-85566700-1451036268_thumb.png

post-846696-0-98971400-1451036299_thumb.png

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).

 

post-846696-0-67383700-1451036345_thumb.png

post-846696-0-31170000-1451036369_thumb.png

Enjoy and Good Hack :) !

Share this post


Link to post
Share on other sites
Advertisement

Im the first  :P . Looks good but all our guides are not pinned and no noob can reach them easily  :rofl:

Share this post


Link to post
Share on other sites

Manually Install Legacy Clover and prepare GPT disk in Windows (for dual boot UEFI Windows and OSX)

 

Prerequisites
1.  GPT FDisk aka "GDisk"
2.  7-Zip
3.  Windows X64
4.  Bootice program
5.  Clover ISO downloaded from Sourceforge

 

 

Erase Hard Disk to RAW state with Diskpart.exe
Open an administrative command prompt and type the following lines, followed by the <Enter> key after each line....

diskpart
list disk
sel disk # (where # is the disk number of the disk you wish to erase)
clean
exit

 

 

Microsoft Windows [Version 10.0.10586]
© 2015 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>diskpart

Microsoft DiskPart version 10.0.10586

Copyright © 1999-2013 Microsoft Corporation.
On computer: XPSM1530

DISKPART> list disk

  Disk ###  Status         Size     Free     Dyn  Gpt
  --------  -------------  -------  -------  ---  ---
  Disk 0    Online          465 GB  1024 KB        *
  Disk 1    Online          931 GB   871 GB

DISKPART> sel disk 1

Disk 1 is now the selected disk.

DISKPART> clean

DiskPart succeeded in cleaning the disk.

DISKPART> exit

Leaving DiskPart...

 

 

 

 

Use GDisk to convert the Hard Drive to GPT and create partitions for dual booting UEFI Windows and OSX
In this example, I have a 1 TB hard disk which I plan to divide up as follows....

 

  • Partition 1: 200MB EFI System Partition
  • Partition 2: 128MB Microsoft Reserved Partition
  • Partition 3: 60GB NTFS Partition for Windows
  • Partition 4: 871GB HFS+ Partition for OSX

Notes -

  • EFI System Partition is preferably made the first partition for compatibility with OSX.
  • I usually leave 128MB of free space before and after the HFS+ partition or OSX Disk Utility will complain about a lack of "loader space".

1.  Open an administrative command prompt and cd to the gdisk installation folder
2.  Type gdisk64 #: (where # is the disk number of the disk you are creating partitions on - in this example it is disk 1)
3.  Use the following gdisk options:
     n to create a new partition
     x to access the experts menu
     a to change partition special attributes (needed for EFI System Partition)
     m to return to the main gdisk menu
     p to print the partition table
     w to finalize and write changes to the disk

Eg

 

 

 

C:\WINDOWS\system32>cd \gdisk

C:\gdisk>gdisk64 1:
GPT fdisk (gdisk) version 1.0.0

Partition table scan:
MBR: not present
BSD: not present
APM: not present
GPT: not present

Creating new GPT entries.
************************************************************************
Most versions of Windows cannot boot from a GPT disk except on a UEFI-based
computer, and most varieties prior to Vista cannot read GPT disks. Therefore,
you should exit now unless you understand the implications of converting MBR
to GPT or creating a new GPT disk layout!
************************************************************************

Are you SURE you want to continue? (Y/N): y

Command (? for help): ?
b back up GPT data to a file
c change a partition's name
d delete a partition
i show detailed information on a partition
l list known partition types
n add a new partition
o create a new empty GUID partition table (GPT)
p print the partition table
q quit without saving changes
r recovery and transformation options (experts only)
s sort partitions
t change a partition's type code
v verify disk
w write table to disk and exit
x extra functionality (experts only)
? print this menu

Command (? for help): n
Partition number (1-128, default 1): 1
First sector (34-1953525134, default = 40) or {+-}size{KMGTP}: 40
Last sector (40-1953525134, default = 1953525134) or {+-}size{KMGTP}: +200M
Current type is 'Microsoft basic data'
Hex code or GUID (L to show codes, Enter = 700): L
0700 Microsoft basic data 0c01 Microsoft reserved 2700 Windows RE
3000 ONIE boot 3001 ONIE config 4100 PowerPC PReP boot
4200 Windows LDM data 4201 Windows LDM metadata 4202 Windows Storage Spac
7501 IBM GPFS 7f00 ChromeOS kernel 7f01 ChromeOS root
7f02 ChromeOS reserved 8200 Linux swap 8300 Linux filesystem
8301 Linux reserved 8302 Linux /home 8303 Linux x86 root (/)
8304 Linux x86-64 root (/ 8305 Linux ARM64 root (/) 8306 Linux /srv
8400 Intel Rapid Start 8e00 Linux LVM a500 FreeBSD disklabel
a501 FreeBSD boot a502 FreeBSD swap a503 FreeBSD UFS
a504 FreeBSD ZFS a505 FreeBSD Vinum/RAID a580 Midnight BSD data
a581 Midnight BSD boot a582 Midnight BSD swap a583 Midnight BSD UFS
a584 Midnight BSD ZFS a585 Midnight BSD Vinum a601 OpenBSD data
a800 Apple UFS a901 NetBSD swap a902 NetBSD FFS
a903 NetBSD LFS a904 NetBSD concatenated a905 NetBSD encrypted
a906 NetBSD RAID ab00 Apple boot af00 Apple HFS/HFS+
af01 Apple RAID af02 Apple RAID offline af03 Apple label
af04 AppleTV recovery af05 Apple Core Storage be00 Solaris boot
bf00 Solaris root bf01 Solaris /usr & Mac Z bf02 Solaris swap
bf03 Solaris backup bf04 Solaris /var bf05 Solaris /home
bf06 Solaris alternate se bf07 Solaris Reserved 1 bf08 Solaris Reserved 2
bf09 Solaris Reserved 3 bf0a Solaris Reserved 4 bf0b Solaris Reserved 5
Press the <Enter> key to see more codes:
c001 HP-UX data c002 HP-UX service ea00 Freedesktop $BOOT
eb00 Haiku BFS ed00 Sony system partitio ed01 Lenovo system partit
ef00 EFI System ef01 MBR partition scheme ef02 BIOS boot partition
f800 Ceph OSD f801 Ceph dm-crypt OSD f802 Ceph journal
f803 Ceph dm-crypt journa f804 Ceph disk in creatio f805 Ceph dm-crypt disk i
fb00 VMWare VMFS fb01 VMWare reserved fc00 VMWare kcore crash p
fd00 Linux RAID
Hex code or GUID (L to show codes, Enter = 700): EF00
Changed type of partition to 'EFI System'

Command (? for help): x

Expert command (? for help): a
Using 1
Known attributes are:
0: system partition
1: hide from EFI
2: legacy BIOS bootable
60: read-only
62: hidden
63: do not automount

Attribute value is 0000000000000000. Set fields are:
No fields set

Toggle which attribute field (0-63, 64 or <Enter> to exit): 0
Have enabled the 'system partition' attribute.
Attribute value is 0000000000000001. Set fields are:
0 (system partition)

Toggle which attribute field (0-63, 64 or <Enter> to exit):

Expert command (? for help): m

Command (? for help): n
Partition number (2-128, default 2): 2
First sector (34-1953525134, default = 409640) or {+-}size{KMGTP}:
Last sector (409640-1953525134, default = 1953525134) or {+-}size{KMGTP}: +128M
Current type is 'Microsoft basic data'
Hex code or GUID (L to show codes, Enter = 700): 0c01
Changed type of partition to 'Microsoft reserved'

Command (? for help): n
Partition number (3-128, default 3): 3
First sector (34-1953525134, default = 671784) or {+-}size{KMGTP}:
Last sector (671784-1953525134, default = 1953525134) or {+-}size{KMGTP}: +60G
Current type is 'Microsoft basic data'
Hex code or GUID (L to show codes, Enter = 700): 0700
Changed type of partition to 'Microsoft basic data'

Command (? for help): n
Partition number (4-128, default 4): 4
First sector (34-1953525134, default = 126500904) or {+-}size{KMGTP}: +128M
Last sector (126763048-1953525134, default = 1953525134) or {+-}size{KMGTP}: -128M
Current type is 'Microsoft basic data'
Hex code or GUID (L to show codes, Enter = 700): AF00
Changed type of partition to 'Apple HFS/HFS+'

Command (? for help): p
Disk 1:: 1953525168 sectors, 931.5 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 584D0F77-3CE2-43C7-8663-CE867C61149D
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 1953525134
Partitions will be aligned on 8-sector boundaries
Total free space is 524294 sectors (256.0 MiB)

Number Start (sector) End (sector) Size Code Name
1 40 409639 200.0 MiB EF00 EFI System
2 409640 671783 128.0 MiB 0C01 Microsoft reserved
3 671784 126500903 60.0 GiB 0700 Microsoft basic data
4 126763048 1953262990 870.9 GiB AF00 Apple HFS/HFS+

Command (? for help): w

Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING
PARTITIONS!!

Do you want to proceed? (Y/N): y
OK; writing new GUID partition table (GPT) to \\.\physicaldrive1.
Disk synchronization succeeded! The computer should now use the new
partition table.
The operation has completed successfully.

 

 

 

4.  Use Diskpart to assign drive letters and format the EFI and Windows Partitions to FAT32 and NTFS respectively....

 

 

 

C:\gdisk>diskpart

Microsoft DiskPart version 10.0.10586

Copyright © 1999-2013 Microsoft Corporation.
On computer: XPSM1530

DISKPART> sel disk 1

Disk 1 is now the selected disk.

DISKPART> list part

Partition ### Type Size Offset
------------- ---------------- ------- -------
Partition 1 System 200 MB 1024 KB
Partition 2 Reserved 128 MB 201 MB
Partition 3 Primary 60 GB 329 MB
Partition 4 Primary 871 GB 60 GB

DISKPART> sel part 1

Partition 1 is now the selected partition.


DISKPART> assign letter=s

DiskPart successfully assigned the drive letter or mount point.

DISKPART> format quick fs=fat32 label="EFI"

100 percent completed

DiskPart successfully formatted the volume.


DISKPART> sel part 3

Partition 3 is now the selected partition.

DISKPART> assign letter=w

DiskPart successfully assigned the drive letter or mount point.

DISKPART> format quick fs=ntfs label="Windows"

100 percent completed

DiskPart successfully formatted the volume.
DISKPART> exit

 

 

 

Install legacy Clover bootsectors in Windows

 

Overview
The Clover wiki describes the legacy booting process:

Essentially BIOS--->MBR--->PBR--->boot--->CLOVERX64.efi--->OSLoader

In terms of the bootsectors we will be using in this tutorial
BIOS--->boot0af in MBR--->boot1f32alt in the PBR of the EFI System Partition--->boot6 in ESP--->CLOVERX64.efi in ESP--->OSLoader

Procedure
1.  Download the CloverISO tar.lzma file from Sourceforge and extract the ISO with 7 Zip
2.  Copy the following boot files from \usr\standalone\i386 folder
     boot0af, boot0ss, boot1f32, boot1f32alt

 

post-846696-0-11393200-1455486159_thumb.png

    and boot6, boot7 from \usr\standalone\i386\x64 to somewhere convenient

 

post-846696-0-24359500-1455486181_thumb.png

    The EFI folder will also be needed later....

 

post-846696-0-25810500-1455486220_thumb.png

3.  Open the Bootice program and click Process MBR from the main menu

 

post-846696-0-13825000-1455486236_thumb.png

4.  At the Master Boot Record screen, click restore MBR

 

post-846696-0-15547900-1455486261_thumb.png

5.  For the Restore file, browse to the boot0af or boot0ss file we extracted in step 2

 

post-846696-0-59456100-1455486304_thumb.png

6.  Click the Restore button and you should get a confirmation that the operation completed successfully.  Click the close button.

 

post-846696-0-35281700-1455486331_thumb.png

7.  Click Process PBR from the main menu


8.  At the Partition Boot Record screen, select the FAT32 EFI System Partition as the destination and click the Restore PBR button.

 

post-846696-0-05841700-1455486350_thumb.png

 

9.  For the Restore file, browse to the boot1f32 or boot1f32alt file we extracted in step 2.  In this example, I used the alternate booting PBR (boot1f32alt), which gives a 3 second pause to enable the user to input his/her choice of boot file during bootup (default is boot6).

 

post-846696-0-55147400-1455486372_thumb.png

post-846696-0-18318900-1455486396_thumb.png

 

10. Click the Restore button and you should get a confirmation that the operation completed successfully.  Click the close button and exit the program.
11. Open Task Manager as administrator and open a new task.  Browse "all files" and navigate to the EFI System Partition (which we assigned the drive letter S: earlier).

 

post-846696-0-98469900-1451035903_thumb.

You should now be able to copy the EFI folder from the Clover ISO (as well as boot6 and boot7) into the EFI System partition.  If you used boot1f32 for your PBR, rename "boot6" to "boot".

 

post-846696-0-09360100-1455487178_thumb.png

 

12. Make the necessary edits to the EFI\CLOVER\config.plist for your system and make sure you have FakeSMC.kext in EFI\Clover\kexts\Other.  If you have a DSDT &/or SSDTs that works for your system, place them in /EFI/CLOVER/ACPI/patched.

13. Reboot the computer and it should boot to the Clover Main Menu :) .
 

Share this post


Link to post
Share on other sites

Had to do this without guides when my hack suddenly deleted the partition table after running out of battery in sleep mode on Mac OS X. Now at least people know how to do it with this very detailed guide. Thanks.

Share this post


Link to post
Share on other sites

Thanks a lot for the guide! After messing with dual installation, I couldn't load MAC OS X without USB. Your guide helped, only had to download EasyUEFI and copy Clover folder from my USB.

Share this post


Link to post
Share on other sites

Thanks a lot for the guide! After messing with dual installation, I couldn't load MAC OS X without USB. Your guide helped, only had to download EasyUEFI and copy Clover folder from my USB.

If you need the USB, then that means you're missing the EFI folder in SSD/HDD's root EFI partition: Installing Clover to EFI root

Share this post


Link to post
Share on other sites

If you need the USB, then that means you're missing the EFI folder in SSD/HDD's root EFI partition: Installing Clover to EFI root

Yeah, I know. I stumbled upon ways to fix it in the Mac OS X and got a lot of helpful advice in another thread, but couldn't make anything work regarding this issue(now I get why, I did some steps wrong).

Using this guide for Windows I fixed everything. Thanks anyway, the link can come handy someday.

Share this post


Link to post
Share on other sites

Quick tip for mounting and unmounting the EFI partition in WIndows - open elevated Command Prompt (right-click and Run as Administrator) and use the following:

 

-for mounting

mountvol H: /s

this one will mount the EFI partition as H: (you may use whatever drive letter you want, as long as it's available).

 

for unmounting

mountvol H: /d

Share this post


Link to post
Share on other sites

Oh damn it! I never thought that it would be possible to install Clover from Windows (until I happened to search for it and found this post). I was there man, Sierra was properly installed on its partition and booting, the only problem was I couldn't install Clover from it and booting from the USB would be hassle. Ironically I {censored}ed up the USB installation drive and spent the whole weekend trying to prepare it again, which is quite difficult since I don't have access to a Mac right now and I couldn't manage to run it on VirtualBox.... The only option left is to connect my old drive and boot Mac from there.

Share this post


Link to post
Share on other sites

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.60

2 x Intel® Xeon® processor X5650 2.66 GHz, 12MB cache 1333 MHz memory, 6-Core

24GB DDR3 RAM

GFX: Nvidia QUADRO 6000

Windows 10 on RAID0 LSILogic RAID SAS 1068E Controller ( 3 x 420GB SAS HD)

Backup SAS HD 1TB on LSILogic RAID SAS 1068E Controller

Sierra on Kingston 120GB SSDNow  on SATA port 1

 

First 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. I spent time searching for a possible solution to identify Raid0 in sierra, but due to specific configuration of my system, there are not many solutions on the net.

 

I've been thinking about a solution to install the bootloader (Clover, or EasyBCD) on to Windows  EFI partition and boot from it, and to add OS-X Sierra as second entry.

 

Then I found this post and I think that would be the solution to my problem.

 

I have only one question:

If I install the  Clover on Windows efi partition, could come to conflict with Clover installed on the OS-X partition ?

 

PS: this is my first post on InsanelyMac after 6 years of hibernation, where a lot of things happened and changed. I'm glad to be back again and see how the "new kids on the block" rule the matter!

 

RESPECT!

Share this post


Link to post
Share on other sites

Thanks for this guide @fusion71au this helped me finally solve my issue of only being able to boot from installer usb! :thumbsup_anim:   I used Clover 3333 because the newer versions didn't have the CLOVER folder (only pkg).  Btw love your Tintin avatar! :D

Share this post


Link to post
Share on other sites

Just going to jump here: sadly EasyUEFI now requires a paid license to add/edit/remove UEFI entires, basically it's useless in its "Free" form. 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.



  • Similar Content

    • By zebity
      Hi Hypervisors,
       
      I have been working to move my Late 2009 Xserve MacOS Server onto Ubuntu 18.04 LTS QEMU/KVM based virtual machine using OVMF and Clover.
       
      After much effort and testing based on the following information from: Kraxel's, Kholia, Gordon Turner and Clover site:
      https://www.kraxel.org/blog/2017/09/running-macos-as-guest-in-kvm/
      https://github.com/kholia/OSX-KVM
      https://gist.github.com/gordonturner/2a2e5ecde5e7860b52e2
      https://clover-wiki.zetam.org/Home
       
      I have now managed to get OVMF/Clover boot and install of MacOS Sierra.
       
      I started with Ubuntu 16.04 initially but this required download and compile of QEMU to get update of machines to: pc-q35-2.9 or better, so I moved to Ubuntu 18.04, which has pc-q35.2.11 available as standard.
       
      So I am now working with standard Ubuntu 18.04 LTS based systems with following packages: kvm/qemu/libvirt/bridge-utils/ovmf/virt-manager
       
      As I want to use PCIe Passthrough for a number of PCIe card currently installed in the server (SmallTree 10GbE & Areca ARC-1883 SAS RAID) I set up my machine with linux kernel boot configuration (/etc/default/grub) of: 
      GRUB_CMDLINE_LINUX_DEFAULT="iommu=1 intel_iommu=on" (as my machine is intel VT-d based HW virtualisation)
       
      This resulted in creation of a number of iommu groups (see /sys/kernel/iommu_group directory for this and this posting for information: https://forum.level1techs.com/t/ubuntu-17-04-vfio-pcie-passthrough-kernel-update-4-14-rc1/119639 , noting that Ubuntu 18.04 LTS has kernel version: 4.15.0-22-generic so there is no need to do kernel update for iommu to work).
       
      Using bare minimal Clover config.plist:
       
       
      And following Clover UEFI drivers:
       
      I can boot MacOS, but it is very very slow... it sits on the apple boot logo for over a minutes before finally moving onto the progress bar.
      The other problem I have is that no PCI or Network devices appear in the "About This Mac" System Information Report and I cannot get any network connectivity from bridged E1000 network device.
       
      Here is my virtlib.xml dump for the virtual machine:
       

      Can any one advise of whether I need to update the CLOVER config.plist to add extra items in to allow network and PCI Passthrough to work.
       
      Thank you.
       
      Regards,
       
      Zebity
       
    • By frankiee
      Hi there, time for my first guide after asking so many things
       
      Updated for newer Clover versions and with additional instructions for more apps: gdisk and RU.
       
      So what may be overlooked sometimes in the whole boot loader discussion is the ability of UEFI to do more than just loading an OS. This is why I see ".efi" files as "apps" because in fact they just are, built on a special kind of API: UEFI. So, you can actually do stuff like editing, diagnosing, testing certain stuff at the lowest possible system level without booting to any OS.
       
      DISCLAIMER: Use this guide at your own risk! For educational purposes only! Should do not any harm, but remember you are dealing with rather low level stuff. But at least for me everything went flawless.
       
      Prerequisites:
      Working clover installation Clover Configurator or some app to edit the config.plist  
      1) Memtest
       
      This is how to install the UEFI version of Memtest with Clover:
      Download memtest, I used this link: Image for creating boot-able USB Drive Open the archive by double clicking on it. Mount the file memtest86-usb.img within by double clicking again. Now, you should see a folder named EFI in this volume, containing a folder BOOT. Open it. The files containing it are the actual app, in 32 and 64 bit versions. Think in almost all cases we want to use the 64 bit version. Now, mount your EFI partition, using Clover configurator. Create a folder named MemTest86 in the EFI folder on your main drive. Copy all files in the EFI/BOOT folder from the mounted image to your newly created folder. That ends the basic setup! Now, we add the correct Menu entry to the clover boot menu, so that we can actually start this app.
       
      Get into clover configurator, open your standard config.plist from your boot drive and go to the GUI section. Under "Custom Entries", add an entry like this:
       

       
      Please note while the path you enter is not case sensitive, you must make sure you use the backslash "\" for entering paths, and not a slash. So basically what we do is tell clover where it can find the app, give it a name, and tell clover it is a "Windows" app. Note: with older Clover versions we had to set this to "Linux", but for now "Windows" is the setting that works.
       
      If you prefer to do a manual config, add this entry to your config.plist, under GUI/Custom/Entries:
      <dict> <key>CustomLogo</key> <true/> <key>Disabled</key> <false/> <key>FullTitle</key> <string>MemTest86</string> <key>Hidden</key> <false/> <key>Ignore</key> <false/> <key>Image</key> <string>\EFI\CLOVER\themes\Icons\os_mint.png</string> <key>Path</key> <string>\EFI\MemTest86\BOOTX64.efi</string> <key>Type</key> <string>Windows</string> <key>VolumeType</key> <string>Internal</string> </dict> Now, save and reboot and you should see the newly created entry. Note that I also used a custom Icon - this is optional - in case you don't you will just see a generic windows icon instead:
       

       
      And this is how it looks like:
       

       

       
      PS: also noticeably faster and you get also more features with this version than with the older version, for example it does now write a log file. For more Information, see: http://www.passmark.com/forum/showthread.php?4315-Memtest86-Version-5-Beta-%28Pure-UEFI%29
       
       
      2) gdisk
       
      Another app you can use is the UEFI version of gdisk (aka GPT fdisk), which you can use to edit and change your partitions.
       
      Warning! Install and use this app at your own risk! If you do something wrong here you might nuke your drive(s), so only use that if you know what you are doing.
       
      This is how to do it (even easier):
      Download here: https://sourceforge.net/projects/gptfdisk/files/gptfdisk/1.0.1/gdisk-binaries/gdisk-efi-1.0.1.zip/download Mount your EFI partition Unzip the file and copy the resulting folder to your EFI Folder, so your path goes like this "/Volumes/EFI/EFI/gdisk-efi" Get into clover configurator, open your standard config.plist from your boot drive and go to the GUI section. Add an entry like this:  
      If you prefer to do a manual config, add this entry to your config.plist, under GUI/Custom/Entries:
      <dict> <key>CustomLogo</key> <false/> <key>Disabled</key> <false/> <key>FullTitle</key> <string>GDisk</string> <key>Hidden</key> <false/> <key>Ignore</key> <false/> <key>Image</key> <string></string> <key>Path</key> <string>\EFI\gdisk-efi\gdisk_x64.efi</string> <key>Type</key> <string>Windows</string> <key>VolumeType</key> <string>Internal</string> </dict> When everything went OK you should see this after selecting the respective entry in Clover:
       

       
       
      3) RU
       
      I recently found one more app that might be interesting to some, and thats "Read Universal" or in short "RU". This is a tool that enables you to debug your BIOS and read (and modify!) every imaginable data, including UEFI variables, ACPI Tables etc.
       
      Warning, again! I think blindly messing around with this app is even more dangerous, but on the other hand it gives you access to a lot of potentially interesting stuff.
      Download here: http://ruexe.blogspot.de/ The next steps are basically the same as above so make a folder in your EFI partition, copy the .EFI files and make another custom entry in your config.plist Here are some screens:
       

       

       

       
       
      So this is what you also can do with UEFI and clover. I am curious which other useful applications might exist!
       
      Anybody who knows, maybe post it here?
    • By TimNeumann
      MB: Asus X99 A-II
      RAM: G.Skill Ripjaws V F4-3200C16D-32GVK (3200MHz, 4x 16GB DIMMs, so Total 64GB) in quad-channel configuration.
      CPU: i7 6800k @4.0Ghz
      GPUs: GTX 1080 Ti and GTX 1060 3GB
      (each one a monitor, because I can't get DVI to run parallel with DP on the 1080Ti, and my second monitor only has DVI/VGA)
      OS: High Sierra 10.13.2 (17C88) / Clover revision: 4392
       
      Hello everybody,
      I occasionally have system crashes and suspect that it is related to RAM. However, this RAM is completely new, and a run with MemTest86+ from the USB stick showed no errors. However, if I use Memtest on MacOS, I get a bunch of error messages, but sometimes none (I restart the computer between tests).  
      As I just discovered, my RAM is not on the recommended vendor list of my motherboard, nor is it on the manufacturer side of the RAM. I have read several times that the RAM may not have been tested by the manufacturer on this platform. Not a single X99 motherboard is listed for this RAM.
      So I also suspect that my RAM is not compatible.
      But if that were the case, how could it sometimes work completely error-free?
       
      During RAM tests in summer 2017 (a slightly different setup, 4x8GB but still G.Skill Ripjaws V) I had no errors at Memtest under MacOS, if I remember correctly. At that time it ran under Sierra 10.12.6. AptioMemoryFix.efi could also cause problems.
      I am appreciative for any help!
       
      Here is an excerpt from a faulty test.
      It is noticeable that it is always the same address during the test, but a different one after each test.
      Memtest version 4.22 (64-bit) Copyright (C) 2004 Charles Cazabon Copyright (C) 2004-2008 Tony Scaminaci (Macintosh port) Licensed under the GNU General Public License version 2 only Mac OS X 10.13.2 (17C88) running in multiuser mode Memory Page Size: 4096 System has 12 Intel core(s) with SSE Requested memory: 57232MB (60012990464 bytes) Available memory: 57232MB (60012990464 bytes) Allocated memory: 57232MB (60012990464 bytes) at local address 0x00000001033e1000 Attempting memory lock... locked successfully Partitioning memory into 2 comparison buffers... Buffer A: 28616MB (30006495232 bytes) starts at local address 0x00000001033e1000 Buffer B: 28616MB (30006495232 bytes) starts at local address 0x00000007ffc4d800 Running 1 test sequence... (CTRL-C to quit) Test sequence 1 of 1: Running tests on full 57232MB region... Stuck Address : ok Linear PRN : testing 7 of 16 FAILURE! Data mismatch at local address 0x0000000e88133d30 Expected Data: 0xc4c340079ac9a645, Actual Data: 0xc4c3400788468846 Running comparison tests using 28616MB buffers... Random Value : ok Compare XOR : ok Compare SUB : ok Compare MUL : ok Compare DIV : ok Compare OR : ok Compare AND : ok Sequential Increment: ok Solid Bits : ok Block Sequential : testing 80 of 256 FAILURE! Data mismatch at local BUFA address 0x000000078b8c7530, BUFB address 0x0000000e88133d30 BUFA Data: 0x4f4f4f4f4f4f4f4f, BUFB Data: 0x4f4f4f4f88468846 Checkerboard : testing 3 of 64 FAILURE! Data mismatch at local BUFA address 0x000000078b8c7530, BUFB address 0x0000000e88133d30 BUFA Data: 0x5555555555555555, BUFB Data: 0x5555555588468846 Bit Spread : testing 1 of 128 FAILURE! Data mismatch at local BUFA address 0x000000078b8c7530, BUFB address 0x0000000e88133d30 BUFA Data: 0x0000000000000005, BUFB Data: 0x0000000088468846 Bit Flip : testing 74 of 512 FAILURE! Data mismatch at local BUFA address 0x000000078b8c7530, BUFB address 0x0000000e88133d30 BUFA Data: 0x0000000000000200, BUFB Data: 0x0000000088468846 Walking Ones : testing 40 of 128 Clover Files attached
      config.plist
      drivers64UEFI.zip
      kexts.zip
      ACPI.zip
    • By BurpSuite
      screenshot:
       

       
      description:
      github: https://github.com/burpsuite/clover_theme
×