User Guide

After running particular diagnostic tests and viewing the status messages generated by the tests in the result file, you can erase the contents of the file so that it is clear for the next set of messages generated. Otherwise, the next messages are added at the end of the previous ones in the file.

Output Device for Error Messages

Ordinarily, all error messages appear only on the screen. This parameter allows you to direct error messages to either a printer or a file, in addition to the screen. If you choose the File option, error messages are written to the result file used for status messages. This file is automatically created on a diskette that you insert into drive A when prompted. If you are running the diagnostics from a utility partition on your hard-disk drive, the result file is created on the hard-disk drive. If the result file already exists, new error messages are added to it.

To troubleshoot components or devices, run the appropriate test (test group or subtest) in the diagnostics on your diagnostics diskette. The diagnostics exercises the functional components and devices of your computer system more vigorously and thoroughly than they are exercised during normal operation. The diagnostics is organized by components into test groups and subtests within each test group. Each subtest is designed to detect any errors that may interfere with the normal operation of a specific device of the computer.

NOTE: Some subtests requiring hardware not listed in the System Configuration area of the diagnostics screen appear to run, but they conclude with a status message stating Component not present (or disabled).

The diagnostic test groups, their subtests, and comments concerning their use are listed in Table 2.

Table 2. Dell Diagnostic Test Groups and Subtests

RAM Test Group

The RAM Test Group subtests check all the directly addressable RAM.

The RAM Test Group program has parameters for the subtests that you can set: Test Limits and Options.

Three subtests are available for RAM: the Quick Memory Test, the Comprehensive Memory Test, and the Secondary Cache Memory Test. The Quick Memory Test performs an address check to determine whether the computer is properly setting and clearing individual bits in RAM and whether the RAM read and write operations are affecting more than one memory address location at one time. This subtest checks all available RAM. The Comprehensive Memory Test also performs an address check, as well as the following:

• Data pattern checks, to look for RAM bits that are stuck high or low, short-circuited data lines, and some data pattern problems that are internal to the memory chips

• A parity check that verifies the ability of the memory subsystem to detect errors

• A refresh check, to verify that the dynamic RAM (DRAM) is being recharged properly

The Secondary Cache Memory Test confirms the functionality of the computer’s cache controller chip and the cache memory.

Why Run a RAM Test?

Faulty memory can cause a variety of problems that may not, at first glance, appear to be happening in RAM. If your computer is displaying one or more of the following symptoms, run the subtests in the RAM Test Group to verify that the memory is not at fault:

• A program is not running as usual, or a proven piece of software appears to malfunction and you confirm that the software itself is not at fault. (You can confirm that the software is functioning properly by moving it to another computer and running it there.)

• Your computer periodically locks up (becomes unusable and must be rebooted), especially at different places and times in different programs.

• You get parity errors (any error message that contains the word parity) at any time during operation. These errors are usually accompanied by a reference to an address—the location of the portion of memory where the error occurred—which you should record on a copy of the Diagnostics Checklist.

System Set Test Group

The subtests in the System Set Test Group check the computer’s basic system board components and verify their related functions.

The subtests that constitute the System Set Test Group and the computer functions they confirm follow:

• CMOS Confidence Test

Checks the NVRAM for accessibility and reliability of data storage by performing a data pattern check and verifying the uniqueness of memory addresses.

• CMEM Confidence Test

Verifies the accessibility and reliability of the 8 kilobytes (KB) of RAM on the Extended Industry-Standard Architecture (EISA) Configuration RAM chip, which stores the EISA hardware configuration information. On systems without flash RAM, performs a data pattern and address uniqueness test.

NOTE: This test applies only to systems with an EISA bus.

• DMA Controller Test

Tests the direct memory access (DMA) controller and verifies the correct operation of its page and channel registers by writing patterns to the registers.

• Real-Time Clock Test

Confirms the functionality and accuracy of the computer’s real-time clock (RTC).

• System Timers Test

Checks the timers used by the microprocessor for event counting, frequency generation, and other functions. Only the functions that can be activated by software are tested.

• Interrupt Controller Test

Generates an interrupt on each interrupt request (IRQ) line to verify that devices using that line can communicate with the microprocessor and that the interrupt controllers send the correct memory addresses to the microprocessor.

