3
Comprehensive Tests
The comprehensive test probes for the same items as the Quick Test, but in greater depth. In addition, it identifies
the keyboard and mouse, the COM1 and COM2 ports, the LPT port, the floppy drive, and the onboard video
controller with its memory. The system will identify drives attached to any SCSI controllers in the system, not just
the onboard controller.
When running the quick test, verify that the configuration that is displayed following the probe includes all of the
hard disks, memory, and processors that are installed in the system. If the configuration does not identify all of
these items, exit by pressing
<CTRL+BREAK>
and review the troubleshooting section later in this document.
An example of a comprehensive test configuration is shown below in the
Using the Intel Server Board Platform
Confidence Test
section.
The tests executed are a superset of the quick tests. The processor floating point unit (FPU) is tested and more
extensive tests are run on the memory and cache. Extensive tests are also run on the onboard peripheral controllers,
integrated components, and the chipset.
The test duration is dependent on the number of processors and the amount of memory installed. With a 800 MHz
processor and 64 MB of memory the comprehensive test will run to completion in about 2.5 minutes. Each
additional 64 MB adds about 2 minutes to the test time. The video tests drive the monitor using what appears as
random test patterns.
On completion of the test and after the test results are displayed, the program returns to the main menu.
Comprehensive Test with Continuous Looping
The comprehensive test with continuous looping is identical to the comprehensive test, but it continuously loops
through the tests until the user presses
<CTRL+BREAK>
. This mode of operation will help to identify
intermittent failures in a Field Replaceable Unit. When the test is halted, the normal comprehensive test result
summary is displayed, but the status reflects the sum of all tests. Therefore, if a test failed one or more times during
the run, it will be reported as failing. The number of times the test cycle was repeated is displayed in the result
summary screen.
