Windows XP for Home Users, Service Pack 2 Edition

2017-07-07 02:10:07

Now that the preliminaries are out of the way, let's get down to the main event.

You have a problem, and you need it fixed!

The following sections present the most common Windows-related problems you're likely to encounter. I've provided some advice on the probable causes of each problem, and the steps you can take to fix the problem.

I can't guarantee that I've presented every possible problem or solution. I only hope that your particular problem is included, and that my advice is sound!

Your Computer Doesn't Start You Hear No Noises and See No Lights

(To be fair, this isn't likely to be a Windows-related problem. I'm presenting it here just to be helpful!)

First things first don't panic!

Now, very calmly, look at the back of your system unit. Is the power cable plugged in to the right connector? Follow the power cord to the other end. Is it firmly connected to a power outlet? Check the wall switch. Is it turned on? Walk to your fuse or circuit-breaker box. Is the fuse good or the circuit breaker set? Go back to your computer. If it still isn't working, unplug the computer and plug in something that you know works a lamp or a radio, perhaps. If the appliance doesn't work, you have a bad power outlet. If the appliance does work, you really do have computer problems.

If you're positive that your computer is getting power and that you're turning it on correctly, you probably have a hardware problem. The most likely suspect is the power supply in the system unit. To determine the culprit and fix the problem, however, you'll need to call in professional help. Take your system to a certified repair center and let its technicians get to work.

Your Computer Doesn't Start, But It Makes the Normal Startup Noises

