Updated drivers for Windows XP SP3 and Windows 2003 SP2 (x32/x64) for modern hardware

[reboot12]

8 hours ago, K4sum1 said:

It would be cool to have a reg file to add it to the right click or shift + right click menu for increased efficiency.

No problem, copy setcsum.exe to WINDOWS folder then add registry settings:

Windows Registry Editor Version 5.00

; === EXE ===
[HKEY_CLASSES_ROOT\exefile\shell\setcsum]
@="setcsum"

[HKEY_CLASSES_ROOT\exefile\shell\setcsum\command]
@="cmd.exe /k setcsum.exe \"%1\""

; === DLL ===
[HKEY_CLASSES_ROOT\dllfile\shell\setcsum]
@="setcsum"

[HKEY_CLASSES_ROOT\dllfile\shell\setcsum\command]
@="cmd.exe /k setcsum.exe \"%1\""

; === SYS ===
[HKEY_CLASSES_ROOT\sysfile\shell\setcsum]
@="setcsum"

[HKEY_CLASSES_ROOT\sysfile\shell\setcsum\command]
@="cmd.exe /k setcsum.exe \"%1\""

[Dietmar]

I had no idea,

how I can test, if the kdnet.dll in the clothes of kdcom.dll for Lan-Windbg on XP bit64 is loaded or not.

Because when a degugger runs, no other can work at the same time in real life time situation.

So I come to the crazy idea, to use the capslock-LED on my keyboard.

And it works.

Here is small demonstration of ps2.exe

Dietmar

https://www.upload.ee/files/19348155/ps2.zip.html

[Dietmar]

@reboot12

I think, that now I am good enough to go away from @Mov AX, 0xDEAD

and build my own kdnet.dll from scratch for XP bit64 for Windbg.

And voila, this is the correct decision.

I already initialize my driver kdnet.dll, it starts and wants to get RX and send TX packages to Windbg.

The wlan 9560 driver was such a hard school, but for me very good

Dietmar

T66 K0 RETURN_SUCCESS + PCI SCAN
T66 PCI SCAN FOR 8086:1539
T66 FOUND I211
T66 BDF bus=0x0000000000000005 dev=0x0000000000000000 func=0x0000000000000000
T66 CFG00 vendor_device=0x0000000015398086
T66 CFG04 command_status=0x0000000000100007
T66 CFG08 class_rev=0x0000000002000003
T66 CFG0C bist_hdr_lat_cache=0x0000000000000010
T66 BAR0=0x00000000DF200000
T66 BAR1=0x0000000000000000
T66 BAR2=0x000000000000C001
T66 BAR3=0x00000000DF220000
T66 BAR4=0x0000000000000000
T66 BAR5=0x0000000000000000
T66 IRQPIN_LINE=0x000000000000010B

T66 SAVE

T66 TX
T66 TYPE=0x0000000000000003

T66 RX TIMEOUT

T66 RESTORE

T66 SAVE

T66 TX
T66 TYPE=0x0000000000000007

T66 RX TIMEOUT

T66 RX TIMEOUT

T66 RX TIMEOUT

 

[reboot12]

@Dietmar

Wow, your kdnet.dll work ???

I compiled kdnet_patch 64-bit, I patch kdnet.dll 8.1 but I didn't test it because it requires a boot.ini file and I can't use it on Dell in pure UEFI because I use a BCD file and I don't think it's possible to provide data for debugging there as in the boot.ini file

C:\WINDOWS="KDNET DHCP"        /noexecute=optin /fastdetect /DEBUG /DEBUGPORT=NET /HOST_IP=192.168.5.1 /HOST_PORT=50000 /ENCRYPTION_KEY=make.winxp.great.again /CPUFREQ=3000

You can test this but in Legacy (CSM) when you use boot.ini on other PC - not on Dell kdnet_patched.dll

But:

• this not work because no jump to merged code in kdnet.dll
• the code only searches for files - not patch

Edited May 16 by reboot12

[Dietmar]

@reboot12    Yessssssaaaa

[Dietmar]

@reboot12

Oha, yes, just now we need boot.ini

but the fun will go on

Dietmar

[Dietmar]

@reboot12

Have you tried csmwrap.efi on the Dell Wyse 5070?

I see, we have some work more to do

Dietmar

[Dietmar]

@reboot12

I just looked around, if there is another board with CNVi Wlan, and CSM, Gemini Chipset and the j4105 cpu.

I found 2.

Gigabyte J4105N H has this ans also CSM via manual, but I do not find any board

