@SkOrPn

Probably you need to look on how-to add the INF and related catalogue files to the WIM of the installer.
I saw many guide or thread or something around, even here.

Anyway if you look on any search engine for something like "ADD device drivers to install.wim" or "ADD INF driver to WIM" you'll be able to :p

Yeah I know, I have done it many times before using vlite and ntlite (since their initial creation) however I am always looking for something new and unknown. So, I was directing the question towards SenseNotCommon in order to see how he gets it done (which he already revealed). If you don't ask people questions, even when you know the answer, you won't ever discover new things which I am ALWAYS on a quest to discover new things, always always always. Life as a tech is boring otherwise... I know how to use Google, which is how I was running NVMe on x58 a year before this thread was created. lol

So when you see my questions like this, assume I already know the answer and I am just digging for new things to learn ;)

I also recommend creating your own install.wim instead of using vlite type editors, with install.wim creation you can easily install anything (programs, drivers etc) you want or put anything you want into desktop, documents etc and it will always be there.

Yes I agree.

Windows 7 requires a hotfix. This article describes how to manual add the patch to a wim.
https://support.microsoft.com/en-us/help...indows-7-and-wi . For other articles, try Googling "Windows 7 NVME" regardless of whether your M.2 drive is NVME.

Hi guys
I need some help.
I have a problem with the DUET REFIND 2017 installation.
After starting the computer with a connected USB device, the BError error is written in red font. The computer crashes before loading the UEFI console.

Are you able to help me?
The specification of my computer is in the signature.
I'm sorry for my english :)

Hi again,

I wanted to say thanks for the suggestion and link to getting nvme into win. I read Microsofts article and it was interesting. However during the research I came across the MSI Win7 Smart Tool and it took less than a few minutes to get NVMe into the wim. Burnt the iso to a usb and sure enough Windows 7 saw and installed perfectly to the Samsung nvme drive on a ASRock x58 Extreme board.

So yeah I cheated, but that was what the Win7 smart tool was designed to do.

@irrealis, can you provide a video of the issue perhaps? Did you mean to say when you start the computer with a connected duet USB text turns red with a error?

@SkOrPn, Yes, exactly what I meant.

Video a link from creating a usb to an error (3min): https://www.dropbox.com/s/6pzl63h6l2yhuvh/IMG_0857.MOV?dl=0

Zitat von irrealis im Beitrag #398

---

@SkOrPn, Yes, exactly what I meant.

Video a link from creating a usb to an error (3min): https://www.dropbox.com/s/6pzl63h6l2yhuvh/IMG_0857.MOV?dl=0

---

I've plug in the DUET / REFIND USB for the Lenovo T530i laptop. The result is visible on the video.
https://www.dropbox.com/s/kc32bjcrtrlx7xt/IMG_0858.MOV?dl=0

EDIT1: I checked every usb slot. In all of them is the same - red BError.

EDIT2: I tried witch DUET/REFIND 2015 version - redBError.

I dont have any other USB device. I have hdd. Can i install DUET on it?

Zitat von irrealis im Beitrag #400

---

I don't have any other USB device. I have hdd. Can i install DUET on it?

---

@SkOrPn
The BError mean there an miscommunication (DiskError) on the startup sequence of DUET.
That error occur when the LegacyBios pass wrong BPB(LBA) data in real mode, it's an exposure of bad implementation of 0x7c00 code\management.
Proprietary code or embedded proprietary hardware could also cause the INT13 failure.

@irrealis
If the USB stick is know-to-work on another intel x64 machine and the DUET build attached on the first post doesn't work on your motherboard, you might either need to patch the bootsector by yourself on the DUET source with the supposedly "accepted" or "tagged" coord of your actual reported disk sector, ask the motherboard vendor to fix it or try CLOVER to see if something changes.

B(oot)Error! = unsupported

@SkOrPn
USB stick formated using BDUtility ver.2.1.023 -> DUET-REFIND 2017 installed on it (full sequence) -> BError
USB stick formated using BDUtility ver.2.1.023 -> DUET-REFIND 2017 installed on it (DUET->REFIND) -> NO BError but computer stops at the same moment.
HDD formated using BDUtility ver.2.1.023 -> CLOVER 4722 installed on it -> NO BError but computer stops at the same moment. If i unplug hdd disk witch win7 and computer restart, CLOVER is loading -> "6" is showing, and after that blinking _ white sign. Computer not responding - only hard reset helps.

Qemu Simple Boot v1.3
HDD formated using BDUtility ver.2.1.023 -> CLOVER 4722 installed on it -> 2 errors (links below in order of showing errors)
https://www.dropbox.com/s/0ja250qwi3wp9l...art%21.jpg?dl=0
https://www.dropbox.com/s/3it2v86uy50eyr...ted%21.jpg?dl=0

T530i Spec:
Intel Core i3-3110M 2,4 GHz
MB: 2394BK4
OS: Win7 PRO 64-bit SP1
UEFI BIOS: 2.62
USB stick formated using BDUtility ver.2.1.023 -> CLOVER 4722 installed on it -> CLOVER is loading -> "6" is showing, and after that blinking _ white sign. Computer not responding - only hard reset helps.

@noInk
I doubt that the motherboard manufacturer / supplier can help me. I am determined to run UEFI on this machine. If I learn something extra - plus for me. However, I need some tips on how to do it -> "to patch the bootsector by yourself".

EDIT: Im reading user manuals from UDK 2018. Is there any option to compile DUET with specs matching to my machine? Can i get somehow binaries with my spec and put it in to my personal compilation of DUET?

@irrealis
The notebook may already have UEFI. 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:

@noInk
I just installed clover-4152 with UEFI v2.60. The problem is computer stops responding after writing few signs (doesn't matter what i wrote).
link: https://www.dropbox.com/s/rq362eao19wsqt...i-2.60.JPG?dl=0
Any ideas?

If i understood, UEFI is only for machines with intels processors? Is there no possibility to run UEFI on AMD or any other processors, like ARM for exemple? Is there no upgrades or patches for this kind of problems?