Dietmar

@Andalu There may be an more elegant solution for now: Because install to nvme via ntldr works, you can install the Ramsey XP with the Microsoft 2.0 nvme driver. When this is XP is started, you can change on this running nvme XP the nvme driver from Microsoft against the one from Kai Schtrom nvme1.3 Dietmar EDIT: Does not work for me.

@Andalu After crazy testing a lot, I found the reason for this message "Could not load SYSTEM hive!". It is the same message as Bsod 0x7b, bootdevice cant be found. You can test this with an Ramsey XP on normal harddisk. There ntldr and freeldr boot work. And voila, now procedure is straight: You have only to add the nvme 1.3 driver from Kai with its storport.sys by hand. This needs some correction for Ramsey;)). You can do this with an Ramsey XP on harddisk. No nvme driver before, only after boot from harddisk. This nvme driver has to be shown to your nvme device, from where you later want to boot. Then make a copy of this harddisk and then install grub. And, voila, this crazy message is past Dietmar

@reboot12 These new acpi.sys bit64 files are made from sources. So I think, they should be stable. But strange, that you get an acpi,sys error, because this board <Skylake. I remember a comment from @Skulltrail about this old acpi.sys bit64 Bsod, when you use winload.exe. "You will get BSOD A5 0x0000002". Yepp, it is this Bsod *** Fatal System Error: 0x000000a5 (0x0000000000000002,0xFFFFFADFD02F5790,0xFFFFFA80008CA010,0xFFFFFADFD03D7A3C) So I think, the only instability can happen because of winload.exe. And not on all boards winload.exe works for to boot XP. Ask @George King for more tested acpi.sys for XP bit64, they exist Dietmar

@Andalu I make a try with my original XP SP3 Iso and put it with fake name Windows XP Professional SP3 x86 - Integral Edition 2022.9.9 (Vanilla).iso into the Ramsey folder. I use the same settings 3,5,A,C,D,E,J as before. Now I get again the "no Hive" message as before, only with freeldr load. Ntldr works. So it looks like an driver problem for freeldr, may be USB, so that the Arcpath cant be found. Just now I repeat the same but now with minimal settings for the Ramsey drivers, no USB at all, 5,C,E,J Dietmar EDIT: Even with this minimal configuration and my original XP SP3 CD I get with the driver integration via Ramsey the message "Could not load SYSTEM hive!" So, freeldr ist much more sensitive about driver integration. Nlite works. So, when you integrate all drivers by hand and use an original XP SP3 CD, you can boot via nvme with ntldr or freeldr, see my very first post here. There I did all by hand.

@reboot12 Do you use ntldr or freeldr or winload.exe? I never succeed with ntldr (XP SP3), no matter if it is on Fat32 or NTFS partition for legacy boot via nvme and the Option Rom. On older motherboards, the legacy part from the 950 Pro Option Rom works only together with freeldr or winload.exe. So, if you use winload.exe and not ntldr for XP bit64, there is chance for legacy boot. I just test this crazy message about "not load Hive". May be it is a driver problem, for example USB. I dont know, if there is a freeldr for bit64, but nearly for sure not for NTFS, only for Fat32 Dietmar

@Andalu Yepp, freeldr does not like something in Ramsey's XP. With original XP SP3 CD install via Kais nvme 1.3 driver and acpi.sys 7777 it works. The driver from Kai I integrated via Nlite. When you just copy acpi.sys to the build xp.iso, before each reboot you have to check, that acpi.sys is still 7777 version and that storport.sys is at Windows\system32\drivers Dietmar PS: This is, how to integrate storport.sys correct into setup CD from @daniel_k Just add this to TXTSETUP.SIF, under storprop.dll storport.sys = 1,,,,,,3_,4,0,0,,1,4 This must also be present in DOSNET.INF, in section [FloppyFiles.x] (where x can be 1, 2 or 3) and in section [Files]. d1,storport.sys No more files need to be edited. Got this from Server 2003 and it definitively works. Kai nvme1.3 and acpi.sys 7777 https://ufile.io/k2wvn2rv

