Zitat von noInk im Beitrag #240

---

@SkOrPn

Could you check if the application is locked, under one of the property tab? Usually both's FORMAT&CLEAN are not safe to be prompted from some random application, could be a security setting, or something since it doesn't happens here.
Eventually, I can point to the system folder, unless the above work, if %SystemRoot%\system32 is indeed already registered on the environment variable ( system property tab ).
Also, be careful with the D:\ drive on view within the screenshot. The USBSetup.exe in reality target any removable disk, not just USB type.

---

@noInk thank you VERY much for your help and your little program to call up diskpart and to make the DUET and REFIND flash drive. This should help the ones who fear using the command prompt.

Suggestion, shouldn't the buttons be in-line like below? Or did you need the middle space for the indication FeedBack "Warnings/Success etc"?

"Drive Letter DropDown"

CLEAN
FORMAT
BOOT
EJECT (Or UNMOUNT)
DUET
REFIND
CLOSE (Or CANCEL)

@SkOrPn

The "%SystemRoot%\System32" should be registered by default.
Glad it work, and, about the random application I was referring to USBSetup.

For files coming from other PC, on windows there a group policy defined as "attachment manager".
If enabled, there could be an "This file came from another computer and might be blocked to help protect this computer" security warning under the "General" tab of the application.

The empty space on the background of the application is used to display, in reflection of the application status, certain output message.
Making the button align "in-line" would leave either far to much space open or a even bigger form, but could be easily done.
About the EJECT (UNMOUNT) option.. certain device require physical removal, certain none and some USB might not even work at all and/or stuck on the writing endlessly.
--
Anyway, I've updated it on 1.0.0.6. Those error message should now be themed with the app scheme :D
Thanks for the testing SkOrPn!

Thanks for the information. I'm on a fairly fresh install of Windows 10, and the System32 variable was not in the path by default. I had to create it myself using the New button and typing it out. I was not aware of that until I checked yesterday. Sorry about that.

EDIT: FYI, Windows 10 will soon update to Spring Creators update code named Redstone 4 build 1803. My buddy (in Merseyside UK) just got his update this morning but my computers here in New Mexico USA has not yet.

Nice, so.! if it is working.. I'm going, later on, update the HOW-TO on the first page with the sequence of some previous post.
If you have any idea, or wish something to be implemented lemme know.

Giving to you the credit on adopting and testing the whole thing :P

The current archive is on 2017 but the truth is: it's from December-January 2018, so it's still pretty much up-to date.
Anyway. 1366 (WESTMERE) is still keeping up versus today consumer desktop grade ! :D
Let's hope Win10 PRO make altogether the telemetry, for anything not related to the store, opt-out-puttable before it reach it's END.

Zitat von noInk im Beitrag #245

---

Nice, so.! if it is working.. I'm going, later on, update the HOW-TO on the first page with the sequence of some previous post.
If you have any idea, or wish something to be implemented lemme know.

Giving to you the credit on adopting and testing the whole thing :P

The current archive is on 2017 but the truth is: it's from December-January 2018, so it's still pretty much up-to date.
Anyway. 1366 is still keeping up versus today consumer desktop grade ! :D
Let's hope Win10 PRO make altogether the telemetry, for anything not related to the store, opt-out-puttable before it reach it's END.

---

@SkOrPn

The sys32 PATH > Environment Variable, should in theory still be there.
I can't check on a fresh install right now.. but, supposedly you can call, on a fresh install, any sys32 files from a command prompt without adding manually the variable.
Mine install come initially from the CORE\PRO USB EDITION(2015), so IDK, might be a requirement of something else. Dunno :D
--
I fixed some UI behavior, DPI issue on win10, misspell, added some error handling and also bumped up to version 1.0.1.4 by adding a runtime detection of the BIOS type,
( Orange text = the board is running in UEFI, else in compatibility mode or LEGACY ) plus, I dropped down the size back to 95KB :O
Certain unpacked directory are now run vs MD5,
if needed the integrity check can be bypassed by adding the "-DisableMD5" (w/o quote) switch.
By doing so, the application will look like that;

I have just tried this, and when I boot from the USB It comes to a screen with BErrorart! in red on the screen... Any Ideas?

@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.)

Hey Folks, I am new here.
You all really seem up to date and recent on X58 M.2 Support.

I have questions before I give up. Unless there is a video on that DUET thing. (It gives me a headache reading those instructions lol)

But anyways.
My system is a X58 Asrock Extreme Evo 960 M.2 + Pci Express Adapter (I know about 960 not having legacy or w/e) 950s are too expensive...
I tested a riser on pci E slot as well, and it reads the same shown below.

So my Bios is update to date and set to AHCI. (after enabling AHCI, the drive would pop up on Windows 10 installation)
I can view the Drive on Windows 10 installation.
But then when I try click next, it says This computer may not support booting to this Disk.
Windows 7 USB ISO wouldn't show drive at all.

No one ever mentions this, so I felt like I won half the battle. It's frustrating because I think I am there. but I believe I have to do a lot more to get it going.

So what should i try that will give me the least headache?
Is there Windows 7 or Windows 10 that's modded to support this.
Or Bios mod for Asrock X58?
Or Mod to my M.2?

What should i try to do?


