It worked! Getting 1600 mb/s read. Thank you to bootmaster400.

4k benchmarks inline with native?

Hello, would you please share intel dq77mk bios mod as bin files?

Hello im trying to do it but it says http error can you help me? This error appear when creating the usb and when it finish there are no files on the usb

I have an HP proliand dl360e g8

@Sag2014 this is the wrong forum thread for bios mod files.
@gerard04 which usb are you talking about the clover boot usb or the windows installation usb ?

The clover bootusb when i use the tool and i click on create the usb it says http error and dont download the files.

i have successfully booted both windows and ubuntu on pcie nvme disk but there is a problem
i am getting code 10 error on high definition audio controller means have no sound
it is not a driver issue. i uninstalled and installed so many times. problem exists for both OS

[Updated]

@sibliss wrote: "One small note is you should back up the sata drive before you use the bdu to create the clover partition on the sata drive as the bdu will wipe the whole drive ..... however after clover partition is created it is perfectly safe to partition the rest of the drive and use it like normal. This is how I am currently using clover boot on my personal computer."

LOL, yeah. What happened this morning is: My NvME boot installation thanks to Clover thanks to Win-Raid Forum, fails to boot! :(
I thought I DID back up the BDU stick (<200MB), but while I do find all other backups, just that one isn't among them.

I would now recommend anyone, to ALSO BACKUP THE BDU STICK (if you use it).

What, I assume, happened in my case: Yday I had to switch another USB right next to the BDU stick, and I heard the MS beeps that made clear my hand must have brushed the BDU stick.
Now my guess today is: THAT must have happened JUST at a moment when the BDU stick was being accessed (Only Sibill know why, lol). But it's clear today that the BDU stick now fails the NvME Boot Installation, because my second/backup Win install that I kept on another SSD in the Dell, still works: I can write this here.

Now off to re-investigating how I had created the BDU stick, and doing it all over AGAIN....
Always backup even the last 200MB!

[Update]
Why BDU-Clover stick no longer booted: 4 hrs searching for and trying online "solutions", and nothing letting me access nor format nor clear nor chkdsk the flashdrive, despite that all its content was still shown in Win10(!), I had to conclude that the flashdrive has bad sectors (happens easily when you brush or even intently remove a stick WHILE it's being written to).
Somehow I finally managed to get the "Format" option clickable, and now for the last five hrs or so it's doing a full format (to repair bad sectors while moving along).

That particular flashdrive is now a minimum of 11 years old, so this could play a role as well, I don't know how long this off-the-mill 256MB stick is meant to last.
In the meantime, on another 1GB tiny SD card I re-created the whole BDU-Clover-Plist-configured Boot drive, with the values in plist that had from a backup. Cannot test the new drive now, as it's still formatting the old one...

New resolution, for the current year: Once it's working again, I will clone the entire NVME installation AND the BDU-Clover boot drive onto my other (normal SATA) SSD, to have always one environment in working order. :)

Those of you who cannot do that, as a minimum, I would suggest to keep a clone of the BDU-Clover boot stick, such that a power cut or such cannot kill your NVME installation altogether!

As for power cuts and surges: I got myself an EATON UPS 350W (the smallest, ~70-90 Euro it was I think) - which, I found out only later, is PLENTY with this Dell Tower and Monitor. Glad I didn't buy a bigger one. Huge Monitor is using 22W, and the Dell RUNNING is using 34-35W, so together no more than 57W peak. :)
Gives me HOURS of time to turn off the system when power is still not back - if I can bear the annyoing Eaton beeps that long! Last time it was still beeping 5hrs later (I had turned the monitor off then to save energy).

I have been successful loading clover and installing a WD SN750 nvme m2 w/pcie x4 adapter into two different 2009ish PCs. The easy one is an Intel based Gigabyte GA-G41m-es2l w/E6500 (PCIe 1.0). Zero problems.

The 2nd is an xfx mi-a78s-8209 (nforce motherboard)
w/Athlon x2 7750 am2+. This one took a while to figure out it wasn't hanging booting clover, it just took 15 minutes. I never figured out why but instead generated a sata based loader generated with BDU in the Intel system. I then was able to simply move the nvme with W10 installed plus the sata HDD with clover installed from the Intel system to the AMD system and it boots in 30 seconds. The real motivation was to get the Xfx motherboard operational is because it's PCIe 2.0. Here is 1st run of Crystal:

I always found it fascinating how I was always able to move a windows 7 HDD between these two systems and they were always able boot without any intervention.

@meakcey

This could be a result of the hardware emulation being performed by clover. apparently this sound device is for audio on the hdmi port.

I find i am repeating myself yet again do not use rufus to create your bootable installation media usb. rufus sets up the boot environment differently to how microsofts media creation tool does this is why much of the time usb installers made with rufus will not boot from clover. even if they do boot outside of clover.

please for the sake of sanity both yours and mine use the microsoft usb media creation tool NOT rufus it will give you less problems.

Hi,

I'm new here.

I recently knew about Clover after I installed my NVMe.

I installed Clover into USB using BDU and copied the NVMedriver to both BIOS and UEFI folder.

I already followed the steps to boot Clover through USB but my BIOS cannot detect FAT32 USB. When I changed it to NTFS, my BIOS can detect the same USB.

How to solve BIOS not detecting the USB in FAT32?

Can we use Clover for BIOS or not? Or this method is only for UEFI?

Thanks

@darkstar_86

Hi and welcome to the forum this clover method is for both uefi and legacy bios.
most modern bios have an option to enable support for legacy boot devices such as what clover uses, please enable this setting to boot to clover.
NTFS is a proprietary windows file system and as such cannot be used for clover.

I hope this helps.
If you need further help report back here with more details such as computer or motherboard model, the brand and model of your nvme drive and whether or not you are using an adapter card for your nvme drive.

Hi Sibliss,

Just an update:

After I change my USB, I managed to get BIOS to detect Clover (FAT32).
For some reason, BIOS only detected my Kingston USB.

However, I run into these problems. Please refer to images attached.

Questions:
1. Do I have to install the Windows in the USB? Can I just clone my current windows directly to the NVMe drive ?
2. How to solve the problem on the DSC_0071JPG?
3. In DSC_0072JPG, which boot should I use? Why there are so many options to choose.
4. DSC_0073JPG, is one of the boot options that I choose from Clover boot page in DSC_0072JPG


My current setup:
Processor: i5 750
Mobo: ECS P55H-A
NVMe: XPG SX8200 Pro 1TB (with Adapter card)

Thanks for your help