@Krukermann

Thank you for the report.
Yeah, that part is kinda messy dunno if ANSI\ASCII text will go trough without issue.
I've made a change on the way the directory are stacked together on that passage.
Only English OS code page (UTF8) is currently supported by USBSetup.
Accented character or special ANSI\ASCII code by relative path (EG: User ŃĂMÊ) it's not natively handled by the (StandardInput [StreamWriter : TextWriter]) run-time on which the application run on (C#) probably a bug on the on the virtual class encapsulation of (Stream BaseStream ) or by the "Default" encoding since by console output or by log to file the encoding is generated fine.
Will look on it, someday.
StreamWriter class is unreliable for the operation or require double write while on memory to stick.
If the error message say "Unable to find" whatever.
I can potentially "fix" it by introducing unhanded issue with 437 DOS encoding for the operation but since this will break someday down, or with multiple invalid character within the directory path I rather not.
If it fail with the BOOT stage move the application directory on C: or use the CreateUSB.

Updated the non-standalone graphical user interface USBSetup ver.1.0.3.0
 

Try to get windows 10 onto a nvme drive via clover. The closest I've got is clover working with the nvme driver installed but when I select the win 10 install (rufus disk per instructions) all I get is a line of text saying it is loading but nothing happens. I've tried the bu utility moving the drivers into the correct dirs, I've also tried boot directly fro the iso with no joy any ideas?

https://www.amazon.com/gp/product/B06VSL...0?ie=UTF8&psc=1
https://www.amazon.com/gp/product/B07RXQ...0?ie=UTF8&psc=1

@scottfree123

This is not Clover but it might work with the 2015 version.
If you decide to use this method requirement are different.

Download the DUET (UDK2015) version and connect the Windows installation USB media made by Rufus.
• Start the USBSetup application and select the USB media made by Rufus.
• Remove all information, partitions and the MBR bootloader made by Rufus from the USB drive by clicking on: CLEAN
• Once done disconnect the USB, close the USBSetup application and follow the text below.



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

@Krukermann

I -should- have actually fixed the diacritics (accents) in the file path for the boot utility with USBSetup ver.1.0.3.1
Issue was duo C# memory UTF16 string begin wrongly auto-converted in UTF8 by the runtime (TextWriter) output console interface (DOS shell).
Dropped the usage of the DOS console in favor of powershell for quicker handling in the USBSetup boot MBR processing\patching and updated the given parameter.
Should now let you have almost any type of allowed windows character on path by encoding the on memory UTF16LE string with UNICODE base64 and making use of that value as direct command.

Also enabled the -GenBootLOG switch for USBSetup.
It should does just that, log the boot process parameter used while making the USB bootable.
To decode the Base64String on powershell use the following command:

[System.Text.Encoding]::Unicode.GetString([System.Convert]::FromBase64String('Base64String'))
 

Base64String & EncodedPathCommand should always mach.


Maybe it's not required anymore to remove manually the USB during the process, IDK.
Removed the unplug\plug message.

Updated the non-standalone graphical user interface USBSetup ver.1.0.3.2
 

@noInk

Hello
thanks for that great tutorial and software.

I installed yesterday DUET 2019 with REFIND.
It is working. (I read 20 pages of this thread)
But i am not shure how good it is working...

Asus Rampage III Extreme Black Edition Chipset intel X58 without uefi wihout NVME support :D
Intel 990X Extreme
28GB DDR3
NVME 1TB (Sabrent 1TB Rocket NVMe PCIe M.2 2280 SSD) with PCI EXpress Adapter 4 lanes 2.0
USB device to boot 16 GB Intenso USB stick
Gigabyte GeForce GTX 1660 GAMING OC 6G 6GB

I want to have only one Windows 10 (without a selction) it should boot as fast ass possible form a NVME 1TB PCI Express M2 SSD

But now i have some questions:
It is very slow. (I check the linked videos to compare the time)
around 1 minute take the loading proccess.

Can i do something to make it faster ?
may without Rewind ?
Is it possbile to use only the DUET without the REWIND to speed it up?

Do i have to do some changes in the BIOS ?
(found some videos they show some stuff like Intel C state shoud be disabled)

