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

@ward201185 Make a try with disabling your HD sound driver from your graphikcard in Device Manager Dietmar

@geeb21 I think it is enough, to disable all UEFI in Bios and to disable "Fast Boot" in Bios Dietmar

@geeb21 In Patches\ACPI drivers change the acpi.sys 7777 -> acpi.sys 6666 version from the folder.

@geeb21 Make a try with the other acpi.sys 6666 Dietmar PS: This Bsod because of acpi.sys is strange, because before you dont get. Set in Bios everything to "Legacy", no UEFI at all. Disable "Fast Boot" in Bios.

@geeb21 Do you use the last XP SP3 from Ramsey from 9 September 2022? On which compi you try to install XP now? Make a photo of the acpi.sys blue screen Bsod Dietmar

@geeb21 Try the XP SP3 from Ramsey with settings 1, 3, 5, 6, A, C, D, E Dietmar

@geeb21 Only MBR works for now with XP. Use Firadisk install as described in https://www.zone94.com/ together with this nice XP SP3 from Ramsey Dietmar https://ufile.io/qz4e1an9

@geeb21 This compi has the Intel cpu N3000 with graphik HD 400. The Bios has CSM, so you will be able to install XP but no 3D graphik for HD 400 under XP Dietmar

@dizzydevil Just look on left side above in Core Temp https://www.alcpu.com/CoreTemp/ how much the power consumption is with 0% cpu load. It should be less than 20 Watt, then all is ok Dietmar

@dizzydevil Just put this modified intelppm.sys into windows\system32\drivers of your XP from an outstanding OS Dietmar https://ufile.io/908ky4hm

@Damnation All *.pdb are loaded. I make a test with the usbxhci.sys and usbhub3.sys from the Ramsey XP together with all your files from win10. They work via this way. I think, that this message mean, that usbxhci from win10 cant work together with the other files Dietmar

@Damnation Here is result for the win10 usb3 driver: 0: kd> !devnode 8a8ab6d8 DevNode 0x8a8ab6d8 for PDO 0x8a861710 Parent 0x8a861db8 Sibling 0x8a8ab5a8 Child 0000000000 InstancePath is "PCI\VEN_8086&DEV_A2AF&SUBSYS_A2AF1849&REV_00\3&11583659&0&A0" ServiceName is "USBXHCI" State = DeviceNodeRemoved (0x312) Previous State = DeviceNodeInitialized (0x302) StateHistory[08] = DeviceNodeInitialized (0x302) StateHistory[07] = DeviceNodeAwaitingQueuedRemoval (0x30f) StateHistory[06] = DeviceNodeInitialized (0x302) StateHistory[05] = DeviceNodeUninitialized (0x301) StateHistory[04] = DeviceNodeRemoved (0x312) StateHistory[03] = DeviceNodeInitialized (0x302) StateHistory[02] = DeviceNodeAwaitingQueuedRemoval (0x30f) StateHistory[01] = DeviceNodeInitialized (0x302) StateHistory[00] = DeviceNodeUninitialized (0x301) StateHistory[19] = DeviceNodeRemoved (0x312) StateHistory[18] = DeviceNodeInitialized (0x302) StateHistory[17] = DeviceNodeAwaitingQueuedRemoval (0x30f) StateHistory[16] = DeviceNodeInitialized (0x302) StateHistory[15] = DeviceNodeUninitialized (0x301) StateHistory[14] = DeviceNodeRemoved (0x312) StateHistory[13] = DeviceNodeInitialized (0x302) StateHistory[12] = DeviceNodeAwaitingQueuedRemoval (0x30f) StateHistory[11] = DeviceNodeInitialized (0x302) StateHistory[10] = DeviceNodeUninitialized (0x301) StateHistory[09] = DeviceNodeRemoved (0x312) Flags (0x000022f0) DNF_ENUMERATED, DNF_IDS_QUERIED, DNF_HAS_BOOT_CONFIG, DNF_BOOT_CONFIG_RESERVED, DNF_RESOURCE_REQUIREMENTS_NEED_FILTERED, DNF_HAS_PROBLEM CapabilityFlags (0x00002000) WakeFromD3 Problem = CM_PROB_FAILED_ADD Here is the whole Windbg output Dietmar https://ufile.io/k6dxz0kn

