Jump to content

Booting XP via freeldr from NTFS


Dietmar

Recommended Posts


And this means,

now nvme boot :cheerleader::cheerleader::cheerleader: 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:))..

 

20221018-151636.jpg

Edited by Dietmar
Link to comment
Share on other sites

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

 

Link to comment
Share on other sites

@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 by Andalu
Link to comment
Share on other sites

@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

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...