 |
|||||
 |
|||||
 |
|
|
|
|
|
RELEASED AUGUST 22, 2007 |
||||
 |
||||
|
||||
 |
||||
|
|
|
|
|
 |
|||||||||||||||
|
|||||||||||||||
 |
|||||||||||||||
 |
 |
||||||||||||||
 |
|||||||||||||||
 |
|||||||||||||||
 |
|||||||||||||||
 |
|||||||||||||||
 |
|||||||||||||||
(front cover).......................................(back cover) |
|||||||||||||||
 |
|||||||||||||||
DETAILS
|
|||||||||||||||
|
|||||||||||||||
 |
|||||||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||
|
|
|
ABOUT THIS BOOK
"Macintosh Troubleshooting Efficiency" contains over 20-years worth of Macintosh problem-solving experience. This has included diagnosing and repairing computers owned by individuals as well as businesses.
In the beginning, the methods used to solve Apple ][ and Macintosh computer problems were to get involved with the "rocket science" and try to determine exactly what caused the problem. This usually took up a lot of time and when the dust cleared, the solution would typically be to reinstall the program or the Operating System or to adjust some general technology.
After many years of working this way, I began to wonder if there wasn't a better, more direct and reliable, way of fixing Macintosh problems. At about this time, I became an Apple Mass Market Representative in Asheville, North Carolina. One of my duties was to call on the large retail stores which carried Macs, such as Office Depot, Office Max, Best Buy, Montgomery Ward, Sears, Circuit City, etc. Setting up new Macs on the showroom floor, training the Sales Staff and answering customer questions was a common routine for me -- all of which I enjoyed.
If there were any technical questions or problems I couldn't resolve, I was to call a special Apple tech support number. These technicians knew they were speaking with Apple Reps and could therefore "cut to the chase" whenever they were helping us troubleshoot a problem.
During those years, I started to realize their problem-solving approach. Basically, they never got bogged down in the details of a problem. They simply asked questions so they could isolate the problem into a specific area. Once they knew the area, they prescribed the solution -- fix the area and solve the problem.
I then began using this same method whenever I was hired to solve a Macintosh problem.Over time, I realized almost all Macintosh-related problems could be isolated into various areas or compartments and the associated solution would be to correct that general technology or module.
When I began writing "Macintosh Troubleshooting Efficiency", I poured this experience onto the pages -- compartmentalizing the various problems. I then broke down the solutions into modules or technological areas. When I linked the Problems and Solutions together, I discovered that I had created a very valuable problem-solving chart. THIS is the heart of this book.
My Macintosh troubleshooting approach is so simple just about anyone can use it to solve their Mac's problems. If you know the difference between a "folder" and a "window", aren't afraid to connect a USB cable to your Macintosh, and know how to download files from Apple's web site, you can use this book.
Experts will probably just use my "Problems And Solutions Chart" as a memory jogger, when solving problems. Beginners will simply look up the problem in the "Problems" column of the chart, look in the "Solutions" column for the page number of the first solution and follow the steps. If the problem isn't solved, move on to the second solution and continue until the problem no longer exists. If you've gone through all the solutions for that problem, and the problem is still there, you'll be instructed to repair or replace that device. Since most problems are "software-based", this book won't have you taking apart your Macintosh. Of course, if you're comfortable doing this, the steps in this book will indicate when this will be necessary.
Another aspect of Macintosh troubleshooting, which this book will not force you into, is the use of Apple's "Terminal" program. This program allows typing of various combinations of letters and numbers which modify the Macintosh at a very deep level. A single accidental keystroke can cause a serious problem, such as erasing your entire hard drive. Based on my programming experience, and after hearing about some of the problems encountered by a few experts, I decided long ago to never use this program.
My main goal in creating "Macintosh Troubleshooting Efficiency" was to simplify Macintosh problem-solving and to help as many Macintosh users as possible to feel comfortable and empowered to solve their own Macintosh problems.
TABLE OF CONTENTS
Overview
Compartmentalize The Problem
Modules And Solutions
Fixing The Modules (pages 28 - 143)
What Caused The Problem?
What’s Connected To What?
Quick Fixes
Who To Turn To?
General Dos And Don’ts
Maintenance
Buying Advice
A Summary Of Contact Information About The Author Glossary Index
Click on the above image to see a sample page
PRODUCING THIS BOOK
We are very proud that "Macintosh Troublshooting Efficiency" is printed in the U.S.A. In fact, when you place your order through our Vantages store, only then is your copy printed. This means extra copies are not simply sitting around in a warehouse somewhere hoping to be purchased or waiting to be sent off to a land fill.
FROM THE AUTHOR
I wrote "Macintosh Troubleshooting Efficiency" because Macintosh users want to be empowered... They want to fix their own glitches but they don't want to get involved with all the "rocket science" which is normally required to diagnose and repair most Macintosh problems.
With this book, I've used my Macintosh troubleshooting experience to figure out the best and simplest approach to solving just about every Macinosh-ralted problem. I then created a type of problem-solving "road map" which will guide you through to solving the problem. What could be easier than looking up the problem on a chart and following the steps in the associated solutions? |
||
|
|
|
|
||
|
|
|
|
||
|
|
|
