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

[reboot12]

@Dietmar

WinDbg looks for symbols in several locations e.g. for .dll file:

DBGHELP: c:\symbols\halmacpi.pdb - file not found
DBGHELP: c:\symbols\dll\halmacpi.pdb - mismatched pdb
DBGHELP: c:\symbols\symbols\dll\halmacpi.pdb - file not found

• direct in c:\symbols
• in subdirectory c:\symbols\dll - found but mismatched because I use modded hal.dll
• in subdirectory c:\symbols\symbols\dll

I tried install symbols in c:\symbols\symbols but then WinDbg search files in subdirectory: c:\symbols\symbols\symbols\

I think I'm doing well now. You need to install symbols such as the system you are debugging, so if the SP2 system is the symbols for SP2, if the SP3 system is the symbols for SP3, etc.

[Dietmar]

Hi,

I just test my last versions of i219 and RTL8125 on the Asrock z690 Extreme board with 12900k cpu.

And voila, here they work both. The RTL8125 is a Dragon RTL8125BG chip, while on the Gigabyte z690 UD DDR4 the

RTL8125 chip was a version RTL8125A, so this driver seems to be really generic

Dietmar

Edited February 24 by Dietmar

[reboot12]

@Dietmar

I had exactly same problem (0 sent / 0 received) with other integrated NIC 1 Gb card Realtek Dev 8168 on Dell Wyse 5070 (GeminiLake CPU) when I using old driver 5.824.0107.2014
https://forums.mydigitallife.net/threads/winxp-64-bit-on-a-modern-pc-iso-boot-wim-install-wim.88435/page-9#post-1884898

Realtek LAN VEN_10EC&DEV_8168 not work. The driver is installed correctly, detects a connected/disconnected network cable but there is no IP configuration from DHCP or static does not work. Something is wrong - I don't know what yet.

To solve the problem, it was enough to change the driver to the newer 5.836.125.2018
https://forums.mydigitallife.net/threads/winxp-64-bit-on-a-modern-pc-iso-boot-wim-install-wim.88435/page-9#post-1885400

I wanted to see the differences in WinDbg, but unfortunately, even though I have a COM port in Dell Wyse, debugging does not work

Edited February 24 by reboot12

[Dietmar]

@reboot12

When you send me the test results for XP SP3 for i219-LM with the commands for Windbg which I give to you,

there is a chance that I can figure out what happens

Dietmar

[Dietmar]

@reboot12

What is the name of your board with the i219-LM lan and which Bios Version you have on it?

May be I have or some very similar

Dietmar

[reboot12]

@Dietmar

OK, I make WinDbg commands: https://www.upload.ee/files/19105963/i219_kd_09d8_2026-02-24_12-25-59-595.log.html

My motherboard is industrial Advantech AIMB-786 REV:A1 19A1078602-01, BIOS AMI UEFI V5.00

Edited February 24 by reboot12

[Dietmar]

@reboot12

I found this in your comments about the not working DHCP router:

"I'm not sure but I also changed the various settings on the Advanced tab and I unchecked Allow the computer to turn off this device to save power on Power Management tab:"

I am quite sure, that this enabled "Power Saving" is the reason for no send no get

Dietmar

[reboot12]

1 minute ago, Dietmar said:

I am quite sure, that this enabled "Power Saving" is the reason for no send no get

But in your drivers no Power Management Tab for change settings

[Dietmar]

@reboot12

Yes. But your board is a very expensive Industrial motherboard and so, they can set this Power Saving everywhere enabled as standard.

You can make an easy test: Take your Wise board with the not working lan driver and DISABLE there the Power Saving function,

voila

Dietmar

[Dietmar]

@reboot12

Try this and send me result

Dietmar

.logopen /t c:\i219_kollege_kd.log
!sym noisy
.reload /f
lm m i219
lm m ndis
x i219!*LowPower*
x i219!*Ulp*
x i219!*Link*
x i219!*Media*
x i219!*Oid*
x i219!*PacketFilter*
x i219!*Send*
x i219!*Rx*
x i219!*Interrupt*

bc *
bu i219!I219MiniportInitialize ".echo I219MiniportInitialize; r; gc"
bu i219!I219LowPowerExitFixup ".echo I219LowPowerExitFixup; r; gc"
bu i219!I219DisableUlpPhy ".echo I219DisableUlpPhy; r; gc"
bu i219!I219LinkFromStatus ".echo I219LinkFromStatus; r; gc"
bu i219!I219IndicateMediaState ".echo I219IndicateMediaState; r; gc"
bu i219!I219SetPacketFilter ".echo I219SetPacketFilter; r; gc"
bu i219!I219OidQueryInfo ".printf \"OIDQ  OID=%08x Len=%u\\n\", poi(@esp+8), poi(@esp+0x10); gc"
bu i219!I219OidSetInfo   ".printf \"OIDS  OID=%08x Len=%u\\n\", poi(@esp+8), poi(@esp+0x10); gc"

x NDIS!*IndicateStatus*
bu NDIS!ndisMIndicateStatus ".printf \"ndisMIndicateStatus GS=%08x Size=%u\\n\", poi(@esp+8), poi(@esp+0x10); gc"
bu NDIS!ndisMIndicateStatusComplete ".echo ndisMIndicateStatusComplete; gc"

x NDIS!NdisMMapIoSpace
bp NDIS!NdisMMapIoSpace "r $t0=poi(@esp+4); gu; .printf \"MMIO=%p\\n\", poi($t0); gc"

g

 

[reboot12]

@Dietmar

https://www.upload.ee/files/19106032/i219_kollege_kd_0b1c_2026-02-24_12-58-28-751.log.html

13 minutes ago, Dietmar said:

You can make an easy test: Take your Wise board with the not working lan driver and DISABLE there the Power Saving function,

Where I need disable this ???

[Dietmar]

@reboot12

On the settings of this Realtek 8168 driver you told in the chat, that you uncheck the mark for Power Saving on

Dietmar

[reboot12]

6 minutes ago, Dietmar said:

On the settings of this Realtek 8168 driver you told in the chat, that you uncheck the mark for Power Saving on

No, network work OK even if option power save is select:

[Dietmar]

@reboot12

I mean the "notworking older driver" for this Wise with realtek 8168. Uncheck there the mark for "Power Saving" and take a look what happens

Dietmar

[Dietmar]

@reboot12

Here are next steps for Windbg

Dietmar

bc *
bu i219!I219LinkFromStatus ".echo I219LinkFromStatus; gc"
bu i219!I219IndicateMediaState ".echo I219IndicateMediaState; gc"
bu NDIS!ndisMIndicateStatus ".printf \"ndisMIndicateStatus GS=%08x Size=%u\n\", poi(@esp+8), poi(@esp+0x10); gc"
bu NDIS!ndisMIndicateStatusComplete ".echo ndisMIndicateStatusComplete; gc"
g