I followed everything step by step, but when dialog shows where i need to select drive for win 10 installation, win 10 setup gives me notice that drive which i selected is not supported for booting. Anyway, i find solution, by accident.I tried DUET tutorial, but with no success, so i came back to CLover tutorial, recreate my usb stick with BDU, and BDU says there is http error downloading CLOVER, i qucikly find solution for that in BDU configuration, newest version of CLOVER then was installed on usb stick.After that i tried to start win 10 setup but with no succes, so i was desperate and i tried manualy to start win 10 setup through efi shell, and setup started, and there was no message that my NVMe drive is not bootable hardware,must notice this that i did not copied nvme efi drivers in folders where tutorial says it need to be.After setup copied neccesary files computer rebooted, after reboot Clover did not see nvme as boot option, i go back to usb stick and copied nvme efi drivers to folder where it should be.After that Clover in boot menu sees new Win installation, so i can continue further.Strange huh...

Notice:
MoBo is Gigabyte GA-F2A88XM-D3HP Bios ver. F2

UEFI only - selection for boot

I have a Dell T7400 Workstation and a Samsung 970 Evo 500GB and using this method I can successfully boot to Windows 10.
However, for the one of the applications I need to copy files to a floppy disk. The floppy drive works perfectly.
When I boot from Clover, in Device Manager under "Floppy drive controllers" there is a "Standard floppy disk controller" but the "Floppy disk drives" section is missing.
The drive does not appear in Windows Explorer. How do I get a floppy drive to work under Clover?

Floppy drive should be visible in Windows regardless of Clover.
Check, if you didn't flipped data ribbon on one of the ends (and if 1,44MB[?] floppy is enabled in BIOS).
Also, does floppy drive have a letter assigned to it ?

@agentx007
When I do a standard MBR boot from HDD the floppy works and appears as drive A:
So it it not a problem with BIOS settings or ribbon connector.
The "Floppy disk drives" entry appears normally in device manager
https://www.use.com/Ohs14

When I do a Clover USB UEFI boot to NVMe, the "Floppy disk drives" entry does not appear in device manager
https://www.use.com/Ohs16

So it does seem that the issue is with Clover.

Hi,
Thanks for this tutorial I tried to follow, but without any success…
Actually, the system can’t boot off my Win8.1 installation stick.
I get the following error message.

https://drive.google.com/file/d/1QxD_tlc...iew?usp=sharing (sorry I can't get the image displayed directly)

Any idea of what has gone wrong ?

Btw, I don’t think it is related to this but the NvmExpressDxe-64.efi path on the Clover boot drive is not the one indicated in the tutorial.
I found the file in \EFI\CLOVER\drivers-Off\drivers64UEFI\ instead of \EFI\CLOVER\drivers-Off\drivers64\ (Clover version r4862)…
I copy/pasted it at the indicated path anyway.

The purpose is NOT to see the installation-Stick in CLOVER-boot!
In BIOS/UEFI you put the CLOVER-Stick at the first position, but choose the install-stick in the boot-menu to install the OS!
On the first reboot the system should boot from the prepared clover-stick: on this way windows can boot from the PCIe-NVMe-drive; this drive is not detected by the MB-BIOS (otherwise you had not needed this tutorial).

Zitat

---

the NvmExpressDxe-64.efi path on the Clover boot drive is not the one indicated in the tutorial.
I found the file in \EFI\CLOVER\drivers-Off\drivers64UEFI\ instead of \EFI\CLOVER\drivers-Off\drivers64\ (Clover version r4862)…
I copy/pasted it at the indicated path anyway.

---

Since a couple of month the source-path has been changed!
So as you did was right.

Zitat von Thiersee im Beitrag #261

---

The purpose is NOT to see the installation-Stick in CLOVER-boot!

---

Zitat

---

In BIOS/UEFI you put the CLOVER-Stick at the first position, but choose the install-stick in the boot-menu to install the OS!...

