Dietmar

@Andalu Make a new folder Symbols2 for your own files. Put it to W:\Symbols2 and put all your files there into. And then set on left side above in Windbg the path for everything also (via ; ) to W:\Symbols2 Dietmar Here is mine C:\symbolssss;C:\symbols;C:\symbolss;C:\symbolsss;E:\binaries.x86fre\Symbols;https://msdl.microsoft.com/download/symbols;srv*

@Damnation @daniel_k did this trick to fake OS version in acpi.sys. The last acpi.sys driver from @Outbreaker use this trick also Dietmar

@Andalu Which Lan card you bought for success? Dietmar

@Damnation Yepp, and you also have to grab a brandnew Win7 bit32 LAN driver for all the i219 variants and to check their dependencies also. And check dependencies from this win7 i219 bit32 driver in XP and also in win7. I think, when you check dependencies in Win7, at once you see, what have to be done at least Dietmar https://docs.microsoft.com/en-us/windows-hardware/drivers/network/overview-of-ndis-versions

@Damnation Because all tries to hack a driver for example from i211 to fake as i219 failed, I think, the problem is, that we have to change whole Ndis5 (XP) to Ndis6 (>XP) Dietmar PS: Yesterday I tried to hack again the Windbg driver for the i219 on the Asrock z370 gaming k6 board. On the i211 the hacked driver works also as original but on the i219, compi just restarts without any message. Here is my hacked and the original version kd_02Intelwin81 https://ufile.io/rw27ju7j

@Mov AX, 0xDEAD Are you now working on acpi.sys based on the Sources for win2003? When you have time for, I am very much interested in a driver for XP for the Intel i219 lan device. I would also do by myself but I dont know where to start Dietmar

@daniel_k I tried this already for the i219, does not work Dietmar

@Andalu I just test the V4 version. It has Dev_8161 and installs under XP SP3 only with the very last driver from Realtek from 2018. But it works also with Windbg over Lan, see photo from just now Dietmar PS: I disabled for this the i211 and the i219 lans in Bios of the z370 Asrock gaming k6 board. The V2 version has Dev_8168 , which is a much more common chip from Realtek. I would buy V2 version of tp-link TG-3468 . EDIT: Even from version v2 exists different cards. My has 2001500224 but now most v2 have 2001500217.

They are different. V2 Version has chip SG24701A V4 has chip LG2013D Dietmar

@Andalu This is a fake picture from Amazon, because they deleted the Versions number on it Dietmar

@Andalu I have 11 times this one https://www.amazon.de/-/en/TP-Link-TG-3468-2001500224-KB-6160-Gigabit/dp/B07H7PM1QQ It works on really every compi with an PCIe connector, even under Win98 Dietmar EDIT: There are different hardware versions of this Realtek device. I have V2. There exists V1, V2, V3, V4. I dont know anything about differences, for sure works very good V2.

@Mov AX, 0xDEAD Yes, I mean for my Intel Lan i219 Ven_8086&Dev_15B8 i211 Ven_8086&Dev_1539 Dietmar

@Mov AX, 0xDEAD Thanks for to make things clear. So, until now no "win10" debug of XP SP3 is possible on real compi. Not important, which kdnet10.dll you use (I mean from which version of Win10). The Asrock z370 with Intel Lan i211 and i219 reboots at once with the special kdstub.dll from project Dietmar

@Mov AX, 0xDEAD Has the patched kdnet.dll driver from win8.1 to stay together on Target compi with the win10 kdnet10.dll and also together with kdstub.dll from win8.1 Dietmar PS: I just see, that there is also a kdstub.dll from win10. But for "win10" Lan debug I should use all together kdnet.dll (via patch from win8.1) kdstub.dll (renamed from kd_02_8086.dll from win8.1) (from readme this kdstub.dll has to be taken from projekt) kdnet10.dll (renamed from kd_02_8086.dll from win10) When I use kdstub.dll from the Projekt (only about 3kB), the Target compi at once reboots when I enable debug.