Can i use USB 3.0 for the Booting USB to speed it up?

Is it better for the old hardware to use the 2015 Version ?


And a question for my bad knowledge about this topic

When the windows is startup nothing of the DUET RWIND is running anymore ?
It is just like antoher bios?

So i my case a nomal legacy bios
then i have a extra bios for the SATA 6 Controler (i know very old chipset)
an then the machine starts DUET adds the EFI support and the NVME driver it make a ram check/do the adressing
after that it loads the REWIND HMI
and finally it starts up windows 10.

Thanks for your help, sorry for my bad english, let me know if something is wrong or about missing things.

mujuli

@mujuli

The slow booting process might depend by an incompatible driver stalling or try to load few time before giving up on the hardware.
If it's happening with either the 2015 and the 2019 version you should try to disable anything not essential to boot within the bios to see what is interfering or to determine what the issue.
Restoring the default bios value might also help.
Embedded USB 3.0 on X58 are issue prone unless updated to pretty much last available firmware version.

Adapter and NVME could play a role but usually unless it's running below the spec it shouldn't really matter.

Using the optional REFIND included shouldn't increase the booting process time, in fact its the opposite duo the predetermined countdown of DUET.
If you made the USB with REFIND to bypass the OS selection change the timeout to -1 on the [USB]\EFI\Boot\refind.conf
With only DUET you can't change the hardcoded default 5 seconds delay shell value to auto load the first external available EFI found.

On mine system the 2019 version take around 25 seconds from DUET entry point to the OS login screen.
Less if I count to OS Logo (DUET END point), or more if I start from the POWER-ON bios sequence.

With this DUET version once the OS logo is loaded there should nothing left except for the UEFI environment.

@noink

thanks for your super quick answer.

Ok i will check this out tonight and will write a report.


1. I will reset the bios to defaults
2. I will check the 2015 Version.
3. if no effect i will disable nearly everything in bios to figer out what it could be.

Ok in my case no USB 3.0 because i remeber at the begining the driver was a mess.

Thanks for the -1 i forgot to write this. In my last try yesterday night i changed it to -1. (but the total time was the waiting time between end of the normal bios (the red writing) to the HMI (short (1 sec.) grey screen with -1)

On the last run with -1 the keyboard was not detected in the OS anymore .. may the keyboard (logitech RGB ) is the problem. Ah and my logitech mouse was not deteced in the REWIND screen. both are connected with wire to the mainboard usb 2.0 ports

One more question i was wondering what taktes that long time to load, because the files are in total 2.XX MB "big" .
So my question is what need the most of the 25 seconds in your case?
Is it to load the drivers or to adress the RAM ?
(is it depending on the usb ? ) i have a SATA Samsung SSD :D may i try this too :D but 2,XX shouldn`t be the problem.

is somewhere a log file created ? or is a description for DUET available ?

Maybe one more thing befor i found this i follows this instructions
[Guide] NVMe-boot without modding your UEFI/BIOS (Clover-EFI bootloader method)

but i was able to boot from usb but after selecting the bootable device i was not able to install windoes it show up "klick a key to boot from ....." and after that nothing happend and it also took a long time to load the menue. ( I think both ways use same componets infact i think your right with the driver issue. )

thanks

mujuli

@mujuli

For the keyboard and mouse use the USB 2.0 port, voltage issue can cause a wide range of problem USB inconsistency is one.
There no textual log by default on this version of DUET.
On the system at mine disposal both 2015 and 2019 work seamless like in the video posted by @SkOrPn
Clover uses it's own DUET version to allow the change of the hardware readable configuration by injecting code and offer specific customization required by OSX.
This DUET|REFIND version its a bare sort of self deleting EFI environment upon shutdown.

So my Report that worked for my hardware:

Asus Rampage III Extreme Black Edition Chipset intel X58 without uefi wihout NVME support :D
Intel I7 X990 Extreme
28GB DDR3
NVME 1TB (Sabrent 1TB Rocket NVMe PCIe M.2 2280 SSD) with PCI Express adapter 4 lanes 2.0
USB device to boot 16 GB Intenso USB stick
Gigabyte GeForce GTX 1660 6GB


The Version 2019 takes 1 minute and 52 seconds from the end of legacy bios to Windows boot logo
Only with this version i have the keyboard issue. During legacy bios keyboard is working also in REFIND. But after rewind in Windows it is not working. I have to un-plug it.

The Version 2015 work in my chase much better 37 seconds.
It works perfect, also the keyboard.
In my case i use the -1, i don`t want to change the OS.


Is it possible to enable NUM in DUET (the num Block) ?

But my opinion is there is much more performance possible, but i am unable to get/fix it :D
@noink hope thats okay for you.
so i have to wait 46 seconds for the whole boot(it is like a HDD :D), but after that its unbelievable fast.

Thanks for your help.

@mujuli

I'm using it on a samsung 960 along an asus hyperX adapter and from the BIOS DMI (DUET) to the windows boot logo it take roughly 10\11 seconds with the -1 REFIND config with the 2015 version and 11\13 with the 2019.
Difference is duo the fact more driver execution environment (DXE) are included with the 2019 version.
If the 2015 version work, use that.
It just mean something on the board is off-specification for the newer driver included.
Probably a PHY device firmware (not loaded with the 2015 version) is not compatible with the USB BUS changes introduced with the 2017>2019.
An wrongly firmware configured PHY device can cause anything on data\voltage level, gate bypass etc etc.
Both 2015 and 2019 version are up-to date anyway and certain change are mirrored or back-ported.
About windows not seeing the keyboard or mouse that's on your bios settings and OS driver loaded.
Disable or update the USB NEC 3.0 controller or use an 2.0 ICH10R USB port on the 2019 version.

hey,


hm 10/11 sec from the red text to the bootlogo is fast...

I am sure it is some specical hardware, because the board has onboard wifi /bluetooth/ and the not on the X58 chipset implemented SATA 6 and USB 3.0 controller.
may i try to disable all this "specical devices" (specical because of the age of the mainboard it was not really common )

i do not use the USB3.0 port only USB 2.0 at any time.

I will disable everthing in the bios.

thanks

@mujuli

Dunno. That how it boot on mine X58 legacy board with the -1 on the 2019 version.
On an EFI DX58SO2 board with the NEC Renesas uPD720200 I had to update the USB 3.0 controller firmware to get it to boot DUET without issue.
USB 3.0 port are blue.

See this post about and without using any other command on the admin command prompt type;

W200FW36 /srom ? > uPD720200FW.txt
W200FW36 /srom 0 >> uPD720200FW.txt
 

Find the newly generated uPD720200FW.txt file within the directory and either change the PCI Subsystem Vendor ID and PCI Subsystem ID within the CFG.INI file and update your own board controller or attach the content.
Should be something like the following:

This Device is uPD720200(Revision 3).
    MX25L512/2005/4005A/4005C/2006E/4006E(MACRONIX)/Pm25LD512C/010C/020C(Chingis)   Type : 2, PageSize = 0x100, Chip Erase = 0x60
Bus:0x01 Device:0x00 Function:0x00
This Device is uPD720200(Revision 3).
     FW Version : 3.0.3.4-0.8
     PCI Subsystem Vendor ID : 0x8086
     PCI Subsystem ID : 0x5332
 

Updated REFIND to build 1.0.5
 

@noInk

Hello,
Now I try a new build of DUET with an updated USBsetup. What to say: after pressing "BOOT" I get an eternal "Wait" at the preparation stage, and ..... it does not end((
Here is the screen:



Earlier I solved the problem for myself (and now writing from a computer, working from the SSD using DUET). However, I can be a little bit tester for your labor.

P.S.: If this somehow help in the solution, then the second computer from which USBsetup correctly created the bootable USB flash drive, was also with the operating system in Russian (Win10 x 64 Pro Rus).
I suppose, the problem is not in the OS language, but, possibly, in the OS version, or in the type of account, from under which USBsetup works.

@Krukermann

Dunno! maybe the power shell is also not available on the system.
Can you run the USBSetup with -GenBootLOG switch?
From the Administrator command line start the app with:

USBSetup.exe -GenBootLOG
 

Click on the BOOT option check the newly USBSetup.txt info and attach the content of the file.