US20110029816A1 - Personal computer diagnostic test before executing operating system - Google Patents
Personal computer diagnostic test before executing operating system Download PDFInfo
- Publication number
- US20110029816A1 US20110029816A1 US12/902,650 US90265010A US2011029816A1 US 20110029816 A1 US20110029816 A1 US 20110029816A1 US 90265010 A US90265010 A US 90265010A US 2011029816 A1 US2011029816 A1 US 2011029816A1
- Authority
- US
- United States
- Prior art keywords
- component
- personal computer
- functional test
- module
- computer component
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/22—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing
- G06F11/2284—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing by power-on test, e.g. power-on self test [POST]
Definitions
- the present invention relates to a personal computer component diagnostic module and test thereof. More particularly, the present invention relates to personal computer component diagnostic test before executing an operating system.
- BIOS is equipped with component basic diagnostic program, i.e. detecting whether hardware exists or not. After the BIOS component basic diagnostic program is executed, the software operating system can be loaded and operated.
- a personal computer component diagnostic method is executed before executing an operating system.
- the personal computer component diagnostic method comprising: calling a BIOS program; executing a component basic diagnostic program; and executing a component functional test after executing a predetermined step.
- the component functional test includes a CPU MSR/MTRR test, a hard disk S.M.A.R.T. test, a boot path test and a PCI device scanning test.
- this component diagnostic method can assist users or agents to recognize the computer status or potential problems without a Windows operating system such that a motherboard, a back bone system or a notebook PC need not be sent back to its supplier more often than not.
- FIG. 1 is a flowchart of personal computer component diagnostic test according to one preferred embodiment of this invention
- FIGS. 2 , 3 and 4 respectively illustrate three different embodiments of PC component diagnostic module on the motherboard according to one preferred embodiment of this invention
- FIG. 5 illustrates a complete PC component diagnostic module according to one preferred embodiment of this invention.
- FIG. 6 is a flowchart of personal computer component functional test according to one preferred embodiment of this invention.
- FIG. 1 is a flowchart of personal computer component diagnostic test according to one preferred embodiment of this invention.
- a BIOS program is called.
- a component basic diagnostic program i.e. detecting the hard disk configuration, is executed.
- a command (referred to as a basic command) is sent to a hard disk controller, and a response is sent back from the hard disk controller to provide information on the hard disk type or whether this hard disk supports S.M.A.R.T. (Self-Monitoring, Analysis, and Reporting Technology) or not, etc.
- a component function test is executed after executing a predetermined step and before an operating system is executed.
- the predetermined step can be any step after step 203 and before the component functional test is executed.
- the predetermined step initializes a display device such that the component functional test result can be displayed on the display device.
- the component functional test can further detect potential errors that the component basic diagnostic program (step 203 cannot detect).
- the hard disk can merely be recognized as a hard disk with S.M.A.R.T. functionality in step 203 , but further tests, i.e., a rotation speed test, can be executed in step 205 .
- FIGS. 2 , 3 and 4 respectively illustrate three different embodiments of the PC component diagnostic module on the motherboard according to one preferred embodiment of this invention.
- the component functional test (step 205 ) is executed by a component functional test module, which is installed as an optional ROM on the motherboard 100 .
- FIG. 2 illustrates the component functional test module 110 , which is saved in an independent optional ROM 108 on the motherboard 100 and separate from the BIOS component basic diagnostic module 106 .
- FIG. 3 illustrates the component functional test module 110 , which is saved in a PCI optional ROM 108 b (on a PCI card 107 ) and separate from the BIOS component basic diagnostic module 106 .
- FIG. 4 illustrates the component functional test module 110 , which is saved in BIOS optional ROM 108 a and integrated with the BIOS component basic diagnostic module 106 . No matter what embodiment is used, the component functional test module 110 can achieve the same result.
- FIG. 5 illustrates a complete PC component diagnostic module according to one preferred embodiment of this invention.
- FIG. 6 is a flowchart of a personal computer component functional test according to one preferred embodiment of this invention.
- step 202 when the CPU 102 (illustrated in FIGS. 2 , 3 and 4 ) calls the component functional test program, the component functional test program is duplicated in a random access memory 104 and decompressed. In order to preserve enough buffer memory to execute the component functional test, enough space (at least 512K) in the random access memory 104 should be confirmed first.
- step 204 a personal computer configuration is detected first so as to prepare the following steps of the component functional test program. This step is executed by a detection module 112 in FIG. 5 .
- a scan module 118 of FIG. 5 executes a PCI device scanning test.
- a CPU diagnostic module 120 of FIG. 5 executes a CPU MSR (Module Specific Register)/MTRR (Memory Type Range Register) test.
- CPU MSR Module Specific Register
- MTRR Memory Type Range Register
- a hard disk diagnostic module 114 of FIG. 5 executes a S.M.A.R.T. (Self-Monitoring, Analysis, and Reporting Technology) test.
- S.M.A.R.T. Self-Monitoring, Analysis, and Reporting Technology
- a path module 116 of FIG. 5 executes a boot path test, i.e. a network boot component test.
- Steps 206 - 212 can be executed without specific sequence and can be deducted according to demands.
- the component functional test can be launched by pressing a specific key, i.e. a button or switch connected with the PC system, selected in the BIOS, by a decision made by the component basic diagnostic program. After the component functional test is completed, the test result can be outputted by a display device, a log file containing error codes or a speaker. Users are able to recognize the computer status and potential problems as a reference source to fix the computer.
- this component diagnostic method can assist users or agents to recognize the computer status or potential problems without a Windows operating system such that a motherboard, a back bone system or a notebook PC need not be sent back to its supplier more often than not.
Landscapes
- Engineering & Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Test And Diagnosis Of Digital Computers (AREA)
Abstract
A personal computer component diagnostic method is executed to recognize the status or potential problems of a computer before executing an operating system. The personal computer component diagnostic method comprising: calling a BIOS program; executing a component basic diagnostic program; and executing a component functional test after executing a predetermined step. The component functional test includes a CPU MSR/MTRR test, a hard disk S.M.A.R.T. test, a boot path test and a PCI device scanning test.
Description
- This application is a continuation of application Ser. No. 11/773,809, filed Jul. 5, 2007, which claims priority to Taiwan Application Serial Number 95124697, filed Jul. 6, 2006. The entire disclosures of all the above applications are hereby incorporated by reference herein.
- 1. Field of Invention
- The present invention relates to a personal computer component diagnostic module and test thereof. More particularly, the present invention relates to personal computer component diagnostic test before executing an operating system.
- 2. Description of Related Art
- Without a software operating system, i.e. Windows operating system, users cannot recognize a status or potential problems of a conventional personal computer. Conventional BIOS is equipped with component basic diagnostic program, i.e. detecting whether hardware exists or not. After the BIOS component basic diagnostic program is executed, the software operating system can be loaded and operated.
- In case a BIOS component basic diagnostic program is executed and the software operating system cannot be loaded, an engineer uses “trial and error” methods to fix a personal computer in addition to using low level equipment. However, it is necessary to have extra components to execute a “trial and error” method. Without extra components, a “trial and error” method is of no use. Moreover, users often seek help from the PC system suppliers even if the actual problem occurs in some component.
- For the forgoing reasons, there is a need for a PC component diagnostic method before executing an operating system.
- It is therefore an objective of the present invention to provide a PC component diagnostic method to recognize the status or potential problems of a computer without an operating system being loaded.
- In accordance with the foregoing and other objectives of the present invention, a personal computer component diagnostic method is executed before executing an operating system. The personal computer component diagnostic method comprising: calling a BIOS program; executing a component basic diagnostic program; and executing a component functional test after executing a predetermined step. The component functional test includes a CPU MSR/MTRR test, a hard disk S.M.A.R.T. test, a boot path test and a PCI device scanning test.
- Therefore, this component diagnostic method can assist users or agents to recognize the computer status or potential problems without a Windows operating system such that a motherboard, a back bone system or a notebook PC need not be sent back to its supplier more often than not.
- It is to be understood that both the foregoing general description and the following detailed description are by examples, and are intended to provide further explanation of the invention as claimed.
- The accompanying drawings are included to provide a further understanding of the invention, and are incorporated in and constitute a part of this specification. The drawings illustrate embodiments of the invention and, together with the description, serve to explain the principles of the invention. In the drawings,
-
FIG. 1 is a flowchart of personal computer component diagnostic test according to one preferred embodiment of this invention; -
FIGS. 2 , 3 and 4 respectively illustrate three different embodiments of PC component diagnostic module on the motherboard according to one preferred embodiment of this invention; -
FIG. 5 illustrates a complete PC component diagnostic module according to one preferred embodiment of this invention; and -
FIG. 6 is a flowchart of personal computer component functional test according to one preferred embodiment of this invention. - Reference will now be made in detail to the present preferred embodiments of the invention, examples of which are illustrated in the accompanying drawings. Wherever possible, the same reference numbers are used in the drawings and the description to refer to the same or like parts.
-
FIG. 1 is a flowchart of personal computer component diagnostic test according to one preferred embodiment of this invention. Instep 201, a BIOS program is called. Instep 203, a component basic diagnostic program, i.e. detecting the hard disk configuration, is executed. In particular, when detecting the hard disk configuration is executed, a command (referred to as a basic command) is sent to a hard disk controller, and a response is sent back from the hard disk controller to provide information on the hard disk type or whether this hard disk supports S.M.A.R.T. (Self-Monitoring, Analysis, and Reporting Technology) or not, etc. Instep 205, a component function test is executed after executing a predetermined step and before an operating system is executed. The predetermined step can be any step afterstep 203 and before the component functional test is executed. In this embodiment, the predetermined step initializes a display device such that the component functional test result can be displayed on the display device. The component functional test can further detect potential errors that the component basic diagnostic program (step 203 cannot detect). For example, the hard disk can merely be recognized as a hard disk with S.M.A.R.T. functionality instep 203, but further tests, i.e., a rotation speed test, can be executed instep 205. -
FIGS. 2 , 3 and 4 respectively illustrate three different embodiments of the PC component diagnostic module on the motherboard according to one preferred embodiment of this invention. The component functional test (step 205) is executed by a component functional test module, which is installed as an optional ROM on themotherboard 100.FIG. 2 illustrates the componentfunctional test module 110, which is saved in an independentoptional ROM 108 on themotherboard 100 and separate from the BIOS component basicdiagnostic module 106.FIG. 3 illustrates the componentfunctional test module 110, which is saved in a PCIoptional ROM 108 b (on a PCI card 107) and separate from the BIOS component basicdiagnostic module 106.FIG. 4 illustrates the componentfunctional test module 110, which is saved in BIOSoptional ROM 108 a and integrated with the BIOS component basicdiagnostic module 106. No matter what embodiment is used, the componentfunctional test module 110 can achieve the same result. -
FIG. 5 illustrates a complete PC component diagnostic module according to one preferred embodiment of this invention.FIG. 6 is a flowchart of a personal computer component functional test according to one preferred embodiment of this invention. - In
step 202, when the CPU 102 (illustrated inFIGS. 2 , 3 and 4) calls the component functional test program, the component functional test program is duplicated in arandom access memory 104 and decompressed. In order to preserve enough buffer memory to execute the component functional test, enough space (at least 512K) in therandom access memory 104 should be confirmed first. - In
step 204, a personal computer configuration is detected first so as to prepare the following steps of the component functional test program. This step is executed by adetection module 112 inFIG. 5 . - In
step 206, ascan module 118 ofFIG. 5 executes a PCI device scanning test. - In
step 208, a CPUdiagnostic module 120 ofFIG. 5 executes a CPU MSR (Module Specific Register)/MTRR (Memory Type Range Register) test. - In
step 210, a hard diskdiagnostic module 114 ofFIG. 5 executes a S.M.A.R.T. (Self-Monitoring, Analysis, and Reporting Technology) test. - In
step 212, apath module 116 ofFIG. 5 executes a boot path test, i.e. a network boot component test. - Steps 206-212 can be executed without specific sequence and can be deducted according to demands. The component functional test can be launched by pressing a specific key, i.e. a button or switch connected with the PC system, selected in the BIOS, by a decision made by the component basic diagnostic program. After the component functional test is completed, the test result can be outputted by a display device, a log file containing error codes or a speaker. Users are able to recognize the computer status and potential problems as a reference source to fix the computer.
- According to preferred embodiments of the present invention, this component diagnostic method can assist users or agents to recognize the computer status or potential problems without a Windows operating system such that a motherboard, a back bone system or a notebook PC need not be sent back to its supplier more often than not.
- It will be apparent to those skilled in the art that various modifications and variations can be made to the structure of the present invention without departing from the scope or spirit of the invention. In view of the foregoing, it is intended that the present invention cover modifications and variations of this invention provided they fall within the scope of the following claims and their equivalents.
Claims (10)
1. A personal computer component diagnostic method before an operating system is executed, the personal computer component diagnostic method comprising:
calling a BIOS program;
executing a component basic diagnostic program for detecting the personal computer;
when receiving a trigger event, selecting and executing at least one specific component functional test for detecting a configuration of the specific computer component; and
displaying the configuration of the specific computer component.
2. The personal computer component diagnostic method of claim 1 , the functional test can be terminated by a interrupt signal.
3. The personal computer component diagnostic method of claim 1 , when the bios receiving a trigger event, the component functional test for recognize the computer component status and potential problems.
4. The personal computer component diagnostic method of claim 1 , when bios receiving a trigger event, duplicating and executing at least one specific component functional test for specific of the computer component in a memory.
5. A personal computer component diagnostic module for executing a diagnostic method before an operating system is executed, the personal computer component module comprising:
a random access memory;
a BIOS module;
a CPU for calling and executing the BIOS module in the random access memory; and
a component functional test module for executing a component functional test program;
when bios receiving a trigger event, duplicating and executing at least one specific component functional test program for detecting a configuration of the specific computer component in a memory.
6. The personal computer component diagnostic module of claim 5 , component functional test program for detecting configuration of a hard disk, or configuration of a boot path or configuration of a PCI device, or configuration of a CPU MSR/MTRR.
7. The personal computer component diagnostic module of claim 5 , the component functional test module is installed as an optional ROM on the motherboard.
8. The personal computer component diagnostic module of claim 5 , the component functional test module is saved in an independent optional ROM.
9. The personal computer component diagnostic module of claim 5 , the component functional test module is saved in a PCI optional ROM.
10. The personal computer component diagnostic module of claim 5 , when the bios receiving a trigger event, the component functional test for recognize the computer component status and potential problems.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/902,650 US20110029816A1 (en) | 2006-07-06 | 2010-10-12 | Personal computer diagnostic test before executing operating system |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
TW095124697A TWI323843B (en) | 2006-07-06 | 2006-07-06 | Method and device for pc component diagnostic test before executing operation system |
TW95124697 | 2006-07-06 | ||
US11/773,809 US7836345B2 (en) | 2006-07-06 | 2007-07-05 | Personal computer diagnostic test before executing operating system |
US12/902,650 US20110029816A1 (en) | 2006-07-06 | 2010-10-12 | Personal computer diagnostic test before executing operating system |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/773,809 Continuation US7836345B2 (en) | 2006-07-06 | 2007-07-05 | Personal computer diagnostic test before executing operating system |
Publications (1)
Publication Number | Publication Date |
---|---|
US20110029816A1 true US20110029816A1 (en) | 2011-02-03 |
Family
ID=38920369
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/773,809 Active 2028-06-28 US7836345B2 (en) | 2006-07-06 | 2007-07-05 | Personal computer diagnostic test before executing operating system |
US12/902,650 Abandoned US20110029816A1 (en) | 2006-07-06 | 2010-10-12 | Personal computer diagnostic test before executing operating system |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/773,809 Active 2028-06-28 US7836345B2 (en) | 2006-07-06 | 2007-07-05 | Personal computer diagnostic test before executing operating system |
Country Status (2)
Country | Link |
---|---|
US (2) | US7836345B2 (en) |
TW (1) | TWI323843B (en) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20120096313A1 (en) * | 2010-10-15 | 2012-04-19 | Sony Corporation | Recovery from hdd failure and technical support through wwan |
US20130132657A1 (en) * | 2011-03-29 | 2013-05-23 | Emc Corporation | Retrieveing data from data storage systems |
CN109491826A (en) * | 2018-11-27 | 2019-03-19 | 英业达科技有限公司 | Remote hardware diagnostic system and diagnostic method |
Families Citing this family (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
TWI323843B (en) * | 2006-07-06 | 2010-04-21 | Asustek Comp Inc | Method and device for pc component diagnostic test before executing operation system |
US20100023740A1 (en) * | 2008-07-23 | 2010-01-28 | Seagate Technology Llc | Diagnostic utility and method for a data storage device |
CN102081562A (en) * | 2009-11-30 | 2011-06-01 | 华为技术有限公司 | Equipment diagnosis method and system |
JP4746703B1 (en) * | 2010-03-29 | 2011-08-10 | 株式会社東芝 | Electronic equipment, hard disk drive |
US20120123728A1 (en) * | 2010-03-31 | 2012-05-17 | Perronne Derek D | Testing an electronic device |
CN103955417A (en) * | 2014-04-02 | 2014-07-30 | 江门市未来之星网络科技有限公司 | Computer hard disc data detecting equipment and method |
CN106502847B (en) * | 2016-10-31 | 2020-02-11 | 新华三信息技术有限公司 | Server diagnosis method and device |
Family Cites Families (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6449735B1 (en) * | 1996-07-01 | 2002-09-10 | Intel Corporation | Method and apparatus for providing improved diagnostic functions in a computer system |
US7555683B2 (en) * | 1999-12-23 | 2009-06-30 | Landesk Software, Inc. | Inventory determination for facilitating commercial transactions during diagnostic tests |
US7711859B2 (en) * | 2005-08-17 | 2010-05-04 | American Megatrends, Inc. | Facilitating the configuration of new PCI devices during post |
TWI323843B (en) * | 2006-07-06 | 2010-04-21 | Asustek Comp Inc | Method and device for pc component diagnostic test before executing operation system |
-
2006
- 2006-07-06 TW TW095124697A patent/TWI323843B/en active
-
2007
- 2007-07-05 US US11/773,809 patent/US7836345B2/en active Active
-
2010
- 2010-10-12 US US12/902,650 patent/US20110029816A1/en not_active Abandoned
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20120096313A1 (en) * | 2010-10-15 | 2012-04-19 | Sony Corporation | Recovery from hdd failure and technical support through wwan |
US8261131B2 (en) * | 2010-10-15 | 2012-09-04 | Sony Corporation | Recovery from HDD failure and technical support through WWAN |
US20130132657A1 (en) * | 2011-03-29 | 2013-05-23 | Emc Corporation | Retrieveing data from data storage systems |
US9672146B2 (en) * | 2011-03-29 | 2017-06-06 | EMC IP Holding Company LLC | Retrieveing data from data storage systems |
CN109491826A (en) * | 2018-11-27 | 2019-03-19 | 英业达科技有限公司 | Remote hardware diagnostic system and diagnostic method |
Also Published As
Publication number | Publication date |
---|---|
TWI323843B (en) | 2010-04-21 |
TW200805053A (en) | 2008-01-16 |
US20080010486A1 (en) | 2008-01-10 |
US7836345B2 (en) | 2010-11-16 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20110029816A1 (en) | Personal computer diagnostic test before executing operating system | |
US8156475B2 (en) | Device and method for testing embedded software using emulator | |
KR101019209B1 (en) | Device of automatically extracting Interface of Embedded Software and Method thereof | |
JP3106409B2 (en) | Diagnostic system and interface for personal computer | |
US9262283B2 (en) | Method for reading kernel log upon kernel panic in operating system | |
US20060277443A1 (en) | Method and system for acquiring definitions of debug code of a basic input/output system | |
CN100524241C (en) | Method for integrating and testing platform of multiple operating systems | |
US20070168738A1 (en) | Power-on error detection system and method | |
US7882395B2 (en) | Debug device for embedded systems and method thereof | |
EP2615552A1 (en) | System testing method | |
US6550019B1 (en) | Method and apparatus for problem identification during initial program load in a multiprocessor system | |
US20050160405A1 (en) | System and method for generating code coverage information | |
US6028996A (en) | Method and apparatus for virtualizing system operation | |
KR20070121701A (en) | Selecting subroutine return mechanisms | |
US6725396B2 (en) | Identifying field replaceable units responsible for faults detected with processor timeouts utilizing IPL boot progress indicator status | |
US7840948B2 (en) | Automation of keyboard accessibility testing | |
US6532499B1 (en) | Method for switching a plurality of key functions allocated to a special key | |
US7243222B2 (en) | Storing data related to system initialization in memory while determining and storing data if an exception has taken place during initialization | |
Mendonca et al. | Robustness testing of the Windows DDK | |
US6625728B1 (en) | Method and apparatus for locating and displaying a defective component in a data processing system during a system startup using location and progress codes associated with the component | |
US20050268081A1 (en) | Booting system and/or method for initializing peripherals | |
US7827540B2 (en) | Method for program debugging | |
US9009671B2 (en) | Crash notification between debuggers | |
US7617417B2 (en) | Method for reading input/output port data | |
CN101105764B (en) | Computer element fault-detecting method before prosecution of computer operation system and module |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: ASUSTEK COMPUTER INC., TAIWAN Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:PERNG, CHIY-FERNG;WANG, HSIEN-SHAN;HUANG, WEI-MING;AND OTHERS;REEL/FRAME:025125/0235 Effective date: 20070307 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |