Jump to content

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


Recommended Posts


Posted (edited)

@Dietmar

Ahhh. I tried one more time dump and verify BIOS region on my DELL with FPT.efi and works OK. Previously, I did the incorrect verify:

dump.png

verify.png

Edited by reboot12
Posted

@reboot12

I make also an IRQ version of the XP SP3 driver for the Intel i225. It has very small ping <1ms to DHCP router.

But compared with the polling version from above it shows more spikes, when you transfer a big file (1.3 GB).

Now it is also stable.

I look intensive at the Linux operations at the i225, does not make it better at all.

So, this is near to the maximum what can be reached under XP SP3 for a driver for i225

Dietmar

https://www.upload.ee/files/19158148/i225IRQ8.zip.html

Posted (edited)
2 hours ago, Dietmar said:

Do you can see now CSM or with other name in Bios

But I didn't modify the bios. Normally you can only make a backup and flash of the 14.9 MB BIOS region:

fpt -bios -d BIOS_region.bin

Thanks to the Service Mode jumper, you can make a backup and flash of the full 16 MB BIOS (the entire SPI chip):

fpt -d full_SPI.bin

I wrote earlier that changing hidden BIOS options does not help and CSM does not work.

P.S. I still need to test different settings of the JMP2 jumper of the COM1 port - because now WinDbg does not work with the default setting:
JMP2-COM1.png

WinDbg require null-modem cable with bridge pin 1-6:
https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/setting-up-a-null-modem-cable-connection#null-modem-cable-wiring

Maybe this jumper block working WinDbg - I need test it.

EDITED
=====

I test all jumper combinations but not help. WinDbg not work because OS debug mode not boot and only black screen. This COM1 port is not useable to debug :(

Edited by reboot12
Posted

@reboot12

Dont worry.

We will mod the Bios of the Dell Wyse 5070 for CSM and then we can use Windbg via the Rj45 Realtek lan-connection

on XP Sp3 with the nice tool from @Mov AX, 0xDEAD.

I think, with some work we can also build our own tool for XP 64, that will do the same

Dietmar

Posted

@reboot12

Please post a photo of your Wlan card from the Wyse 5070 with

VEN_8086&DEV_31DC&SUBSYS_40308086&REV_03

because there exist a lot of different models, all with the same name

9560NGW

Dietmar

 

Posted (edited)
11 hours ago, Dietmar said:

I think, with some work we can also build our own tool for XP 64, that will do the same

Yea, I once asked @Mov AX, 0xDEAD about the 64-bit version LAN WinDbg and he said he was not interested :thumbdown Also someone create issue on github but not any reply:
https://github.com/MovAX0xDEAD/KDNET/issues/2

Long time ago I create also topic on WinCert forum but no anyone reply:
https://www.wincert.net/forum/topic/18512-kdnet-for-winxp2003-64-bit/

I compiled kdnet_patch.asm in FASM OK but this is probably 32-bit code (not 64-bit):
kdnet-FASM.png

64-bit tools for kdnet patch (checksum64.exe, chsize64.exe, xdelta3_64.exe) - https://www.upload.ee/files/19161602/64-bit_kdnet.zip.html

My WLAN card: dell-wlan.png

Edited by reboot12
Posted

@reboot12

I already succeed to build an 9560.sys, which  send packages via Wlan 9560 TX for both different divices

VEN_8086&DEV_31DC&SUBSYS_40308086&REV_03 yours is on Gemini board Dell Wyse 5070 VEN_8086&DEV_7AF0&SUBSYS_42348086&REV_11 mine name is on my Alderlake board Biostar z690A Valkyrie

Dietmar

Posted
1 hour ago, Dietmar said:

I make a try to convert whole @Mov AX, 0xDEAD for KDNET at git from XP bit32 ==> XP bit64

I try compile only KDNET_PATCH_X64_TEMPLATE.ASM in FASM assembler but this generate only 1 byte size .bin file :(

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...