sk9392 Posted April 8 Posted April 8 (edited) Thank you @Dietmar and everyone for the incredible job of making Win XP compatible. I have a question and sorry if it's a noob question, I am very much new to modding and slipstreaming WinXP. I am interested in installing Windows Home Server 2007 on a Lenovo ThinkCentre M700. It seems to have Intel B150 Chipset as per this spec sheet: https://psref.lenovo.com/syspool/Sys/PDF/ThinkCentre/ThinkCentre_M700_Tiny/ThinkCentre_M700_Tiny_Spec.PDF. I tried the Windows XP Integral Edition and used patch integrator to make a modified iso with relevant NVMe and SATA and AHCI drivers. Then I mounted the image and used WinSetupFromUSB to select the virtual drive folder (since the i386 folder lies in the root of that modded ISO). And then I installed it and it works perfectly. But Windows Home Server 2007 seems to have some difficulty. What I did: 1. Opened .iso of WHS2007 in gBurner. The SRV2003 folder contains i386 folder and main files, so I cut everything inside the SRV2003 folder and put it in the root of the iso. Then saved it and renamed to WHS2007_Vanilla.iso 2. In the patch integrator script, I replaced "XPSP3RES.DL_" by "XPSP2RES.DL_". Then I ran it with options 2, 3, 5, A, B, C, F, M (same options that worked perfectly with the Integrated Edition vanilla iso). The script detected the WHS2007_Vanilla.iso, performed all its operations and created the modded WHS2007 iso. 3. I mounted the modded WHS2007 iso and used WinSetupFromUSB to select the virtual driver letter But when I install from that bootable USB, I get a 0xDEADBEEF BSOD. And I have no idea what to do in this case. Any help would be highly appreciated. Edited April 8 by sk9392
Dietmar Posted April 8 Posted April 8 @sk9392 ntoskrnl.exe from XP SP3 and W2003 are not the same. They have some similarities but also big differences. So, when you use the Patch Integrator, I think it will always fail, when you use modded drivers, that depend on ntoskrn8.sys . Other drivers, which make no use of the ntoskrn8.sys, should work Dietmar PS: By the way I noticed, that the USB AMD 145 driver gives Bsod c0005 on z690 boards, even with the patch from @reboot12 .
Dietmar Posted April 9 Posted April 9 (edited) Hi, just for fun, for to look what is possible to do with the WDK 7600 under XP SP3, I wrote a pure Assembler program, for to calculate the sum of 1^3 + 2^3 + 3^3 + 4^3 + ...+ 10.000.000.000^3 = [n*(n+1)/2]^2 (zur Probe). The stupid compi has to add all one by one.. But he did this very tricky, for to avoid multiplication, uses always the "6" as constant difference in 3. order sum, and now only has to sum everything up. On my X58 board the program gives the time out of nearly exact 120 sec. The whole program kubik.exe is only 3kb in size. This program kubik.exe should run on a lot of different Windows versions. And I make an interesting discovery: I wrote another kubik.exe program, that make use of the 4 cores of my i920 cpu on this x58 board. Now, the cpu last goes up from 13% ==> 53%, means all cores are involve. But now I get nearly 200sec as result.. Dietmar PS: Here is the program kubik.exe and the whole Source Code that you run in commandline, nice(!).. https://www.upload.ee/files/19235972/kubik10.zip.html EDIT: I make a small joke: I just fake the Header PE signature. Now kubikOS.exe should also run on win95 >=Win95 XP 108: 03 05 10A: 0A 01 110: 03 05 112: 0A 01 https://www.upload.ee/files/19236111/kubikOS.exe.html .686 .model flat, stdcall option casemap:none EXTERN GetStdHandle@4:PROC EXTERN WriteFile@20:PROC EXTERN ExitProcess@4:PROC EXTERN GetTickCount@0:PROC .data sum0 dd 0 sum1 dd 0 sum2 dd 0 sum3 dd 0 sum4 dd 0 cube0 dd 1 cube1 dd 0 cube2 dd 0 cube3 dd 0 d10 dd 7 d11 dd 0 d12 dd 0 d13 dd 0 d20 dd 12 d21 dd 0 count0 dd 540BE400h count1 dd 2 startTick dd 0 elapsed dd 0 hout dd 0 bytesWritten dd 0 outptr dd 0 outlen dd 0 timeptr dd 0 timelen dd 0 prefix db 'Zeit ms: ' outbuf db 128 dup(0) timebuf db 32 dup(0) .code start PROC call GetTickCount@0 mov startTick, eax L1: mov eax, sum0 add eax, cube0 mov sum0, eax mov eax, sum1 adc eax, cube1 mov sum1, eax mov eax, sum2 adc eax, cube2 mov sum2, eax mov eax, sum3 adc eax, cube3 mov sum3, eax mov eax, sum4 adc eax, 0 mov sum4, eax mov eax, cube0 add eax, d10 mov cube0, eax mov eax, cube1 adc eax, d11 mov cube1, eax mov eax, cube2 adc eax, d12 mov cube2, eax mov eax, cube3 adc eax, d13 mov cube3, eax mov eax, d10 add eax, d20 mov d10, eax mov eax, d11 adc eax, d21 mov d11, eax mov eax, d12 adc eax, 0 mov d12, eax mov eax, d13 adc eax, 0 mov d13, eax add d20, 6 adc d21, 0 sub count0, 1 sbb count1, 0 mov eax, count0 or eax, count1 jnz L1 call GetTickCount@0 sub eax, startTick mov elapsed, eax mov edi, OFFSET outbuf add edi, 127 mov byte ptr [edi], 0 dec edi mov byte ptr [edi], 10 dec edi mov byte ptr [edi], 13 dec edi L2: mov ebx, 10 xor edx, edx mov eax, sum4 div ebx mov sum4, eax mov eax, sum3 div ebx mov sum3, eax mov eax, sum2 div ebx mov sum2, eax mov eax, sum1 div ebx mov sum1, eax mov eax, sum0 div ebx mov sum0, eax add dl, '0' mov byte ptr [edi], dl dec edi mov eax, sum0 or eax, sum1 or eax, sum2 or eax, sum3 or eax, sum4 jnz L2 inc edi mov outptr, edi mov eax, OFFSET outbuf add eax, 127 sub eax, edi mov outlen, eax mov edi, OFFSET timebuf add edi, 31 mov byte ptr [edi], 0 dec edi mov byte ptr [edi], 10 dec edi mov byte ptr [edi], 13 dec edi mov eax, elapsed cmp eax, 0 jne L3 mov byte ptr [edi], '0' dec edi jmp L4 L3: mov ebx, 10 L3A: xor edx, edx div ebx add dl, '0' mov byte ptr [edi], dl dec edi test eax, eax jnz L3A L4: inc edi mov timeptr, edi mov eax, OFFSET timebuf add eax, 31 sub eax, edi mov timelen, eax push -11 call GetStdHandle@4 mov hout, eax push 0 push OFFSET bytesWritten push outlen push outptr push hout call WriteFile@20 push 0 push OFFSET bytesWritten push 9 push OFFSET prefix push hout call WriteFile@20 push 0 push OFFSET bytesWritten push timelen push timeptr push hout call WriteFile@20 push 0 call ExitProcess@4 start ENDP end start Edited April 9 by Dietmar
Damnation Posted April 10 Posted April 10 @sk9392 You can comment out the KeBugCheckEx(0xDEADBEEFL parts of the ntoskrnl extender code to get rid of the DEADBEEF BSOD's.
K4sum1 Posted April 12 Posted April 12 On 2/24/2026 at 3:19 AM, Damnation said: @Dietmar I added an RTC8125.rc resources file to your project just for the aesthetics, it's nicer with one. https://buzzheavier.com/ziftf00d8rg9 Also, when I build this with the windows 7 DDK - I got an inconsistent DLL linking error in NdisMInitializeScatterGatherDma and had to use #pragma warning(disable:4273) to get it to compile. Is that normal? I wanted to compile the driver and I decided your one might be better to do this with. However I noticed your link doesn't exist anymore and I thought I had downloaded it, but I can't find it. Can you reupload pls.
K4sum1 Posted April 12 Posted April 12 (edited) I made a GitHub page for it since it helps me keep track of and organize changes better. I tried compiling as a x64 driver, and it compiles. I tried modifying the inf to install on x64, but I get the same "The parameter is incorrect error" that I got on Server 2003 and I have no idea how to fix please help. https://github.com/the-r3dacted/RTL812 X-WinXP/issues/1 8125x64.7z Edited April 12 by K4sum1
Dietmar Posted April 12 Posted April 12 @K4sum1 I make a new version for RTL812x. Then I compile everything for XP SP3 free, chk and 2003 NT5.2 bit 64 also free and chk. I have not tested, good luck Dietmar https://www.upload.ee/files/19243043/RTL8125_NT52_x86_x64_patched_v3.zip.html 1
K4sum1 Posted April 13 Posted April 13 15 hours ago, Dietmar said: @K4sum1 I make a new version for RTL812x. Then I compile everything for XP SP3 free, chk and 2003 NT5.2 bit 64 also free and chk. I have not tested, good luck Dietmar https://www.upload.ee/files/19243043/RTL8125_NT52_x86_x64_patched_v3.zip.html Thank you. I gave this a try. First though I noticed you included a COMPARE_8125x64.txt and here's my replies to it. Quote - The uploaded x64 INF only matches PCI\VEN_10EC&DEV_8125. - It is AMD64-only and does not cover the broader 8125/8126/8127 family. Current build I decided to only do for 8125 since it (supposedly) works on it, and I figured I would need to basically remake the driver for 8126 to work with it, and make another for 8127. I didn't think it would be so relatively few code changes to combine them all. Quote - It uses a single generic CatalogFile=rtl8125.cat entry. - It does not split SourceDisksFiles by architecture. I'm not even sure what the purpose of the cat file is since there is no cat file that exists here. Also I figured I'd just ship a different inf for x86 and x64 so I didn't try to combine them. Quote - The uploaded rtl8125.sys is a real PE32+ amd64 kernel driver. - The embedded PDB path points to objfre_wnet_amd64, which suggests it was built in a WNET amd64 environment. - The PE optional header reports MajorOperatingSystemVersion=6 and MinorOperatingSystemVersion=1, while the subsystem version is 5.2. I built it with the Win 7 DDK, but I built it with a Win 7 machine. Could that be why those versions are 6 and 1? Should I try building it on XP? Quote - The exact cause of the "The parameter is incorrect" install error cannot be proven here without SetupAPI/Device Manager install logs from XP x64 or Server 2003 x64. So I have the same issue with this driver, and this is what I found in setupapi.log for it. [2026/04/12 16:28:27 260.255] #-198 Command line processed: "C:\WINDOWS\system32\mmc.exe" "C:\WINDOWS\system32\devmgmt.msc" #I060 Set selected driver. #-019 Searching for hardware ID(s): pci\ven_10ec&dev_8125&subsys_7c911462&rev_04,pci\ven_10ec&dev_8125&subsys_7c911462,pci\ven_10ec&dev_8125&cc_020000,pci\ven_10ec&dev_8125&cc_0200 #-018 Searching for compatible ID(s): pci\ven_10ec&dev_8125&rev_04,pci\ven_10ec&dev_8125,pci\ven_10ec&cc_020000,pci\ven_10ec&cc_0200,pci\ven_10ec,pci\cc_020000,pci\cc_0200 #-019 Searching for hardware ID(s): pci\ven_10ec&dev_8125&subsys_7c911462&rev_04,pci\ven_10ec&dev_8125&subsys_7c911462,pci\ven_10ec&dev_8125&cc_020000,pci\ven_10ec&dev_8125&cc_0200 #-018 Searching for compatible ID(s): pci\ven_10ec&dev_8125&rev_04,pci\ven_10ec&dev_8125,pci\ven_10ec&cc_020000,pci\ven_10ec&cc_0200,pci\ven_10ec,pci\cc_020000,pci\cc_0200 #-019 Searching for hardware ID(s): pci\ven_10ec&dev_8125&subsys_7c911462&rev_04,pci\ven_10ec&dev_8125&subsys_7c911462,pci\ven_10ec&dev_8125&cc_020000,pci\ven_10ec&dev_8125&cc_0200 #-018 Searching for compatible ID(s): pci\ven_10ec&dev_8125&rev_04,pci\ven_10ec&dev_8125,pci\ven_10ec&cc_020000,pci\ven_10ec&cc_0200,pci\ven_10ec,pci\cc_020000,pci\cc_0200 #-019 Searching for hardware ID(s): pci\ven_10ec&dev_8125&subsys_7c911462&rev_04,pci\ven_10ec&dev_8125&subsys_7c911462,pci\ven_10ec&dev_8125&cc_020000,pci\ven_10ec&dev_8125&cc_0200 #-018 Searching for compatible ID(s): pci\ven_10ec&dev_8125&rev_04,pci\ven_10ec&dev_8125,pci\ven_10ec&cc_020000,pci\ven_10ec&cc_0200,pci\ven_10ec,pci\cc_020000,pci\cc_0200 #I022 Found "PCI\VEN_10EC&DEV_8125" in c:\new\RTL8125.inf; Device: "Realtek RTL8125 2.5GbE"; Driver: "Realtek RTL8125 2.5GbE"; Provider: "Dietmar"; Mfg: "Dietmar"; Section name: "RTL812x.ndi.NT.5.2". #I087 Driver node not trusted, rank changed from 0x00002001 to 0x0000a001. #I023 Actual install section: [RTL812x.ndi.NT.5.2]. Rank: 0x0000a001. Driver date: 04/12/2026. Version: 0.0.0.16. #-124 Doing copy-only install of "PCI\VEN_10EC&DEV_8125&SUBSYS_7C911462&REV_04\6&52F7D12&0&0048020A". #W360 An unsigned, incorrectly signed, or Authenticode(tm) signed file "c:\new\rtl8125.inf" for driver "Realtek RTL8125 2.5GbE" will be installed (Policy=Ignore). Error 0xe000022f: The third-party INF does not contain digital signature information. #-024 Copying file "c:\new\amd64\rtl8125.sys" to "C:\WINDOWS\system32\DRIVERS\rtl8125.sys". #W360 An unsigned, incorrectly signed, or Authenticode(tm) signed file "c:\new\rtl8125.inf" for driver "Realtek RTL8125 2.5GbE" will be installed (Policy=Ignore). Error 0xe000022f: The third-party INF does not contain digital signature information. #-166 Device install function: DIF_REGISTER_COINSTALLERS. #I056 Coinstallers registered. #-166 Device install function: DIF_INSTALLINTERFACES. #-011 Installing section [RTL812x.ndi.NT.5.2.Interfaces] from "c:\new\rtl8125.inf". #I054 Interfaces installed. #-166 Device install function: DIF_INSTALLDEVICE. #E161 Processing of call to class installer failed. Error 87: The parameter is incorrect. I tried testing the x86 driver on XP x86 since it didn't work for me there with the old driver, but I encountered a code 10 on both the 8125 and 8126 I'm testing with. I was also curious about more modern Windows versions, so I tested 8.1, and get a code 31 from both. Would be nice to have something working for the 8126/8127 since it has no native 7/8 driver. Also I think the compiled driver is supposed to automatically copy to the amd64 and x86 folders, but that didn't happen on my end. I had to manually copy them there.
reboot12 Posted April 14 Posted April 14 (edited) On 4/7/2026 at 7:28 PM, Dietmar said: The driver is nearly ready but still no able to find Wlan traffic I found in my Dell bios hidden settings: Setup Question = CNVi Mode Token =2F9 // Do NOT change this line Offset =871 Width =01 BIOS Default =[01]Auto MFG Default =[01]Auto Options =[00]Disable // Move "*" to the desired Option *[01]Auto Default is Auto 01. Using AmiSetupWriter.efi I changed it to Disabled 00 and the card still works in Win10. Maybe after disabling CNVi your driver will work on WinXP? Only yours may have a different offset !!! My is 0x871 P.S. I noticed an interesting thing. It is impossible to change the hidden CSM Support option to 01 because after a restart it returns to 00, but I can change another option - Enable Legacy Option ROMs to 1. Then, after the restart, I cannot enter the BIOS or call BootMenu via F12. However, my WinXP 64-bit boots from the M2 SATA disk and when I run my UefiMenu.exe application, I see that there are new devices on the list and VBIOS is used instead GOP. This means that the computer is running in UEFI+CSM mode: Please compile driver 64-bit version for WinXP 64-bit - I want to test. Edited April 14 by reboot12
Dietmar Posted April 14 Posted April 14 @reboot12 I have this switch in Bios also, because with hack for ME I can see everything in the Bios of the Biostar z690A Valkyrie. I just switch this CNVi from Auto ===> disable. But because of those "IF" constructions there, then the whole device 9560 disappears. May be with ru.efi I can switch ONLY this CNVi but until now I have not tested because I do not think, that this will help me Dietmar PS: On your Dell the switch for CSM is write protected. But you can read out the whole Bios, switch this CSM to enabled and flash Bios back. This was the only way, how I can enable CSM on the N100 board. 0x41D1B Form: Connectivity Configuration, FormId: 0x2720 {01 86 20 27 75 02} 0x41D21 Text: Statement.Prompt: CNVi CRF Present, TextTwo: No {03 08 F8 16 F9 16 FA 16} 0x41D29 Text: Statement.Prompt: CNVi Configuration, TextTwo: {03 08 FC 16 FC 16 00 00} 0x41D31 One Of: CNVi Mode, VarStoreInfo (VarOffset/VarName): 0x734, VarStore: 0x6, QuestionId: 0x5E, Size: 1, Min: 0x0, Max 0x1, Step: 0x0 {05 91 76 02 FD 16 5E 00 06 00 34 07 10 10 00 01 00} 0x41D42 One Of Option: Disable Integrated, Value (8 bit): 0x0 {09 07 FF 16 00 00 00} 0x41D49 One Of Option: Auto Detection, Value (8 bit): 0x1 (default) {09 07 FE 16 30 00 01} 0x41D50 End One Of {29 02} 0x41D52 Suppress If {0A 82} 0x41D54 QuestionId: 0x5E equals value 0x0 {12 06 5E 00 00 00} 0x41D5A Gray Out If {19 82} 0x41D5C String Ref: No (0x16FB) {4E 84 FB 16} 0x41D60 String Ref: No (0x16FA) {4E 04 FA 16} 0x41D64 Match {2A 02} 0x41D66 End {29 02} 0x41D68 One Of: Wi-Fi Core, VarStoreInfo (VarOffset/VarName): 0x735, VarStore: 0x6, QuestionId: 0x5F, Size: 1, Min: 0x0, Max 0x1, Step: 0x0 {05 91 77 02 00 17 5F 00 06 00 35 07 10 10 00 01 00} 0x41D79 One Of Option: Enabled, Value (8 bit): 0x1 (default) {09 07 03 00 10 00 01} 0x41D80 One Of Option: Disabled, Value (8 bit): 0x0 {09 07 04 00 00 00 00} 0x41D87 End One Of {29 02} 0x41D89 One Of: BT Core, VarStoreInfo (VarOffset/VarName): 0x736, VarStore: 0x6, QuestionId: 0x60, Size: 1, Min: 0x0, Max 0x1, Step: 0x0 {05 91 78 02 01 17 60 00 06 00 36 07 10 10 00 01 00} 0x41D9A One Of Option: Enabled, Value (8 bit): 0x1 (default) {09 07 03 00 10 00 01} 0x41DA1 One Of Option: Disabled, Value (8 bit): 0x0 {09 07 04 00 00 00 00} 0x41DA8 End One Of {29 02} 0x41DAA Gray Out If {19 82} 0x41DAC QuestionId: 0x60 equals value 0x0 {12 06 60 00 00 00} 0x41DB2 One Of: BT Audio Offload, VarStoreInfo (VarOffset/VarName): 0x737, VarStore: 0x6, QuestionId: 0x271E, Size: 1, Min: 0x0, Max 0x1, Step: 0x0 {05 91 79 02 02 17 1E 27 06 00 37 07 14 10 00 01 00} 0x41DC3 One Of Option: Disabled, Value (8 bit): 0x0 (default) {09 07 04 00 10 00 00} 0x41DCA One Of Option: Enabled, Value (8 bit): 0x1 {09 07 03 00 00 00 01} 0x41DD1 End One Of {29 02} 0x41DD3 End If {29 02} 0x41DD5 End If {29 02} 0x41DD7 End If {29 02}
Dietmar Posted April 14 Posted April 14 @reboot12 Yessssaahh.. today is break through with the XP driver for wlan 9560. Crazy, I was one step away from to give up. Now I build around 1000(!) different versions of this driver. Now I have prove, that my 9560 driver connects to my router. Nowhere in Internet you can find any like this for Wlan and XP Dietmar Intel 9560 Wi-Fi Driver for Windows XP Current Status (rr12) 1. What this driver is This is a ground-up NDIS 5.1 miniport driver for the Intel 9560 Wi-Fi project on Windows XP. It does not rely on Intel's original Windows XP Wi-Fi driver, because no such complete modern driver exists for this hardware path. Instead, it loads the real Linux iwlwifi firmware and talks directly to the hardware with Linux-style low-level commands, DMA rings, RX/TX queues, and firmware notifications. In the current test logs, the active hardware path is the Intel CNVi device with PCI ID 8086:7AF0 and firmware API 77 (SoJf B0 family, build f92b5fed). 2. What already works The driver now performs the full low-level hardware and firmware bring-up successfully: - PCI BAR mapping - device reset and wake-up - interrupt registration - DMA/RFH/RX queue allocation - firmware loading - ALIVE notification handling - bootstrap completion After firmware startup, the driver can run the modern Linux-style UMAC scan sequence: - pre-scan command 0x03 - full scan request 0x0D - scan request ACK - UMAC iteration notification B5 - UMAC complete notification 0x0F This is important, because earlier revisions only got ACK/COMPLETE without usable scan results. The newer revisions now receive real scan-result traffic from the hardware. 3. What the driver can do right now At the current rr12 stage, the driver can already do the following: - initialize the hardware and firmware reliably - run real over-the-air Wi-Fi scans - receive real 802.11 management traffic from the air - parse scan-result notifications from the modern UMAC scan path - detect beacons / probe responses in the RX path - populate the Windows XP BSSID list - return real networks through OID_802_11_BSSID_LIST - repeat scans reliably when Windows XP requests them - detect whether a scanned network is open, WPA, or WPA2/WPA-family encrypted - set the Privacy flag for encrypted networks so the XP Wi-Fi UI can distinguish protected networks In plain words: The driver is no longer only loading firmware. It is now actually hearing Wi-Fi signals and building a real network list that Windows XP can query. 4. What the current logs prove The latest successful logs show all of the following: - firmware boot completes cleanly - ALIVE status is received - scan commands are accepted - B5 UMAC iteration results are returned - management frames are parsed - at least one BSS entry is created - OID_802_11_BSSID_LIST returns count = 1 instead of 0 This means the scan path is now real and functional. This is the first major milestone where the XP driver is no longer "talking to firmware only", but is actually receiving real radio data and exposing it back to Windows XP. 5. What is proven about radio reception The logs now prove real RF reception. That means this is no longer a fake scan, a synthetic result, or a firmware-only illusion. The driver is now receiving real scan-result data from the radio path and converting it into BSS entries. The current successful logs clearly prove real reception on 2.4 GHz. The scan also runs on 5 GHz channels, but in the currently confirmed logs the strongest proven decoded result is from the 2.4 GHz side. So the safe statement is: - 2.4 GHz reception is proven - 5 GHz scanning is active - 5 GHz reception is very likely, but should still be confirmed with a clearly decoded 5 GHz BSS entry in the log 6. WPA / WPA2 status WPA / WPA2 support is currently present at the scan-detection level, not yet at the full connection level. What works now: - RSN / WPA-family information can be recognized from scan results - encrypted networks can be marked as protected - the driver can expose that protection state in the BSS list What does not work yet: - no full WPA/WPA2 association - no 4-way handshake - no PTK/GTK installation - no real data traffic under WPA2 yet So at the moment: The driver can see WPA/WPA2-protected networks. 7. What still does NOT work yet The following major parts are still unfinished: - association / authentication sequence - full connect logic - WPA/WPA2 key installation - real TX data path for connected traffic - full RX data path for normal user packets - IP traffic over Wi-Fi - stable end-to-end network connection So the current status is: Scanning works. Discovery works. BSS list reporting works. Encryption detection works. Connection does not work yet. 8. Current technical limitation Although scan reception is now real, the management-frame decoding is still not fully clean. The latest logs show that the driver is extracting real BSS data, but some parsed fields are still not fully trustworthy in every case. That means the scan-result path is alive, but the embedded frame interpretation still needs refinement. So the remaining scan-side work is no longer "make scanning work at all". It is now much narrower: - improve exact management-frame alignment inside the B5 result path - refine SSID / BSSID / channel extraction - confirm 5 GHz decoding with a clean real entry - keep WPA / RSN interpretation attached to the corrected frame parser 9. Practical summary What the Intel 9560 XP driver can do now: - bring up hardware - load real firmware - run real Wi-Fi scans - receive real over-the-air management frames - build a real BSS list - show at least one real access point in Windows XP - detect protected networks as encrypted What it still cannot do yet: - associate - authenticate fully - complete WPA2 handshake - pass normal network traffic 11. Bottom line This project has now moved beyond basic firmware bring-up. The Intel 9560 XP driver is already capable of: - real firmware initialization - real radio scanning - real management-frame reception - real BSS list reporting - WPA/WPA2 network detection during scan The next big milestone is no longer scanning. The next big milestone is full connection support: association, key handling, and real data traffic. Current state in one sentence: The driver can already see real Wi-Fi networks under Windows XP, including protected WPA/WPA2 networks
Mark-XP Posted April 14 Posted April 14 (edited) Congratulations @Dietmar! And meanwhile i think that Linux is really much superior to Windows (XP or 7): Lately found a Kingston mSATA ssd in the attic and - without any other application for it - had the idea to use it as transport media from the pc to the notebook utilizing this mSATA-USB3-adapter - mainly to avoid lost file attributes when transferring files to Linux. Had to wait about 2 weeks for the shipping from ShenZhen ($ 2.50 shipping costs? ) so i had enough time to wonder if i could additionally apply some OS's on that stick. After assembly i (MBR-) partitioned the 'disk': A first ntfs system partition for XP, an Extended (ntfs) partition (with Data + Win-7 sub-partitions) and a third ext4 partition for linux. This is what happened: Win XP: xxCloned mbr + bootrecord + the system from a standard ssd (like a dozend times before) in 3 minutes: really fast - but booting from the usb/mSATA resulted in a 07B bsod (0xB84C3524,...). Win 7: it presented all the partitions of the mSATA stick accurately - but stated immediatly that it's uncapable to install on a "scsci" media. Deplorable! Linux: installed flawlessly. Without any single issue. No noticeable performance difference compared to a standard ssd. Fun-fact: GRUB found the first Win-XP partition as bootable and offeres it in it's boot-menu... Edited April 15 by Mark-XP link added
Dietmar Posted April 14 Posted April 14 @Mark-XP Hihi, the situation is a little bit other. There is no driver for Win7 for the wlan 9560 card. But soon will be there a driver for XP. Oh..soso much crazy things happen to me today. First I get Wlan contact to my router with this Wlan card for the very first time. On 2.4 GHZ on channel 6 and on 5 GHZ on channel 100. Later I was wondering, why suddently I get contact on channel 1. Interesting, it is from neighbor. But in the meantime, my router switched to 2.4 GHZ channel 11, but why Dietmar PS: From a user I get a hint, that it is possible to use Win11 and on the same board a virtual machine with XP for to pass through this Wlan device 9560. On his board is such a 9560 Wlan card, running under win11. He reported, that with my driver version 9560rr15 under XP SP3 he already gets contact with 6 different WPA2 sources. Hm, I always think that for tests, XP on real hardware is better. But in the same time I never make such a try with real hardware devices, and I think it is very difficult. I make pass through only one time with Linux in summer 2012 for the game Moorhuhn and sound.
canonkong Posted April 15 Posted April 15 If Intel 9560AC can work on Xp, I think other Wi-Fi 6/6E/7 cards also can work on Xp too. Most Wi-Fi 5/6/6E/7 cards can work well on win7 now, but MT7927, QCNCM865 can not.
Dietmar Posted April 15 Posted April 15 I have the Speedport W 724V router from the Telekom germany. There I notice, that the channel can change (automatisch) or can be fixed to one channel. So, I can and will really test everything (WPA, WPA2, WEP, unsecured) with the Wlan driver 9560 for XP Dietmar
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now