![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(272, 44%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EL%3C/text%3E%3C/svg%3E)
I saw that other thread, and at this point, I guess I agree with Daavee that you should go to a specialty forum such as bleepingcomputer for help in ensuring that your system is malware-free.
In the end, however, it may be simpler to backup your data files and do a reinstall -- IF that family friend who built the PC gave you a Windows XP install CD with it and if you can find the drivers. I agree that the Mercury site seems to be pretty worthless as far as your mobo is concerned, but I did find the SATA driver for your board here --> http://download.driverguide.com/driver/KVT600X-L/Mercury/d357122.html (if you have SATA hard drives).
For the other hardware (video card, sound card, network adapter) you'll have to go to the individual manufacturers. Model identifications should be visible in Device Manager or System Information (Start > Run > msinfo32 > OK).
I haven't tried the following so I can't vouch for either its effectiveness or its safety, but if you're willing to gamble (after you're pretty confident that malware is gone) ...
Microsoft claims that the TCP/IP system is such a "core" part of Windows XP that it isn't removable but only "resettable" -- and you've tried the reset process with no luck. Some, however, disagree ...
The following is from http://smokeys.wordpress.com/2008/07/20/how-to-recover-a-really-dead-windows-xp-sp2sp3-tcpip-stack/ I've added a few edits (in bold italics) based partly on what I know of INF files, but as I said, I haven't tried this procedure, with or without my suggestions.
Also see http://www.electrictoolbox.com/reinstall-tcpip-windows/
How to recover a really dead Windows XP (SP2/SP3) TCP/IP stack
About this article
Author/source: Hublerb – Tech Support Guy
- Complete destruction and restoration of dead TCP/IP stack
- Recovery from fatal failure or partial or complete corruption of TCP/IP
Related error messages / occurrences
- IP Driver Error Code 2.
- TCP/IP network transport is not installed error message from active sync.
- TCP/IP driver missing from devmgmt.msc showing hidden devices.
- Ipconfig produces immediate failure message.
- An Internal error occurred: The request is not supported.
- Unable to query host name.
- The specified device instance handle does not correspond to a present device message regarding DHCP service in services.msc
- Net start tcpip >>> fails with system error 2, The system cannot find the file specified.
- Ping error: Unable to contact IP driver, error code 2.
- Repair Local Area Connection: Failed to query TCP/IP settings of the connection. Cannot proceed.
-TCP/IP Protocol Driver Service Failed To Start, system cannot find the file specified.
- The TCP/IP Protocol Driver service failed to start due to the following error: The system cannot find the file specified.
Failed repair methods
- Netsh int ip reset resetlog.txt >>> no effect
- Non-full reinstall of TCP/IP using only the have disk method. >>> no effect
- Netsh Winsock reset >>> no effect
- Winsockxpfix >>> no effect
- Reinstalling network card >>> no effect
Solutions
Repair install
Note: A Windows Repair Install is supposed to keep your data and your installed applications intact. Nevertheless, a backup is always prudent.
- Insert and boot from your WindowsXP CD
- At the second R=Repair option, press the R key
- This will start the repair
- Press F8 for I Agree at the Licensing Agreement
- Press R when the directory where WindowsXP is installed is shown. Typically this is C:\WINDOWS
- It will then check the C: drive and start copying files
- It will automatically reboot when needed. Keep the CD in the drive.
- You will then see the graphic part of the repair that is like during a normal install of XP (Collecting Information, Dynamic Update, Preparing Installation, Installing Windows, Finalizing Installation)
- When prompted, click on the Next button
- When prompted, enter your XP key
- Normally you will want to keep the same Workgroup or Domain name
- The computer will reboot
- Then you will have the same screens as a normal XP Install
- Activate if you want (usually a good idea)
- Register if you want (but not necessary)
- Finish
Hardcore method when nothing else is working
Step #1
- Back up the Registry using ERUNT or similar
- Locate the Nettcpip.inf file in %winroot%\inf, and then open the file in Notepad.
- Locate the [MS_TCPIP.PrimaryInstall] section.
- Edit the Characteristics = 0xa0 entry and replace 0xa0 with 0×80.
- Save the file, and then exit Notepad.
4a. Rename %winroot%\inf\Nettcpip.pnf to %winroot%\inf\Nettcpip_pnf.old
- In Control Panel, double-click Network Connections, right-click Local Area Connection, and then select Properties.
- On the General tab, click Install, select Protocol, and then click Add.
- In the Select Network Protocols window, click Have Disk.
- In the Copy manufacturer’s files from: text box, type c:\windows\inf, and then click OK.
- Select Internet Protocol (TCP/IP), and then click OK.
Note This step will return you to the Local Area Connection Properties screen, but now the Uninstall button is available.
- Select Internet Protocol (TCP/IP), click Uninstall, and then click Yes.
- Restart
Successful uninstallation of TCP/IP will remove numerous keys from the registry including:
HKLM/system/CurrentControlSet/services/tcpip
HKLM/system/CurrentControlSet/services/dhcp
HKLM/system/CurrentControlSet/services/dnscache
HKLM/system/CurrentControlSet/services/ipsec
HKLM/system/CurrentControlSet/services/policyagent
HKLM/system/CurrentControlSet/services/atmarpc
HKLM/system/CurrentControlSet/services/nla
These represent various interconnected and interdependant services.
For good measure you should delete the following keys before reinstalling TCP/IP in step #2:
HKLM/system/CurrentControlSet/services/winsock
HKLM/system/CurrentControlSet/services/winsock2
Step #2
Reinstall of TCP/IP
Following the above substep #3, replace the 0×80 back to 0xa0, this will eliminate the related “unsigned driver” error that was encountered during the uninstallation phase.
If a new Nettcpip.pnf file was created, delete it.
Return to “local area connection”> properties > general tab > install > Protocol > TCP/IP
You may receive an “Extended Error” failure upon trying to reinstall the TCP/IP, this is related to the installer sub-system conflicting with the security database status.
To check the integrity of the security database
esentutl /g c:\windows\security\Database\secedit.sdb
There may be a message saying database is out of date
First try the recovery option
esentutl /r c:\windows\security\Database\secedit.sdb
If this don’t work for you, you need the repair option
esentutl /p c:\windows\security\Database\secedit.sdb
Rerun the /g option to ensure that integrity is good and database is up to date.
Now return to the “local area network setup”
Choose install > protocol > TCP/IP and try again
Reboot.