example, look at the list in table 2-1. These area fewexamples to get you thinking about problems. Look atthe condition and try to determine possible causes.Look in the documentation; it usually has a section thatlists conditions and possible causes. Ask the users whatprogram they are using. Ask the users what keys theydepressed and in what sequence. Ask what they weretrying to do. Always check for error messages. Checkany status information on the screen. You might want todevelop a separate list for each component or for eachsoftware package. You might add to the lists in thedocumentation. Diagnostic routines can also help youfind problems.DIAGNOSTIC ROUTINES.— Most microcom-puter systems come with online diagnostic routines.These are tests you run from the keyboard. They are inaddition to the diagnostic tests the system automaticallyruns when you turn it on. Your system will probablyprovide a disk read test, a keyboard test, memory tests,and a power-up test. The diagnostic program will tellyou what commands to use to perform each test, what tolook for, and how to stop each test.A major hardware failure could prevent the systemfrom being able to display error messages on the displayscreen.Should this happen, your microcomputersystem unit may have diagnostic light-emitting diodes(indicator lights) to help isolate the problem. Follow theinstructions in the owner/user manuals.Table 2-1.—Checklist for Identifying ProblemsSUMMARYIn this chapter on computer center operations, wecovered trouble reports, computer system output,environmental conditions, console operations, virusprotection software, AIS requests, and the medialibrary. This is but a sampling of what will be expectedof you as you enter the computer center. You will buildon this foundation with the skills you have and thoseyou will learn.2-35
Integrated Publishing, Inc. - A (SDVOSB) Service Disabled Veteran Owned Small Business