(Also not likely to be a problem caused by Windows but it's still important enough to mention here.)

If your system is making noise, at least you know that it's getting power. Because you can rule out a bad power cord, the most common things to look for are poorly connected cables or a nonfunctioning monitor.

Begin by checking your monitor. Is it turned on? Is it plugged into a power outlet? Is the power outlet turned on? Is the monitor connected to the correct port on your system unit? Is the connection solid? Is the connection solid in the back of the monitor? Are the brightness and contrast controls turned up so that you can actually see a picture?

If everything is connected and adjusted properly, you might have a monitor that needs repair. Is the monitor's power light on? If not, your monitor may have power supply problems that need attention from a professional. If your monitor's little green light is on but nothing shows onscreen, the video card in your system unit may be loose or set up incorrectly. Turn off your system, open the computer case, and check the video card to make sure it's installed, seated, and connected properly.

It's also possible that your keyboard isn't plugged in properly, or that you have some other internal problem that causes your system to halt during start-up. Check all your connections before you try rebooting.

Your Computer Starts, But the Monitor Displays an Error Message (Before Loading Windows)

(The last non-Windows problem, I promise. How do I know this isn't caused by Windows? Because Windows hasn't loaded yet, that's why!)

Your system uses error messages to communicate with you when it encounters certain problems. Table 25.1 details some of the most common error messages you may encounter on startup (before Windows loads), their causes, and how to fix each problem.

Table 25.1. Startup Error Messages
Error Message	Causes/Solutions
Non-system disk or disk error Replace and press any key when ready	You see this message when you have a nonbootable disk in drive A. (Assuming your system has a floppy disk drive A, of course.) Check the floppy disk drive and remove the disk, and then press any key to restart your computer using your hard disk drive.
Keyboard error, press F2 to continue	It sounds kind of silly to ask you to use your keyboard to confirm that your keyboard isn't working, doesn't it? This message is generated when the rest of your system works but the PC can't find the keyboard. If you receive this message, your keyboard prob ably is disconnected, has a loose connection, or has a stuck key. Check the connecting cable (at both ends) and reboot. If you still receive this message, you have a keyboard problem. Verify this fact by plugging in a keyboard from a friend's machine. If you do have a keyboard problem, it's probably cheaper to buy a new keyboard than to get your old one fixed.
File allocation table bad, drive x:	This message is not good. Something has messed up your FAT (File Allocation Table), the part of your hard disk that holds vital information necessary for your system to operate. One of the most common causes of this problem is a computer virus. Another cause is some sort of physical damage to your hard disk, caused by contaminants or plain old wear and tear. If you have actual physical damage to your disk, you may need to use a third-party utility program, such as Norton Disk Doctor, to repair the damage or you may want to drop back ten and punt by letting a technical professional handle the situation from here.
General failure reading drive x General failure writing drive x	These very serious messages mean that something is wrong with your computer but it has no idea what the trouble is. Try shutting down your system for a few minutes and then rebooting; sometimes this message is generated when your system gets a little cranky. More likely, however, is that you have something seriously wrong with your hard disk, which means it's time to hop in the car and drop off your PC at your local computer repair center. The pros there have diagnostic software and equipment that can pinpoint problems much easier than you or I can.
Invalid drive specification Drive not ready	Either of these error messages indicates that you're having problems with the drive you're trying to boot from. If you're booting from a floppy disk drive, your bootable floppy may be bad. Try using another bootable disk. If you're booting from a hard disk drive, the problem may reside in the drive mechanism itself. Sometimes an older drive can operate too slowly to always boot properly; try rebooting your system. If the problem persists, have a professional check out your system. The drive in question may need to be replaced.
CMOS RAM error	This message appears when something is bad in the setup held in memory by your system's CMOS RAM chip. (This chip holds important system information in permanent, battery-powered memory.) When you see this or any similar message, you are given the opportunity to press the F1 key to continue. Do this, and adjust your CMOS setup accordingly. (See your system's documentation for information on how to do the latter.) If this message persists, you may have a dead CMOS battery; see your repair center to replace the battery.
Memory size error Memory size mismatch Not enough memory Insufficient memory Parity check xxx Parity error x	Any of these messages indicate that something is wrong with your computer's memory. Your CMOS setup may be incorrect, or you could have some bad or improperly seated memory chips. It's also possible that you recently added extra memory to your system and it isn't configured correctly. If this is the case, enter your CMOS setup menu and reconfigure your system for the new memory. If you can't fix this problem via the setup rou- tine, you should probably consult a computer professional for further assistance.

Your Computer Starts, But Windows Doesn't and You Receive an Error Message

(Okay, this one really is a Windows problem!)

If Windows doesn't load if your system, after the standard boot procedure, just "hangs" in place then there is probably something wrong with the way Windows is installed or configured. This typically happens after you add something new (hardware or software) to your system. The new thing changes the settings to a configuration that doesn't work.

It's also possible for Windows to have trouble loading even when you've done nothing new or different to your system. Even the 32-bit Windows XP can be finicky at times, and can surprise you with what it does or doesn't do.

If you receive an error message while Windows is loading, it's likely that Windows is trying to load a bad or incorrect device driver of some sort. In fact, the error message will more often than not tell you exactly which driver it's having trouble with. After you know which driver is causing problems, you can either reinstall that driver, or eliminate that driver from the loading process by using the options in the System Configuration utility.

If the error message doesn't tell you which driver is causing the problem, you can determine that yourself by using the System Configuration utility to perform a selective startup. Restart Windows in Safe mode, then run the System Configuration utility and follow the instructions I gave earlier in this chapter.

If you'd rather not go through the entire selective startup business, just launch the System Restore utility. Choose to restore your system to some prior restore point, and get on with your business. (Of course, you might not figure out what was actually causing the problem but at least you'll be up and running!)

Your Computer Starts, But Windows Doesn't and You Don't Receive an Error Message

What if you can't load Windows and don't receive an error message? In this instance you want to start Windows in Safe mode, and then disable any other programs that may be loading when Windows starts up. Click the Start button and select All Programs, Startup. Use your mouse to move all items in the Startup menu to another menu (any menu will do, as long as you remember which one it is!). Now restart Windows and see what happens.

