March NewsLetter - Computer Feedback!

Should You Be Telling Us This?

Every now and then, I get email from somebody telling me that I tend to go a little overboard on the disclaimers; that I don't need to constantly tell everyone I'm not responsible for anything they do to their computers.

Of course, the liability protection is needed. And yet, I haven't had a lot of email from people complaining of computer problems as a result of something I've suggested.(Please don't start now). I know it happens! And it's going to, no matter how you learn.

On the other side of the coin, I do get some questions as to whether I should be making certain suggestions, or if I should be sharing my opinions with readers that may be new to computers. I know a wrong opinion (and I've had a few), or a mistake on the user's part(or mine), can result in computer pains. But come on, you have to start somewhere!

Here are a few of your comments:

"You shouldn't be telling people to use the Registry Editor, or showing them how to change the Registry."

Of course, this isn't the entire letter. The general message however, was that a mistake in the Registry can keep your computer from working properly. That you shouldn't be using the Registry Editor unless you know what you are doing, and that there is usually a better way to make the changes using 3rd party utilities or software.

These are valid points, and something I believe I have mentioned repeatedly. However, buggy software and hardware fixes may involve Registry changes, often provided by the manufacturer, which may involve manipulating values and adding or removing Registry Keys. Should you be learning how to move around the Registry, and use the Editor, when you are on the phone with technical assistance?

Yes, many utilities now offer safer means of changing certain entries in the Registry. And, if they're available on the particular computer you are working on, its best to use them. However, performing the same function by manually manipulating the Registry is an invaluable learning tool. That's why you'll see some Registry tweaks in this month's Tips & Tricks section.

I still find myself in the Registry when troubleshooting computers. Besides, understanding the Registry can give you some insight as to why things happen the way they do in Windows. For more info on the Registry, click here.

"Not everybody should be working inside their computer's case."

Not everyone should be lifting the hood on their car either, but if they are going to, then maybe they should learn some precautions and safety measures. For more on the inside of your computer, click here.

"Maybe you shouldn't recommend unconditionally updating drivers."

This was a tough one, because it holds a lot of merit. People often end up with trouble after downloading and installing updated drivers.

Several things can cause this:
Number one, downloading the wrong driver. Its easy to do. Maybe you've downloaded from the proper manufacturer, and chosen the newest driver for your internal 56K fax/modem, but did it say anything about 'voice'. Maybe you've now lost that capability.

Secondly, your new installed driver may not have kept the same configuration settings as the old one and you have to go through setup again. Or maybe the problem was with your old setup, and your old .ini or .cfg file is causing problems with the new driver.

Also, there could be the possibility that the new driver has a conflict with another driver/software/hardware already installed.

As I said in my NewsLetter, I still believe that your computer will tend to run smoother and more reliably when you keep your drivers updated.

I want to remind you that I always suggest making a single change at a time, and make sure your system is functioning properly before making the next change.

In other words, download a single driver, install it, reboot and check all the functions of that particular device before installing another update.

Also, you shouldn't try to install a new driver when the one being replaced is presently running. For example, if you're updating your video driver, it might be safer to do it in safe mode with a 16-bit generic VGA driver in operation.

"Maybe you shouldn't ask for questions if you don't plan on answering them."

I'm sure this came as a result of me saying I couldn't find the time to answer all the questions that I receive, and that you should post these questions in the forums. Unfortunately, this is true (and the very reason I set up the forums).

Most the time, responding to a technical question may take 10 minutes to a half hour, but usually results in 6 or 7 follow- up messages, over a period of days or weeks. I was receiving 20-30 of these emails a month! And my regular emails on top of that.

I beleive the only questions I ever asked for were questions on the Website or NewsLetter. Don't get me wrong, I enjoyed working with you on some of your technical problems, it just got to be more than I could handle, and I had to put a stop to it.

"Maybe some things are better off left for the local computer technician."

Absolutely true! But by learning what can and can't be done, and how to do it, maybe each person can be made aware of their own individual limits, and when they need to have their problems solved by someone else. Besides, some of our subscribers are your local computer technicians(should I mention the forum here again?).

In closing this section, I'd like to repeat myself again. You will not learn everything from a single source. In fact, you will not learn everything. I know my ideas sometimes differ with what you've read somewhere else. The suggestions you've read somewhere else, may not support another author. Sometimes you will have to make your own conclusions based upon differing or conflicting opinions or ideas. Try to err on the side of safety.

Return To March's Title Page
Return to Archives