Andalu

Here are the two lines of text containing the generic hardware ID for a sata/ahci disk controller: a) %PCI\CC_010601.DeviceDesc%=variable, PCI\CC_010601 b) PCI\CC_010601.DeviceDesc ="variable" In both lines of text, the term "variable" should be changed following the information about the other Hardware IDs already listed.

There would be two alternative ways that do not involve the use of an Asmedia eSATA PCIEx card: 1. since there is more than one version of the ASMedia sata driver that allows GPT disk recognition even with some non-ASMedia controllers, you could try installing the ASMedia driver v2.0.3.1 or earlier versions for your Silicon Image card; 2. already reported here: https://msfn.org/board/topic/181911-read-gpt-hard-disk-on-windows-xp/?do=findComment&comment=1258361 In both cases, the .inf file needs to be edited by adding the usual two text lines for recogniton of a generic disk drive. If you want to give it a try, it is a good idea to first save an image of the system disk to restore in case it becomes unbootable. Most important: try it at your own risk

Hi, I do not believe that the missing Core Storage Volumes Driver (csvol.sys) can result in the GPT disk not being recognized. The Paragon driver that should enable GPT disk recognition is "gpt_loader.sys" which has no correlation with the csvol.sys driver as can be seen from the following image (where csvol.sys is not listed under 'Module' section): The failure to start the Core Storage Volumes Driver due to the error related to missing file most likely relates to missing "cng.sys": I could not find the version of the cng.sys driver for XP, and in any case, even if you added the Win10 or Win7 version of the cng.sys file to the Paragon HFS+ program, the Core Storage Volumes Driver itself would still not work in XP since many essential functions are missing for ntoskrnl.exe (currently not even covered by the ntoskrn8.sys Emu_Extender): Regarding the GPT disk listed in XP's Device Manager but not in Disk Management is a situation that always occurs when a GPT disk is not recognized. Below is an example with a 4TB Seagate GPT disk: 1. disk connected to a USB3 port via sata adapter or with a USB enclosure: 2. same disk connected to the external eSATA port of a ASMedia PCI Express to eSATA card:

@Dave-H I don't know if there are any ASM1061 cards in a different format than PCI-Express. Regarding the driver for the ASMedia card, the oldest version that can be found on the net seems to be 1.1.7.110 for which the accompanying 'readme.txt' file clearly reports that Win98 is not supported. So that solution can't be applied. You reported that the 3TB GPT disk is correctly recognized in XP by connecting it directly to a sata port on the motherboard (sata cable to sata port). So what @jaclaz suggested seems to be the best solution: a bracket with an external eSATA port connected internally to the motherboard with a sata cable. This way you could connect your 3.5" HDD box with the eSATA cable to the eSATA port on the bracket without involving the Silicon Image card. Is this a practicable solution? Or have I misunderstood or skipped some steps?

@Dave-H Hi, to have the external 3TB GPT data disk recognized via eSATA connection, if your motherboard has a free PCI Express slot, you can try a PCIEx to eSATA card equipped with the ASMedia 1061 chipset. About the driver for this card you can download the Asmedia ASM-106x Sata controller driver package v3.3.2 or v3.3.3 and install the asahci32.sys v3.2.0 (both packages contain the identical version 3.2.0) from the "scsi" folder without doing any modifications for the .sys and .inf files. In my system, in addition to this driver I used the disk.sys v5.2.3790.4006 and partmgr.sys v5.2.3790.4171 from Win2003, and scsiport.sys v5.1.2600.6073. The Paragon GPT driver is no longer needed. Here is an image of my 8TB GPT data disk connected as an external drive to the eSATA port of the ASM1061 card: On the first boot (and probably on every reboot) with the GPT disk connected, the "File System Check" screen for the GPT disk may appear. I preferred to disable permanently this check for the GPT drive (and also for all drives) by modifying the value "BootExecute" under the key "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager". In addition to the above, there is also an alternative way in case you have an intel board. Below an image: This time to get GPT disk recognition you need the driver asahci32.sys v2.0.3.1 and a small modification to the .inf file (I think no hint is needed for it :)). In your case, no longer need for PCIEx card. A simple bracket with an eSATA port as has already been suggested to you is enough, and most likely, again, the eSATA connection should work as intended for your external GPT disk. Obviously, a GPT data disk can be also used as internal drive connected to a free sata port.

Thanks for the link even though the version that will be downloaded is 16.21 and not v16.22. The v16.22 can be found here: https://www.filehorse.com/download-process-explorer/37741/ I have tried the various versions and the only one in the 16.xx series that does not attempt to connect to the internet is indeed v16.22. Attempts to connect start occurring from v16.10, until v15.40 I have not detected any.

Please keep in mind that this version will definitely have a few less features than the newer ones. However, at least it does not attempt to "phone home"

As much as possible, I try to avoid those programs that arbitrarily try to connect to servers. In any case, all the programs running on my pc are monitored (not only with the firewall) and have rules in order to run. The only missing monitoring tool is the antivirus, uninstalled since 2008 and no longer used not even for on-demand scans :)

@AstroSkipper Thanks for the link Even with v16.26 I detected connection attempts to the following IPs: 2.21.14.112 2.23.155.162 2.21.14.97 195.22.200.40 2.23.155.136 195.22.200.33 92.122.251.85 192.229.221.95 23.59.69.139 104.18.15.101 104.18.14.101 With this version the IPs that Process Explorer v16.26 attempts to connect to when it starts are 11, 3 more than version 16.32 I do not like this behavior. I will continue to use v15.11, which I also prefer for cosmetic reasons

Already only because of attempts to connect to IPs 95.101.114.48, 95.101.114.196, 23.220.255.25, 23.220.255.21, 23.59.69.139, 192.229.221.95, 104.18.15.101 and 104.18.14.101 performed by Process Explorer v16.32 when it started (and without any possibility of disabling them via a program option), I would discard such version. I would also like to try version 16.26, but it is no longer available for download.

@TheFighterJetDude here the USB function just lost for some HID devices: in this case, the system hangs always also on shutdown.

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: