iBook G4 (Mid 2005) User's Guide (Manual) - zZounds.com

iBook G4 (Mid 2005) User's Guide (Manual) - zZounds.com iBook G4 (Mid 2005) User's Guide (Manual) - zZounds.com

c3.zzounds.com
from c3.zzounds.com More from this publisher
03.07.2013 Views

5 Troubleshooting 5 If you have a problem working with your iBook G4, check here first for solutions and advice. When you experience a problem working with your iBook, there is usually a simple and quick solution. Be aware of the conditions that led up to the problem. Making a note of steps you took before the problem occurred will help you narrow down possible causes and find the answers you need. Note the following:  The applications you were using when the problem occurred. Problems that occur only with a specific application can indicate that the application is not compatible with the version of the Mac OS installed on your computer.  Any software that you recently installed, especially software that added items to the System folder. (Certain applications install extensions that might not be compatible with the Classic environment.)  Any new hardware that you installed, such as additional memory or a peripheral. You can also find more troubleshooting information in Mac Help and on the Apple Service & Support website at www.apple.com/support. Problems That Prevent You From Using Your Computer If the computer doesn’t respond or the pointer doesn’t move  Press Command (x)-Option-Esc to force a frozen application to quit. If a dialog appears, select the application you want to quit and click Force Quit. If you are working in the Classic environment, hold down the Option and Command (x) keys and then press the Esc key. Next, save your work in any open applications and restart the computer to make sure the problem is entirely cleared up.  If you are unable to force the application to quit, press and hold the power button (®) for a few seconds to shut down the computer. 61

5 Troubleshooting<br />

5<br />

If you have a problem working with your <strong>iBook</strong> <strong>G4</strong>, check<br />

here first for solutions and advice.<br />

When you experience a problem working with your <strong>iBook</strong>, there is usually a simple and<br />

quick solution. Be aware of the conditions that led up to the problem. Making a note of<br />

steps you took before the problem occurred will help you narrow down possible<br />

causes and find the answers you need.<br />

Note the following:<br />

 The applications you were using when the problem occurred. Problems that occur<br />

only with a specific application can indicate that the application is not <strong>com</strong>patible<br />

with the version of the Mac OS installed on your <strong>com</strong>puter.<br />

 Any software that you recently installed, especially software that added items to the<br />

System folder. (Certain applications install extensions that might not be <strong>com</strong>patible<br />

with the Classic environment.)<br />

 Any new hardware that you installed, such as additional memory or a peripheral.<br />

You can also find more troubleshooting information in Mac Help and on the Apple<br />

Service & Support website at www.apple.<strong>com</strong>/support.<br />

Problems That Prevent You From Using Your Computer<br />

If the <strong>com</strong>puter doesn’t respond or the pointer doesn’t move<br />

 Press Command (x)-Option-Esc to force a frozen application to quit. If a dialog<br />

appears, select the application you want to quit and click Force Quit. If you are<br />

working in the Classic environment, hold down the Option and Command (x) keys<br />

and then press the Esc key.<br />

Next, save your work in any open applications and restart the <strong>com</strong>puter to make sure<br />

the problem is entirely cleared up.<br />

 If you are unable to force the application to quit, press and hold the power button<br />

(®) for a few seconds to shut down the <strong>com</strong>puter.<br />

61

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!