• Reset Button Test

Confirms that the reset button works.

• System Speaker Test

Checks the functionality of the speaker by generating eight tones.

• Coprocessor Calculation Test

Checks the use of different types of numbers and the math coprocessor’s ability to calculate correctly.

• Coprocessor Error Exception Test

Verifies the math coprocessor’s ability to handle errors and to send IRQs to the microprocessor.

• PC Card Controller Test

Tests the functionality of the PC Card controller on the system board.

• Thermal Control Test

Checks the functionality of the thermal-monitoring and microprocessor speed-switching device on the system board.

• Multiprocessor Test

For systems with multiprocessors, confirms that the secondary microprocessor is operational.

• USB Register Test

Checks the onboard registers of the Universal Serial Bus (USB) interface. This subtest does not test USB peripherals.

• USB Memory Structure Test

Monitors the ability of a USB controller to process a simple set of memory-resident instructions.

Why Run a System Set Test?

The System Set subtests double-check many system board components, such as the computer’s input/output (I/O) circuitry, that are tested by other test groups or subtests in the diagnostics. You should run the System Set Test Group if you are having a problem and cannot isolate the failure or malfunction to a particular system board component.

The System Set Test Group also verifies the proper operation of other computer components, such as the speaker, that are not tested elsewhere in the Dell Diagnostics.

The following symptoms usually suggest a problem with a component or subassembly that warrants running a System Set subtest:

• A program is not running as usual, or a proven piece of software appears to malfunction and you confirm that the software itself is not at fault. (You can confirm that the software is functioning properly by moving it to another computer and running it there.)

• An option card you previously accessed can no longer be accessed.

• You get parity errors or page fault failures (any error message that contains the word parity or page fault) at any time during operation. These errors are usually accompanied by a reference to an address, which you should record on a copy of the Diagnostics Checklist.

• Correcting errors in the system configuration information in the System Setup program does not resolve a problem.

• The computer’s clock/calendar stops.

• The speaker no longer functions. The problem could be a failure of the system timers as well as a failure of the speaker itself. Run the System Timers Test, followed by the System Speaker Test.

• If a peripheral device appears to malfunction, run the Interrupt Controllers Test.

• A spreadsheet program or other type of mathematical application runs abnormally slow, generates error messages concerning calculations or operations, runs incorrectly, or generates incorrect results, or a proven piece of the program appears to malfunction and you confirm that the software itself is not at fault. (You can confirm that the software is not at fault by moving the program to another computer and running it there.)

• The computer periodically locks up, especially at different places and times in different programs.

• The computer halts in the middle of performing calculations or complex mathematical operations.

Video Test Group

The subtests in the Video Test Group verify the proper operation of the video controller and the video control circuitry installed in your computer. These subtests check for the correct operation of the readable registers in the video circuitry and the controller. They write, read, and verify data patterns in the cursor registers of the controller. The Video Test Group also tests all the video memory and provides additional subtests to test the color features of a color monitor.

The eight subtests in the Video Test Group confirm the following video functions:

• Video Memory Test

Checks the read/write capability of video memory in various video modes.

• Video Hardware Test

Checks the cursor registers and the horizontal and vertical retrace bit registers in the video controller.

• Text Mode Character Test

Checks the video subsystem’s ability to present data in text modes.

• Text Mode Color Test

Checks the video subsystem’s ability to present color in text modes.

• Text Mode Pages Test

Checks the video subsystem’s ability to map and present all available video pages on the screen, one page at a time.

• Graphics Mode Test

Checks the video subsystem’s ability to present data and color in graphics modes.

• Color Palettes Test

Checks the video subsystem’s ability to display all of the available colors.

• Solid Colors Test

Checks the video subsystem’s ability to show screens full of solid colors. Allows you to check for missing color subpixels.

Many of these tests display characters or graphics on the screen for you to verify. Samples of these screens are shown in "Diagnostics Video Tests."

NOTE: The default limit for testing super video graphics array (SVGA) modes is No. If you are testing an external monitor, change the default to Yes.

Why Run a Video Test?

Many of the symptoms that would prompt you to run a subtest in the Video Test Group are obvious, because the monitor is the visual component of your computer system. Before you run the Video Test Group or any of its subtests, you should make sure that the problem is not in your software or caused by a hardware change. You should also try running all of the software support utilities provided for the monitor and the video subsystem.