If Windows now starts properly, that means that one of the programs that used to start up when Windows started is causing you problems. One at a time, drag those programs back to the Startup menu (using the same procedure as before), then restart Windows. Each time Windows starts properly, you know that particular program is okay. When Windows doesn't start properly, you know that particular program is a problem so leave it out of your Startup folder.

If, on the other hand, removing the programs from your Startup folder didn't fix your problem, then you have a problem with a specific device driver. If you're technically minded (and very patient), you can use the System Configuration utility's startup diagnostics to try and isolate the problem driver.

A better bet is to run the System Restore utility and restore your system back to an earlier state presumably before you installed or updated the driver that is causing your problems.

If even this doesn't work, it's time to reinstall Windows. If you have a Windows XP installation CD, use it. If your computer manufacturer provided some sort of hard disk-based complete system restore utility, use that instead. If you don't have any type of Windows installation or restore disks or utilities, contact your computer manufacturer's tech support department and ask them how the heck you're supposed to restore Windows without any disks or utilities. (This is a particular beef of mine, sorry.)

And if restoring Windows doesn't fix your problem, then it's definitely time to contact a technical professional.

Your Computer Starts, But Windows Doesn't and You Can't Enter Safe Mode

Sometimes Safe mode isn't safe enough. Any number of conditions can cause Windows not to start in Safe mode:

Your system is infected with a computer virus. You may need to reinstall Windows to eliminate the effect of the virus, then use an antivirus program to initiate a more complete cleansing of your system.

Your computer's CMOS settings are incorrect. During boot-up, check your CMOS settings, and make corrections as necessary. If your CMOS battery is weak and not holding its settings, replace the battery.

You have a hardware conflict. Some device in your system is conflicting with some other device; the most common conflicts are IRQ conflicts. Ask a technical professional (or just an old geek who knows how to use DOS) to hunt down the errant device with the Safe Mode with Command Prompt option.

If you have persistent problems starting in Safe mode, try choosing the Last Known Good Configuration startup option. If even this doesn't work, you may need to reinstall Windows XP from scratch.

Your Computer Starts, and Windows Enters Safe Mode Automatically

Windows starts up in Safe mode automatically when it senses a major driver problem or conflict. Follow the steps in the "Your Computer Starts, But Windows Doesn't and You Receive an Error Message" section to track down the source of the problem. (Or just launch System Restore and restore your system to some prior condition.)

Your Computer Starts, Windows Starts and So Does Another Program or Utility That You Don't Want to Start

Many programs, when first installed, have the audacity to think that you want them to run whenever you start up your PC. So they configure themselves to launch when Windows launches whether or not you want them to.

If you want to stop a program from launching automatically when Windows starts, you first have to find out from where it is being launched. The first place to check is the Startup menu. Click the Start button, then select All Programs, Startup. If the offending program is here, right-click it and select Delete from the pop-up menu. (This doesn't delete the program itself it just removes it from the Startup menu.)

If the offending program isn't in the Startup menu, it's probably being loaded via a setting in the Windows Registry. There are several keys in the Registry that can contain autoload instructions. If you find the offending program in any one of these, delete it!

Here are the keys to check, using the Registry Editor:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\ CurrentVersion\RUN

HKEY_USERS\DEFAULT\SOFTWARE\Microsoft\Windows\ CurrentVersion\RUN

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\ CurrentVersion\RUN

Windows Freezes Your System Unit Has Power, But Your Keyboard and/or Mouse Isn't Working

If no error messages appear onscreen but you can't type a thing, you probably face a simple problem: Your keyboard is unplugged. So plug it back in.

Same thing if your mouse quits working. Check to see if it's firmly connected, then try rolling it again.

In fact, you may have both your mouse and keyboard plugged in, but to the wrong jacks. It's all too easy to plug your mouse into the keyboard jack, and vice versa. (That's why many PC manufacturers are now color-coding their mouse and keyboard connectors and jacks.) Even if it looks like both your mouse and keyboard are plugged in, trace the cables to make sure they're not mixed up.