@reboot12 yepp, because this board has only PCI-e II. This values you show are the absolut limit for this board, have a nice day Dietmar PS: Just now my Asus board from Ebay arrives, the same as yours. I am blind as much as possible about UEFI boot of XP . So, when you write Tutorial, I can check everything;)).

@Andalu I test this procedure on my Toshiba RD400 nvme. Hm, now I get the same strange message under freeldr "Could not load SYSTEM hive!" This I never saw before. Just now I test, if this depends on Ramsey's XP, just doing the same from original XP SP3 CD Dietmar

Waaoohh I think, this is the first time in world, that XP 64 boots in UEFI mode via nvme!!! Please write Tutorial step by step. All users will say thank you so much for such a Tutorial. Sometimes a small thing is important, have a nice day Dietmar

@Andalu New day, new try:)). Format your nvme device in an USB box with RMPrepUSB, Settings ntldr, force LBA calls, NTFS. No grub. Make an install with the Ramsey XP direct to the nvme device. But this time with the nvme driver from Kai Schtrom vers. 1.3. Dont use any IDE or AHCI driver. This can be done with settings 3,5,A,C,D,E,J . After testing if this XP boots via ntldr from your nvme device, make the procedure with grub as described in my Tutorial: For this, put your nvme device again in USB box. With RMPrepUSB Install "grub4Dos" (right, middle, in pink) on MBR. Install grldr. After RMPrepUSB finished, copy all the files from folder "Bootfiles" to the root of your XP on your nvme device in the USB box. Good luck Dietmar

@Andalu I just find this: https://reactos.org/wiki/A_Layman's_Guide_-_Installing_from_a_USB_memory_stick There the same message appears about Hive system, if you try to boot from another harddisk, which is not your first HD Dietmar

@Andalu Send me from XP in Windows\system32\config the file system. May be, that in Mounted Devices in system you have another letter than C:\ and then the HIVE system cant be found by freeldr.sys. In this case, you should see for a short moment the running bar in freeldr Dietmar

@Andalu freeldr cant find your windows. You can change the settings in the freeldr.ini for next harddisk. Is the nvme device the first in boot order in your Bios? It is something in this direction Dietmar

@CIACIACIACIACIACIA Such an adapter makes everything more complicate. The driver has to be for your IDE device, if your motherboard has no Sata at all Dietmar

@Andalu From the pictures, all looks ok. Do you have other harddisks connected to your compi? Disconnect all, only the nvme should stay. Make a try to disable all IDE and AHCI devices in Bios. Disable Fastboot and set everything to legacy. Enable CSM. If you have Secure Boot, disable this also or set to "Other OS". The freeldr.sys works, but cant find the windows installation of your XP Dietmar

@CIACIACIACIACIACIA Because you need the Bios files for to boot XP vita AHCI, there is no easy way to overcome this. And the question is also, for what, because IDE will be as fast as the Sata on this board Dietmar

@CIACIACIACIACIACIA You can install for your IDE or Sata device this driver via rightclick on iaAHCI.INF on running XP. https://ufile.io/qa2m4uog But there is risk. After install you have to enable AHCI in Bios Dietmar

@reboot12 For cloning the AOMEI 7.0 tool is best Dietmar

@CIACIACIACIACIACIA When you have a working HD driver for XP, it is ok. When you want to change to another sata driver, be aware that after this try you may have to install XP new. I get for example some crazy results, when I try to mix the working ehci USB2 driver with the driver for USB3. Needs new install. If your board supports Sata, this you can see in Bios. When the board is not older than from 2008, it should work. I just look, the Intel ICH5 is the first chipset with 2× SATA-1 ports Dietmar

@CIACIACIACIACIACIA Here you go. Also the nvme driver from Kai 1.3 version works. Dont forget to read the whole install instruction Dietmar https://ufile.io/p9sp8ofm

@Andalu Yepp, the part with the installations menu via grub for ntldr and freeldr is ok. So it depends on your XP installation. There is something, with that freeldr cant work, for example XP on other partition Dietmar

