[Guide] NVMe-boot for systems with legacy BIOS and UEFI board (DUET-REFIND)




UEFI DUET Installer - REFIND boot manager




PREVIEW


ATTENTION!

By using these files YOU WILL BE SOLELY RESPONSIBLE FOR ANY TYPE OF DAMAGE !!!


• Current download link for DUET (EDK2015) with REFIND included
 

    PROPRIETARY FILE SYSTEM

    In case the OS uses some specific type of partition or the UEFI OS installer is not showing up in REFIND: You'll might find the right driver inside the binary release of REFIND
    To add the DXE, unpack the .EFI driver within the drivers directory located in /EFI/Boot/drivers of the DUET USB: REFIND will auto load them for you.

What's new (20-06-2020) major fixes:
1
2
3
4
 

UTILITY: Adjusted the cluster count to FAT32 value.
DUET: Added VT-x/nested page table - booting\memory segmentation multi processor support.
 
 



• Current download link for DUET (EDK test Build 2020) with REFIND included




HOW to MAKE THE USB flash drive ( bootable ) for DUET.

Booting the NVME drive from non-UEFI legacy board - DUET with optional REFIND - with USBSetup:


1) Connect a USB flash drive and start the USBSetup application

2) Select the USB flash drive letter from the drop-down combo box

    Warning.
    The following step will completely remove all information and partitions on the selected USB flash drive

3) Remove all information and partitions from the drive by clicking on: CLEAN

4) Format the selected drive by clicking on: FORMAT

5) Make the selected drive bootable by clicking on: BOOT

6) Copy the required DUET files by clicking on: DUET

7) Copy the optional graphical boot manager REFIND by clicking on: REFIND

8) Connect the USB on the target system and set Boot from USB as the first option in your system BIOS Boot order




Booting the NVME drive from non-UEFI legacy board - DUET with optional REFIND - from command line:


1) Connect a USB flash drive and open the Windows Command Prompt with the Run as Administrator option

2) In the command prompt CD to the DUET_UDK2019_REFIND folder: cd C:\DUET_UDK2019_REFIND

    Warning.
    The following command will completely remove all information and partitions on the selected DISK volume
    Replace the Drive_Letter: with the USB flash drive letter.

3) Remove all information and partitions from the selected DISK volume by typing: CreateUSB Drive_Letter: CLEAN

4) Optional format the selected DISK volume with: CreateUSB Drive_Letter: FORMAT

5) Make the selected DISK volume bootable by typing: CreateUSB Drive_Letter: BOOT

6) Disconnect and plug back the USB flash drive.

7) Copy the required DUET files with: CreateUSB Drive_Letter: DUET

8) Copy the optional graphical boot manager REFIND: CreateUSB Drive_Letter: REFIND

9) Connect the USB on the target system and set Boot from USB as the first option in your system BIOS Boot order






HOW to MAKE THE USB flash drive (non-bootable) for REFIND.

Booting the NVME drive from UEFI capable board - REFIND mass-storage without DUET - with USBSetup:


1) Connect a USB flash drive and start the USBSetup application

2) Select the USB flash drive letter from the drop-down combo box

    Warning.
    The following step will completely remove all information and partitions on the selected USB flash drive

3) Remove all information and partitions from the drive by clicking on: CLEAN

4) format the selected drive by clicking on: FORMAT

5) Copy the graphical boot manager REFIND by clicking on: REFIND

6) Connect the USB on the target system and set Boot from USB as the first option in your system BIOS Boot order




Booting the NVME drive from UEFI capable board - REFIND mass-storage without DUET - from command line:



1) Connect a USB flash drive and open the Windows Command Prompt with the Run as Administrator option

2) In the command prompt CD to the DUET_UDK2019_REFIND folder: cd C:\DUET_UDK2019_REFIND

    Warning.
    The following command will completely remove all information and partitions on the selected disk volume.    
    Replace the Drive_Letter: with the USB flash drive letter.

3) Remove all information and partitions from the selected DISK volume by typing: CreateUSB Drive_Letter: CLEAN

4) Optional format the selected DISK volume by typing: CreateUSB Drive_Letter: FORMAT

5) Copy the graphical boot manager REFIND: CreateUSB Drive_Letter: REFIND

6) Connect the USB on the target system and set Boot from USB as the first option in your system BIOS Boot order







NOTE
• Ensure no other DUET USB KEY are inserted while booting


Know to BOOT -- TESTED