Of course, the solution might not be quite that simple. If replugging your keyboard or mouse doesn't work, you might have to reboot your computer to recognize the replug. (You'll probably have to turn off your system with the main power switch or button if you can't click or type, you can't exit Windows normally!)

If you still experience difficulties after rebooting, you actually may be the not-so-proud possessor of a bad keyboard or mouse. Try plugging in another keyboard or mouse to your PC, or your keyboard or mouse into another PC, to determine whether device failure is at the root of your problem.

Windows Freezes and Displays an Error Message

Windows XP can sometimes exhibit perplexing behavior. Computer people refer to this as "unstable" behavior. I prefer to call it "screwy."

When Windows freezes up, it sometimes displays some sort of error message. These messages are just nice ways to say that something (who knows what) has bombed.

More often than not, it's just your current program that has frozen, and not all of Windows. In this case you get a Program Not Responding error message. Try pressing Ctrl+Alt+Del to bring up the Windows Task Manager, and then manually shut down any unresponsive program.

If the error message you get is displayed on a blue screen (known in the industry as the "blue screen of death"), follow the onscreen instructions to get rid of the blue screen. You may have to press Enter to close the program causing the error, or press Ctrl+Alt+Del to reboot your computer. After you encounter the blue screen, your system typically gets unstable, so I recommend rebooting your entire system, even if you're able to close that particular program manually.