If the following symptoms still occur, run the appropriate test(s) as follows:

• If your monitor shows a partially formed or distorted image, run all of the subtests in the Video Test Group.

• If the alignment of text or images is off, regardless of the program you are running, run the Text Mode Character Test, Text Mode Pages Test, and Graphics Mode Test.

• If you have a color monitor or a program that runs in color, but the color is intermittent or not displayed at all, run the Text Mode Color Test, Color Palettes Test, and Solid Color Test.

• If your monitor malfunctions in one mode but works fine in another (for example, text is displayed correctly, but graphics are not), run the Text Mode Character Test, Text Mode Color Test, Text Mode Pages Test, and Graphics Mode Test.

Keyboard Test Group

The subtests in the Keyboard Test Group verify the correct operation of your keyboard and the keyboard controller chip.

The five keyboard subtests confirm the following keyboard functions:

• Keyboard Controller Test

Confirms the ability of the keyboard controller chip to communicate with the keyboard and the programming of the controller chip

• Keyboard Key Sequence Test

Verifies that the keys on the keyboard function correctly when you press the keys in a predefined order

• Keyboard Interactive Test

Checks the internal microcode of the keyboard and the external interface of the keyboard controller chip for a malfunctioning key

• Stuck Key Test

Checks the internal microcode of the keyboard and the external interface of the keyboard controller chip for a repeating key signal

• External Key Pad Test

Checks the contact beneath the key for an electrical impulse to ensure that the key is working properly

Why Run a Keyboard Test?

Keyboard problems are not always caused by the keyboard. For example, a complete lockup of the computer system, rendering the keyboard inoperable, is more likely caused elsewhere. There are three symptoms that are likely to be keyboard-related. Sometimes, the configuration of a program changes the function of a key or key combination. Likewise, key configuration programs such as ProKey can change a key’s function. Because these programs are memory resident, you should be sure to clear them out of your computer’s memory before running a subtest in the Keyboard Test Group. (Clear them from memory by booting your computer from the diagnostics diskette.) When these possibilities have been eliminated, and if the following symptoms occur, you should run one or more of the subtests in the Keyboard Test Group:

• When you press a key, the character represented by that key appears repeatedly; the key seems to be stuck. Run the Stuck Key Test.

• When you press a key and the response is different from the usual response or the response you anticipated, the key contact may be damaged. Run the Keyboard Interactive Test.

• When a key does not work at all, run all of the subtests in the Keyboard Test Group.

Mouse Test

The Mouse Test checks the functionality of the mouse controller (which coordinates cursor movement on the screen with corresponding movement of your mouse or touch pad) and the operation of the mouse keys/touch pad.

There are no subtests for the Mouse Test Group.

Why Run the Mouse Test?

Mouse or touch pad problems are as likely to originate in RAM as they are to be caused by a faulty mouse or touch pad. Three sources of RAM-related problems include the configuration of a program (which changes the function of the mouse or touch pad), memory-resident programs such as Sidekick or ProKey, and failure of a device driver (the software that controls the function of the mouse or touch pad). If these possibilities have been eliminated and the following symptoms persist, run the Mouse Test:

• When you press a mouse button or the touch pad, the function of the button (or touch pad) continues; that is, the button (or touch pad) seems to be stuck.

• If the response when you press a mouse button or the touch pad is different from the usual or anticipated response, the button (or touch pad) contact may be damaged.

• A mouse button or the touch pad does not work at all.

• The cursor does not respond on the screen in accordance with the movements you make with the mouse or touch pad.

Diskette Drives Test Group

The subtests in the Diskette Drives Test Group allow you to test both 5.25-inch and 3.5-inch diskette drives of all capacities.

The four diskette drive subtests available in the Diskette Drives Test Group confirm the following drive functions:

• Change Line Test

Checks for bent pins on the diskette drive controller and for defective lines on the diskette cable

• Seek Test

Checks the drive’s ability to search for a specified track on the diskette and to position its read/write heads to all tracks

• Read Test

Positions the read/write heads at each cylinder of the diskette for reading data and verifies that all tracks on the diskette can be read correctly

• Write Test

