I have done a test to check the behavior of the Paragon GPT Loader driver with the 2TB limit in an XP system configured in IDE mode.
After formatting my 4TB Seagate ST4000LM024 GPT disk in Win10, I started to fill it always in Win10 by copying in a progressive way the files numbered from 01 to 432 until to reach 2,194,897,825,792 bytes (at the end of the copy I made sure that all the files were uncorrupted):
After connecting the disk to the XP system with Paragon GPT Loader installed, I first verified again that all files were not corrupted and then copied a single file to the disk reaching a total of 2,199,889,600,512 bytes:
Checking once again the integrity of all files, I noticed that the first file copied a few days earlier (the one marked with the number 01) was now corrupt while all the others were intact. But on the next system reboot, here is what happened:
The problem encountered is almost the same as the one I detected using the asmedia asahci32.sys driver in a system configured in SATA/AHCI mode. The difference, which is no insignificant, is that at least with the asmedia driver, by following the identical procedure above, the drive was still accessible in XP and other files were still correctly available although the 2,199,023,255,552 bytes limit was exceeded.
At this point, I also have serious doubts whether the GPT Loader can effectively work on 3TB GPT disks. It certainly does not work on 4TB GPT disks.