@Damnation You just forget 5 funktions in ntoskrn8.sys EtwSetInformation MmMapIoSpaceEx ExQueryWnfStateData ExSubscribeWnfStateChange ExUnsubscribeWnfStateChange Dietmar

@Mov AX, 0xDEAD On XP SP3 when doing dxdiag.exe, the "Input" fails. It depends on USB. When I disable all usb on any z690 board, no crash happens. I try a Windbg session for to look at this crash. The only information I get is LPC[ 270.2fc ]: csrss.exe Attempted ReplyWaitReceive to Thread 89ab2468 (dxdiag.exe) LPC[ 270.2fc ]: failed. MessageId == 12669 Client Id: 9d4.9d8 LPC[ 270.2fc ]: Thread MessageId == 0 Client Id: 9d4.9d8 Do you have an idea, how to get more information about this crash from dxdiag or do you have an idea, why this happens Dietmar

@Damnation I test via windbg the usbxhci from win8.1, which you send to me. Here is result Dietmar USBXHCI: Controller enumeration failure in WdfEvtDevicePrepareHardware Break instruction exception - code 80000003 (first chance) USBXHCI!Controller_WdfEvtDevicePrepareHardware+0xe7: b95b32a9 cc int 3 4: kd> g Unloaded modules: b8073000 b807d000 WppRecor.sys b4588000 b45cb000 USBXHCI.SYS b455d000 b4588000 ucx01000.sys b49bb000 b49cf000 Parport.SYS b650b000 b650e000 DumpDrv.SYS b57af000 b57ba000 imapi.sys b57bf000 b57ce000 redbook.sys b5d70000 b5d75000 Cdaudio.SYS b5be7000 b5bf7000 cdrom.sys b6523000 b6526000 Sfloppy.SYS b5bf7000 b5c03000 Flpydisk.SYS b5d78000 b5d7f000 Fdc.SYS ba318000 ba322000 WppRecor.sys b9585000 b95c8000 USBXHCI.SYS b92a0000 b92cb000 ucx01000.sys DevNode 0x8a1eb6d8 for PDO 0x8a1f0340 InstancePath is "PCI\VEN_8086&DEV_A2AF&SUBSYS_A2AF1849&REV_00\3&11583659&0&A0" ServiceName is "USBXHCI" State = DeviceNodeRemoved (0x312) Previous State = DeviceNodeStartCompletion (0x306) Problem = CM_PROB_FAILED_START Failure Status 0000000000

@Andalu I remember a check from @Mov AX, 0xDEAD, and he noticed, that with this tool no trim at all was done on any nvme device. But at this time he has not the Silicon driver, so who knows Dietmar

@Andalu This "frozen" happens, when you use an nvme device, that has been used for some time (or formatted(!)). So, trim your nvme device and do not use "format" under XP, because this shortens the lifetime. The nvme device can be "trimmed" for example under win8.1 (tools for disk). When you use an nvme device under XP, until now I do not know a tool, that can trim an nvme device under xp and so this "frozen" happens. It goes away after one time "trim" Dietmar

@Damnation There exist a checked version of win8.1 and I have. The same to win8.0 You can compare the file size, the checked version always produce bigger files Dietmar

@pappyN4 Only the Microsoft nvme driver version 2.0 works without problems Dietmar

@Damnation BSOD 0x7E 0x80000003 If exception code 0x80000003 occurs, a hard-coded breakpoint or assertion was hit Dietmar PS: Today I do have not much time but on Wednesday.

@pappyN4 Yepp, also on the Asus WS z390 Pro XP does not like 128 Gbyte ram, only 64 Gb Dietmar