Andalu

@Dietmar It doesn't work. Just a note for clarification that my disk drive with the host system configuration is the same one that worked for debugging eight months ago. I kept that drive intact precisely so as not to repeat the procedure from the beginning. At that time I no longer had the error of the symbols not found.

@Mov AX, 0xDEAD @Dietmar please let me know what is wrong or what is missing in my configuration: Target system (here with the letter D: because the boot was executed from another system disk): Host system (the log continues by giving the input "g" but the result is the same as in my previous post):

@Mov AX, 0xDEAD Here is the log related to debugging by choosing the "KDNET Checked" option in boot.ini after replacing the free acpi.sys and acpi.pdb files with the debug version (SHA-1: DE3B6993BBAADEE0F875DD234BBC65C87E9ACA52 and 2F62065C1520EF31246BEFDF133650B605A17AE0). The configurations of the target and host systems are the same. I do not understand the reason for the error regarding symbols not found if nothing has changed from the "KDNET FREE" option (except the version of acpi.sys and acpi.pdb).

Hi, If I have not misinterpreted what is reported in the debug log, it seems that in acpiV6 (SHA-1. 4D8A256457B6D3F5E2FB3E6574DA5A1446BF68F5) the AMLILoadDDB patch is missing:

@Dietmar It has been eight months since I last debugged and it is difficult to remember the whole procedure in a short time. I will look for the way on how to do it as soon as possible.

@Mov AX, 0xDEAD @Dietmar Thanks for the compiled acpi.sys v6. It works on the asus Q370 but does not work with the GA-H470 HD3 and the MSI Z590-A with BSOD A5 (0x11,0x08,....,....) both for installing XP and replacing the existing working version.

@Comos As an alternative to the Hitachi microdrive you could try Diskmod. The link is this one: http://reboot.pro/topic/9461-page-file-in-usb-hard-disk/?hl=diskmod although it seems unreachable at the moment. The initial page of the topic can be viewed here: https://web.archive.org/web/20210624032336/http://reboot.pro/topic/9461-page-file-in-usb-hard-disk/?hl=diskmod The download also does not seem to be working. However, the direct download link is here: hXXp://www.techportal.it/dl/diskmod.zip

I just installed the Silicon Motion Generic_NVMe_10.4.49.0 driver in XP x64 and have not encountered any problems. TRIM with O&O works as well: Same for the Samsung 3.3.0 driver here "orphaned" by secnvmeF.sys: In both cases, no services refer to secnvmeF.sys. It could also be that the BSOD 7B may have occurred if you have installed the SiliconMotion driver by replacing the Samsung one. Eventually it is so, to avoid such error, before you uninstall the samsung NVMe driver or install a different one over it, remove in the registry the string "LowerFilters"="secnvmeF" from the key "HKLM\SYSTEM\CurrentControlSet\Class\{4D36E967-E325-11CE-BFC1-08002BE10318}" and then reboot the system. I wonder if secnvmeF.sys is really necessary.

@reboot12 I have executed TrimCheck twice even though there are three images I posted. The second one (running trim) is just to show the scroll bar of O&O and Naraeon indicating that trim is running. Regarding the Samsung v3.3.0.2003 driver, I thought you were using a non-Samsung model.

Still according to what is reported by TrimCheck, the Naraeon tool appears to perform trim for NVMe drives as well. Tested with MS and Samsung drivers. Below are images with the Samsung driver (here working even without secnvmeF.sys): before trim: running trim: after trim: I have not yet verified what the "semi-automatic trim" option consists of.

@reboot12 Regarding the Samsung NVMe 3.3.0.2003 driver, the secnvme.inf file must be modified to recognize non-Samsung generic NVMe drives. The Generic NVMe 10.4.49.0 driver works correctly on XP 32 bit. I have never tried the x64 version.

@reboot12 @George King It also depends on the NVMe drivers and the drive model. I have tried O&O Defrag for all my NVMe drives (Samsung, WD, Crucial, Sabrent) and the trim icon becomes available for all of them only with MS and Samsung drivers (note that the latter sometimes gives an error at system shutdown). Only for the Samsung 970Evo the trim is enabled in O&O with all NVMe drivers.

