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

@reboot12 Thank you for files! Which Tool do you use, for to check the Checksum Dietmar EDIT: I just found, that in your Csmcore.raw at the 2 places always only your Device ID 0xA808 appears. So, the MMtool makes an mistake and you have to set the correct Device ID by hand in the 950 Pro legacy.img before integrating. Repairs the MMtool a wrong checksum automatically?

@reboot12 I integrate with the MMTool the legacy part of the image.rom from 950 Pro. Then I check with Winhex for Vendor ID 0x144D and Device ID 0xA804 for my Samsung 960 Pro. I found 144D (vice versa because HEX) at 2 places in csmcore.raw . And strange enough, at the second place I found A802 (which is the device ID of the original 950 Pro). Do you get the same Dietmar

@reboot12 I put Plop into Bios only because of legacy XP SP3 boot. Because Plop then automatically loads the correct nvme boot device, no chance on other way in Bios settings of the Asus P8H77-M board. Can you please upload your unmodded Bios for the Asus B85M-E (without crazy cap) and also the last version of your whole modded Bios (also without cap), and the cut off image.rom file from 950 Pro and your used DXE file for UEFI nvme boot from the nuked forum. My board from Ebay comes tomorrow but your changes I will test today Dietmar PS: One year ago I also make a try with my own (UEFI cut off) image.rom from the 950 pro, but it does not work for me.

@reboot12 Have you tested XP SP3 install via the modded Bios? We need to make a Tutorial, step by step, that works for all motherboards and nvme devices. Nice work Dietmar

@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

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

@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

@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

@reboot12 I just test win10 bit64 install in pur UEFI mode (CSM disabled) on the Asus p8h77-m with Option Rom from the 950 Pro in its Bios. The 960 Pro is recogniced, but later install crashes with comment: Cant install driver. Also legacy win10 on MBR cant be installed, not bit32 not bit64. So, the Option Rom from the 950 Pro is only good for legacy "install" of XP SP3 or win7 Dietmar PS: But I know, that the DXE nvme Bios file from the nuked forum works for UEFI install of win10. EDIT: By the way you see, that the freeldr.sys is by far better than any other loader from any other OS.

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

Hi, just now it is possible to boot XP SP3 via freeldr.sys also from NTFS partition Dietmar https://ufile.io/7ma5i0m2

@George King I succeed to make an harddisk with XP SP3 on BTRFS filesystem. This harddisk with its content I can see from outstanding XP SP3, with installed btrfs.sys driver via its *.inf and reboot. I think, with freeldr.sys from reactos, XP SP3 will boot on BTRFS. But nothing happened via Quibble and my try for UEFI boot of XP SP3. I also make a try with to rename quibble.efi to bootia32.efi, then I see a single white point on screen, on a pure Fat32 partition but nothing more Dietmar EDIT: I also try with Reactos after this instructions: https://reactos.org/wiki/User:Illen/UEFI_Boot UEFI boot does not work at all on real hardware using Quibble.

@reboot12 Temperature is always about 61 degrees Celsius. For tests I run the nvme device without heatsink, but when you integrate it into your compi, it would be much better to get them a little bit more cold Dietmar PS: Tell me, if you have success with the Option Rom from the 950 Pro. Maybe Quibble is an alternative. Trim does not work under XP until now. When you use your nvme device or SSD intensive, transfer rates go down to 20 Mb/s, much less than any harddrive. I have an win8.1 installation on harddisk, which I nearly use only for trim. Today I make test for boottime of XP: Without trim 27 seconds, after trim 7 sec.

@George King Hi, of course I want them! What I understand from the git page is, that only the Quibble has to sit on an Fat32 partition. So, for the UEFI Bios files and then OS may be possible to use also NTFS, have a nice day Dietmar

@reboot12 Did you ever had success with using Quibble for to boot XP on Uefi? From last discussion about Quibble, see @George King it seems to be possible. There has been a special version for Quibble for to boot XP SP3 on UEFI, but this file is gone on zippyshare. Then, nvme boot of XP via UEFI would be much more easy, just using the UEFI nvme DXE file. And with Bios driver for ntfs, it may be work also on ntfs partition, as long as Quibble sits on Fat32 Dietmar

@reboot12 Can you please tell me, which CPU and which Bios version you use on your ASUS B85M-E board? I will buy via Ebay and make a try for nvme boot, also UEFI XP, Win10, win7, looking if this is possible to full ONLY with the extracted ROM from the 950 Pro Dietmar

I think, that for UEFI nvme boot of XP the UEFI dxe file is enough Dietmar New uploaded bios3.fd https://ufile.io/rwzx80ld XPviafreeldr.7z https://ufile.io/m16iwzzh