Positions the read/write heads at each cylinder of the diskette and verifies that all tracks on the diskette can be written to correctly

Why Run a Diskette Drives Test?

Very often, a diskette drive problem may first appear to be a diskette problem. A box of defective diskettes might produce faulty-drive error messages. The test results can be confusing, so Dell suggests running the subtests in the Diskette Drives Test Group more than once using diskettes from different sources.

Another possible cause of diskette drive problems is human error—typing a command in an incorrect form (usually called a syntax error). Be sure you have entered the command in the proper form.

When the diskette(s) and command syntax are eliminated as causes, the following symptoms usually suggest a drive problem and warrant running a subtest in the Diskette Drives Test Group:

• An error message appears on the screen stating that the computer cannot read from or write to a diskette.

• A diskette cannot be properly formatted, or format error messages appear on the screen.

• Data on diskettes is corrupted or lost; these problems may be intermittent.

Hard-Disk Drives (Non-SCSI) Test Group

The subtests in the Hard-Disk Drives (Non-SCSI) Test Group check the functionality of up to four hard-disk drives (two on each channel) of any capacity. The subtests check the storage capability of a drive as well as the hard-disk drive controller (which affects the ability to read from and write to the drive). The subtests are for all hard-disk drive types except for small computer system interface (SCSI) drives. To test SCSI drives, use the SCSI Devices Test Group.

The five subtests in the Hard-Disk Drives (Non-SCSI) Test Group confirm the following drive functions:

• Disk Controller Test

Checks the internal microcode of the hard-disk drive controller

• Forced Error-Correction-Code Test

Checks the ability of the hard-disk drive to identify and correct errors

• Seek Test

Checks the drive’s ability to search for a specified track on the drive and to position the read/write heads of the drive to all tracks

• Read Test

Positions the read/write heads at each cylinder of the drive for reading data and verifies that all tracks on the drive can be read correctly

• Write Test

Positions the read/write heads at each cylinder of the drive and verifies that all tracks on the drive can be written to correctly

Why Run a Hard-Disk Drives Test?

If you check your hard-disk drive to determine the amount of available space, your operating system will probably report problem areas. Problem areas on hard-disk drives are common, because most hard-disk drives have a small amount of space that is not usable. The hard-disk drive keeps a record of this space so that your computer will not attempt to use it. Identification of unusable disk space, unless it is an unusually large amount (over five percent of the possible total), should not be regarded as a cause for testing the hard-disk drive.

These are the most common symptoms that might prompt you to test the hard-disk drive:

• The hard-disk drive fails during the boot routine.

• Seek errors are reported by the operating system or application programs.

• An error message appears on the screen stating that the computer cannot read from or write to the hard-disk drive.

• Data on the hard-disk drive is corrupted or lost; these problems may be intermittent. Once saved by a program, files cannot be properly recalled.

IDE CD ROM Drives Test Group

The subtests in the IDE CD ROM Drives Test Group check the functionality of up to four IDE CD-ROM drives connected to the primary and secondary IDE ports. Before conducting an IDE CD-ROM test, insert a CD with audio and data tracks (such as a multimedia CD) into each CD-ROM drive.

NOTES: All of the subtests except for the Audio Output Test require a CD with data tracks. The Audio Output Test requires a CD with audio tracks. If a CD-ROM drive is empty, or if it contains a CD that does not have the required data or audio tracks (depending on the subtest[s] being conducted), the subtest(s) will fail.

The five subtests in the IDE CD ROM Drives Test Group confirm the following drive functions:

• Drive Controller Test

Causes the drive to execute its internal self-test.

• Seek Test

Checks the drive’s ability to search for each block on the device.

• Read Test

Positions the read heads at each block of the device for reading data and verifies that all blocks on the device can be read correctly.

• Audio Output Test

Causes the drive to begin playing the first audio track on an audio CD. To determine whether the test passed, listen to the audio output of the drive.

NOTE: To conduct the Audio Output Test, you must select it individually. It will not run as part of the test group.

• Eject Removable Media

Checks the drive’s ability to eject its CD.

Why Run an IDE CD ROM Drives Test?

If you encounter a problem while using an application program on a CD, the problem could result from the disc or from the drive. When you encounter problems, first try using a different CD. If the problem recurs, run the IDE CD ROM Drives Test Group.

