This guide is intended for people who are reasonably computer literate (i.e. can navigate folders, use common programs, and generally know basic skills) but who are not necessarily experts.
Something important to note is that professional Technical Support people are usually provided by the makers of most commercial software products. They are always a great resource. This guide is intended for people who are trying to figure out the problem on their own, either because the technical support was incompetent (hopefully not the case), they just want to learn how to do it, or they simply don't want to call Technical Support unless they have to (sometimes because it costs extra money). Just keep in mind that they are yet another resource in trying to solve these problems.
Keep these things in mind while you're trying to figure out what's wrong. They apply to almost any problem.
Do NOT skip this part!!
Generally, people remember what steps they used to do to get something to work, and something's wrong when the same steps stop performing the desired action. Make sure that you are taking the same steps you used to take when whatever feature you're using worked, and that the same steps now fail to work.
Are you sure that this feature used to work? Are you sure you're accessing it the same way? If it never worked before (or you don't know), things are harder. Check instructions and online references to find out exactly how to set up whatever you're trying to use.
If it used to work and now it won't, well then continue on.
If it's something you've never used before, read the manual. The functionality (or apparent lack thereof) you're noticing may be a feature, not a bug, as the expression goes. See if you're using it the right way.
Computers don't spontaneously break. I can't emphasize this enough.
To understand better, It helps to know a bit about how computers work. Programs are generally like mathematical functions: a given input always results in a given output. Input can come from a variety of sources, including configuration files, the Windows registry (on Windows, of course), the operating system, and of course, user input. Output is usually what shows up on your screen, though it can also be files generated or printouts created. Theoretically, with the same environment (configuration) and user input, you will always end up with the same output. So if something suddenly stops working, one of these two has failed. We've already ruled out user input (see step one above!), so the configuration has changed.
Common causes for changes in configuration include (but of course are not limited to):
Editmenu. On Linux, this can be in any menu (or I just don't know enough to say which one is most common).
In my experience, people always say "I didn't change anything." Invariably, though, they missed something, because (as I said before) computers don't spontaneously break.
If you can figure out what has changed, see if you can reverse it (if you decide you want to), or (especially for upgrades and settings changes) search Google to see if there's a workaround for whatever problem you're having with the new version or different setting. (Do you see yet why Google is your friend?)
If you can't figure out what's wrong based on things you have recently changed, you have to start taking educated guesses and doing some research.
Although more and more software is coming without documentation, it is still
an essential tool to figure out what's wrong. If there's no hard-copy manual,
see if there's an electronic one. Especially for individual programs, there
should be a Help menu from which you can access an index or search
for what you're looking for. With Windows or Linux in general, it's not so easy,
although with the latter you can always try
to find out what programs do, and how to use them. Finally, try the developer's
website, which you can probably get by going to Help -> About <program
name>, or else searching google or even just guessing.
Often answers to frequently asked questions (FAQ's) are in the help system, whether it's a hard-copy manual, an electronic manual shipped with the software, or on the manufacturer's website. Many manufacturer's even have forums in which issues can be discussed, and answers found (this goes along with what will be mentioned about searching online). Unless you have some obscure problem, there may have been somebody else who has already experienced (and hopefully solved) your problem.
Despite their often cryptic nature, error messages can be your friends. Often a simple search on google (excluding very specific information, like filenames and the like, unless they are system files) of the error messages in quotation marks will yield lots of results. Many will be forums where people asked a question matching yours. These can be especially helpful (mostly the responses). Experts-Exchange is an especially common (and often useful) place to find such answers.
If you don't get an error message, or your searches turn up too few (or too many) results, try describing the symptoms. These searches usually are best not in quotation marks, because you can use keywords that won't necessarily appear right next to each other. It's still a good idea to quote certain phrases (or even compound words) that you know should be near each other, e.g.
"hard drive" respond slowly after
"right-click" windows xp
sluggish response to right-click windows
I used these search phrases to find out why my computer started behaving very slowly after right-clicking documents. It took several different searches using various combinations, but I eventually found some answers (though I still haven't fixed the problem completely - one of the only ones that continues to plague me....).
It helps to include the program name and/or the operating system, if applicable.
Even hardware names are useful, if it's related to that, e.g.
Stealth 3 s540 causes "illegal exception".
Sometimes you can find exact answers to your questions, in which case you're all set. More often, though, you'll get vague responses that will point you in the direction of some solutions, or at least give you ideas for more search queries. It's hard to give specific advice, because I'm trying to keep this document relatively general. Try things you think might work, especially if you're pretty sure you can reverse the changes if you have to. Keep track of what you change so that you can easily go back and restore things to the way they were.
Good luck with solving your problems. For questions and comments about this guide, feel free to email me, but please understand that I cannot help you with fixing individual computer problems.
Back to Computing and Security Info
Back to Phoenix Web Home.
© 2003 Dave
Last updated 2003-09-16