@SkOrPn
This DUET build is updated to the 2017 version w/o the IEEE 1394 DXE
Maybe the 1394 is something else on that board and the driver must be customized, anyway almost nobody boot out of it.
So, if this let the board boot&load windows w/o issue, lemme know.

To use it just place it on the DUET/REFIND USB manually by overwriting the Efildr20 on the root directory.

Solid work +1 So yeah now I can get the older Duet if I need it.

Zitat von noInk im Beitrag #376

---

To use it just place it on the DUET/REFIND USB manually by overwriting the Efildr20 on the root directory.

---

OK I know what wrong. I forgot to download the new version that you posted yesterday, sorry. Let me do this again. Will report back and thanks.

EDIT:
The new DUET_UDK2015_REFIND version is broken, MD5 mismatch and it says it has missing files.

EDIT2: Yeah the DUET from yesterday is broken, every time I click on a button it spits out a MD5 mismatch error. Downloaded it a second time and the same thing happens. Not sure if I should try using it from command line?

@SkOrPn
If it doesn't boot with the build on msg59127 use the 2015 version ( that's the last build before the 2017 anyway ) and either create a shortcut to USBSetup.exe with the "-DisableMD5" parameter ( this will bypass the check ) or manually replace the Efildr20 on the USB.
--
I've updated the MD5 of the 2015 DUET version.
If you download it right now it shouldn't be necessary to add any additional parameter.
Thank you for the head up!

Yep, the new 2015 MD5 fixed version works on his motherboard with REFIND. I will make a video to show @1xstealthx1 how it looks with Refind, instead of the ugly UEFI Shell being visible during bootup. All these terms Legacy BIOS, UEFI, DUET, REFIND, NVMe, M.2 etc etc are confusing the users, lol.

Thanks @noInk

Hello All,

System Info:

Intel DX58SO Motherboard
Intel i7 920 CPU
Intel 760p M.2 512gb SSD (in PCIe x4 adapter)
Nvidia GeForce GTX 1060

BIOS Ver. SOX5810J.86A.5529.2010.1214.2317
Windows 7 Ultimate N


This forum, among others, has been very useful in getting me to this point. Much thanks. However, I'm stuck at a point where the Win 7 install still does not see the SSD drive.
I've got a Win 7 USB UEFI installer using Rufus.
I was originally using DUET with Refined till I saw your post about the DX58SO, so I've also tried the install without DUET. In the BIOS there is an option to enable/disable UEFI, so I have also played around with this.
The BIOS does see the PCIe SSD board and I've tried it with the board in the PCIe x4 and x16 slots on the MB.

Attached are some images of how the BIOS is currently set up. And how I set up Rufus when creating the Win7 USB installer.

@SenseNotCommon

On the DX58SO set the UEFI Boot option to ENABLE and follow the HOW to MAKE THE USB flash drive (non-bootable) for REFIND.

Booting the NVME drive from older-UEFI capable board - REFIND mass-storage without DUET - with USBSetup:

I've confirmed that have my USB setup just as you've indicated "HOW to MAKE THE USB flash drive (non-bootable) for REFIND".
UEFI boot option = ENABLE

I've been getting to Windows Install UI without an problems and attempting to point it to the boot nvme driver, but it throws the following msg (see attachments for screen captures): No signed device drivers were found. Make sure that the installation media contains the correct drivers, and then click OK.

Am I misunderstanding what driver it is asking for or perhaps I need to get a different driver?

Edit:
I have a very old Win7 ISO and I was doing some more reading on Win 7 NVMe driver support. It seems like this was not added till a little later in the life cycle. So, perhaps I just need a newer ISO that can see the NVMe driver. Does that make sense?

@SenseNotCommon

Yep, there aren't any INF Windows driver provided within the archive.
See the NVMe manufacturer site.

The one you are looking for might be these under the "Client-x64.zip" selection: give it a try or look for your specific OS storage device driver.
https://downloadcenter.intel.com/downloa...-for-Intel-SSDs

@SenseNotCommon

Yeah Windows 7 doesn't understand NVMe natively, like Windows 8 or above does, so yes it is just needing the NVMe drivers. I have as of yet not experienced that myself, but I have also not yet tried a Windows 7 install on NVMe media. I soon will try myself though. Windows 10 and Linux are the ONLY OS's I have been trying and both have been working fantastic on my NVMe ssd.

Did you find any proper working guides on slipstreaming NVMe into the Windows 7 iso? I'm curious...

@SkOrPn

Making a new directory on the OS installer (or anywhere accessible during the setup) usually suffice to point on the INF once asked\required.

Yeah, that is what I normally do myself. Either on the install media or on a separate USB device, either way works. But I have a client that wants it in his windows 7 iso natively.

Awesome, that did the trick. I really appreciate the help from both of you. I was a little concerned getting the nvme SSD on my platform, but I knew I would always question myself if i settled for a SATA SSD. And you guys made this even easier than I thought it would be.

One thing I noticed was at one point I had the SSD in the PCIe x4 slot and the transfer was set to 2.5GT/s, but when I have it in the PCIe x16 slot it is set at 5GT/s. All PCIe slots on the DX58SO should be PCIe 2.0, so I would expect them to both read 5GT/s. That drew my attention to the graphics card which was set at 2.5GT/s in either of the PCIe x16 slots. It is a PCIe 3.0 compatible with 2.0, so I don't understand why that would be the case.

Anyway, thanks again. I just thought I throw a few more questions at you encase you are familiar with the PCIe bus at all.

@SenseNotCommon
Nice you got it working.
About the DX58SO.
The PLX chip act as semaphore for two PCI 2.0 x16 SLOT and, depending by the board revision, the configuration could be:

Two 2.0 x16 with ( signal split )
One 2.0 x4
Two 1.1

The pair on the pci lane is also done by the power linearity and signal strength, so.. as usual use some good power supply/cable/adapter.
That's mine (202) and it's pretty much normal