It is working with 2020. I spent quite a while on it. It has been a long while since DUET was utilized. The catch is Win10 cannot write the DBR. Win10 on my system had trouble cleaning/formatting the drive, for which MiniTool was utilized (without success - read on).

The GUI does not clearly indicate failure. The last step is the only one to show up, MBR succeeded or something similar. It doesn't make sense to indicate a final 'success' after something (i. e. DBR) failed.

The solution was to use a Win7 VM. VirtualBox combined with any generic 7sp1 media (unactivated is fine) does the job. Vanilla win7sp1 does not have .NET to utilize the GUI. The command line utilities are case sensitive, an oddity. I was aware of this and the other issues (after researching my own posts in this thread). It would be stressful for the uninitiated.

Never the less, it was a success. DUET+REFIND 2020 is prepared and the system again boots Win10, albeit without a working keyboard until GUI, causing a separate difficult to troubleshoot Win10 issue (freeze at login, causing difficulty because the 5 or F5 to select Safe Mode is not registered - the workaround is using installation media and manually editing the BCD string).

Kudos for continuing the project's support. As always, if I can be of any assistance, please do ask. Keep up the good work.

@silekonn

The helper gracefully fail or complete the task and the GUI doesn't read the output. It a sort of stub duo the textual line x size constriction of the GUI.
On WIN7 and under certain circumstance on older WIN10 version (2015) the original BootSectImage & GenBootSector found on UDK2014 [ZIP]\BaseTools\Bin\Win32\ must be used.
About the keyboard try to see if your require the PS2 protocol found in [ZIP]\DUET_EDK2020_REFIND\DUET\EFI\Drivers on VM it's required and not included on the last binary.
An user must put the driver within the [USB]/EFI/Boot/drivers

@noInk Thank you for the response. The GUI should be increased is what was understood. The system with no keyboard fails with a USB or PS/2 keyboard. Are you suggesting PS/2 might correct the USB issue?
TIA

@silekonn

The process work by reading certain unique information out the USB boot sector, these value are merged with the bootloader and wrote back on the USB.

If the information are not available that's an underlying issue with the device used.
Usually running a full format and the clean command restore the USB sector affected.

The application and it's helper require administrative privilege access.
A miss-configured account or broken system policy can affect the privilege escalation process.

About the keyboard, if what appear an USB keyboard doesn't work it might be an staged USB device with something else wrapped with keyboard capability.
Change keyboard.
For Virtual Box or by using the PS2 port the Ps2KeyboardDxe and Ps2MouseDxe are required to be dropped in [ZIP]\DUET_EDK2020_REFIND\DUET\EFI\Drivers on 2020.

hello. sorry for the lack of updates. most of the issues i've found i seem to have traced back to just..
a wank motherboard.

i decided to buy another motherboard wich offers overclocking.

but so far i havent had success yet in booting.

I bought a gigabyte g1 guerrilla rev 1.0 wich is also x58. updated the bios so it supports 4tb hdds and some bug fixes.


from what i've seen. it only allows to boot from legacy (only cd boot offers legacy or efi mode)
the only thing regarding "efi i've found is this in the manual

"Hybrid EFI Technology combines the benefits of GIGABYTE's mature BIOS platform including stability and compatibility with 3rd party products with 3TB+ HDD support from EFI technology, allowing GIGABYTE to offer the best of both worlds through a quick and easy BIOS update using GIGABYTE's @BIOS utility that is freely available from the GIGABYTE website.
GIGABYTE DualBIOS™ is a patented technology that automatically recovers BIOS data when the main BIOS has crashed or failed. Featuring 2 physical BIOS ROMs integrated onboard, GIGABYTE DualBIOS™ allows quick and seamless recovery from BIOS damage or failure due to viruses or improper BIOS updating. In addition, GIGABYTE DualBIOS™ now supports 3TB+ (terabyte) hard drive booting without the need for partitioning, and enables more data storage on a single hard drive."


i've used the same usb drive i've used on the previous motherboard and tried the 2015 and 2020 version of the bootable method you provided.


when i tried to boot from the usb that booted on the intel board. i see the text "restart" in red and then a red blinking cursor forever.