VIRTUAL BOX inside VM WARE on INTEL VT-x
1
2
3
4
 

DUET EDK2015 -- BOOT
DUET EDK2020 -- BOOT
 
 


INTEL DX58SO2
1
2
3
4
 

DUET EDK2015 -- BOOT
DUET EDK2020 -- BOOT
 
 



CHANGELOG:


(06-06-2020)
1
2
 

DUET: Reverted the SMBIOS memory mapped table reporting for older hardware support.
 

(16-03-2020)
1
2
3
 

DUET: Added VM (Virtual Box) support, changed the platform boot timeout - Updated the EFI Shell.
REFIND: Removed string print for empty boot option.
 

(07-03-2020)
1
2
3
 

REFIND: Updated to build 1.0.5 - Changed the timeout behavior.
USBSetup: Updated the non-standalone graphical user interface USBSetup ver.1.0.3.2 - Fixed diacritics in file path. Added -GenBootLOG command switch.
 

(27-02-2020)
1
2
3
 

USBSetup: Updated the non-standalone graphical user interface USBSetup ver.1.0.3.0
REFIND: Added internal build versioning. Build note: 1.0.4: Fixed an issue on pointer removal. Updated LodePNG encoder/decoder. Removed unused OSX code.
 




(13-02-2020)
1
2
3
 

USBSETUP: Updated the non-standalone graphical user interface USBSetup ver.1.0.1.8
CREATEUSB: Changed the folder structure and updated the scripted process.
 




(28-10-2019)
1
2
 

DUET: Changed the NonPaged low limit to 1MB
 




(24-10-2019)
1
2
 

DUET: Added BIOS Block IO to support INT 13 devices (EDD)
 




(01-10-2019)
1
2
 

DUET: Extended the EFI_GRAPHIC_OUT_PROTOCOL for native resolution support
 




(30-4-2018)
1
2
 

USBSETUP: Updated the non-standalone graphical user interface USBSetup ver.1.0.1.4
 




(08-4-2018) :
1
2
 

USBSETUP: Added the non-standalone graphical user interface USBSetup ver.1.0.0.1
 




(14-12-2017)
1
2
3
 

DUET: Comprehensive stability update to the DXE handles and dependent CPU library, updated core module to EDK2
REFIND: Added handled mouse and keyboard driver. Should give less problem with USB switches / KVM
 




(11-12-2017)
1
2
 

DUET: Improved NVME boot performance / execution time
 




(10-12-2017)
1
2
3
4
 

DUET: Updated the USB bus
DUET: Added OHCI ( firewire IEEE 1394 ) DXE driver
REFIND: Changed the file format of the screenshot functionality in PNG
 




(08-12-2017)
1
2
3
 

REFIND: Optimized the on screen draw & clear function
REFIND: Fixed the screenshot functionality ( F10 -> DUET_USB\\EFI\Screenshot )
 









ADDITIONAL INFO
• The CreateUSB.bat came from KeshavA2016 "Tianocore Uefi Duet Installer" project, it has been adapted by me.
• The Bootsector files came from from UDK2017 DuetPkg, a copy of the BSD license can be found within the Licenses directory.
• The Binaries files are built with UDK2017 Basetools, a copy of the BSD license can be found within the Licenses directory.
• The "shellx64.efi" is built with UDK2017 Basetools, a copy of the BSD license can be found within the Licenses directory.
• Added REFIND as OPTIONAL BOOT MANAGER see changelog for changes, a copy of the GNU license can be found within the Licenses directory.
• Added the Google Material Design icons in REFIND Minimal theme, a copy of the APACHE 2.0 license can be found within the Licenses directory.
• Added the non-standalone graphical user interface ( USBSetup ) to manage the USB of DUET/REFIND.
• SPECIAL THANKS TO: @SkOrPn for all the testing and the HOW-TO VIDEO&BOOTING PROCESS!
• THANKS to @eierhals for the testing done on the AMD platform and suggestion leading to additional fixes!


USBSetup PREVIEW


CMD HELP


VIDEO HOW-TO (CMD) By @SkOrPn

(video is outdated follow the textual procedure)


DUET-REFIND BOOT PROCESS By @SkOrPn








