Coffee Crone: Taming Coffee Blog

November 29 2006

The Geeky Way

After bragging that I hadn't had to rebuild my computer for eons, the universe got back at me. I was sitting on the couch with RT, watching TV and blowing my nose (yes, this cold may be with me forever), when, out of the corner of my eye, I saw my computer reboot. Huh?

I got up, logged in, and darn, right as Windows opened up, it happened again--only this time, it happened before it got to the log-in screen. RT and I did all the usual tricks (boot disk, safe mode, last known good configuration, bios crap) and nothing worked. Our diagnostic disks wouldn't even run.

Every time I would try again, the time between boot-ups decreased, until there was basically no time between them at all. This was on a machine that I knew to be free of both viruses and spyware, having done thorough scans for both earlier that day as part of my usual Monday routine.

The only changes I had recently made to the machine involved installing the updated java engine.

I finally gave in, and rebuilt the sucker yesterday. Even with a current back-up, a library of all of the programs I had installed over the 'net, a spread sheet with all of my license keys, and a task list that guaranteed that I wouldn't forget anything, it was an all day affair.

And as I did it, I wondered if it was just one of those off things that happen, or if something in how I set my particular machine up was incompatible with some update from Microsoft or the java engine and would just happen all over again. So far so good.

Because the order in which you install software matters in weird ways, I did it the smart way. I got all of my updates done (54 from Microsoft alone)before I started adding in programs. I also made sure I was running the latest versions of all the freeware, before installing. I then was very, very careful as I worked, creating restore points as I went along, cleaning out the extra bits leftover from installs before adding new things, and rebooting even when the program didn't require it.

Still, it's a crap shoot.

It also involves a level of skill that the average person shouldn't be expected to have.

As we travelled throughout Ontario visiting friends for the past two weeks, we spent a fair amount of time fixing things for our hosts. We installed hardware, set-up Email accounts, secured wireless networks, updated software, cleaned various infestations up--all the usual stuff Joe and Jane Geekfree run into and either avoid doing until they end up buying a new problem free machine, or shell out relatively big bucks to have someone like me come in and fix.

Digital life shouldn't be like that. And no, the answer is not a Mac.

posted by taming at 02:59 | link | comments (3)|
motimers subscribe to taming
Del.icio.us Mo'Tags: tech

Comments:

#1 29 November 2006 - 03:21

Excellent post. I now understand what a labor of love it is for my techie son-in-law to do anything for our computers. Every week, at least one of my students suffers from either a partial or total system failure. Today's college students have to do everything online, and many systems aren't compatible with the university system. Just yesterday, one of my genius students, who is a Mac user, told me what he has to do to complete my online assignments, which sounded like putting a square peg into a round hole. I asked him about compatible programs, and he told me it was a matter of independence; he would not change his system to conform with something he didn't believe in.

Twenty years ago, who'd have thought that our computing styles would be so indicative and reflective of our individual personalities and lifestyles?

InMyLife

#2 29 November 2006 - 04:02

We also visited my son in the US, who is a professional geek too. When I contrast the knowledge that we have, with the way most of our non-techie friends manage to just get by on-line, I get angry. On-line life should be pleasurable, and for way too many folks, it's just a pain in the bum.