According to what is reported by TrimCheck, O&O Defrag v17.5.559 seems to perform the trim in XP also for the NVMe drives: before trim: running trim: after trim:

There is also a version of CFF Explorer with a bug already fixed: https://lifeinhex.com/cff-bug-in-rva2offset/

After the GPT to MBR conversion the disk is still recognized only when connected as a USB3 device: It is not detected when connected as a sata disk.

Hi, I restored an old USB 3.0 External HDD enclosure with ASM1051 chipset. By using disk.sys and partmgr.sys from Win2003, it correctly recognizes a Seagate ST4000LM024 as GPT disk: As shown in the image, it is listed as a local disk in Windows Explorer and Disk Management and not as a removable device, although in the systray it can be safely removed. It is no longer detected when connected as a sata disk, despite the Paragon GPT loader.

@jaclaz thanks for the links, I was not aware of these possibilities. There is always something new to learn. However, I was referring to the software shown in the image (PClinq5) that does not allow data exchange between Windows and Android.

Below is a screenshot related to PC-to-PC data transfer in XP using a USB3 bridge cable: Unfortunately, the software does not transfer data from PC to Android.

@jaclaz freeldr displays the message "cannot load boot driver system32\drivers\firadisk.sys!" when the firadisk.sys file is no longer found in the system32\drivers folder even though references to it are still present in the registry. I have noticed this behavior by moving firadisk.sys from the system32/drivers folder to system32 without first uninstalling it in Device Manager and without editing the registry to delete its references (in any case some of them cannot be removed in the normal way because blocked by the system).

@jaclaz at the end of the XP installation, one of the first things I do is uninstall the firadisk driver from the hidden devices and delete its file from the system32\drivers folder to avoid any conflict with other drivers. I did not expect that message to appear with freeldr, which does not appear with ntldr, although the registry is the same.

@Dietmar I did a partition clone from the working NVme drive under freeldr (970Evo) to the non-working NVMe drive (970evo plus) and now the latter also boots via freeldr. I still don't know the reason for the non-working drive by applying the same copy method that worked for 4 other NVMe drives and 3 SSDs. I also noticed that when deleting the firadisk.sys file, booting via freeldr displays the message "cannot load boot driver system32\drivers\firadisk.sys!" even though booting then proceeds normally. I add more notes regarding the NVMe drivers used during my tests on the MSI Z590-A board: OFA drivers v1.3 and v1.5 sometimes fail to boot via freeldr (in most cases) and ntldr (fewer times) giving bsod D1 for nvme.sys. On the times when booting works, the bsod often occurs at shutdown. Both versions of the OFA driver give the above D1 bsod already during GUI mode on the first attempt to install XP. The MS and Silicon Motion drivers work in both modes.

I did some tests with NVMe drivers to check how well the copy procedure worked to get XP booting via freeldr. I completed five fresh installations of XP from Ramsey using four different drivers and five different NVMe devices. The copy procedure worked in four out of five NVMe devices tested. The only failed attempt was on a samsung 970 Evo Plus with the MS NVMe v2.0 driver. I tried 4 times without success. The strangest thing is that booting worked fine on a samsung 970 Evo using the same MS NVMe v2.0 driver. I have also noticed other things, but I think the one above is the strangest.

@Dietmar I just tried your method on a not-working XP via freeldr and it now works!!

@Dietmar I cloned the 128GB SSD partition containing XP which boots via freeldr on a 256GB SSD also having two existing partitions, not the entire disk, just the system partition, leaving the size of the target partition unchanged (although the difference between the 2 partitions is minimal, less than 1GB). After removing the MountedDevices key and re-installing grub, XP boots smoothly via freeldr even in this case. Later I will post some images.

@Dietmar Not much to add, I simply used an SSD with two already existing partitions. During TXT mode, once I selected the partition where to install XP, I chose to format it in NTFS (quick mode). TXT and GUI modes were completed without any problems. On the first boot, I removed the MountedDevices key from the registry and installed grub. Rebooting XP again via ntldr, I verified that the MountedDevices key had been recreated correctly (it now had two \DosDevices\ entries). Rebooting the system via freeldr, XP also booted correctly in this way. Edited to correct numerous spelling errors, sorry.