Log in

No account? Create an account

Previous Entry | Next Entry

Computer Hell

It's About Time for Some Computer Hell

I have not had any severe computer problems for quite some time, so apparently I am due.

It started yesterday when my son Paul told me that his system was flaking out, crashing frequently. I took a look at the system and we tried running Spybot and Ad-Aware. The former found some things that we removed, but Ad-Aware kept crashing in the middle of checking.

So, we decided to put a new hard drive in the machine with a fresh install of XP. I bought a new 160GB drive and planned to copy everything from the 120GB drive on my own desktop computer to the new drive, and then wipe away the 120GB drive and put it in Paul's computer. I started the WDC Data Lifeguard program for copying disks and let it run.

After about 4 hours it was almost finished, but we got a sudden, freak thunderstorm that knocked the power out briefly three times in a time period of about 10 seconds. All of the other computers in the house recovered from the blackout no problem, but my desktop would not boot. It got to through the black Windows XP loading screen, moved to the blue XP sign-on screen, and just hung there. I saw occasional bursts of activity on the hard drive from the indicator light, so I hoped that maybe XP was smart enough to resume the copying process that had been interrupted. So I let the system run all night. In the morning it was still hung there.

Next it was research time. I did not find a description that matched my specific problem, but found one web page dealing with a hang-on-bootup issue that recommended repairing the XP with the XP CD console. So I ran the repair console and hoped that the process would replace only defective files. Nope. It performed a full re-install, back to the original version of XP, which meant I would have to upgrade to SP2, re-do all of the security updates, etc.

So, I waited for 40 minutes for the install to finish, and then went to Windows Update. The update process hung, no matter what I tried. Plus, Adobe Acrobat kept popping up, telling me it wanted to install something, and then giving me error messages. So I uninstalled Acrobat. Further research indicated that my hard drive letter had been changed from C: to E: and that this was a possible cause of the update failure.

Next step, changing the drive letter back to C:. I couldn't do it with administrative management tools because the drive was in use. I found a Microsoft page describing how to get around this by editing the registry, changing C: to Z:, E: to C:, and then Z: to E: and then rebooting.

On reboot, I was back to the hanging blue login screen.

Next step: Format the new drive from the XP setup CD and spend hours on the service pack and security updates.
Then, copying critical data files from the old to new drive.
Next, wiping the old drive clean.
A. Format old new drive from the XP setup CD in Paul's system and spend hours on the service pack and security updates, and drag important files from his old drive onto the newly installed one.
B. Spend hours reinstalling all of my programs on the new drive in my system.

At least A and B can be done simultaneously. So, we're probably talking about 12 or so hours of tedious work.


( 2 comments — Leave a comment )
Jun. 11th, 2005 03:43 am (UTC)
Computer hell
I hear you brother. My computer problems over the last several days are similar to yours--hours of tedious work. What a mess. I'm glad to hear that you have straightened things out.
Jun. 12th, 2005 11:10 am (UTC)
Re: Computer hell
Well, the last resort procedure was straightened out in my head, but the computer situation itself is not. I did a fresh XP install on the new hard drive and had planned to copy the important data files from the old drive to the new. First surprise: almost all of the files from the old drive were already on the new drive from the original disk copy process. I thought the crash would have corrupted them. This sounds like a good thing, but because the disk copy process did not complete, none of the program files are properly registered in the registry, so I can't run them. Result: a whole bunch of junk on the hard drive that I will have to sort through to decide what to delete, and then the long process of reinstalling all of these programs from scratch.

Reviving my own desktop was not as high priority for me as getting Paul's computer running again, so I ignored the work that needed to be done on my own computer for now. I deleted all but a few files on my old drive and hooked it up to Paul's computer to go through the XP reinstall and upgrade process. I flipped the power switch and -pop- the power turned on and instantly turned off. A couple more tries. The same thing. Paul has a bad power supply unit. Which is probably the real reason why his system kept crashing. Which means now I have to visit Best Buy for a new power supply unit.

Oh well, Paul was due for a larger drive and fresh install of XP anyway, so this will not be a total waste. Just a partial waste.

For a much more serious computer problem that involved betrayal and cover-ups, see this recent post by my friend, Gina: http://www.livejournal.com/users/avocadonumber/129433.html

I am so glad that I am not her father at this moment. I could easily imagine myself doing what he did, screwing things up royally with good intentions. I don't know if I would have lied the way he did, however. I'd like to think not, but in my life I have not always behaved as I thought I should and would.
( 2 comments — Leave a comment )