Hi,

just now it is possible to boot XP SP3 via freeldr.sys also from NTFS partition

Dietmar

https://ufile.io/7ma5i0m2

 

 

 

Edited October 18, 20223 yr by Dietmar

And this means,

now nvme boot  is possible also from any filesystem,

on any compi that never heard anything about nvme in its life,

here Asus P8H77-M

Dietmar

PS: Boottime is 3 sec:))..

 

Edited October 18, 20223 yr by Dietmar

I want to ask a question is it possible to boot windows xp 32 bit from NVME and with what motherboard models and how?

 

 

Edited October 18, 20223 yr by CIACIACIACIACIACIA

@CIACIACIACIACIACIA

Yes, but you have to integrate the image.rom from the Samsung 950 Pro in the Bios of your motherboard.

For this you need EEpromer.

Until now it works on any tested motherboard as long as it has an free PCI-e connector

Dietmar

Can this be used to boot Vista X64 (or XP X64) to install and boot from NVMe disks? If yes, how can be done?

@Sergiaws

The freeldr.sys can work only on 32 bit.

You need a compi with legacy nvme support or you can use the winload.exe for bit64.

Dietmar

Edited October 18, 20223 yr by Dietmar

I want complete details about this procedure of how to integrate this image.rom.

How about booting from an SSD usb adapter?

I want to ask another question it works with all NVME's or just with SAMSUNG 950 PRO?

 

 

 

Edited October 18, 20223 yr by CIACIACIACIACIACIA

@CIACIACIACIACIACIA

It works with all nvme devices I think. I tested a lot.

Here are the needed files for to integrate image.rom into Bioschip.

https://ufile.io/a1rnswgb

 

I dump the NVME Option Rom for the 950 Pro from Website, looking for "55 AA" Signature in those files for Option Rom.
And I flash it with MMTool 4.50.0.23,
Load Image (Whole Bios from compi)
Load Module file (Option Rom)
Enable "For Option ROM only" via "Link present"
Put Vendor ID and Device ID in (for Samsung 950 Pro Ven 144D, Dev A804)
Save Image as ..
Flash to Bioschip of compi ( I use Revelprog IS for this, best EEpromer ever)

The Option Rom is put via MMTool at the end of RAW file in CSMCORE .

I make some fun with the Asus mainboard P8Z68-V LX of ⇗ @dencorso ).
Voila, legacy nvme boot of XP SP3 works there also.
I only integrate the image.rom extracted from the Samsung 950 pro
with Ven_144D&Dev_A808 for the Samsing 1TB 970 Pro.

 

@Dietmar

Hi,

could you please make a step-by-step tutorial for boards with legacy NVMe support as well?

 

Edited October 18, 20223 yr by Andalu

@Andalu

Most easy way is to install XP normal to harddisk.

And than install the Microsoft 2.0 nvme driver from @Outbreaker,

during connecting your nvme device to the board.

And then make a copy with Aomei 7 to your nvme device.

I hope, that I understand you correct

Dietmar

 

@Dietmar

Thank you for the explanation. Tomorrow, I'll try your method.

Hi @Dietmar, this is great news, thank you sir. 

@Dietmar

Tried on a MSI Z590-A board with a Crucial P5 NVMe 500GB drive.

Here what I did:

- XP installed on the HD drive;

- inserted the NVMe drive into the M.2 slot and installed the Microsoft NVMe driver v2.0 (NVMe drive recognized correctly);

- cloned the HD drive to the NVMe drive using a bootable USB stick of Aomei Partition Assistant Pro v8.6 (prepared in Win10 with WinPE);

- removed the NVMe drive from the M.2 slot and inserted into the NVMe to USB adapter;

- applied the RMPrepUSB settings as per the "Tutorial.txt" and 6 files copied to the NVMe root replacing existing ones;

- re-inserted the NVMe into the M.2 slot as the only drive connected to the board;

- XP only boots via NTLDR.sys, since choosing to boot via the ReactOS loader I got this message:
"Could not load the SYSTEM hive!".

Did I make a mistake or miss something?

Edited October 19, 20223 yr by Andalu

@Andalu

Run again the RMPrepUSB "Install grub4dos" to MBR and copy grldr. All with the nvme in USB box.

Copy first freeldr.sys on it and after this the other files.

This happened to me also and I was very astonished,

that new install of Grub4Dos on this nvme does not destroy the content of the nvme device

Dietmar

@Dietmar

just tried without success.

I also used a different NVMe drive (WD SN750) and adapter (RTL9210B insted of JMS583) with same results.