![]() I am still using it and "usually" there is no harm. Re-install WinXP with the installation CD (use the "upgrade" option).Īfter the re-installation completed, I got everything back.īTW: I had this problem twice after using Ad-Aware 6.0 (the spyware cleaner) which deleted some files and registries off my computer. This time it ends successfully, the IP is now ".x" (which is another problem).Ġ9. Execute in a Command window: "netsh int ip reset c:\resetlog.txt". Export the Winsock2 key to a Winsock2.reg file, to save it.Ġ8. ![]() HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock2.Ġ5. Export the Winsock key to a Winsock.reg file, to save it. HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock.Ġ2. These are the steps I've used (mybe not everything is necessary: ![]() I have combined some partial Win2K methods(there you can uninstall TCP/IP), which then changed my problem to the famous .x problem (where DHCP cannot be connected), then I re-installed XP - and it works! I had all the issues describes above (IP=0.0.0.0, "netsh" failed, etc). I was able to re-establish the connection to the Internet. I cam across this very same issue twice in the last week (1st time I had to re-install complete new WinXP), but I think I got it now.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |