Andalu

Thanks for the new version, but CPUs are not listed correctly in Device Manager: The same on the Z790 board.

I have to use some programs that do not work in the 64-bit version. Also, it is not very stable, at least on my boards: sometimes at startup the system crashes to a blank screen and the USB3 driver does not work properly for my KVM switch, the mouse and keyboard stop working when switching between systems.

I installed XP from scratch with the Win7 NVMe driver and PAE 4GB on my Asus Prime Z790-P and MSI Z590-A PRO boards. Once XP installed I switched from the Win7 NVMe driver to the "(New)" NVMe driver: no issues detected, both systems worked fine. Here the images:

Hi, the (intel) board with the faulty reboot when a PS/2 keyboard is connected is the Asrock B250M Pro4 with a Nuvoton LPCIO (strangely cpu-z didn't detected the chipset in this case): assuming that we are talking about the same version of the "new" nvme driver (.1007), could you please report what problem and under what circumstances such driver gives problems in XP x32 with PAE 4GB? I ask because even though I had tested it for a while on my intel system without encountering any problems, it is likely that I forgot to test it in that specific condition.

@Dietmar @Mov AX, 0xDEAD I have found the culprit! It is the usual approximative BIOS that accompanies Asus motherboards. The item responsible for the boot delay is "Boot performance mode" which I had left on "Auto" by default. It is located in the Advanced -> CPU Configuration -> CPU Power Management Control menu and has 4 options: Auto, Turbo Performance, Max Non-Turbo Performance, and Max Battery. Here is how the options behave for booting in XP: Max Battery = no delay Maximum non-turbo performance = no delay Turbo performance = 35-second delay By logic, the Turbo Performance option should be the one that allows faster startup, but instead it is the one that causes the 35-second delay and therefore, the "Auto" option corresponds to "Turbo Performance". Obviously, there is no reference to these options in the motherboard user's manual, but neither is there any reference to all the others BIOS options, another usual habit for Asus.

@Dietmar @Mov AX, 0xDEAD I forgot to report that the boot delay already occurs during XP installation before GUI-mode starts. No matter which ISO is used, the 35-second delay occurs anyway. I had already tried acpi6666 from outer space but without success. I did other tests such as installing an ISO with only the acpi.sys and sata driver integrated as well as switching the video card from ATI to nVidia but did not get the desired results. Bootvis doesn't seem to detect anything unusual either:

XP installs smoothly on the Asus Prime Z790-P WiFi D4 but this board has a strange behavior: after POST completion, once XP is selected to boot, it takes 35 seconds to display the XP logo with the scroll bar below. No activity of the HDD led during this time. Regardless of whether XP is installed on SSD or NVMe, the elapsed time is always the same. Adding these 35 seconds to the 12 seconds that this system takes to complete boot, it results in it being 4 times slower than the MSI Z590-A in the same conditions. Nothing changed by modifying the options in the BIOS, and there were no results by trying previous versions of acpi.sys (v6666 and v5048 included) (strangely, the acpiV6 that gave BSOD A5 on the MSI Z590 here allows booting without problems). Since this behavior does not occur in XP x64, Win7, Win8, Win10 because the respective logos appear after a few seconds, I wonder if this oddity could be considered acpi-related.

@Dietmar Firadisk worked on my Z590 for the XP x64 installation with the nvme driver we are testing. I used the acpi.sys from @George King (SHA-1: 9E777A69395BE58011D6493A07238F7138F66D5F) and the modded script from Ramsey although the USB3 x64 from @George King did not work during the setup.

Hi, you could create a shortcut for shutdown on the desktop containing this command: %windir%\system32\shutdown.exe -s -f -t 0 This way you will avoid going through the Start Menu. I, too, have a board (even if desktop system) that has the same problem of freezing on restart. In my case it occurs when using a PS/2 keyboard. No issues with a USB keyboard.

@Dietmar to enter on the desktop with the XP from Ramsey you can try to delete winxpup.inf from the prepared ISO. In this way you will encounter many errors for missing files (the first one during TXT mode for winxpup.inf) but by clicking "esc and OK" on the various messages the installation can be completed anyway. XP so installed will be almost unusable, and unfortunately, you will not be able to install the video driver either, which I believe is the factor that causes a change in XP's configuration that leads to the conflict with the nvme driver we are testing. With other NVMe drivers and in XP x64 with installed the driver we are testing the NVMe drive and the video card share the same IRQ 16 but I never encountered the BSOD 7F.

@Dietmar I, too, would like to get to that information but still haven't figured out how to proceed after changing the first byte in DriverEntry to EB FE: what commands to give, when to give the 'Break', and how "Then you can change (in the to memory loaded nvme.sys driver) those 2 bytes back to its original ones." Never got that message. EDIT: I arrived here:

@Dietmar I got it:

@Dietmar here the log without the ed Kd_nvme_Mask 0x7FFFFFFF command:

@Dietmar other errors:

First input and first error encountered:

@Dietmar I'm stuck on the first step:

@Dietmar Here is what happens with the crazy nvme driver integrated into the XP ISO: a) with the Integral Edition the installation of XP completed successfully, but the system gives BSOD 7F before accessing the desktop for the first time; b) with the original ISO XP installs and runs smoothly until the video driver is installed. With the video driver installed, the system starts to give BSOD 7F on reboot. I thought the only practicable way to try to understand something about this behavior is to debug situation b), after installing the video driver. How can I do that? To complete the information I would add that the same driver doesn't give any problems when installed for an nvme data disk and that in XP x64 it also works when installed for a system nvme disk.

