Filter
Top Products
3. Select the Audio Diagnostics from the main menu.
4. Select Tests from the menu bar and press Enter.
5. Select All tests from the pull-down menu and press
Enter.
Run options are set to test once and stop on error as
defaults. Other options can be selected by the
pull-down menu of Setting-up.
6. Follow the instructions that appear on the screen to
proceed with the tests.
7. If the tests end and no errors are detected, the “All
tests passed OK” message appears.
8. If an error is detected, the FRU code and error
description message appear. Go to “FRU Codes” on
page 220 and replace the FRU.
9. To exit from the test screen, press Esc.
Diskette Drive Test
Do the following to isolate the problem to a controller,
drive, or diskette. A scratch, write enabled, non-defective
2HD diskette is required.
Warning: Make sure that the diskette does not have
more than one label attached to it. Multiple labels can
cause damage to the drive or can cause the drive to fail.
1. Do the following to select the test device:
a. Select the advanced diagnostic mode and select
Tool;
b. Select the icon FDD-1 or FDD-2 and press the
space key.
A √ mark appears next to the selected icon.
Insert the blank diskette when instructed.
2. Run the diskette drive test.
3. If the controller test detects an error, FRU code 10
appears. Replace the system board.
4. If the controller test runs without errors, the drive
read/write tests start automatically.
5. If the drive test detects an error, FRU code 50 for
FDD-1 or 51 for FDD-2 appears. If the diskette itself
is known to be good, replace the drive.
6. If the drive is attached through a Port Replicator as
FDD-1 or FDD-2 and the test detects errors, move
the drive to the computer's diskette drive connector
directly, and test it again as FDD-1.
If no errors occur at the FDD-1 position, the drive is
not defective. Go to “Port Replicator Checkout” in
“Common Devices Checkout” section to isolate the
replicator problem.
7. If the drive is attached through an Expansion Unit, go
to the service manual of the Expansion Unit to isolate
the problem.
206 IBM Mobile Systems HMM