Andalu

@Dietmar to bypass that problem, I chosen to use a ramdisk (W:\ drive) with the option 'save on shutdown' disabled. I copied on it only the Windbg and the symbols folders which are re-created on each reboot.

@Mov AX, 0xDEAD @Dietmar @Damnation first of all, thank you so much for supporting me Here an image from my last attempt when I included all files in one folder only: https://anonfiles.com/l9r4i0Zcx5/Debug_png P.S.: I'm using the same HOST and TARGET systems as before. I don't know for where the "TerminalServer SingleUserTS" comes from.

@Mov AX, 0xDEAD here the option from the boot.ini that I'm using: C:\WINDOWS="KDNET FREE" /noexecute=optin /fastdetect /DEBUG /DEBUGPORT=NET /HOST_IP=192.168.1.1 /HOST_PORT=50000 /ENCRYPTION_KEY=1.2.3.4 /CPUFREQ=3300 /TARGET_IP=192.168.1.3 /BREAK /ONECPU For compiled acpi.pdb do you mean the version you sent me (that's what I did by copying it in the folder c:\nt\base\busdrv\acpi\driver\nt\obj\i386\)? Or I need to re-compile it? The associated acpi.sys (451.968 byte) where needs to be copied?

@Damnation here the image: https://anonfiles.com/B9Reg4Zbxc/Symbols_folder_png

@Damnation the symbols path is on the host system where the WinDBG process runs. I just uploaded the logfile.

@Mov AX, 0xDEAD I followed your instructions but I still got errors. I have to figure out how to set the correct symbols paths and where other files type (*.exe, *.sys) need to be copied. Here the log containing the errors: https://anonfiles.com/bem2gfZ1x8/H470_txt I tried to copy acpi.pdb in the compiled folder (in my case c:\nt\base\busdrv\acpi\driver\nt\obj\i386\ created from scratch) and also in the symbols path (in my case W:\Symbols1\sys folder, replacing the existing acpi.pdb) but the errors are still there. Thanks.

Thanks for your help. I still need to understand the right place for these files. Windbg.exe continues to give me error for ntkrpamp.exe.

@Dietmar it is the model I had posted here, one of the few realtek cards that could be delivered in a short time.

Finally I can see the "Kernel Debugger connection established" message for my host (with intel i217 chipset) and target (with realtek 8111GS chipset) systems. I now need info for a correct configuration for the installed symbols to overcome the errors reported in the following log: https://anonfiles.com/R1IcR5Ybx6/Debug_GA-H470_TXT

@Damnation shipping much faster up on Amazon than on ebay and return possibilities within 14 days (even without motivating) with pick up of the product at home.

No problem. I prefer not to resort to P2P. Despite having 2 licenses for Win10 I have at the same time a complete refusal for this OS that I never really used.

@Dietmar it's hard to find on amazon.it (I prefer it for the fast shipping) a card with the SG24701A chipset as for the LG2013D. @Damnation This card has the RTL8111G (without the final "R") chipset but I don't know if it can be the right card. RTL8111GR seems to be present on motherboards only. My research continues.

@Dietmar @Damnation thanks, I will search for a model that has one of the two recommended chipsets

@Dietmar there are the same images on the tp-link site

@Dietmar it is no longer available on amazon.de and amazon.it. I have to looking for an alternative model. Edit: this seems be the same model

Can I get that library only after a win10 update? Whenever I have to use and even worse, connect to the network with that operating system I get urticaria.

@Dietmar which Realtek chipset must have the PCI Express LAN card to make sure I can get debug in XP?

@Dietmar both kdstub.dll and kdnet10.dll are already in the system32 folder on the target system. I don't have a realtek card now to test. I'll buy it in the next days.... I won't give up! Edit: I'll try in the next days starting from scratch once again. Thank you so much @Dietmar for your help Have a good night.

I had already obtained the patched files from the @Mov AX, 0xDEAD guide on github. Both files (kdnet.dll and kdstub.net) have the same SHA-1 of the versions that @Mov AX, 0xDEAD sent me. The only difference is for the kdnet10.dll: the version from Mov,Ax has a size of 219.960 byte, "mine" has a size of 142.656 byte (kd_02_8086.dll renamed in kdnet10.dll for the intel controller, if I correctly remember). I never used "my" version in any attempt...... edit: and I had done right not using "my" version....nothing changed with it, still no debugging

