Zitat von Ghaben im Beitrag #89

---

Major problem is that system won't start at all if on-board USB 3.0 chip is enabled.

---

Hi, guys.
Since I got zero feedback on the Clover thread, I've updated DUET to UDK2015 few month ago.
That build also linked here has the NVME DXE from UDK2017 support by default, reduced boot time (versus the 2013 version flooting on the cricket guide) and minor other changes.
Is someone using it?
DUET UDK2015 for X58 -- Windows 10 Fall Creator Update (FCU 1709) has been reported to been NOT able to make the USB bootable. << sort of fixed that.
I'm using it on mine revived x58 and well, no big issue to report! :D

Going to try this on a system or two tomorrow. Thanks much! Please LMK if you could use any help from a technically skilled non-programmer. Anything you'd like if it works half as well as expected.

@noInk:
I just now saw your last post.
What did you update and why did you update it? Did you see an improvement on somuething?

EDIT by Fernando: Unneeded fully quoted post replaced by directly addressing (to save space)

SkOrPn.
The build linked on the audiocricket guide has UEFI 2.1 (2010) or partial 2.3(2013) IDK right now, this one is @ maximum five year ahead with UEFI 2.5 spec(2015).
There a lot's of changes in code\driver base.

Additional main changes are;
Embedded the NVME/USB DXE within the Efildr (DUET) to have not to deal with the manual load of any driver required to boot from PCIex card.
Updated the NVME DXE to the current 2017 release version for additional asynchronous I/O queue: different buffers and page allocation size.
Reduced the bootloader timeout to 2 sec because why not!? ( it doesn't cause any critical BUGBUG on this platform ).
Modified the handoff text to "ENTERING DXE -- DUET2015" or something in case someone tell me it stuck to WELCOME TO EFI.. ( been there too! ahah! )

Let me know if there are any issue with USB 3.1, mine board doesn't have it so the driver is fully untested and can be eventually updated.
Be it on boot time and fluidity., I do see an improvement on mine side.
Also, keep in mind this is pretty much tailored on the ICH10R and one X5670, anything else is strictly not tested.
Be advised: both's chipset/CPU with higher revision/year, like a different platform altogether, will likely not work or cause issue on boot.

@noInk

Thanks for the build of duet. I am using clover and it never requires for any manual loading of dxe's, it just instantly see's my SM961 and USB 3.1 card/drives. I am also using a 2010 Rampage III (ich10r) with a X5650. I do have a USB 3.1 card though and that is how I install Windows and Linux from, using the XhxiDxe-64.efi which as I said loads automatically by default on clover.

What I would like is a faster boot up, and up to date efi. We know clover is constantly updated, has a nice UI, but it is also highly tailored to OSX.

Now, for the... Um how do I convert my clover usb to duet usb question? lol. Are you suggesting we use the same instructions on Audio Cricket, but instead use the CreateUSB bat you posted above? Or did you have instructions somewhere posted on the internet that I failed to find? Thanks for any tips. I would like to convert back to DUET.

SkOrPn.
If you do already made the DUET USB with the very well written audiocricket guide, use the CreateUSB within this archive and SKIP everthing else.

From the README;

@noInk

Hmm, unfortunately it failed, several times saying it could not read/write to the usb drive. It is a normal 8gb sandisk drive and works with the duet from audicricket. That is confusing... I even used diskpart to format it a 3rd time with the clean, format fs=fat32 quick and active commands, all to no avail. Maybe that failed message is normal and I should just continue on with the rest of the instructions perhaps?

Going to try formating it on a different PC now, which would be surprising if it works. BRB.

Here is a img of the error I am getting. EDIT: OK, tested on two different perfectly good machines, and this duet I downloaded above does not work. During boot it says MBR failed and that there is no operating system found, please install boot media and reboot, or something like that. Now what? lol



EDIT2: I suspect it might be the new Fall creators update for some reason. I just tried it on 3 different USB drives and I get the exact same thing "ERROR: Write DBR: failed - Failed to read/write files (LastError: 0x5)!" on all 3 usb drives from two different machines. That seems impossible to me, especially since these previously worked earlier in the year for the same use.

Nope, that's not normal. Should all goes without error. ( ie. Write DBR: sucessful! )
Can you RUFUS it? and try it again? ..
Testing on Win10 FCU
..
and yep, it's Win10 FCU!
( HOLD ON TESTING ON REAL EFI, might be duo the memory protected area on emulator )
OK.
Mine real machine with Win10 without the FCU work stright away.
So, could be either duo EFI running with EMU variable, or that Win10 FCU lock something in that area.
ADDEDUM: same machine ( x58 ) the genbootsector work on both Win10 pre FCU and Win7, it seems microsoft is doing something with the FCU.
Will check on that and let you know, sorry I didn't know.

@noInk

OK, I used refus 2.17 three times with varying changes, i.e with and without boot support etc, with and without rufus mbr. All three times the duet fails at the same write DBR part. I don't understand now... I want to find another windows machine, but all my other machines are Linux based.

@noInk

Good news and bad news.

Bad news first, both my XEON machines fail to succesfully format any usb drive using duet and both machines are on build 1709.

Good news, all of them worked on my fathers (had to run next door) x79 system using the very first ever released Windows 10 (he never ever updates for some reason).

So I have it formatted, but have not tried it yet. Doing that now. Thanks for replying here.

EDIT: OK, it worked and it booted my windows install straight away.

I updated the previus post, glad you self-solved the issue.
I have no way to quick solve it duo the time required for the DL/installation of the fall creator update to just check on hardware.
Anyway, same machine x58 it work from both Win10 pre FCU and Win7, so it seems microsoft is doing something with the FCU.

Yes, and I noticed that Clover also failed. It actually finished the format just fine and said everything was succesful, but when I tried booting to it, it was just a black screen that never booted. So, both my xeon machines failed, but my fathers x79 and his i7 worked just fine on much older Win10 build. Weird...

One of my machines is x58 with X5650 running 1709 (clean 1709 ISO install), but the other machine is a Asus P5B Deluxe with a E5450 XEON running on 1709 FCU (updated install from Windows update). So yeah Microsoft must be doing something strange on some machines, or a missed bug?