Tag: computers

I’m glad the computer ‘Help Line’ doesn’t handle suicide prevention

Frustrated_man_at_a_desk_(cropped) Sometime between Sunday afternoon and Monday morning, my computer slipped from its normal “sleep mode” and into a deep coma. This became apparent after hitting the space bar and getting no reaction whatsoever, not counting a low-pitched whirring sound that — if I didn’t know better — I could swear was snoring.

Realizing there might be a serious problem, I gathered all of my computer troubleshooting experience and, over the course of the next 10 minutes, applied that experience by hitting the space bar no less than 400 times. When that didn’t work, I unplugged the computer and plugged it back in. Tried a different outlet. Switched keyboards. Wiggled my mouse. Considered finding a different occupation, preferably one involving explosives. I eventually realized the only thing left to do was call the Help Line listed in the service manual and hope someone there could either (a) talk me through this or (b) talk me down should our conversation move to the rooftop. Continue reading I’m glad the computer ‘Help Line’ doesn’t handle suicide prevention

Computer acting up? Backhand it with an anti-static wrist strap

It’s Sunday, which God reserved for rest, reflection and — I’m pretty it’s in the Book of… something — “Sunday Flashbacks on Ned’s Blog.” The fact that I am still typing proves He has a sense of humor. Or is quite possibly reading someone else’s blog. Either way, I’ll take it as an affirmation to reach back into the archives, to a time before Creation — at least in terms of this blog — when he looked upon what had been made and said in a mighty voice, “Meh.”

Today’s post is a column from 2004, when I was having some computer issues on a regular basis. On an unrelated note, I also got my gun permit about that time…

As a last resort, you may chose to place you computer on top of a trash receptacle and threaten it at gunpoint. Remember: Threatening the monitor is a waste of time. (And yes — sadly, this is a current photo of my computer system)
Today, we will be covering basic troubleshooting techniques for your computer. By the end of this column, you will know how to identify a problem within your system, and then determine whether you can:

a) Fix it yourself, or

b) Save yourself the trouble by taking your computer somewhere and shooting it.

To begin with, most of us have absolutely no idea how a computer works. This is illustrated by the fact that, when there’s a problem, we get really mad and yell at the monitor. This is sort of like yelling at the refrigerator because the container we thought was “Cool Whip” actually turned out to be refried beans left over from last year’s Cinco De Mayo party. Continue reading Computer acting up? Backhand it with an anti-static wrist strap

Monday should always start with a comatose computer

Frustrated_man_at_a_desk_(cropped) Sometime between Sunday afternoon and Monday morning, my computer slipped from its normal “sleep mode” and into a deep coma. This became apparent after hitting the space bar and getting no reaction whatsoever, not counting a low-pitched whirring sound that — if I didn’t know better — I could swear was snoring.

Realizing there might be a serious problem, I gathered all of my computer troubleshooting experience and, over the course of the next 10 minutes, applied that experience by hitting the space bar no less than 400 times. When that didn’t work, I unplugged the computer and plugged it back in. Tried a different outlet. Switched keyboards. Wiggled my mouse. Considered finding a different occupation, preferably one involving explosives. I eventually realized the only thing left to do was call the Help Line listed in the service manual and hope someone there could either (a) talk me through this or (b) talk me down should our conversation move to the rooftop. Continue reading Monday should always start with a comatose computer