@Dietmar thanks for the tips about the LAN. I installed XP from scratch with the acpiv3DDBhack driver: no issues. Tried also to restart 4 times without any problems. I'm going to prepare another ISO with acpi.sys without hack. Edit: the XP installation with acpi.sys from acpiFREEv3 package stops with the A5 bsod (0x11, 0x08, 0xF6DA2000, 0x20160527)

@Dietmar about the last acpiFREEv3, in my first attempt I simply replaced the driver on the XP working disk: acpi.sys: A5 bsod (0x11, 0x08, 0xB99AD000, 0x20160527) acpiv3DDBhack: worked 3 times on 4 attempts. It failed one time blocking on the XP logo screen with the scroll bar that flows infinitely. I need some time to prepare the XP ISO to try the installation from scratch Thanks for the msvcrt.dll. I'll try with it.

@Dietmar on the target (guest) system the ethernet controller is the intel i219. Since there is no XP driver for it, there is no LAN and I can't set any IP. The ipconfig command doesn't give any IP address. The only way to set it is throught the bios as I already done (192.168.1.3). Here the boot.ini file on target (guest) that hangs the system: [boot loader] timeout=12 default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect /KERNEL=ntos3.exe /HAL=hal3.dll multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows XP SP3 DEBUG" /KERNEL=ntos3.exe /HAL=hal3.dll /DEBUG /DEBUGPORT=NET /HOST_IP=192.168.1.1 /HOST_PORT=50000 /ENCRYPTION_KEY=1.2.3.4 /CPUFREQ=3300 /TARGET_IP=192.168.1.3 /BREAK Here the boot.ini that doesn't give errors or results: [boot loader] timeout=12 default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect C:\WINDOWS="KDNET FREE" /noexecute=optin /fastdetect /DEBUG /DEBUGPORT=NET /HOST_IP=192.168.1.1 /HOST_PORT=50000 /ENCRYPTION_KEY=1.2.3.4 /CPUFREQ=3300 /TARGET_IP=192.168.1.3 C:\WINDOWS="KDNET Checked" /noexecute=optin /fastdetect /KERNEL=ntos3.exe /HAL=hal3.dll /DEBUG /DEBUGPORT=NET /HOST_IP=192.168.1.1 /HOST_PORT=50000 /ENCRYPTION_KEY=1.2.3.4 /CPUFREQ=3300 /TARGET_IP=192.168.1.3 /BREAK For the "kernel debug" option in WinDBG launched on host, the window displayed already contains the port number (50000) for the "NET" tab. I have to write only the secret key (1.2.3.4). This is what I done for target (guest) and host systems: Host: - installed 'NET Framework 4.0 for Windows XP 32-bit'; - installed 'WindowsXP-KB936929-SP3-x86-DEBUG-symbols-full-ENU-DEBUG' (I had already installed also 'WindowsXP-KB936929-SP3-x86-DEBUG-symbols-update-ENU-DEBUG', I don't know if it is correct), - installed 'x86 Debuggers and Tools-x86_en-us (v6.3.9600.17200)', replacing windbg.exe and dbgeng.dll with patched versions you uploaded. Target (guest): - Boot.ini as above; - Hal3.dll, ntos3.exe, kdnet.dll and kdstub.dll copied in the system32 folder. I also tried with kdnet.dll, kdstub.dll and kdnet10.dll sent me from @Mov AX, 0xDEAD some days ago. I'll try now the last acpi.sys. Edit: both host (msi Q87) and target (GA-H470) have an intel ethernet controller (i217 and i219)

@pappyN4 glad to see you here

@Dietmar after the IP configuration in bios, now WinDBG (from the host system) gives this error never seen before during the debugging attempts: https://pasteboard.co/2JYpHDvVOs9n.png At same time, the target system (GA-H470) hangs as soon as the option "Windows XP SP3 DEBUG [debugger enabled]" is selected in the boot.ini The other boot.ini with the "KDNET" references doesn't give any result (and error).

@Dietmar thanks for your help ;). WinDBG now works but however I'm not able to get debug in my system. I had already tried in Win8.1 thanks to @Mov AX, 0xDEAD. Same situation in XP on an haswell board that I used to install the driver for the intel i217 controller. Here my network configuration: https://pasteboard.co/tzMSZwXIBJIV.png Boot.ini edited as from your instructions. Hal3.dll and ntos3.exe copied in the windows\system32 folder together the minidriver. No debugging when the 'target' machine starts, the system reboots automatically.