@Dietmar the problem did not depend on the files used which are the ones you uploaded but the path of the symbols. I had always extracted the 'Symbolsss.7z' file inside the pre-existing "c:\acpi\symbols" folder and got the missing symbol error for ntkrpamp.exe. Instead now, extracting the .7z file inside the "c:\acpi\Symbolssss" folder, that error no longer appeared: Now though, how should I proceed since the 7F BSOD I get is not necessarily dependent on the nvme driver I am testing? Or rather, the error occurs only when I install that driver on the system nvme disk, then install the video drivers (ATI or nVidia doesn't matter) and finally perform the reboot. No problem when the same driver is installed for an nvme data disk.

@Mov AX, 0xDEAD before the image posted above, since filemon highlighted the reference to that specific folder: I followed the easy way: I created it manually as well as copied in windbg the file ntkrpamp.pdb since its missing was also highlighted by filemon. I don't have that version of ntkrpamp.pdb with that specific signature.

@Mov AX, 0xDEAD @Dietmar thank you for the very useful tips and uploaded files. Unfortunately, the error doesn't want to go away even though ntkrpamp.pdb is correctly in the expected directory: I assume that this error may depend on the different versions of the ntkrpamp.exe and ntkrpamp.pdb files that are present on the Host and Target. However, I have only one ntkrpamp.pdb with SHA-1 0E36280FAD94784C7457E1D05A38E53CB40904D1 linked to ntkrpamp.exe v5.1.2600.7581 (SHA-1 14A56010EDEAED3B171CC9B836BF274DD26D0995).

@Dietmar to avoid any problems, I had already installed XP - IE and configured both Host and Target systems from scratch, but evidently it did not help. The log above comes from them. Once again in the log there is the line: "Product: WinNt, suite: TerminalServer SingleUserTS"

@Dietmar thanks for the tips. Unfortunately, I cannot overcome the error "Symbol file could not be found" related to ntkrpamp.exe. I copied it together with ntkrpamp.pdb to any directory but the error is still there. Here is the log:

@Dietmar Hi, what are the proper commands to give in WinDBG to debug a driver other than acpi.sys?

@Mov AX, 0xDEAD @Dietmar I just tried it with MSI Z590-A and GA-H470-HD3 boards: it works correctly. Thanks

I don't think that will solve the problem. Inside the acpi.sys file is the path to the pdb file which is certainly different from the one already present on my disk. So, changing the path to the folder on my disk to match the path within acpi.sys remains the easier way. I don't know if changing the hex values of acpi.sys can help.