PC-Doctor for Linux 64 BIT 08-16-01 (C) Copyright 2001 PC-Doctor Inc. All Rights Reserved Files: bootcd.iso -- CD-ROM bootable image readme.txt -- This file help-tui.txt -- Help file which is displayed with the UI TO BOOT THE Diagnostic CD 1. Turn on the 64 bit machine with the Bootable CD-ROM in machine. 2. When the EFI boot manager starts up choose the option: EFI Shell [Built-in] 3. When the prompt appears type the command "map". 4. This will give you a list of devices that the shell has recognized. e.g. fs0 : VenHw(Unknown Device:00)/HD(Part1,Sig00112233) fs1 : VenHw(Unknown Device:FF)/CD-ROM blk0 : VenHw(Unknown Device:00) 5. Locate the entry beginning with fs, with the word CD-ROM in it. This is the bootable CD-ROM drive letter. In the above example fs1 is the drive letter of our CD-ROM. 6. To change change directories to the CD-ROM boot partition type the drive letters followed by a colon. e.g. fs1: 7. Finally type the command "elilo" and then hit enter. 8. This will boot the CD-ROM. Note that it can take a while for the CD-ROM to copy the kernel to RAM. You should see a spinning cursor while the Kernel is loading. User Interface DESCRIPTION: The PC-Doctor for Linux Text User Interface (PCDr2KTextUI) provides a simple interface to the PC-Doctor 2000 diagnostics architecture. With it you can view system devices and diagnostic tests, run diagnostic tests, and view results, etc. PANES: After Booting the CD there are three panes that can become active nd accept user input: they are titled "Devices and Tests", "Test Script", and "Log". To select a pane and make it active, press the "TAB" key until the title of the desired pane is bolded. The items displayed in a pane may be scrolled up, down, left, and right by using the arrow keys on the keyboard. The "Devices and Tests" pane displays system devices and the possible tests to run on each device. The first item in this pane, "", is used to populate the "Test Script" pane with a series of tests designed to test key components such as the CPU, hard drive, etc. The second item in the pane, "", is used to populate the "Test Script" pane with all of the available tests. This will provide the most comprehensive test coverage available. Pressing "a" when one of these options is selected will cause the appropriate list of tests to be added to the "Test Script" pane. The "Test Script" pane displays tests in the current script, the percentage complete, and the result of each test once it has completed. The "Log" pane displays informative messages about each test. To view information about a test, press the "TAB" key until the "Test Script" pane is active. Select a test by scrolling up or down using the arrow keys. The highlighted test will have its informative messages displayed in the "Log" pane. The information in the "Log" pane is updated each time a different test is selected. COMMANDS: Next Pane: Pressing the "TAB" key will make the next pane active. Panes are selected in the following order: "Devices and Tests", "Test Script", and "Log". un script: Pressing the "r" key will sequentially run the tests listed in the "Test Script" pane. During the test, the percentage complete will be continuously updated. After the test has completed, the "Result" column will display whether the test passed or failed. Further information about the test can be obtained from the "Log" pane as described above in the PANES section. top script: Pressing the "s" key will stop the currently running script. Pressing "r" will restart the script, beginning with the first test. dd to script: This option is only available when the "Devices and Tests" pane is active. Pressing the "a" key will add the currently selected test to the end of the "Test Script" pane. Pressing "a" while a device is selected will add all the tests listed directly below that device. el test: This option is only available when the "Test Script" pane is active. Pressing the "d" key will remove the currently selected test from the "Test Script" pane. eit: If there is not a currently running script, pressing the "x" key will prompt the user "Do You Want To Exit And Reboot[Y]". Press the "y" key to exit the program. Pressing any other key will cancel the prompt. If a script is running, pressing the "x" key will display the message "INVALID KEY: Tests are running". elp: Pressing the "h" key will show this help screen. To exit help, press the "x" key. EXAMPLE: An example PC-Doctor for Linux session using the text user interface might go as follows. First, the user starts PC-Doctor 2000 with the command: PCDr2KTextUI This will enumerate all system devices and start the user interface. The user will be presented with three panes: "Devices and Tests", "Test Script", and "Log". In the "Devices and Tests" pane, the user may choose any number of tests to be run by selecting the test (using the up and down arrow keys) and pressing "a" to add the test to the "Test Script" pane. For example, to run all tests on the CPU, find the device "CPU: CPU:0". There are six subtests listed beneath it: General Registers Test Floating-Point Registers Test Parallel Integer (MMX) Test Parallel Floating-Point (SIMD) Test Cache Test IA-32 Instruction Set Test To add these tests to the "Test Script" pane, scroll down to the "General Registers Test" selection and press the "a" key. The user should now be able to see the "General Registers Test" in the "Test Script" pane. To add the rest of the tests, repeat this procedure by scrolling down to each one and pressing the "a" key. Once all six tests are listed in the "Test Script" pane, the user may run these tests (in sequential order) by pressing the "r" key. As the script is running, the percentage complete for each test will be listed as 100% once the test has finished running, and the "Result" column will display whether the test passed or failed. To view information about each test, press the "TAB" key to make the "Test Script" pane active. By using the arrow keys, the user can select any one of the six subtests. The currently selected test will have its relevant information, if any, displayed in the "Log" pane. ERRORS AND WARNINGS: EVENT MESSAGE DESCRIPTION CODE --DIAGAGP-- 1 No AGP/PCI bus detected. The PCI bus could not be detected. 3 AGP card disabled. The AGP video card was detected, but appears to be disabled. 4 Version number is too low The AGP version installed is less than ($major$.$minor$). version 1.0, which does not support running the AGP Test. 5 RATE field of AGP There is no data to report in the RATE capabilities status field. register is empty. 6 DATA_RATE field of AGP The DATA_RATE field of the AGP capabilities capabilities command command register is not set. register is not set. 7 Failed to read PC-Doctor could not read the configuration configuration data (bus byte of this device (bus, device, and $bus$ device$ $device function numbers shown). Bus (number shown). function $fun$). 100 Only able to read $bytes$ Only able to read a specified number of bytes of configuration bytes of configuration data. (number of data (bus $bus$ device bytes, the bus, the device and the function $device$ function $fun$). are given). 101 Device $index$ is not Device (device given) is not recognized for recognized for testing. testing. 102 Setup Error in AGP Test. Error Setting up AGP Test. 103 Couldn't read capabilities Could not read the capabilities offset offset. value. 104 Device not found. The device could not be found. --DIAGCD-- 5 No CD detected. Insert a No disk is in the drive. data CD and restart test. 12 Audio CD tracks detected. PC-Doctor CD-ROM test is designed to test Insert a data CD and data CDs only. restart test. 16 DVD detected. Insert a PC-Doctor CD-ROM test is designed to test data CD and restart test. data CDs only. 100 Audio CD detected. Insert PC-Doctor CD-ROM test is designed to test a data CD and restart data CDs only. test. 101 Error $errornum$ Reading PC-Doctor detected a read error (Expected Sector $sector$. value and value received are given). 102 Device not found. The device could not be found. 150 Device is busy. The device is currently busy. 151 Current user privileges The current user cannot access the device are insufficient for this due to insufficient privileges. test to proceed. 152 Unable to open device. The device could not be opened. --DIAGCOM-- 1 DTR->DSR Failed. DTR stuck Indicates a Register problem. high. 2 DTR->DSR Failed. DTR stuck Indicates a Register problem. low. 3 RTS->CTS Failed. CTS stuck Indicates a Register problem. high. 4 RTS->CTS Failed. CTS stuck Indicates a Register problem. low. 100 Framing Error Detected. Framing error detected. 101 Parity Error Detected. Parity error detected. 102 Overrun Error Detected. Overrun error Detected. 103 Timeout waiting to The Data Send and Receive subtest was halted transmit at $baudrate$ on (baud rate shown). Data transmission did baud. not complete within the allotted time. 104 Failed Registers Test. Port failed registers test. 105 Failed External Loopback Port failed external loopback test. Test. 106 Miscompare at $baudrate$ PC-Doctor detected an unexpected result. baud: Read $valueread$H, (read value and expected value shown). Expected $valuewrite$H. 107 Device not found. The device could not be found. 150 Device is busy. The device is currently busy. 151 Current user privileges The current user cannot access the device are insufficient for this due to insufficient privileges. test to proceed. 152 Unable to open device. The device could not be opened. --DIAGCOMI-- 1 Framing Error Detected. Framing error detected on port (port number shown). This is an evaluation program only. 2 Parity Error Detected. Parity error detected on port (port number shown). 3 Overrun Error Detected. Overrun error detected on port (port number shown). The Data Send and Receive subtest completed at (baud rate shown). 4 Timeout waiting to The Data Send and Receive subtest was halted transmit at $baudrate$ on (port and baud rate shown). Data baud. transmission did not complete within the allotted time. 5 Miscompare at $baudrate$ PC-Doctor detected an unexpected result baud: Read $valueread$H, (read value and expected value shown). Expected $valuewrite$H. 7 Failed Registers Test. Port failed registers test (Port number shown). 9 Failed Control Signals Port failed Control Signals test (Port Test. number shown). 10 Failed Data Send and Port failed Data_Send_Receive test (Port Receive Test. number shown). There may be a device attached to the port such as a modem, which is preventing access. 100 Miscompare: Read PC-Doctor detected an unexpected result. $valueread$H : Expected (read value and expected value shown). $expectedvalue$H. 101 Device not found. The device could not be found. 150 Device is busy. The device is currently busy. 151 Current user privileges The current user cannot access the device are insufficient for this due to insufficient privileges. test to proceed. 152 Unable to open device. The device could not be opened. --DIAGCPU-- 1 General Registers Error: General register failed (code shown). $errno$. 2 Integer Arithmetics Error: Arithmetics operation failed for test set $errno$. (operation name and test set name shown). 3 Strings Error: $errno$. String move code failed (code shown). 4 Logicals Error: $errno$. Logical operation code failed (code shown). 5 Floating-Point Registers Floating-Point register failed (code shown). Error: $errno$. 7 Floating-Point Arithmetics Floating-Point arithmetics instruction Error: $errno$. failed (code shown). 10 Parallel Integer Parallel Integer (MMX) instruction failed Instruction Failed (instruction shown). $INSTRUCTION$ ($ERRORNO$) 100 Could not acquire CPU for Could not acquire the CPU to test it. testing. The CPU was not tested. 101 Only a superuser can run A user must have a super user ‘s permissions this test. to run this test. 102 Error stopping memory Unable to stop memory paging to disk for paging to disk. memory in use by the test. 103 Cache Read-Write Error at PC-Doctor detected an error in the cache Physical Address. (Displays value read and value expected). 104 Error obtaining physical Unable to obtain physical memory size. memory size information. 105 Device not found. The device could not be found. 106 Branch Registers Error: Branch register failed (code shown). $errno$. 107 Predicate Registers Error: Predicate register failed (code shown). $errno$. 108 Parallel Floating-Point Parallel Floating-Point (SIMD) instruction Instruction Error: failed (code shown). $errno$. 109 IA-32 Instruction Set An error in the IA-32 instruction set was Error. detected. 110 Could not fork process. The process to test the IA-32 instruction IA-32 instruction set will set could not be created. not be tested. 111 Could not execute process. The file diagcpu32.linux could not be IA-32 instruction set will executed. A likely cause is that the file is not be tested. not in the current directory. --DIAGDVD-- 5 No CD detected. Insert a No disk is in the drive. data CD and restart test. 12 Audio CD tracks detected. PC-Doctor DVD-ROM test is designed to test Insert a data CD and data DVDs only. restart test. 100 Audio CD detected. Insert PC-Doctor DVD-ROM test is designed to test a data CD and restart data DVDs only. test. 101 Error $errornum$ Reading PC-Doctor detected a read error (Expected Sector $sector$. value and value received are given). 102 DVD disk not detected. PC-Doctor DVD-ROM test is designed to test Insert a DVD disk and data DVDs only. restart test. 103 Device not found. The device could not be found. 150 Device is busy. The device is currently busy. 151 Current user privileges The current user cannot access the device are insufficient for this due to insufficient privileges. test to proceed. 152 Unable to open device. The device could not be opened. --DIAGFD-- 100 Error $errornum$ Reading PC-Doctor Detected an error in sector Sector $sector$. (Sector Given) 101 Error $errornum$ Verifying PC-Doctor Detected an error while verifying Sector $sector1$ - a sector (Sector Given). $sector2$. 102 Device not found. The device could not be found. 150 Device is busy. The device is currently busy. 151 Current user privileges The current user cannot access the device are insufficient for this due to insufficient privileges. test to proceed. 152 Unable to open device. The device could not be opened. --DIAGHD-- 100 Error $errornum$ Reading PC-Doctor Detected an error in sector Sector $sector$. (Sector Given) 101 Error $errornum$ Verifying PC-Doctor Detected an error while verifying Sector $sector1$ - a sector (Sector Given). $sector2$. 102 Device not found. The device could not be found. 150 Device is busy. The device is currently busy. 151 Current user privileges The current user cannot access the device are insufficient for this due to insufficient privileges. test to proceed. 152 Unable to open device. The device could not be opened. --DIAGLPTI-- 1 Miscompare: Wrote Byte written is different than byte read $write$H, Read $read$H. back. 100 Failed Registers Test. Registers failed testing. 102 Device not found. The device could not be found. 150 Device is busy. The device is currently busy. 151 Current user privileges The current user cannot access the device are insufficient for this due to insufficient privileges. test to proceed. 152 Unable to open device. The device could not be opened. --DIAGLS12-- 100 Error $errornum$ Reading PC-Doctor Detected an error in sector Sector $sector$. (Sector Given). 101 Device not found. The device could not be found. 102 No media in the device. The device does not contain media. 150 Device is busy. The device is currently busy. 151 Current user privileges The current user cannot access the device are insufficient for this due to insufficient privileges. test to proceed. 152 Unable to open device. The device could not be opened. --DIAGMDM-- 1 Dialtone Not Detected. Modem on (identifier shown): dialtone not detected. 17 Modem command $command$ Modem AT command failed (command shown). returned ERROR. Modem may not support this AT Command. 20 Loopback Data Compare Number of loopback errors detected (number Error: Wrote $wrote$, Read shown). $read$. 21 Modem returned Modem command (command shown) returned value unrecognized response. (value shown). 22 Modem Not Responding to AT A modem command timed out. Command: $command$. Time out may be too short. 100 Error in Specific Modem There is an error in the script line given. Test: Script Line:$line$. 101 Error writing to Modem's There was an error writing to the serial Serial Port. port that the modem is attached to. 102 Error specified device The device chosen for testing did not not enumerated correctly. enumerate. 103 Modem Not Responding to The modem did not respond to the command to Dial Command ATDT. The test the dialtone. The timeout value in the Dialtone Wait time out may p2k file may be too short. be too short. 104 Modem is in use by another Cannot test modem since it is in use. process. 105 Error opening Modem's Cannot open serial port that the modem is Serial Port. connected too. 106 This modem is not in the This specific modem is not on the current Current Modem List. list for testing so a generic test will Running Generic Tests. be run. 107 Device not found. The device could not be found. --DIAGMEM-- 1 Error allocating memory. Internal error: could not allocate memory for testing. You are possibly low on system resources. Try closing applications to free them. 2 Memory Read-Write Error at Pattern test failed: incorrect data at Physical Address offset (offset value shown) Write pattern $physaddr$. (write pattern shown), read back pattern pattern shown), PC-Doctor detected too many errors to continue. The test was halted. 100 Only a superuser can run A user must have the super user privileges this test. to run this test. 101 Error stopping memory Unable to guarantee the memory under test paging to disk. will not be paged to virtual memory. 102 Error obtaining physical Unable to obtain physical memory size. memory size information. 103 Device not found. The device could not be found. --DIAGNET-- 5 Could not find remote host Could not connect to a remote host. for testing. 7 Error reading data from Could not read data from the network. network. 8 Could not communicate with Could not communicate with a remote host. remote host. 10 Error configuring network Could not correctly configure the network to for testing. test it. 11 Error configuring local Could not correctly configure the local network for testing. network to test it. 6 Error writing data to PC-Doctor found an error in writing to the network. network. 104 Send and receive buffers The send and receive buffers are too small. too small. 105 Could not select card for Could not select the card to test it. testing. 108 Card does not have a valid Card does not have a valid address. address. 109 Device not found. The device could not be found. --DIAGPCI-- 1 No PCI bus detected. Indicates an incorrect installation of PC-Doctor. 3 Failed to read The PCI diagnostic locates PCI devices and configuration data (bus attempts to read the first 256 bytes of $bus$ function $fun$). configuration data for each device. This failure would indicate an error with either the PCI device or the PCI bus it is attached to. 7 Only able to read $bytes$ Failed to read configuration byte (bus, bytes of configuration device, function shown). data (bus $bus$ function $fun$). 104 Device $index$ is not The device (index shown) is unable to be recognized for testing. tested. 105 Device not found. The device could not be found. --DIAGPCM-- 1 Card Services report 0 Number of sockets (number shown). PCMCIA Sockets. 2 Card Services Support Card services support level (level shown). Level: $levelmajor$.$levelminor$ 5 Card Services not Card services not installed. installed. 101 Couldn't open or create Could not open /dev device file entry for /dev entry for PCMCIA socket. Socket $socket$. 106 Card Information Structure Card Information Structure verification verification failed for failed for PCMCIA card. PCMCIA CARD in Socket $socket$. 107 PCMCIA driver not running. PCMCIA driver not running. 108 Device not found. The device could not be found. --DIAGSCSI-- 1 Waiting for unit timed This message is generated if the unit fails out. to become ready (the unit is repeatedly polled) within a few seconds. 2 Unit does not support Unit does not support a command. this command. 3 Media is write protected. Media is write-protected. 4 Logical block address out LBA out of range. of range. 5 Media required for this No disk or tape in drive. command. 6 Device is busy. Device is busy. 108 Self Test Failed. SCSI self test failed. 109 Device not found. The device could not be found. 150 Device is busy. The device is currently busy. 151 Current user privileges The current user cannot access the device are insufficient for this due to insufficient privileges. test to proceed. 152 Unable to open device. The device could not be opened. --DIAGSMRT-- 8 Failure Prediction Failure prediction threshold exceeded. Threshold Exceeded. 17 Error encountered while Error reading SMART drive data (drive shown, trying to read SMART drive errors shown). values. 18 Test was aborted by the The user aborted the test outside of host. PC-Doctor. 19 Test was interrupted by Self test routine halted by host with hard the host. or soft reset outside of PC-Doctor. 20 The self test completed This event will be generated by the extended having an unknown element SMART diagnostic module by the second or fail. third subtest. 21 The electrical element of This event will be generated by the extended the self test failed. SMART diagnostic module by the second or third subtest. 22 The servo and/or seek test This message should be interpreted as a Seek element failed. failure that occurred during the SMART drive's self-test. 23 The read element of the The Read element of test failed. test failed. 36 A fatal error occured. The Fatal or unknown error. Unable to complete device was unable to self-test. complete the self test. 101 Unable to open device. Could not open device. 102 Error retrieving SMART Error retrieving SMART info. info. 104 Failed GET_IDENTITY SMART GET_IDENTITY command failed. command. 105 Smart drive information Failed to enable SMART functionality on is not available. SMART drive. Enable Failed. 107 Error encountered while Error while trying to read SMART threshold trying to read SMART data. drive thresholds. 108 Predictive Failure Drive reports predicted failure. Detected on drive. 109 Device does not support Device does not support SMART. SMART. 110 Error encountered while The command to start the self test returned trying to start SMART an error. self test. 111 Drive has failed to start The drive received the start self test self test. command and returned correctly, however the test did not start for an unknown reason. 119 The self test failed for The self test failed for an unknown reason. an unknown reason. 120 Device not found. The device could not be found. 150 Device is busy. The device is currently busy. 151 Current user privileges The current user cannot access the device are insufficient for this due to insufficient privileges. test to proceed. 152 Unable to open device. The device could not be opened. --DIAGTAPE-- 1 Tape Load failed: Error Tape load failed (drive and error shown). = %i. 8 Set tape position failed: Setting tape position failed. Error = %i. 9 Get Tape Position failed: Reading tape position failed. Error = %i. 12 Failed writing data to Error writing to tape. tape. 14 Rewind failed: Error Tape rewind failed. = %i. 13 Data miscompare writing Data miscompare found. and reading from tape. 15 Failed reading tape at Tape read failed. block %lu. 17 No disk in the drive. Media is not present. 18 Insufficient data No data was found on the tape. Test could detected on tape. Test not run. could not run. 103 Timed out waiting for unit Timed out waiting for unit to become ready. to become ready. 106 Set tape position failed: Error setting tape position. Error = $errornum$. 107 Failed seeking to block Failed seeking to block. %lu: Error = %i. 108 Failed seeking to block Failed seeking to block. $block$: Error = $errornum$. 111 Failed seeking to block Failed seeking to block. %lu. 112 Failed seeking to block. Failed seeking to block. 114 Unable to get the drive Unable to get the drive status. Make sure status. Make sure there there is media in the drive. is media in the drive. 115 Device not found. The device could not be found. 150 Device is busy. The device is currently busy. 151 Current user privileges The current user cannot access the device are insufficient for this due to insufficient privileges. test to proceed. 152 Unable to open device. The device could not be opened. --DIAGUSB-- 100 Device not found. The device could not be found. --DIAGZIP-- 100 Error %i Reading Sector Unable to read drive. %u. 101 Device not found. The device could not be found. 102 No media in the device. The device does not contain media. 150 Device is busy. The device is currently busy. 151 Current user privileges The current user cannot access the device are insufficient for this due to insufficient privileges. test to proceed. 152 Unable to open device. The device could not be opened.