Hi @mireque

No this command is correct. At boot my usb is fs0. This is ok. But when i load driver the USB go to fs1 and my nvme SSD get fs0(see picture below)

Here are some picture:
At boot:(here should be loading startup.nsh file, but nothing hepens)
http://i.imgur.com/WFjN3fj.jpg?1

When i load driver:
http://i.imgur.com/YbY3Per.jpg

Then if i try this command (fs1:\EFI\Boot\Bootx64.efi) it boot again from usb.
http://i.imgur.com/uiiTdGY.jpg


This is how i get my startup.nsh file:
http://i.imgur.com/oKtyvKg.png

Did you have any more suggestion what could be wrong.

@Mrus

I get it. It's up to the BIOS/chipset how it gets mapped, so fs0 for NVMe is probably okay and fs1 for USB seems fine too after remapping.

Can you please try following:

- When it boots to UEFI Shell, it will wait for cca 3-5 seconds before attempting to execute startup.nsh.
- When you're waiting, try pressing Esc to get to the shell prompt directly.
- What happens when you type in the prompt - fs0:\EFI\Boot\startup.nsh - does this startup.nsh script ever get executed or not?

Thanks.

@mireque

Script is not working. When i try it manualy i get error:
fs0:\efi\boot\startup.nsh is not recognized as an internal or external command, operable program, or script file.

It look like there is some problem with script file.

@Mrus

What kind of encoding does the startup.nsh file have? From the image you posted it looks like you are using Windows' notepad and afaik there is a option to set encoding upon saving.
Maybe this could be the issue?

Hi @mireque

Finally managed to start working. All you have to do is to create startup.nsh file under shell.
Just go:
Shell> fs0:
edit startup.nsh

Then insert all commands, save and exit.

After restart it worked.

Have another question. Can i skip 5second waiting time, and load startup.nsh script immediately.

@Mrus

Glad you've got it working. So now the startup.nsh resides in root folder of the DUET USB drive? If that's the case, it's interesting, because I've edited/created the startup.nsh via Notepad and saved into fs0:\EFI\Boot folder ...

I've looked into UEFI Shell sources and actually the 5 sec waiting time is hardcoded here, so to change it one would need to recompile it from sources.

Finally, would you mind sharing a little bit info about your setup you got this working on - chipset, cpu, nvme ssd?

Hi @mireque

Yes startup.nsh file is now in root folder. It funny because all commands are same as before.

Here is my rig:
Motherboard: Gigabyte P67A-UD7
Cpu: Intel i7 2600K (overclock to 4.5GHz)
Vga: Nvidia 1080GTX (overclock of course )
SSD: Samsung 960 EVO 512GB
Soud card: Asus Xonar D2X

Everything (almost)is water cooled
Here is picture:
http://i.imgur.com/n6dUAiT.jpg

Seem that your guide is compatible with many chipsets.

Hi all!
Does this work with USB 3.0 flash memory stick inserted in USB 3.0 port?

6.
Boot into the Clover-EFI bootloader.

6a.
Pick your Windowsinstallation media via EFI-Boot.

How exactly do I do that?

I configured the USB-Stick as described, after booting the system comes up with a GUI, see attached photo. I went through all submenues, yet couldn't find anything that resembled picking an installation-device.

This might be a newer version of Clover.

@mireque,

up front, thanks for your elaborate work, the (for me - male, 74) first useful documentation. I spent almost one week trying to resolve this task. My system - ASUS Q87T, 2 years old, latest BIOS. I recently bought a Samsung 960 EVO 500 GB plus adapter and stuck it into the PCIe 3.0 4-Slot. Works fine as drive D:, reads >1.700 MB/s, writes (starting) >1.200 MB/s after driver-update from Samsung.

The bad news are - it won't run as start-drive. Not for money and not for heaven's sake. Tried a billion combinations. I suspect this board just can't do that. Once the NVM..-driver loads it say success and that's it, the system hangs, keyboard locked, the only escape is farmer-reset (see picture).

I spent so much time with this darn thing - if I wasn't an old age pensioner and still got paid, I could have afforded a new system - and that's exactly what I did today - I ordered an ASUS Q170T with an onboard M.2-connector that (hopefully) boots from there, otherwise the dealer gets his stuff back. A new CPU and RAM was also necessary, though.

This whole (U)EFI-business is just too kinky for me and reminds me at the 70ties when I studied in Aachen and ran Fortran on DEC PDP 9.

I will report further.

Hi @humpelpuber,

thank you for your report. From your screenshot, it looks like you aren't using the DUET method and its UEFI Shell as described in the article, but it seems like you've somehow gotten into UEFI shell of your ASUS Q87T mainboard (the first line clearly says it) ...

But your new ASUS Q170T should work fine with your EVO, and even make it correctly bootable.

This is a great and not to difficult solution for older builds that can definitely benefit from an NVMe boot device. I am sure if nicely packaged and fully debugged it would sell like crazy and be licensed by all the PCIe NVMe manufacturers. I successfully used it to boot my Lenovo D30 4229 Workstation with a Toshiba OCZ RD400 Series Solid State Drive PCIe NVMe M.2 512GB & Add In Card (RVD400-M22280-512G-A). It does seem to be quite sensitive to the exact specifications of the install medium. I went through several possibilities on a Rufus boot usb flash drive with a Windows 10 installation iso from Microsoft before I found exactly the right specs to get the windows usb to start up.

I decided I'd try it also with my HP Z800 but ran into a snag. No matter what I do I can't get the Windows 10 installer to start up. I always get an error screen starting with !!!! X64 Exception Type. I've read elsewhere that this type of error comes from an AMD CPU but the HP Z800s use Xeon CPUS. I do have an AMD Sapphire R9 280x video card but that is in the GPU not the CPU. Any suggestions will be appreciated! I am a novice to Clover Linux etc but have been around PCs since they were invented.

A reply to humpelpuber

I get the same screen as you. With my windows 10 install iso on a usb flash prepared by Rufus I generally get three options for the one flash drive: 1. windows boot manager on the flash 2. CD installer on the flash and 3. efi. For me, the efi worked (D30 workstation) with the efi MBR on the flash (2nd option of 3 on Rufus installer.

Strangely it seemed to take several tries with everything right...I suspect that somehow Clover is interacting with the windows usb flash and sets things up over several tries....at least it seemed that way to me.

Hi Mate.

I am doing this method with a notebook and \i have run across a problem. I had installed the clover boot manager on a 8gb usb 3.0 disk and windows 10 64bit installer on another usb 3.0 stick using rufus with uefi gpt partition. Anyway the clover utility boots into the options and I am given a few options. I can either boot with bootmgr efi or with cd something or boot straight from the disk. I have tried all three option and all three do not work the bootmgr method the screen freezes for a while on clover then the screen goes black and nothing happens. With the CD option a lot of code comes up and then the screen goes blank. Finally, the last option, booting straight from disk just does exactly what the bootmgr method does.

I am not sure what I am doing wrong. The usb stick works fine installing windows without clover.....

Any help would be appreciated.

I have an Optiplex 390, H61 express chipset and apparently is stubborn as far as booting from SSD. I have acquired a pcie sata card and am running my SSD through that (PNY 240 gb). It is not an option to boot form in the bios, and in UEFI mode, it simply does nor see anything. I would like to try this method to get things going and I will report back with results. I wonder though, will this work just as well with a pcie card that has a sata ssd attached? or is it NVM only?