so i remade the usb both with the 2015 and 2020 version of DUET and that results into it being stuck on a white blinking cursor on the bottom of the screen.

i've tried to boot the usb as usb-HDD and usb-CDROM with no change.

what would you recommend? thank you in advance ^^

edit. maybe handy info. trying to make the usb drive on another machine. tried it on a laptop wich gets stuck on coyping boot but another laptop running w10 worked right away

@sebaskitty

Download and unpack within the DUET_EDK2020_REFIND directory this archive.
Attach the USB you made for DUET.
Open an Admin command prompt and move to the DUET_EDK2020_REFIND directory and type:

ReadBoot Drive_Letter: SECTOR
 
 

Locate the new DBR and MBR files and attach them, so, at least we rule out the USB.


All info are by the way on the first page.
The gigabyte g1 guerrilla seems to be a legacy type board, if it's compatible and the bios is not a mess you could follow the how to for non-UEFI legacy board.

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

i managed to get clover booting actually and it boots.

same problem with keyboard though.

my gaming keyboard turns off and i have to use a "dumb" keyboard to click enter.

i'll mod some of the clover configs on mac os with clover configurator as that allows greater modification to the plist

so far the sata 3 on the board works fine. i havent testes sata 6 yet as i have a weird bug..

BErrorart! booting from legacy

Zitat von noInk im Beitrag #249

---

@glenlewis09

It mean there an error on the LBA/MBR ( DiskError / BadBootSector or both ),
are you booting from legacy or UEFI? EG: DUET/REFIND or REFIND alone?

Unless you are capable to manually change the OS boot mode, the OS must be initialized (media installation) with UEFI, also check on the root USB the Efildr20 presence.

CPU?
BOARD?
OS?
PROCEDURE? EG: DUET/REFIND (Booting the NVME drive from non-UEFI legacy board (DUET with optional REFIND) with USBSetup.)

---

How to install DUET_EDK2020 on a hard disk with a GPT partition table?
I was unable to execute CreateUSB Drive_Letter: BOOT in GPT

I'm trying to implement DUET_EDK2020 in a multiboot usb flash that uses syslinux (legacy bios boot) and refind (uefi boot). Basically I would like to boot legacy and uefi operating systems on a non-uefi system.
Is there a way to chainload efildr20 so that it loads refind on computers with BIOS/CSM only boot?

Hi all, i have followed the instruction to create USB with DUET, boot from USB and correctly see the graphical BootManager, the large W10 icon on top appears "Boot Microsoft EFI boot from EFI system partition":


Click on it and process stuck on the blue windows flag:


My motherboard is a Asus P6T Deluxe V2 with Samsung 970 Evo.

I have already tested with the same result:
DUET_EDK2020_REFIND, DUET_UDK2019_REFIND, DUET_UDK2017_REFIND and DUET_UDK2015_REFIND; Official Win 10 Pro, Win 10 Ent.

Anyone can help me with some ideas?
Thanks in advance and regards

Try this, go into your BIOS disable Intel VT-d and try again. Let me know if it work, I have one P6X58D-E with X5690 and 24GB RAM, and i think i gonna try that same buy pci-e nvme with 970 evo plus.

THANKS @NPina ! Your suggestion makes the windows boot working perfectly!

As for reference, in BIOS settings I have disabled the "Intel VT-d" (this feature blocks the Windows startup):


Consequently, I think that "Intel Virtualization Tech" is no longer necessary so I disabled it:


Please, can you confirm that CPU Virtualization cannot be enabled at all using DUET?

Thanks and regards

This is Windows compatibility or (*force us buy new hardware), this has nothing to do with DUET, DUET do his job whit success.
I think the latest version compatible with our old* Intel VT-d is the Windows 10 version 1803 or below
Our Intel VT-d feature is too old* my friend
We cannot install any version of windows 10 above 1803 with VT-d Enable on our machines, in anyways.

Can you give me your numbers, readings and writings to give me an idea?
I think it will be around 1200MB's ~ 900MB's, because of the PCI-E 2.0 limitation...

Thanks and regards

Hey folks . I wonder duet can be used for a motherboard that doesnt have uefi to work with a gpu which doesnt support legacy bios motherboard ?? Is it possible . Motherboard is gigabyte ex58-ud5(rev.1) .