How to CLEAN install WINDOWS 10
• Download the windows 10 media creation tool and make the WIN10 ESD-USB directly from the media creation tool.
• Boot the PC with the DUET USB connected and wait for it to reach the graphical boot manager.
• Connect the WINDOWS 10 ESD-USB and refresh the visual representation list by hitting the ESC keyboard KEY to make the "Boot Fallbcak boot loader from ESD-USB" option appear.
• Launch the EFI WINDOWS 10 installer from the WINDOWS 10 ESD-USB by selecting the "Boot Fallbcak boot loader from ESD-USB".
• Select CUSTOM: Install Windows only (advanced) on the next screen delete all the partition till the NVME drive show as "Drive 0 Unallocated Space" and select NEXT, YES, NEXT.
• Once the Windows Setup screen end copying and installing Windows disconnect the WINDOWS 10 ESD-USB before it self-reboot. On some legacy board this is required.

ERROR HANDLING


If the NVME become un-bootable it mean the PC is not booting from the DUET USB.
If the NVME doesn't appear as selectable disk there could either be an broken\hidden hybrid partition or hardware issue locking the EFI installer read access, on WINDOWS 7 a driver must be provided.


To delete an hidden partition and rebuild the disk layout use the DISKPART CLEAN parameter from a command prompt, recovery environment or by when in another WINDOWS OS connected as non-bootable storage.

• With only the NVME inserted.
• Boot the PC with the DUET USB connected and wait for it to reach the graphical boot manager.
• Connect the WINDOWS 10 ESD-USB and refresh the visual representation list by hitting the ESC keyboard KEY to make the "Boot Fallback boot loader from ESD-USB" option appear.
• Launch the EFI WINDOWS 10 installer from the WINDOWS 10 ESD-USB by selecting the "Boot Fallback boot loader from ESD-USB".
• Instead of "Install now" select "Repair your computer" > Troubleshoot > Command Prompt
• In the "Command Prompt" type;

1
2
3
4
5
6
7
8
9
10
11
12
13
 

DISKPART
 
LIST DISK
 
SELECT DISK <DISKNUMBER> (should be 0 without <> if no other DISK are connected )
 
CLEAN
 
EXIT
 
EXIT
 
 

• Select "Turn off your PC" and detach the WINDOWS 10 ESD-USB.
• See How to CLEAN install WINDOWS 10 again from the start.













RAID and TIPS OLD - TO BE DELETED




How to install WINDOWS 7
• Extract\copy the [DUET_ZIP_VERSION]\Refind\drivers\ntfs.efi to the [DUET|USB]\EFI\Boot\drivers folder and connect the USB on the target system.
• Download the Windows USB/DVD Download Tool & follow the on-screen instruction.
• Once the Windows USB/DVD Download Tool is done locate the [WIN7|USB]\efi\ directory and within create a new [WIN7|USB]\efi\boot folder.
• Extract\copy and RENAME from the [WIN7|ISO]\sources\install.wim\1\Windows\Boot\EFI\bootmgfw.efi to the [WIN7|USB]\efi\boot\bootx64.efi new folder.
• Boot the PC with the DUET USB connected and wait for it to reach the graphical boot manager.
• Connect the WINDOWS 7 USB and refresh the visual representation list by hitting the ESC keyboard KEY to make the "Boot Fallbcak boot loader from NTFS volume" option appear.
• Launch the EFI WINDOWS 7 installer from the WINDOWS 7 USB by selecting the "Boot Fallbcak boot loader from NTFS volume".
• Select "Custom: (advanced) and on the next screen provide the NVME driver for WINDOWS with the "Load Driver" option.
• Select "Drive options(advanced) and delete all the partition till the NVME drive show as "Drive 0 Unallocated Space" select "New" and APPLY and OK. NEXT.
• Once the Windows Setup screen end copying and installing Windows disconnect the WINDOWS 7 USB before it self-reboot. On some legacy board this is required.
• When the installation is complete and the new system is bootable delete the [DUET|USB]\EFI\Boot\drivers\ntfs.efi from the [DUET|USB]\EFI\Boot\drivers folder.






NOT healthy USB DRIVE
To FORMAT the USB back into its original state, use the Windows FORMAT utility FIRST.
If the USB became unreadable after using a third party utility:

see DISKPART or try to use the CLEAN function of USBSetup\CreateUSB to restore the USB MBR.





DISKPART ( Optional )
BE SURE TO SELECT THE RIGHT VOLUME. The Diskpart utility will completely erase the partition table on the drive you select.

How to restore the USB disk manually


1) Open the Windows Command Prompt with "Run as Administrator" option ( ie. Run "cmd" as Administrator ).

2) Type "diskpart" ( without quotes ). Enter.

3) Type "list vol" seek and triple check your USB disk: compare the size, the type and the letter before proceeding.