Blue screen messages are often caused when you start running out of space on your hard disk. This might sound odd, but Windows uses a disk cache to supplement conventional memory. (That's the virtual memory that I talked about earlier in this chapter.) If you don't have enough free hard disk space, Windows thinks that it's low on memory, and starts acting flaky.

The blue screen error messages also can be caused by errors on your hard disk. If you get a lot of these error messages, it wouldn't hurt to check for disk errors before proceeding.

Windows Freezes and No Error Message Appears

Sometimes Windows freezes without displaying an error message. One of two things has happened: (1) Windows itself has locked up, or (2) Your current Windows application has locked up.

In either case, the solution is the same: Press Ctrl+Alt+Del.

If Windows itself has frozen, either nothing will happen or you'll start hearing a beep every time you press a key on your keyboard. In which case you'll need to press Ctrl+Alt+Del again to fully reboot, or you may have to turn off your PC at the On/Off button (or at the power source).

If, on the other hand, it's an errant program that freezes up, you should see the Windows Task Manager when you first press Ctrl+Alt+Del. Select the "not responding" program and click End Task. If and when the Wait/Shutdown dialog box appears, go ahead and shut down the offending program.

If the Task Manager doesn't appear, or if you try to shut down a program but your system is still locked up, it's time to fully reboot by pressing Ctrl+ Alt+Del twice in a row.

What causes Windows to freeze? There can be many different causes of a Windows freeze, including the following:

You may be running an application that isn't compatible with Windows XP. If so, upgrade the program.

You may not have enough memory to run Windows effectively. Upgrade the amount of RAM in your PC.

A memory conflict may exist between applications or between an application and Windows itself. Try running fewer programs at once, or running problematic programs one at a time to avoid potential memory conflicts.

You may not have enough free hard disk space for Windows to use for temporary files. Delete any unnecessary files from your hard drive.

Your hard disk may be developing errors or bad sectors. Check your hard disk for errors.

If your system crashes or freezes frequently, call in a pro. These kinds of problems can be tough to track down by yourself when you're dealing with Windows.

Windows Won't Let You Exit

The most common cause for this situation is that you have a misbehaving program. Try closing all your open programs, one at a time. If any individual program is frozen, use Ctrl+Alt+Del to close that "not responding" program.

Beyond a single misbehaving problem, a number of things can cause Windows to not shut down. Believe it or not, one of these things can be a bad sound file! It's that sound you hear every time you go to shut down Windows. If that file is corrupted, the shutdown sequence stops there, leaving Windows running. To fix this problem open the Control Panel and select the Sounds and Audio Devices icon. When the Sounds and Audio Devices Properties utility appears, select the Sounds tab, then pull down the Sounds list and select None. Now click OK and try shutting down your system again. (If you do have a corrupted sound file, you can reinstall this particular file from your Windows installation CD.)

It's also possible that Windows Power Management technology is keeping you from closing Windows. Disable Power Management by opening the Control Panel and selecting the Power Options icon. When the Power Options Properties utility appears, select the Power Schemes tab, pull down the Power Schemes list, and select Always On. You can even go the extra step and configure each setting to always stay on.

If you still can't shut down Windows after trying all these actions, there is probably a "fragment" of a program still running somewhere in your system's memory. It's near impossible to track down that fragment. Instead, you need to reboot via the double Ctrl+Alt+Del procedure.

Windows Won't Wake Up from Standby Mode

What do you do when Windows doesn't wake up from standby mode? Normally you "wake up" your computer by moving your mouse, or pressing any key on your keyboard. Some keyboards have special "wake up" keys that need to be pressed to exit sleep mode. In any event, if you move and click your mouse a bit and then type furiously on your keyboard and Windows stays fast asleep, you have problems. (Make sure, however, that your monitor is actually plugged in and turned on. A switched-off monitor looks suspiciously like standby mode!)

The solution here is to reboot your computer somehow. Try the Ctrl+Alt+Del method first. However, if your system is in a really deep sleep, it might not recognize any keyboard input. So you'll probably have to turn off your system at the main power switch/button, wait a few seconds, and then turn it back on again.

If you're using a notebook computer and this happens, you may have to remove all your power sources. This means unplugging the computer from the wall and removing the battery. Wait a few seconds, and then plug your notebook back in. That should do the trick!

Besides this type of oversleeping, standby mode can sometimes cause other problems. I've had standby mode screw up my video display (dropping me down to a lower-resolution mode!) and cause some programs not to run at all post-wake up. It's fair to say that I've found standby mode to be the most bug-ridden of all Windows features.

If you experience constant standby mode-related problems disable it! Go to the Power Options Properties dialog box, select the Power Schemes tab, and set every option so that all the parts of your computer will always be on. Then take the extra step and disable your system's screen savers, too. They're another big cause of wake-up problems.

It's possible that your system has a different kind of "sleep" function built into the PC's BIOS. If so, you'll need to enter the CMOS BIOS setup during system startup and disable the sleep mode there.

Finally, it's possible that your system woke up but your monitor stayed asleep! Yes, some monitors have their own sleep modes, and if they get stuck in that mode, you won't know whether or not your system is awake. It doesn't hurt to turn your monitor off and then back on (which definitely wakes it up!) just in case the sleep problem is the fault of your monitor, not your PC. (If this problem persists, of course, you may need to repair or replace your monitor.)

Windows Runs Slower Than Normal

TIP

I find that Windows XP runs best when you get up to 256MB of memory and even better when you have 512MB or more. Anything below the 256MB level can cause lots of problems, especially if you have multiple users logged in simultaneously.

The most likely culprit behind a system slowdown is memory or rather, the lack of it.

Are you running any new applications or upgrades of older applications that may consume more memory? Are you running more programs than usual at the same time? Are you running any programs in the "background" during a heavy computing session programs such as Windows Messenger or ICQ? Do you have any "hidden" utilities taking up space in the system tray? Any of these factors consumes more memory and forces Windows to slow down. If you're dissatisfied with the performance of Windows on your system, the answer is simple: Add more memory!

You Accidentally Deleted an Important File

Deleting an important file can be one of the most disconcerting errors you will make in the course of using your computer. How could you do that?

In Windows XP, all deleted files are temporarily stored in the Recycle Bin. To undelete a file in the Recycle Bin, select the Recycle Bin icon on your desktop, then when the Recycle Bin window opens, select the item you want to undelete and select Restore This Item from Recycle Bin Tasks panel.

If a file has been "permanently" deleted from the Recycle Bin, there still might be a way to bring the missing file back from the dead. You see, just because a file isn't accessible doesn't mean that it's been physically deleted from your hard disk. In fact, all deleted files continue to reside on your hard disk, although all reference to the data in the file allocation table (FAT) has been removed at least until the reference data has been overwritten by newer data. There are several third-party programs including Norton Utilities, my favorite that include special "undelete" utilities. These utilities will recover any existing data from the FAT that hasn't been overwritten and thus "restore" the deleted file to your hard disk.

You Can't Delete a File

You tried to delete a file, but it won't delete. This problem can occur for one of three reasons:

The file is currently in use by another program. Try closing that program and then deleting the file.

You're trying to delete a file from a floppy disk that is write-protected. If you're trying to delete a file on a floppy disk, slide the tab in the lower-left corner so that the hole is closed, then try the procedure again.

The attributes of the file have been set so that you can't delete it. Every file has multiple attributes. One such attribute makes a file read-only, meaning that you can't delete it or write to it. To change a file's attributes, right-click the file's icon and select Properties from the pop-up menu. When the Properties dialog box appears, uncheck the Read-Only attribute, then click OK.

You Attempt a File Operation and Get a Windows Error Message

Windows error messages often appear to let you know that you incorrectly clicked or typed something. So if you get such a message, the first action is always to try the operation again, more carefully this time. However, even when you do whatever it is you're doing more carefully, you can still get error messages. Table 25.2 (next page) presents those you're most likely to encounter when working with files.

Table 25.2. Windows File-Related Error Messages
Error Message	Probable Cause and Solution
Cannot find file	The most common cause for this message is that the file in question is either missing or corrupted. Use the Search utility to search for the file. Reinstall the file in question if necessary.
Cannot read from drive x	Windows is looking for a file on drive x: (probably drive A:) and there isn't a disk in the drive. Insert any disk to end the Windows look loop. If a disk is in drive x: and you get this error message, you either have a bad (or unformatted) disk, or something wrong with your disk drive.
Folder xxx does not exist	You have specified a folder that does not exist. Check the spelling of the folder and path name. You might also try selecting View, Refresh to refresh the file/folder display.
File already exists. Overwrite?	You're trying to create or save a file with a name that already exists. Windows is asking if you wish to overwrite the existing file. If so, answer yes. If no, answer no, and assign a new name to your file.
File is missing	When Windows loads, it tries to load any programs that are included in the Startup folder. This message is generated when one of these files no longer exists or has been entered incorrectly. Use My Computer to open the Startup folder and check all programs and associations, removing or editing those that are not correct.
Not a valid filename	You typed an invalid filename. Try again.
The specified path is invalid	You typed an incorrect path for a file operation. Check the path and retype the command.
Write protected disk	You're trying to perform a file operation on a disk that is write protected (probably a floppy). Change disks, or slide the write-protect tab into the down position.

A Particular Software Application Won't Run

Several factors can cause a Windows application to refuse to run:

The program may not be compatible with your version of Windows. Some older Windows programs are incompatible with Windows XP. If an older Windows application won't run and gives you an error message, you probably have an incompatible program. You'll need to upgrade this software to a Windows 2000 or Windows XP version or activate Windows XP's Compatibility Mode. Right-click the program's icon and select Properties, then select the Shortcut tab. Check the Run In Compatibility Mode option, then select another version of Windows that you know the program is compatible with. This will trick the program into thinking it's running on an older version of Windows, and might just fix your problem.

Your system may not have enough memory available to run the program. Try closing other Windows applications before you start this one, or try adding more memory to your system.

Your computer may not have enough disk space to run the program. Windows employs extra disk space as virtual memory. If there isn't enough free disk space available, you may not be able to run some programs. Try deleting unused files from your hard disk before you restart the program.

If you can't get a certain program to run, first be sure that the program is referenced properly from the menu item or icon you selected. Right-click on the item or icon and select Properties from the pop-up menu. When the Properties dialog box appears (see Figure 25.4, next page), select the Shortcut tab and note the file and path entered in the Target box. Now use My Computer to go to that location, and confirm that the target file actually is where it's supposed to be. If the target file isn't there, use the Search utility command to find the file, and then enter the correct location in the shortcut's Target box.

Figure 25.4. Use the Properties dialog box to be sure the right target file is referenced by any given shortcut or to run this program in Compatibility Mode.

If the file is where it's supposed to be but doesn't launch when selected, exit Windows, restart your computer, and try relaunching the program. This "fixes" your problem quite often, surprisingly.

If your program still doesn't launch, be sure that the program is installed correctly. If you have your doubts, uninstall the program (by selecting the Add or Remove Programs icon from the Control Panel) and then reinstall it. (You'd be surprised how many problems get solved by reinstalling the software!)

