reboot12

I tried another 6.3.9600.17238.winblue_gdr.140723-2018_amd64fre_client-core_retail_en-us-IR4_CCRA_X64FRE_EN-US_DV9.iso image and again the kd files have version 6.3.9600.16384 except the kd_02_8086.dll - this one has version 6.3.9600.16442

Nooo, this is not mistake. All files except Intel .dll has version 16384 https://www.upload.ee/files/19165674/kd81x64_KB3000850.zip.html F..k, I downloaded 6.3.9600.17415.winblue_r4.141028-1500_amd64fre_client-professional_core_retail.iso but file kdnet.dll in boot.wim\install.wim still only 6.3.9600.16384 Where can I get version 17276 ??? I think I'm giving up on trying to make a 64-bit version of KDNET - I don't know how to correct the KDNET_PATCH.ASM file for 64-bit anyway. Moreover, I think that the .ASM file contains offsets strictly related only to the 32-bit kdnet.dll file and for the 64-bit version it probably needs to be corrected accordingly.

@Mov AX, 0xDEAD writes in the readme that the driver files can be any 6.3.xxxx but the kdnet.dll file must be exactly 17276. I found only 16384 version files in this update Update for Windows 8.1 for x64-based Systems (KB3000850) in Windows8.1-KB3000850-x64.msu file - all files have version 16384 date 2013-08-22 except kd_02_8086.dll which has version 17276 date 2014-08-08 2013-08-22 13:39 87 904 kdnet.dll 6.3.9600.16384 2013-08-22 13:39 14 176 kdstub.dll 6.3.9600.16384 2013-08-22 13:39 28 512 kd_02_10df.dll 6.3.9600.16384 2013-08-22 13:39 308 064 kd_02_10ec.dll 6.3.9600.16384 2013-08-22 13:39 110 944 kd_02_14e4.dll 6.3.9600.16384 2013-08-22 13:39 33 632 kd_02_15b3.dll 6.3.9600.16384 2013-08-22 13:39 37 728 kd_02_1969.dll 6.3.9600.16384 2013-08-22 13:39 28 512 kd_02_19a2.dll 6.3.9600.16384 2014-08-08 17:55 172 344 kd_02_8086.dll 6.3.9600.17276 Interestingly, all these files are located in a folder called ...transport-network...6.3.9600.17276... I check also files Windows8.1-KB3003057-x64.msu & Windows8.1-KB3014442-x64.msu but no any kd*.dll files

What version is this? Write exactly the full name of the ISO file, system name (RTM or Update), where you downloaded it - maybe there is also a link to the 64-bit version? P.S. I don't understand why there is no such version on BetaWiki or in the BetaArchive Database EDITED I found info on https://ultradefinitive-build-list.fandom.com/wiki/OSes/Windows/8.1 winblue_r2.140808-0433 > Win8.1 Update 2 Post-RTM What KBxxxx update are the files 17276 in this version???

You compiled only 64-bit kdstub.dll for kernel 6.1 (Win7): I read this tutorial: https://github.com/MovAX0xDEAD/KDNET/blob/master/README.md I want to use drivers with Win 8.1, so I want use OPTION A Option A: Original files from Windows 8.1 (boot.wim/install.wim or KB3000850, only kdnet.dll version 6.3.9600.17276 ENGLISH supported) What version of Win 8.1 are these files? Where to download it, because I don't have it - please give me the link. If anyone has 64-bit Win 8.1 6.3.9600.17276, please unpack these files and share: kdnet.dll kd_02_14e4.dll` - Broadcom (v6.3.xxxx) kd_02_10df.dll` - Emulex (v6.3.xxxx) kd_02_19a2.dll` - Emulex (v6.3.xxxx) kd_02_8086.dll` - Intel (v6.3.xxxx) kd_02_1969.dll` - Qualcomm Atheros (v6.3.xxxx) kd_02_10ec.dll` - Realtek (v6.3.xxxx) kd_02_15B3.dll` - Mellanox (v6.3.xxxx) I searched the BetaArchive Database for 6.3.9600.17xxx and there are no such versions According to https://betawiki.net/wiki/Windows_8.1 there was no such version: Update 1 Available build 9600.17031.winblue_gdr.140221-1952 Update 2 Available build 9600.17238.winblue_gdr.140723-2018 Update 3 Available build 9600.17415.winblue_r4.141028-1500 Available build 9600.18009.winblue_ltsb.150810-0600 I downloaded and unpacked also 3 files from Update for Windows 8.1 for x64-based Systems (KB3000850) but no any kd*.dll files Windows8.1-KB3000850-x64.msu Windows8.1-KB3003057-x64.msu Windows8.1-KB3014442-x64.msu How to create a patched 64-bit kdnet.dll file??? https://github.com/MovAX0xDEAD/KDNET/blob/master/src/fasm patch/_merge.cmd Patch kdnet.dll 32-bit version: chsize32.exe kdnet.dll 76432 fasm KDNET_PATCH.ASM KDNET.BIN copy /B /Y kdnet.dll+KDNET.BIN+dummy kdnet.dllnew del /Q kdnet.dll_old ren kdnet.dll kdnet.dll_old ren kdnet.dllnew kdnet.dll chsize32.exe kdnet.dll 77824 checksum.exe kdnet.dll to what size should the original kdnet.dll 64-bit file be cropped with the chsize32 command? we need 64-bit code KDNET_PATCH.ASM for make KDNET.BIN dummy file for 32-bit has 688 bytes - do we use the same one or should it have a different size for 64-bit? what should be the target size of the patched kdnet.dll file, which we set in the last step using chsize32 ?

I can't download it. Upload it to a normal server, e.g. https://www.upload.ee/

64-bit please

@Dietmar I use GUI FASM only. I also ask GPT https://www.elektroda.pl/rtvforum/topic4168197.html

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

Yea, I once asked @Mov AX, 0xDEAD about the 64-bit version LAN WinDbg and he said he was not interested 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): 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:

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: 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

@Dietmar I found way how unlock dump/flash full BIOS using FPT.efi on Dell Wyse 5070 - simply set jumper JMP1 to Service Mode https://www.parkytowers.me.uk/thin/wyse/5070/

@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:

If you could compile the 64-bit driver, I'd be happy :-)

@Dietmar My Dell full spec: CPU: Intel Celeron J4105 iGPU: PCI\VEN_8086&DEV_3185 Gemini Lake RAM: 8 GB (2 x 4 GB) DDR4 Stor: PCI\VEN_8086&DEV_31CC eMMC 16 GB LAN: Realtek Wifi: 9560NGW 2230 key id E BIOS: 1.10.2 I added second disk because eMMC not work in my pure UEFI WinXP 64-bit and Win7 64-bit Stor: M2 SATA SAMSUNG_PM871b 128GB 2280 I use FPT.efi from v4 CSTXE System Tools v4 r6.rar https://mega.nz/folder/aV9UhTSJ#poWeTgkuCzmG_jnOwuo7EA/folder/mM8XSYqZ dump work but verify failed: fpt -bios -d dump.bin fpt -verify dump.bin I use sceefi.efi for make all hidden settings.txt https://www.upload.ee/files/19156985/Dell_efi.zip.html but I not tested flash using this FPT !!!

