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

@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