| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 52832 | 2004-12-31 05:01:00 | CWS Removal Tool | Dannz (1668) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 309202 | 2004-12-31 07:05:00 | Below is a quick and easy way to reinstall TCP/IP in Windows XP - it'll fix most "no traffic" problems. Don't use this for other operating systems, the instructions are different. I can dig them out somewhere if needed. Try this after checking all your firewall settings, etc etc etc. Warning: I take no responsibility if this hose's your PC, causes bedwetting or any other side effects - use at your own risk This fix covers a reinstall of the TCP/IP protocol and WinSock socket layers to resolve "no traffic" problems on a computer as a result of a damaged socket layer, or protocols. This is often as a result of a damaged firewall application, botched SpyWare removal or other layered application difficulties. Step 1: Delete registry keys Open the Registry Editor from the run line. Start --> Run --> regedit --> ok Navigate to both of the following keys and then delete the key (folder): HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Winsock HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Winsock2 Restart the computer NB: It is important to restart the computer after deleting the Winsock keys. Doing so causes the XP operating system to recreate shell entries for those two keys. If this is not done, the next step does not work correctly. Step 2: Install TCP/IP over top of the existing installation: Open the properties window of the network connection. Start --> Connect To --> Show All Connections --> Right-click the Connectoid --> Click Properties --> Select the Networking Tab Click Install Click Protocol Click Add Click Have Disk Type the path to the nettcpip.inf file and click OK. This should either be: c:\windows\inf or c:\winnt\inf (if you click browse, then attempt to browse to the \inf folder, it may not show up in the list as it is a hidden directory) You should now see "Internet Protocol (TCP/IP)" in the list of available protocols. Select it and click OK. Restart the computer If you have any third-party firewall programs, content restriction programs or other similar pieces of software these will probably need to be reinstalled after performing this fix as it'll almost certainly break em. This should probably be a FAQ (if we have such things anymore). |
ninja (1671) | ||
| 309203 | 2004-12-31 07:07:00 | yes. sometimes if spyware isn't removed correctly it can cause loss of internet which with XP is not always an easy thing to fix. Charming. Would have thought the writers of these things would have included that facility ,I mean to say! :groan: |
Cicero (40) | ||
| 309204 | 2004-12-31 07:57:00 | Charming. Would have thought the writers of these things would have included that facility ,I mean to say! :groan: writers of CWShredder or the spyware ?? its really an MS problem. they build tcp/ip hard in so you can't get rid of it, fixit, or reinstall it. so when it gets broken it can be a major to fix. fortunatly theres several work arounds which most of the time will work. |
tweak'e (69) | ||
| 309205 | 2004-12-31 09:00:00 | writers of CWShredder or the spyware ?? its really an MS problem. they build tcp/ip hard in so you can't get rid of it, fixit, or reinstall it. so when it gets broken it can be a major to fix. fortunatly theres several work arounds which most of the time will work. If you are going to write for M/S OS wouldn't you take that into account? You must concede that Bill is a genius,the fact that all these twerps dedicate there lives to undermining his system can't be blamed on him,can it? |
Cicero (40) | ||
| 309206 | 2004-12-31 09:40:00 | If you are going to write for M/S OS wouldn't you take that into account? ????? what are you referring to? cws and other spyware are often desighned so they can't be removed. they are very close to being virus's. you can blame MS for making XP so hard to fix, unlike earlier MS os's in which its easy to reinstall tcp/ip (and/or networking) |
tweak'e (69) | ||
| 309207 | 2004-12-31 10:11:00 | ????? what are you referring to? cws and other spyware are often designed so they can't be removed . they are very close to being virus's . you can blame MS for making XP so hard to fix, unlike earlier MS OS's in which its easy to reinstall tcp/ip (and/or networking) What else has been discussed here apart from cws and adaware?? I have to rely on commonsense here as apposed to an understanding of how M/S OS system works,you seem to suggest that Bill and his team think,how can we make it difficult for people to fix what these blighter's get up to . I am sure you are knowledgeable chap,but would you stand up to the sum of M/S . |
Cicero (40) | ||
| 309208 | 2005-01-01 02:25:00 | afaik all ms os's, untill xp, it was easy to repair the networking should any problems arose. there has always been problems requireing the networking to be fix, spyware related or not. i have no idea why MS has made so difficult to repair tcp/ip in XP but considering MS usuall style of intgrateing things (which always makes it harder to fix anything) its not to suprising they have done that. | tweak'e (69) | ||
| 1 2 | |||||