@Dietmar I tried enable CSM changing this hidden setting but not help: Setup Question = Boot List Token =DA // Do NOT change this line Offset =65A Width =01 BIOS Default =[01]UEFI MFG Default =[01]UEFI Options =[00]Legacy // Move "*" to the desired Option *[01]UEFI Setup Question = Enable Legacy Option ROMs Token =129 // Do NOT change this line Offset =810 Width =01 BIOS Default =0 MFG Default =0 Value =0 // Enabled = 1, Disabled = 0 Setup Question = Enable Attempt Legacy Boot Token =12A // Do NOT change this line Offset =811 Width =01 BIOS Default =0 MFG Default =0 Value =0 // Enabled = 1, Disabled = 0 Setup Question = CSM Support Token =2738 // Do NOT change this line Offset =60 Width =01 BIOS Default =[00]Disabled MFG Default =[00]Disabled Options =*[00]Disabled // Move "*" to the desired Option [01]Enabled Setup Question = Boot option filter Token =1F4 // Do NOT change this line Offset =66 Width =01 BIOS Default =[00]UEFI and Legacy MFG Default =[00]UEFI and Legacy Options =[00]UEFI and Legacy // Move "*" to the desired Option [01]Legacy only *[02]UEFI only Setup Question = Video Token =1F7 // Do NOT change this line Offset =69 Width =01 BIOS Default =[01]UEFI MFG Default =[01]UEFI Options =[00]Do not launch // Move "*" to the desired Option *[01]UEFI [02]Legacy Setup Question = Other PCI devices Token =1F8 // Do NOT change this line Offset =6A Width =01 BIOS Default =[01]UEFI MFG Default =[01]UEFI Options =[00]Do not launch // Move "*" to the desired Option *[01]UEFI [02]Legacy If use CSMWrap all Windows XP, 8, 10 32-bit or 64-bit error loading ACPI problem - A5 BSOD on XP32 and Win10 32-bit ACPI_BIOS_ERROR, Win10 64-bit DRIVER_VERIFIER_DMA_VIOLATION Only Windows 64-bit XP (my modern), 8, 10 in pure UEFI works OK

@Dietmar Oh, I'm sorry but I forgot to write that I can't run any 32-bit system on Dell Wyse 5070 because is pure UEFI. CSMWrap not help. I can only boot 64-bit OS on pure UEFI e.g. WinXP 64-bit I can test the 64-bit version on WinXP 64-bit if you compile it.

@Dietmar lspci -s 00:0c.0 -vvv Win10: - https://pastebin.com/rGXBBjmU Ubuntu - https://pastebin.com/KidZJUGD

Should I specify lspci -vvv of my card in Linux?

Have you removed PCIe graphic card from slot, disabled CSM and set the iGPU as Primary display device in the BIOS? Try this: https://www.upload.ee/files/19152316/vbios.zip.html Test if Windows Boot Manager boot from USB: https://github.com/CSMWrap/CSMWrap/issues/39#issuecomment-3014504946 Using UEFI Shell try VGA Enable in PCI Bridge to which the iGPU card is connected (for me is: mm 0001003e 8 -pci ):

https://github.com/CSMWrap/CSMWrap/releases/tag/1.3.0

Hymmmm.... - UBU and UEFITool finds legacy VBIOS IceLake 1003: So, integrated GPU should work. If not, then disable CSM and try use CSMWrap with this extracted VBIOS: https://www.upload.ee/files/19150243/VBIOS_IceLake_1003.bin.html

@Dietmar I connected the laptop X220 (gigabit ethernet card) and AIMB i219 (gigabit ethernet card) directly with a cable and did file copy tests and speed is same as over Fast Ethernet switch ~ 5.8 MB/s when download from X220 to AIMB ~ 8.8 MB/s when download from AIMB to X220 Driver moreDev tested on WinXP 64-bit and WinXP 32-bit What are your speeds? I'm using TeraCopy 2.3 I test X220 and other PC WinNT 4.0 with gigabit ethernet card: ~ 19 MB/s when download from X220 to PC ~ 33 MB/s when download from PC to X220 I tested i219bind version and has better download 9.8 MB/s: ~ 9.8 MB/s when download from X220 to AIMB ~ 8.5 MB/s when download from AIMB to X220 P.S. bind version display always speed 100 Mbps so if your driver work only at 100 so it's good that he shows it like that https://msfn.org/board/topic/183464-compiling-acpi-v20-driver-for-windows-xp-sp3-and-windows-2003-sp2-x32x64/page/161/#findComment-1285577 but I don't know if this driver is OK for normal use Please fix moreDev and objfre_wnet_amd64 version 32-bit/64-bit to display 100 Mbps

@Dietmar Cool

I have pure UEFI Dell Wyse 5070 with Wifi card 9560NGW type 2230 key id E than no WinXP drv - maybe you try mod drv for this ? I use WinXP 64-bit on this PC and Ethernet Realtek work OK. Wifi card work OK on Win10: This is good PC - small, passive cooling, power consumption only 10W :-)