I use pure serial, it's slower but working... Recent laptops are problematic for debuging XP boot process yes.
@George King I am afraid that KDNET - just like USB, does not support the boot debugging but only kernel debugging.
I once asked him the same thing and he wrote that he was not interested in the 64-bit version. Maybe he has free time now and would help.
Ok so I attempted to boot with the iso made for the surface pro 1 linked in techominus's youtube video. I followed every step carefully but I am running into a 0xc0000017 error upon booting and sometimes a 0xc000009a error instead. I have an AMD processor so could that be related to any memory fragmentation issues? Thanks.
I forgot to specify that one of the reasons why booting XP from UEFI Class 3 using Intel 8th core gen also works is because I have Acpiec set start to 0 (Boot). This is only recommended for modern hardware depending on ACPI (without Acpiec, XP can restart very fast on logon with modern hardware). For older hardware, Acpiec causes bugs (that's why Microsoft set the service to Disabled in XP).
@UsefulAGKHelper From my tests it comes out that the opposite is true - on new computers e.g. Coffe Lake, Haswell ACPIEC Start 4 and on old computers e.g. Core 2 Duo Start 0 I test install my xp64 on pure UEFI (CSM Disabled) and in CSM only on my Intel Gen 8 Coffee Lake and in both modes ACPIEC is Start 4 (Disabled) and OS work OK. Also tested xp32 in CSM Only and also ACPIEC Start is 4: P.S. Haswell is also modern PC and also ACPIEC Start 4: What HAL is in your XP64? In my installed OS is always: acpiapic_mp (ACPI Multiprocessor x64-based PC) - of course, on computers with multi-core (multi-threaded) CPUs P.S. I have one PC multi-core ThinkPad X61 Intel Core 2 Duo and my xp64 installer (and also original installer) set always ACPIEC Start 0