@Andalu i211 works i219 not works, even I tested 3 different kdnet10.dll from 3 win10 bit32 for Intel Lan Debug Dietmar EDIT: I tested also the very first 1909 version von win10 bit from 2015. Microsoft writes, that Dev_15B8 is for my i219-v lan lan debug is supported. EDIT2: I disabled the i211 in Bios. So, only the i219-v stays. But also the switch in boot.ini for to force Windbg by Ven&Dev number, here /PCI_ID=808615B8 for the i219-v does not help. The i211 also does not work with the win10 file kdnet10.dll even I renamed kdnet.dll ---> kdORInet.dll. The i211 with Ven_8086&Dev_1539 is also supported on the Microsoft page for the Win10 1909. So the problem goes to win10^^.

@Andalu Can you please send me the kdnet10.dll file for Intel Debug, that @Mov AX, 0xDEAD send you? I quick set up a Debug session on the Asrock k6 board. It has i211 and i219 Intel lan i211 works for debug, I never tested the i219 Dietmar

@Andalu You can also do the following: Put a Realtek Lan card in an PCIe slot and use the kdstub.dll renamed kd_02_10ec.dll Realtek (v6.3.xxxx) ----> kdstub.dll (only renamed) @Mov AX, 0xDEAD writes, that for i219 you need both (kdstub.dll and kdnet10.dll) together in Windows\system32 on Guest (target).

@Andalu For the Intel Lan i219 on the Guest (Target) ONLY the file from @Mov AX, 0xDEAD from Win10 works. Windows 8.1 kdnet.dll patched via xdelta3.exe -v -f -d -s kdnet_orig.dll kdnet_delta.bin kdnet.dll And from Win10 kd_02_8086.dll ---> kdnet10.dll (only renamed) Dietmar PS: And disable in Device Manager for the Lan i219, even when there is no driver for it under XP.

@Andalu All looks ok. But you miss on the HOST system in Windows\system32 for XP SP3 the Vista msvcrt.dll from @blackwingcat . Replace the existing version of msvcrt.dll with the one from Blackwingcat Dietmar Here it is https://ufile.io/hkptb1hq

Here is the new acpi.sys v3, compiled from Sources for XP SP1 with the new patch v3 thanks to @Mov AX, 0xDEAD . It is the "free" version and I add also the for DDB Bsod binary hacked version, waiting for results from @Andalu Dietmar https://ufile.io/zdm97gg0 @pappyN4 Can you please test on the Gigabyte B450 Aorus M.

@Andalu What is the IP adress of the compi, where Windbg runs? (HOST) Check with ipconfig in commandline direct on this compi What is the IP adress of the compi, where Windbg NOT runs?(GUEST(or Target)) This has Intel LAN? Check with ipconfig in commandline direct on that compi. Write here the content of your boot.ini from the GUEST. Write here, what you write for Kernel Debug in Windbg (Portnumber, Key) on the HOST compi Dietmar PS: Please tell also, which files you put at which place. Can your 2 compis see each other?

@Andalu You need to run in cmd also ipconfig for to get the IP number of the other compi. And those two different IP numbers you put into boot.ini on the GUEST compi (NOT the compi where Windbg is running) Dietmar Debugfiles for Intel Lan https://ufile.io/qtcl0u1e

@WinWord2000 Yepp Dietmar

Does somebody know, how I can disable the Windowssearch in XP SP3? I want only the old one with the little dog Dietmar EDIT: I get rid of this Windowssearch via the following: First I delete whole folder in Registry HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP3\KB940157 and also HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\KB940157 From Microsoft Update catalog I fetch KB940157 https://www.catalog.update.microsoft.com/Search.aspx?q=KB940157 This is the "new" SEARCH, brr.. This I install. And after this, I delete "Windows Search 4.0" using Software in System uninstall Dietmar

@Andalu https://github.com/kbandla/installers/blob/master/windbg/8.1-update/X86 Debuggers And Tools-x86_en-us.msi Dietmar And here are the needed 2 modded files for windbg.exe https://ufile.io/u43tx3xz