Hard Light Productions Forums
Off-Topic Discussion => General Discussion => Topic started by: Kosh on August 14, 2006, 10:11:39 pm
-
Ok, last night my main computer decided to have some serious problems, namly after 5 minutes on the internet it would crap out saying that svchost.exe was having some problems and needed to close (which basically kills the internet). I am pretty sure this is just more bitrot problems, so I think it is time for a reformat.
The problem is that I am trying to find a way to back-up everything I want to keep. My CD-burner is broken, I don't have the time to fix it or the money to buy a new one. I was thinking about using a direct cable connection from that computer to this one, but the only cable I have is a UDP patch cable that came with the DSL modem. My question is, will this work or will I need to buy a networking cable?
EDIT: Crap, looks like bitrot isn't the issue. I'm also havin the same problem on this computer after I set up the DSL connection. The really wierd thing is that if I leave the error window open, the internet will continue to work for a couple of minutes. Anyone have any ides for this one too?
EDIT2: It seems that installing the ISP software will fix this problem, but I really don't understand why. I don't want to use it for a couple of reasons, so does anyone have any idea on how to make the windows networking stuff work?
-
Is it definitely a UTP patch cable and not a phone cable?
Assuming it is an RJ-45 UTP patch cable, you'll still need a crossover adapter to connect two computers with it. Such adapters are about 2 or 3 dollars.
Regarding the error: are you sure it's not a virus? Sasser is pretty rare now and the vulnerability has been patched, but it used to cause a problem like this in an unpatched or SP1 machine.
-
To fix this problem.
Format > Cut internet > WinXP fresh > SP2 > Turn on internet.
-
it sounds like you killed a neccisary service. what services have you disabled?
-
I haven't killed or disabled anything. It started doing that by itself.
This machine is a SP2 install.
Is it definitely a UTP patch cable and not a phone cable?
I'm not a n00b at this, of course I know that it is a UDP cable. I've just never done a "direct connect" before.
Regarding the error: are you sure it's not a virus? Sasser is pretty rare now and the vulnerability has been patched, but it used to cause a problem like this in an unpatched or SP1 machine.
If it was, then why does it work after I install the ISP softare and use their program?
-
actually this could be a bad driver for the network card, or a network card going bad
-
That doesn't explain why it works fine if I use the software my ISP provides.
-
Is it definitely a UTP patch cable and not a phone cable?
I'm not a n00b at this, of course I know that it is a UDP cable. I've just never done a "direct connect" before.
The use of 'UDP' instead of 'UTP' threw me. UDP is a network protocol. UTP is the most common type of ethernet cable.
Regarding the error: are you sure it's not a virus? Sasser is pretty rare now and the vulnerability has been patched, but it used to cause a problem like this in an unpatched or SP1 machine.
If it was, then why does it work after I install the ISP softare and use their program?
Damaged files being replaced by the installer.