---

Okay that's precisely what I did. So the error shows up when Clover-boot launches the installation media as I tried to show in the linked image in my previous post, so from the 6a to 7 steps of the tuto. At that time, there is no windows installation done on the NVMe drive which is still empty at this time...

@Neutral67fr

Sorry for giving you a possibly wrong info!

I'm using Windows7 and I installed my NVMe-System in July 2017, so I must retry to install it on my test-plattform (no NVMs supported): I get next week a new SSD and an PCIe interface-board; at the same time it could be a good possibility to switch to Win10....
I hope I will report a good result.

Hello,

can anybody say, if i can use a Samsung SSD 970 EVO 250GB, M.2 (MZ-V7E250BW) for an old ASUS P5K with P35 chipset?

can anybody say, if i can use a Samsung SSD 970 EVO 250GB, M.2 (MZ-V7E250BW) for an old ASUS P5K with P35 chipset?

Yes you can. But if your board has no m.2 slot, you have to use an m2 to pci card. Where you insert your SSD on the pci-ex card and in turn insert the card into an available slot.

Then follow the tutorials above to boot into a USB stick

Thanks for you answer. I've ordered the DeLOCK PCI Express Card > 1 x internal M.2 NVMe (89370) and the 970 EVO now.

So, first off what a fantastic guide! I managed to get my ancient ASUS P5KPL1600 Legacy BIOS mainboard booting a shiny new NVME drive via an adapter card in the PCIe slot!!!

The only issue I am having is that I cannot get Autoboot to kick in? I have edited config.plist but it is as if CLOVER is not recognizing or using the config file?

I change timeout from 5 to 1 and nothing happens. I have to manually select the boot volume every time.

I tried the same USB key on a newer mainboard that supports UEFI and the countdown shows and will autoboot using the LastBootedVolume option?

Does anyone have any ideas. I can't find any logs on the CLOVER USB key either, do I need to enable logging?

UPDATE - On the newer system I did not have the NvmExpressDxe-64.efi copied to the Drivers64UEFI or drivers64 folder as I am booting from a normal SATA drive. After copying the files Autoboot still worked. SO I tried turning off UEFI and I got the same BIOS looking screen rather than the main CLOVER GUI? Does anyone know what this screen is? It seems to have options to add boot options, manage boot options, etc.

After turning UEFI back on I get the GUI again but no autoloader or countdown on the newer PC now?

UPDATE 2 - I have rebuilt the USB Key and now the new PC refuses to Autoboot? How can that be possible, It was initially? Now it is like my ASUS P5KPL board and sits at the GUI waiting for an input?

UPDATE 3 - I have narrowed down the issue to the following:

Booting the CLOVER USB key in non UEFI mode/Legacy means autoload does not work. Almost as if the cofig.plist file is not being read?
Booting the CLOVER USB key in UEFI mode enables Autoload and it can read the config.plist file as changing values such as timeout from 5 to 10 has an effect.

What is preventing CLOVER from reading the config.plist file in legacy boot mode? The whole point of this is to boot an NVME via UEFI from the USB key on an old Legacy BIOS board thaht can't boot UEFI. Can I copy the config.plist file to another location so it will read it when the USB key is booted in legacy mode?

@millldew
Are those modified :
<key>DefaultLoader</key>
<string>\EFI\Microsoft\Boot\bootmgfw.efi</string>
<key>DefaultVolume</key>
<string>EFI</string>
?
Did you tried earlier version of Clover ?

I have the following:

<key>#DefaultLoader</key>
<string>boot.efi</string>
<key>DefaultVolume</key>
<string>LastBootedVolume</string>

Thanks for replying :)

I edited the config file as you listed and it works!

Why did autoboot work under UEFI? I'm guessing because it automatically checks the Windows EFI parttion and Legacy does not?

Thank you so much. I was up until 4am scratching my head on this.