4) Type "sel vol "DRIVE_LETTER:" (without quotes) - ie: "K:" is the drive letter of MINE USB flash drive.
    Be sure to select the USB Drive the next command will wipe the DISK. Enter.

5) Type "clean" (without quotes). Enter.

6) Type "convert mbr" (without quotes). Enter.

7) Type "create partition primary offset=1024" (without quotes). Enter.

8) Type "format fs=fat32 quick" (without quotes). Enter.

9) Type "exit" (without quotes). Enter.






Boot stuck on MBR Start!
Sometime the USBSetup application is not capable to write the required DBR on the predefined offset.
This is an issue with the per-existent MBR and the active partition on the USB.
If the error keep showing up during the boot process of DUET either:
try to make again the USB, do the process manually (see CreateUSB) or use another USB with lesser size.

Boot stuck on SE Error!
If you receive an SE error the error mean a device booted with a PCI ROM and was also expecting an unavailable EFI driver.
Use an USB 2.0 port and set the SATA controller to AHCI or disable the software RAID.





RAID to AHCI - AHCI to RAID
Windows 10: installing any newer RST software without reducing the "MessageNumberLimit" from the default 80 to 8 could trigger the never ending loading circle, if your ICH10 board never reach the desktop, go to the DELETE RAID driver section.

Self-signed 15.9.8.1050 RST driver with "MessageNumberLimit" set to 1 by default ( value can be changed from the registry ).


1) Open the Windows Command Prompt with the "Run as Administrator" option to run the Import_CERT.bat
2) Open the Windows Command Prompt and type: start devmgmt.msc
3) From the Device Manager "Storage Controller" locate the device and install the corresponding self-signed driver located in the "DRIVER_F4" directory
3) Reboot and open the Windows Command Prompt with the "Run as Administrator" option to run the Setup_RST.cmd



How to use the SATA RAID software option
For the SHELL: find the suitable RST EFI SATA\RAID driver version and place it inside the "EFI\Raid" directory, then modify the "startup.nsh" accordingly or rename the file in "RaidDriver.efi".
For the OPTIONAL BOOT MANAGER: find the suitable RST EFI SATA\RAID driver version and place it inside the "EFI\Boot\drivers" directory.
To boot DUET with the RAID BIOS option enabled on EFI system (non-legacy) the OROM and EFI version must match.


[style=font-size:10pt]
1) Uninstall the RAID or AHCI SATA driver ( intel matrix/rapid storage technology etc ).

2) Open the Windows Command Prompt with "Run as Administrator" option ( ie. Run "cmd" as Administrator ).

3) Type "start devmgmt.msc" ( without quotes ). Enter.

4) In "Storage controller" double check if the Intel(R) ICH10| Desktop/Workstation/Server Express Chipset AHCI or SATA RAID Controller is still there, in case uninstall and also check the "delete drivers" option.

5) Open msconfig > boot tab > check safe boot > restart.

6) Go into the BIOS and set the SATA mode either RAID or AHCI.

7) Boot Windows 10 in safe mode.

8) Open msconfig and under the main menu tab ( general ) click the normal startup circle and restart.

9) Install your AHCI or RAID driver ( intel matrix/rapid storage technology etc ).



DELETE the RAID driver


1) Go into the BIOS and set the SATA mode to AHCI.

2) Boot Windows 10 in safe mode after 3 failed attempt to boot.

3) Open the Windows Command Prompt with "Run as Administrator" option ( ie. Run "cmd" as Administrator ).

4) Type "set devmgr_show_nonpresent_devices=1" ( without quotes ). Enter.

5) Type "start devmgmt.msc" ( without quotes ). Enter.

6) CTRL+V and select "show hidden device"

7) On the "Storage controller" locate the semi transparent Intel(R) Desktop/Workstation/Server Express Chipset | Premium SATA RAID Controller and uninstall by also checking the "delete drivers" option.

8) Open msconfig and under the main menu tab ( general ) click the normal startup circle and restart.





Hello Internet -

Guys, I’m pretty savvy with computers and can’t get past this one. HyperX PCIe SSD Boot: it’s fine if I leave the windows disc in the drive (some of the time), or hit any key a few times and it boots, but reading forums online, I was directed here hearing about a bios mod that boots into windows seamlessly. Please help me out. How do I get the HyperX PCIe SSD to boot seamlessly into windows, or what are the step by step instructions to mod the BIOS on an ASUS X58 P6T Deluxe OC Palm Edition.

Asus P6t Deluxe OC Palm edition
x5680 xeon with a mild OC @4.0GHZ. 20x200
24GB RAM G.Skill Ripjaw at 1603mhz 1.5v
HyperX PCIe 250GB SSD (Boot Drive)
750W Corsair Power Supply
Strix 980ti GPU

Let me know if you need any more info.

Much appreciated for the help,

Best,
Tony

EDIT by Fernando: Thread title customized

Hi and welcome!

Please provide some additional details.
What is the exact model of the SSD?
What BIOS version do you use?
What other devices are enabled in BIOS (like additional SATA controllers)?
What are your boot options in BIOS?

Best regards,
Mr nUUb

Hello Tony,

your problem has obviously been caused during the OS installation. Not all required files of the boot sector (Master Boot Record) have been copied onto the SSD.
Solution:
Look >here<.

Good luck!
Dieter (alias Fernando)

Thank you!

SSD Model: Kingston Digital HyperX Predator 240 GB PCIe Gen2 x4 Solid State Drive 8-Inch SHPM2280P2H/240G
http://www.amazon.com/Kingston-HyperX-Pr…G/dp/B00V01C376

I believe its the latest bios: American Megatrends Date 09/21/2010 Version 2209

I’ve tried RAID and AHCI Boot modes, it has the intel controller for 6x Sata II ports, then a marvel controller for 2x SAS ports.

If I run a normal Sata SSD, it boots fine every time. Since the HyperX is on the PCIe bus, its a little more tricky. It’s the only device enabled under the bios boot menu. All other devices have been disables. The weird part is if I keep the Win 7 disc in the dvd rom drive, it will boot. Otherwise it says “Please insert proper boot media and press any key” And if I press any key like 3 or 4 times, then it will boot to windows. It seems to me that the pcie ssd is showing up as a “DVD” Drive that can be selected to boot from by pressing a key, rather than a HDD or SSD that will boot automatically.

Hello!

I also have X58 motherboard (Rampage II Extreme) and I’ve just installed my HyperX Predator AND I have the same problem.

First of all, imho the problem is caused due to the age of our chipset and partial incompatibility with PCI-E-based boot devices. My first guess would be motherboard expecting the SSD to be ready a bit earlier than it is possible for the drive.

In my case the first press of any button initializes the system, however it still looks rather ugly and I’d love to get rid of this problem. I’m afraid, though, that it might be an EOL situation. :frowning:

@ Istarish:
Welcome at Win-RAID Forum!

This is what I recommend to do:

  1. Make sure, that the attached PCIe connected SSD is the only bootable one within the system. If there are other bootable SSDs/HDDs within the Computer or attached to it, delete the bootsector from these disks by using a tool like EasyBCD.
  2. If the boot problem should persist, try to repair the boot sector of the PCIe connected SSD, for example by using >this< guide.

Good luck!
Dieter (alias Fernando)

Hello, thanks for your advice.

Are you certain that the device would actually be booting correctly once given a bit of additional time, if something was wrong with its MBR?

In fact I’ve spent quite a bit of time investigating this issue and it seems that Kingston doesn’t officially support chipsets as old as X58.

My solution for now (for all the other affected users willing to harness Predator under old but still powerful X58) goes like that:
1) Prepare the spare USB flash memory, its size practically doesn’t matter;
2) Using Rufus (great piece of software btw) configure your pendrive to be prepared with (for example) the bootable FreeDOS - remember to mark “Use Rufus MBR with BIOS ID: Default” - it’s crucial ( http://windows.intowindows.netdna-cdn.co…m-USB_thumb.jpg )!
3) Simply leave the pendrive prepared in the aforementioned way plugged into some rarely used USB port at the rear side of your rig.
4) Configure your BIOS to attempt to boot from your pendrive before trying with the Kingston SSD.

Result: At boot-time your PC will spend a couple of seconds displaying “Press any key to boot from USB…” message and afterwards it will boot the PCI-E SSD without any further problems. Voila!

Hello. Can you please tell me if your solution works for other X58 motherboards? I’m trying to boot from a Samsung SM951 (AHCI version) on a Gigabyte GA-X58A-UD7, via PCIe adapter Lycomm LT120 (no driver needed). The OS lists up the drive correctly and I can even choose it as booting volume from SysPref but of course it doesn’t work because the BIOS doesn’t show up the PCIe attached SSD among boot devices.
Thank you.