Hi, booting XP on this board from any nvme dvice will not work in normal way, because it has no support for nvme in its Bios. I wrote on the nuked forum, that nvme boot can be done with the Bios from the 950 Pro nvme disk, but it is not easy procedure and works only for Fat32 und freeldr.sys from reactos Dietmar http://reboot.pro/index.php?showtopic=22566 Waaoooh:)))))) , I split the Option Rom in 2 parts: First Option Rom is original plpbtrom.bin from Elmar (Plop). I modd this for the Realtek Lan PXE boot on the Asus P8H77-M board via plpbtrom -vendorid 0x10EC -deviceid 0x8168 plpbtrom.bin nvmeua.rom and integrate nvmeua.rom into Bios with MMTool (Replace Methode "Option Rom", here for 10EC 8168). The second Option Rom is from the Samsung 950 Pro. This I modd for the Samsung 960 Pro etc. and integrate it also in the same Bios with MMTool (insert Option Rom with 144D A804). And voila: I can now boot legacy NVME XP SP3 via ntldr(?), via freeldr.sys and via winload.exe on the Asus P8H77-M board from any nvme device. This methode should work on all (needs to be tested) motherboards. It is stable. All works. StandBy works. When I have time I write Tutorial. Now I am going to look at USB3 from ⇗ @infuscomus So the Plop plpbtrom-0.6 for to build Option Rom is a very nice, good tool. New nocumentation should be done for this Plop plpbtrom-0.6 from Elmar Dietmar EDIT: Plop can load freeldr.sys(!) and ntldr. Plop cant load MBR for winload.exe. So in my eyes is winload.exe not a good choice for to run XP. PS: The Option Rom from the Plextor M8Pe does also not work via this way with Plop and also not alone. So I think, the Option Rom Bios of the Plextor M8Pe speaks in other(?) way to its nvme disk. The Option Rom from Vmware see post also does not work. ⇗ [Experimental] NVMe Option ROM Not alone and also not with Plop. Plop bootmanager starts but does not show harddisk and also nvme cant be booted via "Lan" switch in Plop. The legacy nvme disk is recogniced but not correct. This is full readout Bios 1306 8MB from Asus P8H77-M board. It contains the full Samsung 950 Pro Option Rom. It boots XP SP3 from Samsung 950 Pro, Samsung 960 Pro, Samsung 970 Pro and Toshiba RD 400 and Plextor M8Pe. It contains also the Option Rom from Elmar for the Realtek PXE Lan boot on the P8H77-M. ⇗ https://ufile.io/gfnu4jn2 I make some more fun with the freeldr from Reactos with nice result for XP SP3 boot! This Tutorial I tested on 2 different motherboards. 1.) First I take an old 80 Gbyte Sata harddisk and wipe all out with 00 with Winhex. This step is not necessary, but it gives clear start situation. This HD is in an USB box, so that I can easy see, which is the wished 80 GB harddisk and that I do not destroy my other harddisks(!). 2.) Make a Fat32 partition with RMPrebUSB 2.1.739 with ntldr and force use LBA on this 80 Gbyte HD. 3.) With Rufus 2.18 portable (last version for XP) set mark for "Show USB" , Fat32, "Schnellformatierung", "Startffäges Laufwerk erstellen Grub4Dos 0.4.6a" and hit Start. Message about grldr I ignore. And also message about "fehlgeschlagen". 4.) Copy grldr (extracted from RMPrebUSB 2.1.739) on the 80Gb HD. 5.) Make a *.txt file on the 80 Gb HD with content title ReactOS root (hd0,0) kernel /freeldr.sys and rename it to menu.lst . 6.) Copy freeldr.sys and freeldr.ini from Reactos 0.4.13 on the 80GB HD. 7. With Editor open freeldr.ini and replace all ReactOS => WINDOWS . With only the 4 files grldr, menu.lst, freeldr.sys and freeldr.ini on harddisk, you can test already boot possibility for XP. It works from harddisk, USB, nvme.. 8.) With copy and paste copy there a (small, not necessary small) working XP SP3 installation. Not important, if this XP installation comes from ntfs or fat32, all work. ntldr, ntdetect.com and boot.ini dont copy. Also dont copy Recycler, System Volume Information, pagefile. 9.) Now fun starts: Connect this 80 GB HD to a compi. It gives ultrafast start of XP to Desktop via freeldr, faster than with ntldr. 10.) Tell me, if it works for you ) Dietmar PS: I just test my own Tutorial for booting XP via freeldr step by step and it works . EDIT: I just notice, that Rufus 2.18 can be kicked out of the Tutorial, because RMPrebUSB offers also the possibility to install grub4dos and also to install its own and wished grldr. Here are the needed and already edited files for XP boot via freeldr ⇗ https://ufile.io/71t6nooh I just succeed to switch for one and the same XP installation between boot with freeldr from Reactos or via ntldr. For this I use menu.lst (thanks to jaclaz at reboot.pro) with content title XP via ReactOS loader root (hd0,0) kernel /freeldr.sys title XP via normal NTLDR root (hd0,0) chainloader /ntldr This configuration can now boot any XP bootdevice. It can boot more(!) devices than ntldr alone. This is the very first time, that Reactos puts XP a lot forward. Some more tests with other boards I need, then I write new Tutorial Dietmar EDIT: With Reactos freeldr boot, the strange shutdown problem on some boards is gone.

@Damnation I have only interest in XP Dietmar