Clues reveal themselves!
May. 28th, 2009 09:09 am![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
kirby1024So, after This post, I'd almost written off my computer, until, when I turned it on on Monday, it seemed to miraculously recover, as if nothing was wrong with it at all. That is, of course, terribly frustrating - so bloody typical for a computer to start working just after you yell to everyone that it's stopped working.
But it turns out that it's not quite fixed. After a bit of twiddling around, I made the discovery that if I boot up the machine with the network cable unattached, it works perfectly, even if I plug the network cable back in. If I boot with the network cable attached, I get the problems again. In the lull of problems, I scheduled a scandisk of both drives, and they both reported mostly okay, except for one or two bad sectors on my non-primary drive. I then let it boot with the network cable attached, and the problems remain, so it's clearly not a hard drive issue at all.
I'm fairly certain now that the problem is a program that's getting stuck with some internet action at startup, but at the moment I'm not really sure what that program is. Will have to do some more probing. On the plus side, I at least have a workaround, even if that workaround turned out to be very painful and mildly bleedy this morning (note to self: Backs of computers can be very sharp, so be careful when plugging stuff in!)
But it turns out that it's not quite fixed. After a bit of twiddling around, I made the discovery that if I boot up the machine with the network cable unattached, it works perfectly, even if I plug the network cable back in. If I boot with the network cable attached, I get the problems again. In the lull of problems, I scheduled a scandisk of both drives, and they both reported mostly okay, except for one or two bad sectors on my non-primary drive. I then let it boot with the network cable attached, and the problems remain, so it's clearly not a hard drive issue at all.
I'm fairly certain now that the problem is a program that's getting stuck with some internet action at startup, but at the moment I'm not really sure what that program is. Will have to do some more probing. On the plus side, I at least have a workaround, even if that workaround turned out to be very painful and mildly bleedy this morning (note to self: Backs of computers can be very sharp, so be careful when plugging stuff in!)
