|
|
To print: Select File and then Print from your browser's menu
-------------------------------------------------------------- This story was printed from ZDNet Australia. --------------------------------------------------------------
|
Tech Guide: Proceed with care By Rafe Needleman, ZDNet US July 26, 2005 URL: http://www.zdnet.com.au/reviews/software/soa/Tech-Guide-Proceed-with-care/0,139023360,139204108,00.htm
When your computer breaks down, think first before you try to fix it. As I wrote this article, Internet Explorer stopped working on my notebook computer. The program simply wouldn't start up. When I clicked Web links in e-mail, I got a File Save box instead of being taken to IE. It was one of those weird but typical, frustrating computer problems that many Windows users are accustomed to. Now, I've had problems like this in the past, and in many cases, my attempts to fix things have made things much worse. But I like to think that my relationship with Windows has matured and that I'm less likely today to try a rash fix (or a whole bunch of them) that would most likely make the situation worse. So before I dove into troubleshooting, I did a smart thing. And then I did a few more smart things. And you know what? I fixed the problem without making things worse. Here are a few troubleshooting tips I've learned along the way. And I think they apply to a lot of situations, not just fixing PCs. Disclaimer: These are my ideas, based on what I've learned over years of breaking things (for example, reinstalling Windows when the real problem was a software conflict between an old version of Laplink and a video driver). I can't possibly cover every situation, and of course I can't take responsibility for the outcome of following this advice. All I'm really suggesting is this: Fix your PC deliberately. Don't rush it. First, stop Think of your sputtering computer the way a pilot flying high over the ground treats the situation. You have some time to work on the problem. Use it to make yourself smart. Save your data and reboot What's the last change you made? If you've been mucking around and you just installed something, then uninstall it, reboot, and see if your problem still exists. Also, scan for viruses and especially spyware. Then, research Remember, though, that free advice is worth what you pay for it. You need to apply your own commonsense filter to what you read online. And if a fix sounds too involved for your skill level or the instructions are not clear (say, it's a complex registry fix that you have a problem visualising), you might want to remove it from your fix list. Regarding the solutions I found online: what I would have done as a younger man is to implement all of the solutions at once, figuring that if one fix is good, two or three must be better -- which is rarely the case. Make no sudden moves Don't start a fix you can't finish If you call tech support, be a nag There are good and bad tech helpers, and the good ones talk to you, and they move slowly if you ask them. They'll also start by gathering a history of your problem before they launch into a fix. If your helper sets up at your computer and says something like, "OK, let's start by reinstalling Windows," stop that person immediately. Would you want a doctor to operate, or even prescribe a medication, without taking a history? Likewise, when a telephone rep recommends that you start by reformatting your hard disk, have him or her back up and run through a checklist of other options. Better yet, find a more knowledgeable tech. Will it take more time? Yes. But do you want your computer fixed, or do you want to give it a lobotomy? I have no idea what caused my system to break in the first place, but the fix turned out to be the one at the top of my Google results, and it was no more involved than running a program that comes with Windows, the System File Checker. It was not an obvious repair -- I'd never used or even heard of the utility before -- so I did not have high hopes that it would work. But it did, and thanks to the fact that I did some research before I got to work and that I then tried the fix in isolation from other repairs, it ended up being a pretty innocuous problem. It took me about 15 minutes to research, and the System File Checker program ran while I was having dinner; when I came back to my computer, it was working again. If I had only worked like this in the past with other PC bugs, I probably could have saved myself from countless reinstallations of Windows. What's your preferred first step in fixing a Windows glitch? Note: "Buy a Mac" is not a fair answer. Talk back to me below!
Copyright © 2009 CBS Interactive, a CBS Company. All Rights Reserved. |