I read many complains about SSD’s with PCIe x4 lanes like Kingston HyperX Predator running on x58 boards. My guess is the x58 chipset has problem with more then 2 PCIe lanes.
So I decide to go with the Plextor M6e PCIe 2.0 x2 without any issues runnig as boot device Win10Prox64 on Asus Sabertooth x58. Of course the seq. read/write is at “only” 740/560 MB/s but still much faster then a SSD on Intel SATA2 port.

@PPCnostalgic :
Welcome at Win-RAID Forum and please forgive me my late reply.

Which BIOS settings did you choose within the BOOT section?

Regards
Dieter (alias Fernando)

Hi Fernando, thank you for replying. I’ve managed to boot my GA-X58A-UD7 from SM951 using Clover as bootloader. The Bios doesn’t list the M2 as a boot drive but Clover does. All I had to do was cloning my working system onto the SM951 and install Clover on another internal drive visible in the Bios (that’s the HD choosed to boot from). Then when Clover starts at bootscreen it sees the SM951 with the OS, just press enter and the machine boots fine from the M2. This workaround works even installing Clover on a USB stick and choosing to boot from it.
BTW I’m running Mac OS X 10.11.3 on this machine, it’s a Hackintosh but I think it should work with Windows as well. Clover can boot Mac OS X - Linux - Windows even if installed on non UEFI motherboards as mine.
Cheers
Rob (alias PPCnostalgic)

I’m having an issue too with booting off of my Samsung SM951 AHCI on my x58 Rampage 2 extreme.I can boot into clover from a memory stick and clover seems to find the drive but fails to boot from it.Have cloned windows 10
from a 850 pro with acronis and made a bootable USB with windows 10 winch also doesn’t allow me to install windows because windows claims that it wont be bootable… Every time i try to boot into windows 10 from from clover menu all my drives are displayed as legacy drives which is correct.For some reason it won’t load uefi64 either so it doesn’t startup and the underscore keeps blinking.I’m obviously doing something wrong.Do a have to install osx in advance to make it work?Just wanted to clone my existing windows installation

Thanks in advance

@nick29 :
Welcome at Win-RAID Forum!
Since I don’t have an Intel X58 chipset system, I cannot help you myself, but I hope, that you will get support by someone else.
Good luck!
Dieter (alias Fernando)

@Tall_Tony
@mr_nuub :
@Istarish :
@PPCnostalgic :
@wasisdn :
The original thread title had been too specific and didn’t match all the later contributions. That is why I have customized the title of this thread and your posts.

Hoping, that this is ok for you
Dieter (alias Fernando)

Hi Nick29. Try installing Clover this way (see attachement)

Clover.png

Thanks PPCnostalgic. So just to make sure i got this right i have to do that within osx on a separate partition on my 850 pro to be able to install Windows 10 on my sm951. Then select in bios to boot off of the 850 pro. Would i then be able to delete the partition with osx in it cause i don’t need it?

Uhm… I’m not familiar with Windows. I had a working system on a Samsung 850 EVO, then simply cloned it to the SM951. Now I use the 850EVO for audio-video files and Clover is on that disk, in BIOS I choosed the 850EVO as my booting drive, Clover lists all other drives and I can choose the SM951 (with OS X) to boot. It should be the same with Windows, if you have a working system on another HD simply clone it to the SM951 and install Clover on a BIOS bootable HD, when Clover starts you should be able to choose Windows on the M2 and boot.
Cheers
Rob

Installed clover on a memory stick within osx 10.11 and i can boot from it but every drive that’s found in the first screen of clover don’t boot even the ones that definitely have windows and osx on them. What additional files did you use in the clover directory?

Hi nick29. I have these drivers installed into “driver64” Clover’s folder.

64Drivers.png

Couldn’t make it work so i returned the 951 and got the 950 pro and was gonna boot windows off my 850 pro and install all my apps on the 950 pro.As soon as i put the 950 pro in my angelbird m.2 to pcie adapter card i turned on my PC and went strait to the bios and wanted to change the boot order of my hard drives.To my surprise i saw the 950 pro displayed with the rest of my drives which is really really weird. How would my legacy bios be able to see it and not the SM951 ahci…? So without clover or anything else i cloned my 850 pro to the 950 pro restarted and selected in the bios to boot first from the 950 and to my surprise it actually did… Benchmarked it and got 1706MB/s read and 1570MB/s write on pcie 2.0.As far as i know this isn’t possible with non uefi bios so your ques is as good as mine :stuck_out_tongue: