Repair manual

3-5
TROUBLESHOOTING
Command Line Arguments
Examples:
DP2DIAG 1 - run all of the diagnostics; test connectors are installed; parallel port 1 is connected
to the logic board.
DP2DIAG 1 10 - run all of the diagnostics ten times before pausing; test connectors are installed;
parallel port 1 is connected to the logic board.
DP2DIAG 1 20 1 - run diagnostic tests which do not require the test connectors twenty times before
pausing; parallel port 1 is connected to the logic board.
The first argument, which is required, indicates the parallel port which is connected to the logic board.
If this argument is omitted or the parallel port does not exist, a message is displayed and the diagnostics
will not execute.
The second argument, which is optional, is a loop count. Normally, all of the diagnostic tests are executed
and a message is then displayed which indicates that the tests are complete. At this time, the user must
hit a key to restart the tests. If a marginal problem is cropping up on a board, or if you would like to
exercise the board for an extended period of time, you can specify the number of times to loop through
all of the tests with this argument. If you enter 100, for instance, all of the diagnostic tests would be
repeated 100 times with no intervention required from the operator. The diagnostic, however, will pause
if a failure is detected.
The third argument, which is optional, indicates whether the logic board is currently in a complete system.
The later tests, which test signals on the logic board connectors, require special debug harnesses to
execute. If a logic board is in a system, these harnesses will not be plugged in. If this third argument
is non-zero, then the tests which require a debug harness will not be executed. If this argument is not
entered, or if it is zero, it is assumed that the debug harnesses are plugged onto the logic board.
Two more arguments can be used to force the testing of options which may be available. The fourth
argument, if present and non-zero, indicates that tests on the 512K buffer memory should be run. When
the diagnostics are started, a quick test is made to determine if the buffer memory is available. If the quick
test fails, then the assumption is made that the buffer memory is not plugged in, so that additional tests
on the buffer are not performed. With the fourth argument set to a value of 1, the 512K buffer tests are
always run.
The fifth argument, if present and non-zero, indicates that tests on the SCSI daughter board should be
run. When the diagnostics are started, a quick test is made to determine if the SCSI daughter board is
available. If the quick test fails, then the assumption is made that SCSI is not plugged in and further SCSI
tests are not performed. With the fifth argument set to a value of 1, the SCSI tests are always run.