You should also be certain that this particular program is compatible with your computer's particular hardware configuration. Your machine may need more memory, a faster microprocessor, or a higher-resolution video card before your finicky new program consents to run on it.

If all else fails, consult the instruction manual or Web site for this particular piece of software, or call the software publisher's technical support line.

A Software Application Crashes or Freezes

Everything works fine, but then all of a sudden your software bombs!

Fortunately, Windows XP is an exceptionally safe environment. When an individual application crashes or freezes, it seldom messes up your entire system. You can use the Windows Task Manager to close the problem application without affecting other Windows programs.

When a Windows application blows up, follow these steps:

1.	Press Ctrl+Alt+Del.
2.	When the Windows Task Manager opens, select the Applications tab, and then select the application that is frozen from the list. Now click the End Task button.
3.	After a few seconds, a Wait/Shutdown window appears; confirm that you want to shut down the selected application.
4.	Click the End Task button.

This closes the offending application and lets you continue your work in Windows.

Some programs crash with annoying frequency in Windows. The causes are myriad and often difficult to pin down. They include the following:

Your system may have run out of memory. Try running the program while no other Windows programs are running, or add more memory to your system.

The program may be getting caught in a memory conflict with another Windows program. Try running the program by itself.

The program may be an older version that's incompatible with your version of Windows. Upgrade the program to its latest version, or activate Windows XP's Compatibility Mode for that program.