Asrock J4105-ITX  This is the crazy part. It has no CSM, but the Bios is nearly the same as on the N100.

So, already yesterday I modded the Bios from this board, to that now you have the CSM in Bios menu,

even I have not this board until now but in about a week I have

Dietmar

PS: I do not compile my KDNET.dll

 I build it in Assembler from scratch.

Edited May 16 by Dietmar

[Dietmar]

@reboot12

Before winload.exe comes BCD right even for Uefi boot?

There is also a Debug option in BCD.

So, I think my own build kdnet can load via this way also,

may be just small correction

Dietmar

[George King]

On 5/14/2026 at 2:09 AM, wyf180 said:

Could you share older version of ported drivers?I don't know why some drivers in v46 seem older then shown in 2023 and lack some drivers including vga driver?

https://forums.mydigitallife.net/threads/tool-xp2esd-create-modern-windows-xp-installer-v1-6-2.82935/page-134#post-1810919

Generic VGA driver was removed from reason, can consider adding it back in future, when I will play with drivers again.

Current pack is safe for every user and probably in any combination, including OS mix and drivers auto setup.

How do you find "Some drivers are older"?

[wyf180]

19 hours ago, George King said:

Generic VGA driver was removed from reason, can consider adding it back in future, when I will play with drivers again.

Current pack is safe for every user and probably in any combination, including OS mix and drivers auto setup.

How do you find "Some drivers are older"?

In 2023,you showed Generic_USBMassStorage and usb present 6.2.9200,but now they are only 6.1.7601.

[Dietmar]

@reboot12

I do not succeed with Lan-Windbg for 64bit, because I was not able to overcome the crazy encryption for Lan Debug with my own driver from scratch.

It connects to Windbg in bit64, but then tells: No authorisation, check your key..brrr.

At once I understand the hard way, that @Mov AX, 0xDEAD takes,

to use the original kdnet.dll files for win8.1. Because there, the correct encryption is into it.

I get really everything, pdb files for kdstub.dll and kdnet.dll for win8.1 in bit 32 and bit64.

I succeed to mod the files in ram exact as @Mov AX, 0xDEAD did,

so I really translate all(?) from his asm file to bit 64, also the Magic Numbers.

But my problem is then, that my i211 lan card is not found after and so no connection to Lan-windbg even all other works.

I can test with Putty via COM and see, that my patch works..nearly(?!) all.

 

But now comes the good news: I get the Asrock J4105-ITX board today.

And, voila, even no CSM, I can enable this bit with ru.efi.

This time I am lucky, that the Bios is not write protected.

CSM enable:

Variable: Setup
GUID: EC87D643-EBA4-4BB5-A1E5-3F3E36B20DA9
Offset: 0xB6
Byte: 00 -> 01
Bit: Bit 0 = 1

That all. I am on XP SP3 on this board now,

it has exact the same cpu J4105 and chipset Gemini as your Dell Wyse 5070.

In few min fun starts with the Wlan card 9560 there.

Now I have the full Windbg power there for to check what is going on

Dietmar

EDIT: This is the first time, that I am happy to get the Code 10 for the 9560 on this board also!

EDIT2: I switch all power on in Bios for the 9560 Wlan, but does not help.

Windbg shows, that the whole boot-path for this card does not start on the j4105 gemini chipset.

And this card is not a real pci device, just RF. The cpu does all the work for Wlan on this card.

Tomorow I make a full trace track with OpenBSD. This I have done a lot of times before and always understand,

what works and what not. Under Ubuntu the 9560 works on the gemini chipset, so there is hope.

 

Edited May 19 by Dietmar

[Dietmar]

@reboot12

Under OpenBSD the 9560 also not works.

Oh..this will be more work than I thought.

Dietmar

foo# ifconfig iwm0
iwm0: no such interface
 AC 9560" rev 0x03iwm0: can't map interrupt 

EDIT: I try to enable OS Linux in Bios via ru.efi

Setup: 0x4F1 = 03  (linux OS)

                                 <
 

Edited May 20 by Dietmar

[Dietmar]

@reboot12

I found out with Ubuntu, what is going on.

The Gemini chipset with 4105 uses another Firmware, vs 46.

My driver uses vs 77.

So, fun goes on, I just build new driver with Firmware 46

Dietmar

[Dietmar]

@reboot12

I install on the J4105 just now OpenBSD version 74.

There I install by hand the 9560 driver. Now it works there with firmware 46.

Now I hack if_iwm.c for to get all the traces in OpenBSD, what the 9560 is doing until connect.

Then I transfer this to XP SP3

Dietmar