I'll check on those, looks like iCBD.bin not same as ICHAAHCI.bin, version 1.20e I have a programmer if any issues. I did notice that in prior posts that the bios had to be set to RAID, thank you.

Gonna try both and I'll report back. Also will try the INTEL AHCI version 2.00h.

BTW the 3G EFILDR20 did not speed up the boot time. It's the bios Im sure.

@docdude

Even if removing that F2 module doesn't work leave it out of your BIOS.
It's abnormal that it take longer than few second's to load past the boot stage. I'm sorry it didn't work out.
--
Anyway is this happening during the boot phase, memory check or the OS transition?
I doubt something will change but if you want to test these changes, feel free.

https://drive.google.com/uc?export=downl...RcriyTqtF4bXPhB

It happens in the boot phase. It takes at least a minute and a half to get to the memory check. Once at that phase it is still slow but takes only 15 sec or so to get to the menu items.
Im flashing tomorrow I'll report back then.

@docdude

Perhaps this build then will boot almost normally on your config, if it does something different, or nothing at all.. lemme know.

https://drive.google.com/uc?export=downl...mMY41rOh3F5D684

--
I pushed these changes along few other on the 2019 version available on the first page (25/10).
---
If it doesn't work, the only way is to serial on an older version running from another PC to see what going on and to see where and how it stuck/loop.
Sort of "useful" information can be view by starting a shell from REFIND and then type

FS0:
dmem > dmem.txt
memmap > memmap.txt
smbiosview > smbiosview.txt
reset

The result can be found on the DUET USB root dir.
But, anyway I won't be able to fix with delay.

Still plugging away to make a win 7 NVMe install because some hw.bot benchmarks do better in an win7 environment.
But with little success, I have seen some benchmark and game comparisons between win7 and win10. It appears win 10 does have some advantages over win 7, Hirens PE win10 enterprise environment without the telemetry / bloatware is looking promising to limit the processes down to 35.
I have had some success in windows 10 outmatching any Optane DC on a x58 chipset making the 970 EVO plus read and writes do what it was not designed to do.

@1BadMoJoe

To install WINDOWS 7 make the installer media FAT32 to get it see from REFIND without the need of additional driver.
If your USB is made with the Windows USB/DVD Download Tool from Microsoft, or it is NTFS: drop within the "EFI\Boot\drivers" directory of DUET the ntfs_x64.efi extracted from the binary distribution of REFIND.

in addition to this you need the UEFI win7 installer:
Extract the "bootmgfw.efi" from your "USB_LETTER_WITH_WINDOW7:\sources\boot.wim\1\Windows\Boot\EFI\" within a new "boot" directory in "USB_LETTER_WITH_WINDOW7:\efi" and re-name it to "bootx64.efi"


Notice: the windows recovery in case of system failure under window 7 might not be able to restore your OS.
For the NVME driver: place the inf file directly within an directory on the OS USB
Also, perhaps now RUFUS will handle all of that just fine in GPT(FAT32).

Thank you noInk
I think I have been trying RUFUS in MBR(NTFS) for the Win7 install this whole time, thinking it needed that type of disk os environment for windows 7.
Thank you very much for the point in the right direction.

@1BadMoJoe

No problem, it should be pretty straight forward.
Here mine X5670 on win10 1903.

Zitat von noInk im Beitrag #517

---

@bloodfor

Is the memory check happening with this build on your system and the right size is reported?
https://drive.google.com/uc?export=downl...VSZ3B31KlG4Td9u

Can you also check on that if something change?
https://drive.google.com/uc?export=downl...R4WasXUZ93IoH9q

if it doesn't work with this one, perhaps the issue is something else.
https://drive.google.com/uc?export=downl...HjHU1Jl6ad3bRvs

---

@bloodfor

If you found a working version, just use that.
Some linked older version EG:2010|2013 might create a efivar.bin (incompatible with other version) file or could corrupt the MBR USB if the device is removed while in use.
If it doesn't boot but previously it did try to make the DUET USB again.
Also, the 2019 version got updated recently, so, you might just retry that.

the problem has resolved itself


I wish you endless thanks



works perfectly with this link

https://drive.google.com/uc?export=downl...HjHU1Jl6ad3bRvs

(24-10-2019)
performance increase with this


nice working thanks

@bloodfor

Some of the change included on 2015_3G_003 should also be on the 2019 version available on the first page, does that boot on your Z800?
If the version 2019 doesn't boot.. this might could https://drive.google.com/uc?export=downl...pnj3vW25Is29f1I

I've updated the USBSETUP 2015 version on the first page with the version you reported to work on the z800 (2015_3G_003).
Notice that "DUET TEST 003" or something will be displayed during the boot phase.
Thanks.

Thank you for the guide on this post
I successfully make duet usb to install and boot win 10 nvme
After that, I successfully relocate usb boot to internal hdd without erase all hdd data, I follow these steps
- prepare a first primary partition on internal mbr hdd using "EaseUs Partition Master"
- clone duet usb partition into prepare partition and make this active partition
- backup duet usb mbr sector and restore into internal hdd mbr sector using "Bootice"
- boot into bios and set hdd first boot device
And now I can boot to win 10 nvme and don't need to insert duet usb to my pc

DUET 2019
mainboard: supermicro x8dtl - dual cpu xeon x5670

This is phenomenal!
I dug out my old Gigabyte x58a-ud3r with it's Xeon X5660 4.2ghz.
(I retired it a couple years ago because it consumes too much electricity. However, that isn't an issue on my desk at work.)
Dropped in a mighty 240gb Samsung PM981--lots of cheap new systems pulls available around here in Korea.
Easily made the boot USB...and before I knew it the system was already up with the Win 10 that came on the ssd! lol
A clean OS install went quickly, and the benchmarks are beyond anything I ever thought this old board would see--1801MB/s reads and 1287MB/s writes!

EDIT: I too had to disable the on-board USB 3.0 drivers to get it working, but a USB 3.0 card with an internal 3.0 connector (missing from this mobo) was just $8 on AliExpress.
I used the latest 28-10-2019 USK 2019.
UserBenchmark also can't detect my mobo memory config, but that's not really a necessity.