Windows was just feeling cantankerous. Start the program again and hope for the best.

You have a bug in your software or even a corrupted program file. If nothing else pans out, try reinstalling your program from scratch. If this doesn't fix the problem, call the knowledgeable folks at the software publisher's technical support line for assistance. After all, that's what they're there for.

If you have multiple applications that crash on a regular basis, the situation probably can be attributed to insufficient memory. See your computer dealer about adding more RAM to your system.

You Can't Launch a Document File

The likely cause for this problem is that the document's file type is not associated with a program type or with the correct program type. When you select a document file, it should launch the associated program, with the selected document preloaded. If, instead of launching the program, Windows displays the Open With dialog box, you need to select an application to associate with the file.

You also can associate files with applications manually. See Chapter 3, "Managing Files," for more information.

A Newly Installed Peripheral Doesn't Work

This could be one of a number of things. If you installed a new card, it may not be properly seated in the slot. You may not have all your cables connected properly. You may have broken something while you were diddling about inside your PC. You may have a bad part. You may not have completed the installation or setup. Windows XP might not have recognized your new hardware or may have installed the wrong driver by mistake. The driver installed may be corrupted, or may need to be updated.

Whew! That's a lot that can go wrong!

It's also possible that your system doesn't recognize your new component. Depending on what you installed, you may have to do one of several things:

Change CMOS settings (most common for memory and disk drives).

Load new drivers via the Add Hardware Wizard.

Adjust specific jumpers or switches on your motherboard or other specific component.

Remember, after you make any of these changes, you'll need to reboot your system in order for the changes to take effect.