I am eager to join the X58 club. I always wanted one and I love how it functions and the settings. I have like 3 cpus ready to Oc on it.
But I REALLY don't want Disc Drive or SSD with only 200-250 speed. No Thanks lol.
I want to tease my friends with this absolute troll build.


If its too much headache. I just return this M.2 and buy this one.
https://www.ebay.com/itm/Samsung-256GB-P...HoAAOSwSO5a69oX

I just want one with a warranty, be nice if they put that legacy driver back on.. like wtf..

Lastly. I fail completely at following that guide with DUET from audiocricket as it doesn't open no matter what.
Open command line prompt (with admin privileges)
CD to unpacked DUET folder
Run CreateUSB.cmd DRIVE: (where DRIVE: is your DUET's USB stick drive letter)
And the rest of it makes me sick trying to understand it. lol

@1xstealthx1

Thing is;
The Windows7 USB installer must made with UEFI in mind to deploy the OS.

The guide attached upon here allow the creation of the out-of-chip firmware (USB) to call upon the system initialization.

Perhaps I've already mentioned somethings upon mine older post, anyway;
to make the ISO media or whatever, be creative or see some how-to via (www) search with "WINDOWS 7 USB GTP UEFI" in it..
If you succeed,. let's you know.

either OS is fine. but thanks for information. I am a little slow.

I emailed Samsung.. lol.. Why give it to us in the first place if you take it away. I asked it we can have a software to load it to our new NVME M.2s

Yeah I am pretty bad at this stuff. I am good with hardware and some software but not everything.

I ended up returning it. But this would be great if someone resolved this instead of that complicated DUET thing.
Going to go with the Samsung 950 Pro or PM951
Those should be plug in play as I've read, right?

I don't like how I have a bad taste in my mouth, knowing that there isn't a more simple solution for future M.2's Via Pci E/Express.
I felt like I was close but the windows system wouldn't allow the next step. Saying hardware isn't supported but ACTUally showing the drive though...

@1xstealthx1

On the NVME M.2 you need to boot the OS installer from the DUET>REFIND GUI to been able to select it as bootable.

To do so, make the DUET USB by following the DUET/REFIND (Booting the NVME drive from non-UEFI legacy board (DUET with optional REFIND) with USBSetup.)
After the last point, from your Legacy BIOS interface, make sure to change the BOOT PRIORITY ORDER to this new USB disk, save and exit.
By booting from this USB disk you'll see something similar to the preview image attached on the first post.
Once there, attach the OS USB installer and hit the F5 key to refresh the view, this will allow to select and install the OS on the NVME drive.

Thanks.

Yeah i couldn't get DUET to work. (early stages failed me, on just making it bootable, prompt/run wasn't working.)

but anyways
M.2 NVME Samsung 950 Pro and the other one should just work no issues right? once i find good price one of those, I am going to order it.


* I just bought one. seller lowered the price* Samsung NVME M.2 256GB SSD PM951 MZ-FLV2560 MZFLV256HCHP-000MV *
$65 shipped!
So this model should just work normally right?

The ONLY thing I can think of that would be easier would be a bootable_duet-refind.iso format, then all we would need to do is use Rufus on a working windows PC and burn the bootable_duet-refind.iso to usb. Those instructions from the OP copied below here and edited for clarity work perfectly flawless for me every time, and on many multiple computers. I just do not see how it could fail... It's practically fail proof, unless the machine and or user is broken. These instructions are for a working Windows PC.


ALL OF THE BELOW ASSUMES YOU KNOW HOW TO START AND USE THE COMMAND PROMPT!

• 1) Open the Windows Command Prompt with "Run as Administrator" option at the same location you unpacked the DUET to (obviously).

• 2) CD into the DUET_UDK2017_REFIND folder if you haven't already.
EXAMPLE: "cd C:\DUET_UDK2017_REFIND" (without quotes). Enter.

• 3) Note down the drive letter of the USB flash drive.

• 4) Type "CreateUSB Drive_Letter: FORMAT" (without quotes).
Example: "CreateUSB.cmd K: FORMAT" (without quotes) - (K: is the drive letter of the USB flash drive.)
This command will format the selected USB flash drive and set up the MBR boot code and the Boot Sector necessary to boot DUET.

• 5) Safely Remove and Replug the USB flash drive. (crucial).

• 6) Type "CreateUSB Drive_Letter: DUET" (without quotes).
Example: "CreateUSB K: DUET" (without quotes).

• 7) OPTIONAL: REFIND BOOT MANAGER: (this is needed to "easily" boot the Windows installer)
Type "CreateUSB Drive_Letter: REFIND" (without quotes).
Example: "CreateUSB K: REFIND" (without quotes. This will copy all the REFIND files to the USB in order to have a GUI that can boot things, such as Windows).

• 8) Once done remove the USB flash drive.

• 9) Plug in the USB flash drive on the target system and set "Boot from USB" as the first option in your system's BIOS Boot order option.


By the way, the 950 series is a mighty fine SSD, there's no reason to upgrade to the 960 or 970 if your still on the PCIe 2.0 boards, unless of course you plan on upgrading soon to PCIe 3.0 and want the latest greatest tech. That is why I went with the 960 series, because I plan to upgrade to Ryzen this summer.

Good luck with your 950, it should work well, but you can still have issues with them too on older systems.