These are the most common symptoms that might prompt you to test an IDE CD-ROM drive:

• Seek errors are reported by the operating system or application programs.

• An error message appears on the screen stating that the computer cannot read from an IDE CD-ROM drive (typically, drive D or drive E).

Serial/Infrared Ports Test Group

The subtests in the Serial/Infrared Ports Test Group check the computer’s interface with external devices, such as a printer and a mouse, that are connected to the computer through a serial or infrared port. The subtests in this test group are not intended as a diagnostic test for the actual peripheral attached to each port.

NOTES: With certain modems installed, the Serial/ Infrared Ports Test Group subtests may fail because the modem appears to the Dell Diagnostics as a serial or infrared port, but it cannot be tested as a serial or infrared port. If a modem is installed and one of the serial/ infrared ports subtests fails, remove the modem and run the diagnostic tests again. If an external loopback connector is not attached to a serial or infrared port, the Serial External Transmission Test will fail for that port and the results of this test should therefore be ignored. An external modem connected to the port does not substitute for an external loopback connector.

The four subtests in the Serial/Infrared Ports Test Group confirm the following port functions:

• Serial/Infrared Baud Rate Test

Checks the baud rate generator in each serial communications chip against the computer’s clock

• Serial/Infrared Interrupt Test

Checks the serial port’s ability to send IRQs to the microprocessor

• Serial/Infrared Internal Transmission Test

Checks several internal functions of the serial port using the internal loopback mode of the serial communications chip

• Serial External Transmission Test

If a loopback device is attached, checks the line control bits of the serial port and sends a test pattern at several baud rates, checking the returned values

Why Run a Serial/Infrared Ports Test?

If the Dell Diagnostics does not recognize your computer’s serial or infrared ports, enter the System Setup program and check the Serial/infrared Port category to see whether the port has been disabled. The subtests in the Serial/Infrared Ports Test Group cannot test a port unless it is enabled.

When a port is faulty, it may not be immediately evident that the port, and not the device connected to the port, is faulty. Instead, the peripheral (such as a printer or mouse) might behave erratically or not operate at all. If the external device is not properly installed through your software, it also may not function properly. Try operating the peripheral from different programs or through the operating system. If it still does not work, you can eliminate the software configuration as the cause of the problem.

Another possible cause for errors is the external device. Use the documentation that came with the peripheral to troubleshoot it and confirm that it is working properly. (Most printers have a self-test.)

After you eliminate incorrect system configuration information settings, peripheral malfunctions, and software errors as potential causes of port problems, you can run the subtests in the Serial/Infrared Ports Test Group to check your hardware. Although the following symptoms can be caused by faulty peripherals or software errors, they might also suggest a port problem:

• If a peripheral works intermittently or produces intermittent errors, the port may be faulty.

• If the computer displays an error message that is related to the external device connected to a port, but corrections to the device do not resolve the error, run the appropriate subtest in the Serial/Infrared Ports Test Group.

• If your software and the diagnostics do not recognize that you have a serial or infrared port, you should check the Serial/Infrared Port category in the System Setup program, and if necessary, run the appropriate subtest in the Serial/Infrared Ports Test Group.

Parallel Ports Test Group

The subtests in the Parallel Ports Test Group check the computer’s interface with external devices, such as a printer, that are connected to the computer through a parallel port. The subtests in this test group are not intended as a diagnostic test for the actual peripheral attached to each port. (The only exception is a printer, as described in the Parallel Internal Test.)

NOTE: If an external loopback connector is not attached to the parallel port, the Parallel External Loopback Test will fail for that port and the results of this test should therefore be ignored.

The four subtests in the Parallel Ports Test Group confirm the following port functions:

• Parallel Internal Test

Checks several internal functions of the parallel port

• Parallel External Loopback Test

Tests the functionality of the control lines through an external loopback connector, if an external loopback connector is available

• Parallel External Interrupt Test

Tests the parallel port’s ability to generate interrupts from all possible sources, if an external loopback connector or printer is available

• Parallel Printer Pattern Test

Tests a printer and tests the parallel port’s ability to send a pattern to the printer, if connected

Why Run a Parallel Ports Test?

If the Dell Diagnostics does not recognize your computer’s parallel port, enter the System Setup program and check the Parallel Port category to see if the port has been disabled. The subtests in the Parallel Ports Test Group cannot test a port unless it is enabled.

When a port is faulty, it may not be immediately evident that the port, and not the device connected to the port, is faulty. Instead, the peripheral (such as a printer) might behave erratically or not operate at all. If the external device is not properly installed through your software, it also may not function properly. Try operating the peripheral from different programs or through the operating system. If it still does not work, you can eliminate the software setup as the cause of the problem.

Another possible cause for errors is the external device. Use the documentation that came with the peripheral to troubleshoot it and confirm that it is working properly. (Most printers have a self-test.)

After you eliminate incorrect system configuration information settings, peripheral malfunctions, and software errors as potential causes of port problems, you can run the subtests in the Parallel Ports Test Group to check your hardware. Although the following symptoms can be caused by faulty peripherals or software errors, they might also suggest a port problem:

• If a peripheral works intermittently or produces intermittent errors, the port may be faulty.

• If the computer displays an error message that is related to the external device connected to a port, but corrections to the device do not resolve the error, run the appropriate subtest in the Parallel Ports Test Group.

• If your software and the Dell Diagnostics do not recognize that you have a parallel port, you should check the Parallel Port category in the System Setup program, and if necessary, run the appropriate subtest in the Parallel Ports Test Group.

SCSI Devices Test Group

The subtests in the SCSI Devices Test Group check the functionality of up to four SCSI host adapters and all the SCSI devices attached to them.

NOTES: Before conducting these subtests on CD-ROM drives, insert a CD with audio and data tracks (such as a multimedia CD) into each CD-ROM drive. All of the subtests, except for the Audio Output Test, require a CD with data tracks. The Audio Output Test requires a CD with audio tracks. If a CD-ROM drive is empty or if it contains a CD that does not have the required data or audio tracks (depending on the subtest[s] being conducted), the subtest(s) will fail.

The seven subtests in the SCSI Devices Test Group confirm the following drive functions:

• Internal Diagnostic

Causes the device to run its internal self-test.

• Seek Test

Checks the device’s ability to search for a specified track on the device and to position its read/write heads to all tracks.

• Read Test

Positions the read/write heads at each block of the device for reading data and verifies that all tracks on the device can be read correctly.

• Write Test

Positions the read/write heads at each block of the device and verifies that all tracks on the device can be written to correctly.

• Audio Output Test

Causes the CD-ROM drive to begin playing the first audio track on an audio CD. To determine whether the test passed, listen to the audio output of the drive.

NOTE: To conduct the Audio Output Test, you must select it individually. It will not run as part of the test group.

• Eject Removable Media

Causes a CD-ROM drive to eject its CD or a SCSI tape drive to eject its tape cartridge.

• Display Information

Displays a screen of information about each SCSI host adapter in the computer, the resources allocated to each SCSI host adapter, and a list of target devices attached to the SCSI host adapter.

Why Run a SCSI Devices Test?

If you check your SCSI hard-disk drive to determine the amount of available space, your operating system will probably report problem areas. Problem areas on hard-disk drives are common, because most hard-disk drives have a small amount of space that is not usable. The hard-disk drive keeps a record of this space so that your computer will not attempt to use it. Identification of unusable disk space, unless it is an unusually large amount (over 5 percent of the possible total), should not be regarded as a cause for testing the hard-disk drive.

These are the most common symptoms that might prompt you to test a SCSI device:

• A SCSI hard-disk drive fails during the boot routine.

• Seek errors are reported by the operating system or application programs.

• An error message appears on the screen stating that the computer cannot read from or write to a SCSI device.

• Data on a SCSI device is corrupted or lost; this problem may be intermittent. Once saved by a program, files cannot be properly recalled.

Network Interface Test Group

The subtests in the Network Interface Test Group verify the basic operation of the network interface controller (NIC). They test its internal functions, including read and write access to its registers and internal transmit and receive (loopback) capability.

The subtests in the Network Interface Test Group confirm the following functions:

• Registers Test

Writes patterns to the writable registers in the controller and reads the patterns back to verify whether they are accessible and able to retain data. This subtest also tests interrupt generation and register-specific functionality based on the type of controller.

• Internal Loopback Test

Places the controller into its various internal loopback modes and tests its ability to transmit and receive data.

NOTE: For some controllers, this test is not applicable.

• External Loopback Test

Places the controller into its various external loopback modes and tests its ability to transmit and receive data. A loopback plug is required to perform this test.

NOTE: For some controllers, this test is not applicable.

• Shared RAM Test

Performs a memory test on controllers with memory-mapped shared RAM. On controllers with first-in first-out (FIFO)-shared RAM, writes a data pattern to all locations and reads the pattern back to verify the operation. Some controllers do not support shared RAM tests.

• Display Information

Displays addresses and configuration information about the NIC. This information includes the network address used for communication on the local area network (LAN).

Why Run a Network Interface Test?

Running a subtest in the Network Interface Test Group helps diagnose problems that may be encountered while the system is operating in a network environment. Most network failures are caused by one of the following:

• Poor network connections

• Failure in the controller

• Interrupt conflict (the controller trying to use the same IRQ line as another device)

• Software configuration error

If a problem occurs while the system is operating in a network, the network connection should be inspected. If the connection is good, the Network Interface Test Group can be run to indicate whether the NIC is functioning, and if the test group is run in a loop, it can be used to detect intermittent failures.

The Registers Test subtest checks the interrupt generation capability of the controller. The Display Information Test displays the controller’s IRQ level. You can then make sure there is not an interrupt conflict by verifying that the IRQ level is not being used by another device in the system.

Audio Test Group

The subtests in the Audio Test Group check the functions of the audio controller and the computer’s recording and playback features.

NOTE: The following subtests are only applicable for systems with built-in speakers.

The eleven subtests in the Audio Test Group confirm the following functions:

• Software Reset Test

Checks for the presence of an active audio controller in your system

• Compatibility ID Test

Determines if the correct sound controller is installed in your system

• Interrupt Test

Checks to see if the audio controller is generating an interrupt on the IRQ line configured for that controller

• DMA Test

Tests for the presence of a DMA channel on the system chip set, and determines if the DMA controller and audio controller can exchange signals

• FIFO RAM Test

Checks the read/write capabilities and status of the audio controller

• Initial Reset Status Test

Verifies the reset values of the extended registers on the audio controller

• Internal Register Test

Writes test patterns to the internal registers of the audio controller, then reads other registers to confirm that the patterns are correctly interpreted

• Dual Channel Test

Confirms the presence of a second DMA channel on the system chip set and determines if the DMA controller and audio controller can exchange signals on that second DMA channel

• FM Sound Playback Test

Tests whether the system can synthesize sounds and play them through the built-in speakers

• Analog Sound Playback Test

Tests whether the system can play sampled sounds through the built-in speakers

• Record and Playback Test

Checks the ability of the audio controller to generate a sampled sound from signals received from the built-in microphone

Why Run an Audio Test?

If you do not hear sounds from your built-in speakers when you expect to, it is possible that your operating system or sound application uses resource settings different from those of the audio controller in the computer. In the absence of an expected sound, first check the documentation that accompanied your operating system or sound application to see if the sound features are correctly configured to work with the computer. The default settings for the audio controller are:

• DMA channel: 1

• IRQ line: 5

• Port address: 220h

If necessary, change the resource settings in your operating system or sound application to match these default settings.

If you still do not hear sound when you expect to, run the Audio Test Group.

NOTE: Before running the Audio Test group, make sure to enable the built-in speaker(s), and make sure that the speaker volume has not been muted.

Other Test Group

The subtests in the Other Test Group check devices that are currently not covered by one of the other groups.

The three subtests in the Other Test Group confirm the following functions:

• ESM Firmware Status

Checks to make sure the embedded server management (ESM) firmware was downloaded correctly and is operational

• ESM Interface Test

Checks the interface between the host and the ESM hardware to ensure all bits in the data port are working properly

• ESM Sensor Check

Verifies the current measurements of the ESM sensors

When you run a test group or subtest in the Dell Diagnostics, error messages may result. These particular error messages are not covered in this section because the errors that generate these messages can be resolved only with Dell technical assistance. Record the messages on a copy of the Diagnostics Checklist. For instructions on obtaining technical assistance and for informing the support technician of these messages, also see "Contacting Dell."

Back to Contents Page