The important thing to remember is to retrace your steps backward through your installation, and try to determine if everything was done correctly. If all else fails, call the technical support line for your new component, or consult with a technical professional.

After You Add a New Peripheral, Something Else on Your System No Longer Works Properly

This is probably caused by some sort of resource conflict between your new and old components. The most common resource conflicts involve IRQ and/or port settings.

The fastest and easiest solution to this problem is to run System Restore, and restore all your drivers and settings to a point before you added the new peripheral. You also can use the Device Manager to roll back a driver that you think may have been overwritten by the latest installation.

If you want to troubleshoot the cause of this problem, I'd recommend that you start by changing ports. (Many of these types of problems are actually port or IRQ conflicts.) If this doesn't fix it (or if you installed an internal device), you'll need to change IRQ settings for one or both of the devices in conflict.

Also know that conflicts can occur when devices hooked up to two nonconsecutive ports are used at the same time. In other words, if you have two devices trying to use COM1 and COM3 (or COM2 and COM4) simultaneously, both could freeze up. (I've had this happen with a mouse hooked up to COM1 and a modem hooked up to COM3.) If this is your problem, change the port for one of the devices.

Still, it's easier to restore your system and then work out these problems.

Your Computer Acts Oddly Soon After You've Downloaded a File or Opened an E-mail Attachment

What now? You've just pulled several files including a great new game from this new Internet site you found, and now your computer acts as though it needs to be decked out in an electronic straitjacket. It doesn't seem to have any problems with loose connections, incorrect settings, or excess line noise. In fact, your online session went without a hitch. So what's wrong?

Well, along with your nice new files, you have probably downloaded a not-so-nice computer virus! Any time you download a file, run the file, and then find your computer starting to do strange things (running more slowly, mysteriously losing files, displaying unusual messages onscreen), you may have accidentally infected it with a virus. If the symptoms seem to match, refer to the section on viruses in Chapter 11, "Managing Online Security."

You Can't Find Another Computer on Your Network

You open up My Network Places looking for another computer on your network, but it isn't there. Where did it go?

First, try looking a little harder. Click the View Network Computers link in the Network Tasks panel. This should display all connected computers.

If the missing computer isn't there, click the Search button in the My Network Places toolbar. When the Search Companion appears, enter the name of the computer, then click Search. If you don't know the name of the computer, enter an asterisk (*). This should search for (and then display) all the computers on the network.

If you still can't see the missing computer, it's time to check the obvious. Is the other computer turned on? (Sleeping computers don't show up on the network.) Is it connected to the network? (Double-check both ends of the cable.) If you're on an Ethernet network, are both your computers connected to the hub, and does the hub have power? If you're on a wireless network, is the other computer connected to a wireless adapter and is the adapter within receiving range of the wireless hub/router?

Here's another simple thing to try reboot your computer. For whatever reason, "lost" computers on a network will often get found when you reboot the computer that can't see them.

More basics: Have you run the Network Setup Wizard on the second computer? If not, run it now, from the Windows XP installation PC. (And don't assume that because your network worked pre-XP everything will show up after you install XP on your main PC. You'll probably have to run the XP Network Setup Wizard on all your networked PCs.) Try running the wizard again. (Sometimes it takes two tries to get everything recognized.) Now reboot both your PCs and see if they recognize each other.

Now for some serious troubleshooting. Open the Help and Support Center, click the Fixing Problem link, click Networking Problems, and then run the Home and Small Office Networking Troubleshooter. Chances are this will fix most simple networking problems.

You may have a bad network connection on either one of the two computers. To repair a host of connection problems, open the Network Connections utility (from the Control Panel). Right-click the problem connection, then select Repair from the pop-up menu.

If worse comes to worst, delete the problematic connection from the second PC, and then rerun the Network Setup Wizard to reinstall the network. You also may have to rerun the wizard on your host PC (to recognize the new PC).