@Andalu Are you sure, that you load Windows and not try to load Reactos ? I tested my settings only on 1 HD and 1 partition. Content of freeldr.ini [FREELOADER] TimeOut=10 TimeOut=0 DefaultOS=WINDOWS [Display] TitleText=WINDOWS Boot Manager StatusBarColor=Cyan StatusBarTextColor=Black BackdropTextColor=White BackdropColor=Blue BackdropFillStyle=Medium TitleBoxTextColor=White TitleBoxColor=Red MessageBoxTextColor=White MessageBoxColor=Blue MenuTextColor=Gray MenuColor=Black TextColor=Gray SelectedTextColor=Black SelectedColor=Gray ShowTime=No MenuBox=No CenterMenu=No MinimalUI=Yes TimeText=Seconds until highlighted choice will be started automatically: [Operating Systems] WINDOWS="WINDOWS" WINDOWS_Debug="WINDOWS (Debug)" WINDOWS_KdSerial="WINDOWS (RosDbg)" WINDOWS_Screen="WINDOWS (Screen)" WINDOWS_LogFile="WINDOWS (Log file)" WINDOWS_Ram="WINDOWS (RAM Disk)" WINDOWS_EMS="WINDOWS (Emergency Management Services)" Unknown="Unknown Operating System" [WINDOWS] BootType=Windows2003 SystemPath=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS [WINDOWS_Debug] BootType=Windows2003 SystemPath=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS Options=/DEBUG /DEBUGPORT=COM1 /BAUDRATE=115200 /SOS [WINDOWS_KdSerial] BootType=Windows2003 SystemPath=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS Options=/DEBUG /DEBUGPORT=COM1 /BAUDRATE=115200 /SOS /KDSERIAL [WINDOWS_Screen] BootType=Windows2003 SystemPath=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS Options=/DEBUG /DEBUGPORT=SCREEN /SOS [WINDOWS_LogFile] BootType=Windows2003 SystemPath=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS Options=/DEBUG /DEBUGPORT=FILE /SOS [WINDOWS_Ram] BootType=Windows2003 SystemPath=ramdisk(0)\WINDOWS Options=/DEBUG /DEBUGPORT=COM1 /BAUDRATE=115200 /SOS /RDPATH=WINDOWS.img /RDIMAGEOFFSET=32256 [WINDOWS_EMS] BootType=Windows2003 SystemPath=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS Options=/DEBUG /DEBUGPORT=COM1 /BAUDRATE=115200 /SOS /redirect=com2 /redirectbaudrate=115200 [Unknown] BootType=BootSector BootDrive=hd0 BootPartition=1 BootSectorFile=BOOTSECT.OLD Content of menu.lst title XP via NTLDR root (hd0,0) chainloader /ntldr title XP via ReactOS loader root (hd0,0) kernel /freeldr.sys

@reboot12 After some fight with my EEpromer I succeed to flash the original Bios from Webside only with the Legacy part of the Option Rom from the 950 Pro integrated in Bios for my 960 Pro nvme. Hm, I put no ID for my network card in Bios, but can go to Internet as before??? And voila, XP starts from nvme 960 Pro on the Asus P8H77-M board. So, maybe because of 2 different numbers or wrong check sum it does not work last year with only legacy part. NO PLOP IS NEEDED now! But XP boots only with freeldr.sys. With ntldr it hangs as before. The same happens with the original Samsung 950 Pro and also with the Plextor with own Rom. It is a bad behavior of the ntldr of XP. Last year I noticed, that NT4 can boot, win7 and Reactos, only not XP SP3. It depends ONLY on its ntldr, ntldr from XP does not work together with Bios from older (< 2018) motherboards and the Option Rom of the 950 Pro Dietmar PS: Now I try legacy nvme with Win10. EDIT: Install try legacy win10 bit32 shows at once: ntoskrnl cant be found. The install USB stick is original(!) from Microsoft. This behavior I have seen on the z690 boards also. So, just now I burn a DVD with win10 bit32 Win10_21H2_German_x32.iso EDIT2: With the legacy part alone of the Option ROM from the 950 Pro, legacy win10 cant be installed. bit32 crashes at once and bit64 after 20% tells "driver cant be installed".

@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

@reboot12 Thanks, I also calculated last Byte to 7E and get Checksum 00 as wished. Now I integrate this Bios from Website, where I only integrate the 960Pro legacy part of the image.rom from the 950 Pro Dietmar