Content Type
Profiles
Forums
Events
Everything posted by reboot12
-
So I can copy and paste all the code at once and you wrote earlier that I have to enter it line by line Now I can use WinDbg conveniently and pleasantly Typing line by line was very tiring https://www.upload.ee/files/19111494/i219LMbest_kd_diag_fixed_05d4_2026-02-26_07-14-11-281.txt.html i219LMv7 - 100 Mbps but 0/0
-
@Dietmar i219bind log - I do g few times: https://pastebin.com/EgHhp4h8 i219coll 100 Mbps but 0/0 and log: https://www.upload.ee/files/19108296/i219_rescue_windbg_0af0_2026-02-25_08-18-08-125.log.html i219CollFix - 100 Mbps 0/0. If tried connect i219 to GBE device e.g. my laptop then cable unplugged and mouse cursor gets stuck about every 3 seconds Does your i219 driver allDEV work with old 100 Mbps devices or only with GBE devices ?
-
I have everything Disabled except: PCIE Wake for power PC over WOL LAN1 Controller - this is my i219 card so must be Enabled BTW - I have already written several times that the i219 card works OK in Win10 with these BIOS settings Wow - with i219bind driver speed is 100 Mbps but still 0 Sent / 0 Received
-
@Dietmar After installing the i219 driver, I always set a static IP. The DHCP client service is disabled because if WinXP does not receive an IP from DHCP, it takes a long time to start, and if it has a static one, it starts almost immediately. So I don't know if your DHCP commands will be useful for anything. i219DHCP driver not work
-
@Dietmar I copy and paste each line into WinDbg and hit enter - it's very tiring. Can it be somehow speed up or automated? Honestly, I don't want to enter so many lines of data into WinDbg every time Before each use of new commands, I turn off the computer with i219 and close WinDbg, now I run WinDbg and then boot PC with i219 in debug mode
-
@Dietmar Realtek driver 2018 work but only if reboot PC. disable then enable in device manager not help - need restart after install. https://pastebin.com/bdWaG7Qq NOPowersaving version - still not work. I think this is not power problem. I think that the problem is the bad connection speed - always 1 Gbps and should be 100 Mbps because my old router works only in 100 Mbps In WinDbg I see Link 100 Mbps: I219IndicateMediaState vs7_3_6gR_irq: LinkState -> DOWN 100Mb HD I219LinkFromStatus I219IndicateMediaState vs7_3_6gR_irq: LinkState -> UP 100Mb FD but in Windows connection status is still 1.0 Gbps On Dell Wyse Realtek card is GBE but works at 100 Mbps
-
@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 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
-
@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.
-
I debug WinXP SP2 so I need install WindowsXP-KB835935-SP2-slp-Symbols.exe instead WindowsXP-KB936929-SP3-x86-symbols-full-ENU.exe Now WinDbg find all .pdb files except those for custom drivers: ************* Symbol Loading Error Summary ************** Module name Error ACPI PDB not found : c:\symbols\symbols\sys\acpi.pdb Unable to locate the .pdb file in this location sdbus PDB not found : c:\symbols\symbols\sys\sdbus.pdb Unable to locate the .pdb file in this location ntoskrn8 PDB not found : c:\symbols\symbols\sys\ntoskrn8.pdb Unable to locate the .pdb file in this location sdstor PDB not found : c:\symbols\symbols\sys\sdstor.pdb Unable to locate the .pdb file in this location iaStorAC PDB not found : c:\symbols\symbols\sys\iaStorAC.pdb Unable to locate the .pdb file in this location storport PDB not found : c:\symbols\symbols\sys\storport.pdb Unable to locate the .pdb file in this location genahci PDB not found : c:\symbols\symbols\sys\genahci.pdb Unable to locate the .pdb file in this location stornvme PDB not found : c:\symbols\symbols\sys\stornvme.pdb Unable to locate the .pdb file in this location Why on this list not i219 driver ???
-
@Dietmar Not work, 0 sent / 0 receive I have my own way to change the driver in WinXP and it always works - have been using it for many years: uninstall driver from Device Manager search oemx.inf file for the previous installed driver in WINDOWS\inf directory then delete this file (delete also same name oemx.PNF but not necessary) in Device Manager click the computer name at the very top and then Scan for hardware changes button now WinXP finds new hardware where you need to indicate the location of the new driver and install it
-
@Dietmar This forum has a very low number of views - on average 5 users per day, so few people know that you made such drivers and there is no one to test them. I suggest making the drivers available somewhere that is more popular, e.g. record a short video on YouTube. Maybe also create topic on MDL forum - average members per day is about 100 but posts are hidden if you no account.