@noInk,

yeah it does seem weird that it takes 2-3 minutes during duet memory check. It should be only 10 seconds at most like on my old system x58 system.

Ok.

In memory Test, hitting any key doesn't escape it.

In DUET, I can plug Win10 usb and hit esc and it appears :D (one thing that you taught me that i was able to see how it works)

No matter what bios settings, when in DUET and click on 3 colored circles, it show windows logo and then sits, no loading circle ever comes up.


I am going to try 1 ram stick or different ram. brb.

Is your keyboard attached directly on the USB or are you using some type of KVM/switch?
Anyway, change keyboard (without chip in the middle is better) or USB slot and repeatedly HIT ESC KEY during the memory test like only Patrick would do!
That will take you on the DUET "sort of" old BIOS like graphical menu.

Yeah i hit esc during it, does nothing. can I disable the memory test somewhere in bios or on DUET?
I also changed the ram, same thing, and move the usbs to different ports.

Also something I forgot to add. When computers are working correctly my USB LED Keyboard stays with all keys lit up.
so this further confirms something in hardware/bios/something doesn't allow it to enter that windows 10 (only when DUET is the starting operation)
So around the moment the circle should show up, the keyboard shuts off and only rim lights up (this usually happens when computer is not posting or something)
But stays at the Windows 10 splash screen, without circle appearing.

Almost want to consider shipping one of you the motherboard. haha. just because I think it's a very odd issue.
I just think it's amazing how it runs games, mining, and bios works flawless.

I believe it needs to be Rufus Windows 10 for this one to load through DUET.
It tries to read the Windows direct from microsoft and it doesn't have resources or something and just hangs instead of loading in.

Nope, that memory test thing is actually making the RAM available to you inside the OS.
Sort of bounding where the system, user, kernel and all see..
Could be easily fixed, might take 4 line of code. Dunno, since it should already work, or at least it does here under the "expectation":"result".
Change keyboard :D

Yeah my fear is over that it's me. I am sure I am doing it right now. lol.
Scorp said to disable all SATA, so thats 1 last thing I'll try now.

I got ask my partner where to get ISO now and put it on RUFUS. (unless you got link or advice where to get it, I am dumb with this, as I don't remember how dl the ISO, does Microsoft give it to you? I don't think so, only bootable i believe, and I hate torrenting shit)
That will take time as i got customers I am taking care of.

This is a great forum with you two. Dead forums make me sad. Mercedes Forums is Dead :( can't find anyone to talk on those.
3si.org is very populated.

I believe it is just the USB media creation that is not being done correctly. That is almost always the culprit. BIOS settings should not matter and DUET pretty much ignores it altogether since it is using UEFI loaded into memory.

Lets try cleaning the USB using the "clean" command in the command prompt please, then assign drive letter etc. Then try latest Rufus again. Some USB drives are better at some things, so maybe switch them up.

Sending your board to me sounds like a crazy idea, but people have done that before over at Overclock.net, they send me stuff to fix or repair but it is normally for expert soldering work, not for testing DUET and Windows, haha. Its an option none the less.

EDIT: I actually think @noInk would be better suited to get it working since this implementation of DUET w/REFIND is his work. Just not sure he is prepared to do something like that.

Yeah. I just got get time to get the ISO.
Rufus was nice to use I remember.

If my bootable win10 and board wasn't working, I wouldn't even be asking you folks these questions.
I guess it just doesn't work with all the boards if it's pulled direct from microsoft website.

Rufus or other is key, probably.

Thanks
J

Sorry to fill up this thread, but is good to iron out all these issues for future users.

Just for shits and giggles. I tested the DUET+Win10 on FM2+ board for customer they literally just paid for.

It works quicker and goes straight to DUET, tap ESC so doesn't go into shell. Plug Windows 10 bootable, hit esc, see 3 circles, and click on it.
Then it says EFI boot something.
after little while, instead of a windows splash screen, it shows Gigabyte bios splash screen then a rotating circle appears then loads windows 10 loader.
So I think its working.
So it's just the bootable device has to recognize all Legacy stuff (so must have to be RUFUS with this motherboard/hardware)

My idea is 2009 Motherboards and older, I think must have rufus when creating bootable USB. (I will test this when I can)

My windows 7 bootable OS I think was made on RUFUS, how do you make it work on that? it doesn't detect that usb at all when DUET is on and you try refresh it.
And the Win 7 USB works for sure, built OS a few days ago on it.

@SkOrPn
Yay not for me.
I'm a reactional bot type (sort of), just don't pinch me ok? :p

@1xstealthx1 isolated the issue in his test.
He said already more than once it's the DUET USB.
If he disconnect the USB the windows installer goes on..
Anyway like you said, DUET is loaded into the memory, and, just to make it clear, by some point backward the "Entering DXE thing" the firmware is loaded directly into the memory, decompressed and so on.
It's media doesn't matter by this point forward since it's doesn't store any volatile variable on it's disk, etc etc..

Also, DUET doesn't reset the register set by the BIOS or flip any MSR register and what else ( that's require reboot and such )

By knowing that, the USB device still seem cooky cause he's doesn't seems able to HIT the ESC while the "memory testing" is done.

Yeah, when I hit ESC during the DUET memory check it pops up with the normal DUET bios screen, which I never had to use for anything.

It's either the duet USB, or the Win USB, or his board is somehow weirdly not compatible. Too bad he didn't get the Samsung 950 Pro, instead of SM951, he might have just been able to use legacy booting on that.

Some USB doesn't work for the DUET MBR, that would simply fail some step back during the USB creation.
Could be the WINDOWS USB cause that where it mainly fail, or, the USB in general cause his keyboard doesn't HIT the ESC key :D

He should try to install that thing in DEBUG to see where it fail..
but, I'm not writing how LOL that out of the scope.

Keep In mine I didn't yet installed the "latest&greatest" WINDOWS 10 BUILD. (will do now.. T.T)
--
I'm updating..

Hmm, very good point. Maybe it is 1803, lol. But it was failing on him way before I suggested he use 1803 ISO. I think it was failing on his old install media too (which I guess could have been 1803).

If it was my board, I would install Windows 10 fresh the normal way on a SATA drive. Then I would use that fresh clean Windows 10 to make a "new" USB flash using the correct parameters. Then make a fresh clean duet disk as well. And try again.... fresh and clean. Lots of work though.

WEll, I've update to the latest build of WiINDOW 10 o mine X58 (DX58SO) without issue, so, might be still his USB media\host or something.

v1803 build 17134.12

hold on it's not using DUET :D

Updating the other one.... the one with DUET
--
And..
same build 17134.12 no issue.
Might be his USB either the HOB or the DISK

Yeah see if newest from microsoft with their boot software works with DUET. That could be the issue.

I don't think the DUET stick is the problem. It works fine on other newer motherboard.
So i think just the x58 board I have works slow with initial startup. but everything else seems to work.
If it doesn't work with different Window 10 Iso build/Rufus, then we know my DUET stick isn't working right probably.

You fellas know how to get the windows 7 usb with rufus to work? I have a stick ready but it just doesn't detect it, only my windows 10 usb one.

I was told that both Samsung 950 Pro + SM951 have legacy support built in.