US20050198583A1 - State/activity indication using icons on an LCD - Google Patents
State/activity indication using icons on an LCD Download PDFInfo
- Publication number
- US20050198583A1 US20050198583A1 US11/100,884 US10088405A US2005198583A1 US 20050198583 A1 US20050198583 A1 US 20050198583A1 US 10088405 A US10088405 A US 10088405A US 2005198583 A1 US2005198583 A1 US 2005198583A1
- Authority
- US
- United States
- Prior art keywords
- icon
- display
- state
- send
- activity
- 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
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
- G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
- G06F3/0481—Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
- G06F3/04817—Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance using icons
Definitions
- This invention relates to server systems and, more particularly, to successful initialization of servers.
- a headless server is a server system which includes no keyboard, no mouse and no monitor. As expected, headless server systems typically operate without any human intervention. Because of this, headless server systems have higher reliability requirements than most other computer systems. Further, headless server systems ideally operate using minimal or no manual steps.
- the “boot” process is executed by a program, usually located in read-only memory (ROM) of the computer system.
- ROM read-only memory
- the ROM program may be described as including two separate processes: the power-on self test, or POST, and the basic input/output system, or BIOS.
- POST power-on self test
- BIOS basic input/output system
- the POST part of the program executes commands such that different circuitry and components of the computer system may be initialized.
- the BIOS portion includes functions which may be used by software, including POST, for communicating with different devices in the computer system.
- the POST program in the ROM Upon receiving power to the computer system, the POST program in the ROM immediately begins execution.
- the POST performs initialization functions, such as detecting and testing the memory, the display, the non-volatile media, such as hard disk and floppy disk drives, and so on.
- initialization functions such as detecting and testing the memory, the display, the non-volatile media, such as hard disk and floppy disk drives, and so on.
- an abbreviated POST, or “quick-boot,” may be available.
- control is typically transferred to an operating system, usually located on the hard disk drive.
- an operating system usually located on the hard disk drive.
- all run-time operations of the system including any execution of application programs, are controlled by the operating system.
- the operating system may or may not utilize the BIOS functions in communicating with the hardware of the computer system.
- boot processes are designed for systems with a monitor, a keyboard and a mouse. These processes assume that the user is present in front of the system, and may thus be available to respond to any POST or operating system errors. These errors may take the form of beeps, screen displays, or other indicia. Typically, execution of either the POST or operating system program will stop once these errors occur. Manual intervention is generally the only way for the boot process to proceed. Contingencies, such as automatic attempts to boot from other devices, are typically not executed by the POST or operating system programs. Further, information is typically not shared between the operating system and the POST routine.
- FIG. 1 is a block diagram of the system according to one embodiment of the invention.
- FIG. 2 is a block diagram of the LCD display 124 , according to one embodiment of the invention.
- FIGS. 3A through 3F are sample icons according to one embodiment of the invention.
- FIGS. 4A and 4B are flow diagrams for updating the state icon according to one embodiment of the invention.
- FIG. 5 is a flow diagram of the disk activity driver according to one embodiment of the invention.
- FIG. 6 is a flow diagram of the LAN activity service according to one embodiment of the invention.
- FIG. 7 is a flow diagram of the WAN activity driver according to one embodiment of the invention.
- a computer system 100 includes a processor 102 and a memory 104 , connected by a system bus 126 .
- the processor 102 may generally refer to one or more central processing units (CPUs), microcontrollers or microprocessors, such as an X86 microprocessor, a Pentium® microprocessor or an advanced risk controller (ARM), as just a few examples.
- CPUs central processing units
- microcontrollers or microprocessors such as an X86 microprocessor, a Pentium® microprocessor or an advanced risk controller (ARM), as just a few examples.
- ARM advanced risk controller
- computer system may refer to any type of processor-based system that may include a desktop computer, a laptop computer, a headless server, an appliance or a set-top box, as just a few examples.
- the invention is not intended to be limited to the illustrated system 100 , but rather, the system 100 is an example of one of many embodiments of the invention.
- the memory 104 may be one of a number of types of random access memories, such as dynamic random access memories (DRAMs), synchronous DRAMs (SDRAMs), and static RAMs (SRAMs). Other types of memory 104 may include single in-line memory modules (SIMMs) or double in-line memory modules (DIMMs).
- DRAMs dynamic random access memories
- SDRAMs synchronous DRAMs
- SRAMs static RAMs
- Other types of memory 104 may include single in-line memory modules (SIMMs) or double in-line memory modules (DIMMs).
- the computer system 100 further includes a South Bridge 115 , between the system bus 126 and a second bus 128 .
- the South Bridge 115 is an input/output (I/O) controller which includes bridge support between the buses 126 and 128 , as well as providing an interface to a hard disk drive 112 , a modem 120 , non-volatile read-only memory (NVRAM) 116 , and read-only memory (ROM) 106 .
- I/O input/output
- NVRAM non-volatile read-only memory
- ROM read-only memory
- the bus 128 is a Peripheral Component Interconnect (PCI) bus 128 .
- PCI Peripheral Component Interconnect
- the PCI bus is compliant with the PCI Local Bus Specification, Revision 2.2 (Jun. 8, 1998, available from the PCI Special Interest Group, Portland, Oreg. 97214).
- the PCI bus 128 may support a network interface card 118 , for high-speed connection of the computer system 100 to a network 250 , such as a local area network (LAN) or a wide-area network (WAN).
- a network 250 such as a local area network (LAN) or a wide-area network (WAN).
- connection to the computer network 250 may employ the modem 120 .
- the modem 120 is a high-speed PCI modem, connected directly to the PCI bus 128 .
- a computer system 200 Also connected to the network 250 is a computer system 200 .
- the computer system 200 acts as a remote console 200 to the computer system 100 .
- the computer system 200 may perform remote operations which assist in the successful boot of the computer system 100 .
- the ROM 106 includes a power-on self test (POST) 108 program, and a basic input/output system (BIOS) 110 program.
- POST power-on self test
- BIOS basic input/output system
- the POST 108 and BIOS 110 programs may reside in a flash memory device.
- the ROM 106 may also include non-volatile memory devices such as erasable and programmable read-only memories (EPROMs), electrically erasable and programmable read-only memories (EEPROMs), and flash memories.
- EPROMs erasable and programmable read-only memories
- EEPROMs electrically erasable and programmable read-only memories
- the hard disk drive 112 may store an operating system 114 .
- the operating system 114 may be loaded into the memory 104 , for faster execution.
- the headless server may include a small display, such as a small liquid crystal display (LCD), for error reporting.
- the system bus 126 of FIG. 1 is coupled to a display controller 123 , to support a display 124 , such as an LCD display.
- the LCD display 124 may provide additional support for some fail-safe conditions. For example, the LCD display 124 may provide quick system status of the computer system 100 . During initial power on, network access or other connection of the computer system 100 may not yet be established.
- connection to the remote computer system 200 may have been removed. Where network problems occur, the remote system 200 may also be unavailable. Where tasks need to be performed on the computer system 100 itself, such as removing or replacing devices on the system, the LCD display 124 may provide relevant information.
- the LCD display includes a message area 302 , such as for providing text-based error or status messages, and six icon regions 310 - 320 .
- the icon regions 310 - 320 may supply a user with relevant error and status information about the computer system 100 .
- the icon regions 310 - 320 are language-independent graphic elements.
- each icon provides status information for a distinct functional area of the computer system 100 .
- a state icon 310 indicates where in the power-on, or “boot” process, the computer system 100 is currently executing.
- the boot process involves execution of the POST program 108 , loading the operating system 114 , and successful booting of the operating system 114 such that application programs may operate. During this time, it may be difficult to identify where in the boot process the computer system 100 may be. Accordingly, the state icon 310 may supply this information about the computer system 100 .
- Each icon represents a distinct initialization state of the computer system 100 .
- icons 330 - 342 may be used to depict distinct initialization status.
- the icons may be displayed by the POST program 108 or by the operating system software 114 , as described further in FIG. 4 , below.
- TABLE 1 State Icons State Icon Description POST display Machine is in POST.
- BIOS is icon 330 in control OS Booting display Bootstrap about to be loaded icon 332 by BIOS OS Initializing display OS booted and started running icon 334 OS Running display OS fully up icon 336 OS Shutting Down display OS starting graceful shut down icon 338 OS Halted display OS mostly shutdown icon 340 Emergency Mode display System is in emergency mode. icon 342 BIOS is in control
- a disk activity icon 312 provides status information about the hard disk drive or drives 112 .
- the disk activity icon 312 region may be updated during disk accesses, to connote a disk error, to indicate that the disk 112 is being checked, or to indicate that the disk 112 is being rebuilt from a mirror disk or other backup media.
- Table 2 shows how the disk activity icon 312 may be updated in response to four states of the hard disk drive 112 : normal (disk) activity, disk error, disk being checked, and disk being rebuilt.
- FIG. 3B includes icons 344 - 350 , which may be used as disk activity icons 312 .
- a LAN activity icon 314 provides information relevant to the LAN connection of the computer system 100 to the network 250 .
- the LAN activity icon 314 indicates when LAN activity is taking place, as well as when a LAN error occurs.
- Table 3 and FIG. 3C show how the LAN activity icon 314 may be updated with flashing icon pairs 352 a and 352 b for normal operation and a distinct error icon 354 , to indicate a LAN error.
- a wide-area network, or WAN, activity icon 316 also provides network-related information about the computer system 100 , such as for connection to the Internet.
- Table 4 and FIG. 3D show how the WAN activity icon 316 may be updated with flashing icon pairs 356 a and 356 b , for normal operation, while a distinct error icon 358 indicates a WAN error.
- TABLE 4 WAN Activity Icons State Icon Description Normal Operation alternate icons 356a Flickered to show and 356b normal WAN activity WAN Error display icon 358 Shown to depict a WAN error
- a sensor status icon 318 may be used to depict sensor conditions for the computer system 100 .
- the computer system 100 may include sensors for monitoring the voltage, the temperature, the operation of a fan, whether the chassis is opened, and other physical characteristics of the computer system 100 .
- Some possible sensor status icons 318 are shown in Table 5 and FIG. 3E . TABLE 5 Sensor Status (Health) Icons State Icon Description Normal Operation display All sensors are OK icon 360 Temperature Alert display A temperature sensor has icon 362 generated an alert Voltage Alert display A voltage sensor has icon 364 generated an alert Fan Alert display A fan sensor has generated icon 366 an alert Intrusion Alert display The chassis has been opened icon 368
- a “please wait” icon 320 is also provided, in some embodiments.
- the “please wait” icon 320 may be used by the POST program 108 , the operating system software 114 , or other applications to indicate that a process is ongoing, but not yet complete. For example, when a program is loaded, the “please wait” icon 320 may be sent to the LCD display 124 .
- Table 6 shows the “please wait” icon according to one embodiment. TABLE 6 “Please Wait” Icon State Icon Description Normal Operation display System is running normally icon 360 Please wait display Shown when a time consuming icon 370 or critical operation is taking place
- the computer system 100 includes an LCD driver 130 for sending configuration, status, and error information to the display 124 .
- the LCD driver 130 may provide text information for the message area 302 or may update one of the icons 310 - 320 .
- the LCD driver 130 is loaded by the operating system 114 once the computer system 100 is initialized.
- the LCD driver 130 may not be available for sending information to the display 124 .
- the LCD display driver 130 may not be used.
- the computer system 100 includes a function, display icon, in the BIOS 110 for updating the icons.
- the BIOS functions 110 may be used by the POST program 108 , the operating system program 114 , or application programs, as needed.
- the computer system 100 may update the state icon 310 according to the flow diagrams.
- the state icon 310 is updated at different points during the boot of the computer system 100 .
- the POST program 108 is executed (block 402 ) and the state icon 310 is accordingly updated (block 404 ).
- the state icon 310 would be updated with the icon 330 . Because the operating system 114 is not yet loaded, the BIOS function, display icon, is used to update the state icon 310 .
- the display icon BIOS function is again used, this time to update the state icon 310 to indicate that the system is in an emergency mode.
- icon 342 is used.
- the computer system 100 next enters the emergency mode (block 410 ).
- the state icon 310 is updated to indicate that the operating system is booting (block 412 ). Again, the display icon BIOS function is used. Then, the operating system 114 boot loader is called (block 414 ).
- the state icon 310 is once again updated, to show that the operating system 114 is initializing (block 416 ).
- the icon 334 is used.
- the operating system 114 is initialized (block 418 ).
- the operating system 114 now has been initialized such that the LCD driver 130 may be loaded (block 420 ). This time, to update the state icon 310 , the LCD driver 130 is called, to indicate that the operating system 114 is now operational (block 422 ). In the embodiment of FIG. 3A , the icon 336 indicates this state.
- the operating system 114 may be shut down (block 424 ).
- the LCD driver 130 is called, to indicate this new state (block 426 ).
- the icon 338 indicates that the operating system 114 is shutting down.
- the operating system 114 may be halted. Accordingly, the LCD driver 130 is called (block 428 ).
- the icon 340 indicates that the operating system 114 is halted. Following the update of the state icon 310 , the operating system 114 is halted (block 430 ).
- the disk activity icons 312 may also be updated using the LCD driver 130 .
- the operating system 114 controls the disk activity icon 312 using a disk activity driver.
- the disk activity driver acts as a filter between a file system driver and a disk driver, such as used to control the hard disk drive 112 .
- a flow diagram illustrates the operation of the disk activity driver, according to one embodiment.
- access to the disk driver is initiated (block 452 ), such as by a file system driver.
- the disk activity driver then calls the LCD driver 130 , to update the disk activity icon 312 so that it is evident that a disk access is occurring (block 454 ).
- the disk activity driver passes the initial request onto the disk driver (block 456 ).
- the LCD driver 130 is not updated if a disk error occurs, despite detection of a disk access by the disk activity driver.
- the operating system 114 may call the LCD driver 130 during other disk activities. For example, should a back up of the hard disk drive 112 occur, the operating system 114 may call the LCD driver 130 to change the disk activity icon 312 .
- the operating system 114 In one embodiment, periodically calls a LAN activity service.
- the operation of the LAN activity service requests the number of successful sends and receives from a NIC driver using an NDIS query to retrieve the transmit and receive counters.
- the count is compared to a previous count (diamond 464 ). In one embodiment, if the number of transmit and receive packets exceeds the prior count, the LCD driver 130 is called, to indicate that LAN activity is occurring (block 466 ). If the count does not exceed the previous count, this indicates that no LAN activity is occurring, and accordingly, no update of the LAN activity icon 314 is necessary.
- the operating system 114 also controls updating the WAN activity icon 316 .
- the operating system invokes a WAN activity driver, which updates the WAN activity icon 316 on the display 124 .
- the WAN activity driver acts as a filter driver, intercepting requests intended for a modem driver.
- the WAN activity driver receives the request instead.
- the WAN activity drivers sends a request to the LCD driver 130 , so that the WAN activity icon 316 may be updated to indicate WAN activity.
- the WAN activity driver then passes the original request to the modem driver. Further, when all connections have been closed, the WAN activity driver also removes the WAN activity icon.
- the WAN activity driver according to one embodiment is illustrated. First, access to the modem driver is initiated (block 472 ). The WAN activity driver then calls the LCD driver 130 (block 474 ). Then, the original request is passed on to the modem driver (block 476 ).
- the sensor status icon 318 may be updated by the POST program 108 , by the operating system program 114 , or by other application software, such as diagnostic programs.
- the computer system 100 includes distinct sensors for monitoring temperature, voltage, operation of the fan, and whether the chassis is opened. Accordingly, in the embodiment of FIG. 3E , a temperature icon 362 , a voltage icon 364 , a fan icon 366 , and a chassis opened icon 368 may be placed in the sensor status icon 318 position of the LCD display 124 .
- the “please wait” icon 320 may likewise be used by any power-on routine to indicate that an operation may take an extended period of time.
- the “hourglass” icon 370 of FIG. 3F may be called by the LCD driver 130 or by the BIOS 110 function, display icon.
- a system provides a mechanism for the power-on state as well as other activities of a system to be visibly available to a user.
- different icons are available to represent distinct functional portions of the computer system: power-on state, LAN activity, disk activity, WAN activity, and sensor status.
Abstract
An LCD display provides language-independent icons for identifying state and/or activity information about a processor-based system. The LCD display includes a distinct portion for connoting different functional aspects of the system. Icons identifying the power-on state, disk activity, LAN activity, WAN activity, and sensor conditions are supplied.
Description
- This invention relates to server systems and, more particularly, to successful initialization of servers.
- A headless server is a server system which includes no keyboard, no mouse and no monitor. As expected, headless server systems typically operate without any human intervention. Because of this, headless server systems have higher reliability requirements than most other computer systems. Further, headless server systems ideally operate using minimal or no manual steps.
- For a typical computer system, the “boot” process is executed by a program, usually located in read-only memory (ROM) of the computer system. The ROM program may be described as including two separate processes: the power-on self test, or POST, and the basic input/output system, or BIOS. The POST part of the program executes commands such that different circuitry and components of the computer system may be initialized. The BIOS portion includes functions which may be used by software, including POST, for communicating with different devices in the computer system.
- Upon receiving power to the computer system, the POST program in the ROM immediately begins execution. The POST performs initialization functions, such as detecting and testing the memory, the display, the non-volatile media, such as hard disk and floppy disk drives, and so on. In some systems, an abbreviated POST, or “quick-boot,” may be available.
- Once the POST routine completes initialization and testing of the system, control is typically transferred to an operating system, usually located on the hard disk drive. Once the operating system gains control of the system, all run-time operations of the system, including any execution of application programs, are controlled by the operating system. The operating system may or may not utilize the BIOS functions in communicating with the hardware of the computer system.
- Currently, boot processes are designed for systems with a monitor, a keyboard and a mouse. These processes assume that the user is present in front of the system, and may thus be available to respond to any POST or operating system errors. These errors may take the form of beeps, screen displays, or other indicia. Typically, execution of either the POST or operating system program will stop once these errors occur. Manual intervention is generally the only way for the boot process to proceed. Contingencies, such as automatic attempts to boot from other devices, are typically not executed by the POST or operating system programs. Further, information is typically not shared between the operating system and the POST routine.
- Thus, there is a continuing need for a reliable and automated initialization process which may be assisted remotely.
-
FIG. 1 is a block diagram of the system according to one embodiment of the invention; -
FIG. 2 is a block diagram of theLCD display 124, according to one embodiment of the invention; -
FIGS. 3A through 3F are sample icons according to one embodiment of the invention; -
FIGS. 4A and 4B are flow diagrams for updating the state icon according to one embodiment of the invention; -
FIG. 5 is a flow diagram of the disk activity driver according to one embodiment of the invention; -
FIG. 6 is a flow diagram of the LAN activity service according to one embodiment of the invention; and -
FIG. 7 is a flow diagram of the WAN activity driver according to one embodiment of the invention. - In
FIG. 1 , acomputer system 100 includes aprocessor 102 and amemory 104, connected by asystem bus 126. Theprocessor 102 may generally refer to one or more central processing units (CPUs), microcontrollers or microprocessors, such as an X86 microprocessor, a Pentium® microprocessor or an advanced risk controller (ARM), as just a few examples. - Furthermore, the phrase “computer system” may refer to any type of processor-based system that may include a desktop computer, a laptop computer, a headless server, an appliance or a set-top box, as just a few examples. Thus, the invention is not intended to be limited to the illustrated
system 100, but rather, thesystem 100 is an example of one of many embodiments of the invention. - The
memory 104 may be one of a number of types of random access memories, such as dynamic random access memories (DRAMs), synchronous DRAMs (SDRAMs), and static RAMs (SRAMs). Other types ofmemory 104 may include single in-line memory modules (SIMMs) or double in-line memory modules (DIMMs). - The
computer system 100 further includes a South Bridge 115, between thesystem bus 126 and asecond bus 128. The South Bridge 115 is an input/output (I/O) controller which includes bridge support between thebuses hard disk drive 112, amodem 120, non-volatile read-only memory (NVRAM) 116, and read-only memory (ROM) 106. - In one embodiment, the
bus 128 is a Peripheral Component Interconnect (PCI)bus 128. The PCI bus is compliant with the PCI Local Bus Specification, Revision 2.2 (Jun. 8, 1998, available from the PCI Special Interest Group, Portland, Oreg. 97214). - Among other circuitry not shown, the
PCI bus 128 may support anetwork interface card 118, for high-speed connection of thecomputer system 100 to anetwork 250, such as a local area network (LAN) or a wide-area network (WAN). Alternatively, connection to thecomputer network 250 may employ themodem 120. In one embodiment, themodem 120 is a high-speed PCI modem, connected directly to thePCI bus 128. - Also connected to the
network 250 is acomputer system 200. In one embodiment, thecomputer system 200 acts as aremote console 200 to thecomputer system 100. Thecomputer system 200 may perform remote operations which assist in the successful boot of thecomputer system 100. - Looking back to the
computer system 100, in one embodiment, theROM 106 includes a power-on self test (POST) 108 program, and a basic input/output system (BIOS) 110 program. Alternatively, the POST 108 andBIOS 110 programs may reside in a flash memory device. TheROM 106 may also include non-volatile memory devices such as erasable and programmable read-only memories (EPROMs), electrically erasable and programmable read-only memories (EEPROMs), and flash memories. - In one embodiment, the
hard disk drive 112 may store anoperating system 114. Theoperating system 114 may be loaded into thememory 104, for faster execution. - For a headless server computer system, a monitor may not be present. However, in some embodiments, the headless server may include a small display, such as a small liquid crystal display (LCD), for error reporting. Accordingly, the
system bus 126 ofFIG. 1 is coupled to adisplay controller 123, to support adisplay 124, such as an LCD display. - Despite configuring the
computer system 100 such that remote assistance is available, theLCD display 124 may provide additional support for some fail-safe conditions. For example, theLCD display 124 may provide quick system status of thecomputer system 100. During initial power on, network access or other connection of thecomputer system 100 may not yet be established. - Further, as the
computer system 100 is being powered down, connection to theremote computer system 200 may have been removed. Where network problems occur, theremote system 200 may also be unavailable. Where tasks need to be performed on thecomputer system 100 itself, such as removing or replacing devices on the system, theLCD display 124 may provide relevant information. - In
FIG. 2 , the LCD display, according to one embodiment, includes amessage area 302, such as for providing text-based error or status messages, and six icon regions 310-320. Along with themessage area 302, the icon regions 310-320 may supply a user with relevant error and status information about thecomputer system 100. In one embodiment, the icon regions 310-320 are language-independent graphic elements. - In one embodiment, each icon provides status information for a distinct functional area of the
computer system 100. For example, astate icon 310 indicates where in the power-on, or “boot” process, thecomputer system 100 is currently executing. The boot process involves execution of thePOST program 108, loading theoperating system 114, and successful booting of theoperating system 114 such that application programs may operate. During this time, it may be difficult to identify where in the boot process thecomputer system 100 may be. Accordingly, thestate icon 310 may supply this information about thecomputer system 100. - In Table 1, according to one embodiment, are seven different icons that may be sent to the
state icon region 310. Each icon represents a distinct initialization state of thecomputer system 100. InFIG. 3A , icons 330-342 may be used to depict distinct initialization status. The icons may be displayed by thePOST program 108 or by theoperating system software 114, as described further inFIG. 4 , below.TABLE 1 State Icons State Icon Description POST display Machine is in POST. BIOS is icon 330in control OS Booting display Bootstrap about to be loaded icon 332by BIOS OS Initializing display OS booted and started running icon 334OS Running display OS fully up icon 336OS Shutting Down display OS starting graceful shut down icon 338OS Halted display OS mostly shutdown icon 340 Emergency Mode display System is in emergency mode. icon 342BIOS is in control - A
disk activity icon 312 provides status information about the hard disk drive or drives 112. In one embodiment, thedisk activity icon 312 region may be updated during disk accesses, to connote a disk error, to indicate that thedisk 112 is being checked, or to indicate that thedisk 112 is being rebuilt from a mirror disk or other backup media. - Table 2, according to one embodiment, shows how the
disk activity icon 312 may be updated in response to four states of the hard disk drive 112: normal (disk) activity, disk error, disk being checked, and disk being rebuilt. Likewise,FIG. 3B includes icons 344-350, which may be used asdisk activity icons 312. - For three of the states in Table 2, two icons are shown. Where two icons are shown, the
display 124 is updated with alternating icons, to provide an “animated”icon 312. Thus, for example, when disk activity occurs,icon 344 a is displayed, followed byicon 344 b, followed byicon 344 a again, and so on. This creates the animated effect of an arrow flashing above a disk drive.TABLE 2 Disk Activity Icons State Icon Description Normal alternate icons Flickered to show normal Operation 344a and 344b disk activity Disk Error display icon 346 Shown to depict a disk error Check disk alternate icons Flickered to depict that 348a and 348b disk is being checked Rebuilding alternate icons Flickered to depict that mirror 350a and 350b the mirror is being rebuilt from a mirror or from another backup media - Looking back at
FIG. 2 , aLAN activity icon 314 provides information relevant to the LAN connection of thecomputer system 100 to thenetwork 250. In one embodiment, theLAN activity icon 314 indicates when LAN activity is taking place, as well as when a LAN error occurs. - Table 3 and
FIG. 3C , according to one embodiment, show how theLAN activity icon 314 may be updated with flashing icon pairs 352 a and 352 b for normal operation and adistinct error icon 354, to indicate a LAN error.TABLE 3 LAN Activity Icons State Icon Description Normal Operation alternate icons Flickered to show 352a and 352b normal LAN activity LAN Error display icon 354 Shown to depict a LAN error - In
FIG. 2 , a wide-area network, or WAN,activity icon 316 also provides network-related information about thecomputer system 100, such as for connection to the Internet. Table 4 andFIG. 3D , according to one embodiment, show how theWAN activity icon 316 may be updated with flashing icon pairs 356 a and 356 b, for normal operation, while adistinct error icon 358 indicates a WAN error.TABLE 4 WAN Activity Icons State Icon Description Normal Operation alternate icons 356aFlickered to show and 356b normal WAN activity WAN Error display icon 358 Shown to depict a WAN error - A
sensor status icon 318 may be used to depict sensor conditions for thecomputer system 100. In one embodiment, thecomputer system 100 may include sensors for monitoring the voltage, the temperature, the operation of a fan, whether the chassis is opened, and other physical characteristics of thecomputer system 100. Some possiblesensor status icons 318, according to one embodiment, are shown in Table 5 andFIG. 3E .TABLE 5 Sensor Status (Health) Icons State Icon Description Normal Operation display All sensors are OK icon 360 Temperature Alert display A temperature sensor has icon 362generated an alert Voltage Alert display A voltage sensor has icon 364generated an alert Fan Alert display A fan sensor has generated icon 366an alert Intrusion Alert display The chassis has been opened icon 368 - A “please wait”
icon 320 is also provided, in some embodiments. The “please wait”icon 320 may be used by thePOST program 108, theoperating system software 114, or other applications to indicate that a process is ongoing, but not yet complete. For example, when a program is loaded, the “please wait”icon 320 may be sent to theLCD display 124. Table 6 shows the “please wait” icon according to one embodiment.TABLE 6 “Please Wait” Icon State Icon Description Normal Operation display System is running normally icon 360Please wait display Shown when a time consuming icon 370 or critical operation is taking place - Looking back to
FIG. 1 , in some embodiments, thecomputer system 100 includes anLCD driver 130 for sending configuration, status, and error information to thedisplay 124. TheLCD driver 130 may provide text information for themessage area 302 or may update one of the icons 310-320. TheLCD driver 130 is loaded by theoperating system 114 once thecomputer system 100 is initialized. - Particularly during early initialization of the
computer system 100, however, theLCD driver 130 may not be available for sending information to thedisplay 124. For the time prior to successfully loading theoperating system 114, for example, theLCD display driver 130 may not be used. Instead, in one embodiment, thecomputer system 100 includes a function, display icon, in theBIOS 110 for updating the icons. The BIOS functions 110 may be used by thePOST program 108, theoperating system program 114, or application programs, as needed. - In
FIGS. 4A and 4B , thecomputer system 100 may update thestate icon 310 according to the flow diagrams. Thestate icon 310 is updated at different points during the boot of thecomputer system 100. First, thePOST program 108 is executed (block 402) and thestate icon 310 is accordingly updated (block 404). In the embodiment ofFIG. 3A , thestate icon 310 would be updated with theicon 330. Because theoperating system 114 is not yet loaded, the BIOS function, display icon, is used to update thestate icon 310. - If the system is in an emergency mode (block 406), the display icon BIOS function is again used, this time to update the
state icon 310 to indicate that the system is in an emergency mode. In the embodiment ofFIG. 3A ,icon 342 is used. Thecomputer system 100 next enters the emergency mode (block 410). - If the system is not in an emergency mode, the
state icon 310 is updated to indicate that the operating system is booting (block 412). Again, the display icon BIOS function is used. Then, theoperating system 114 boot loader is called (block 414). - Just before initialization, the
state icon 310 is once again updated, to show that theoperating system 114 is initializing (block 416). In the embodiment ofFIG. 3A , theicon 334 is used. Next, theoperating system 114 is initialized (block 418). - In
FIG. 4B , theoperating system 114 now has been initialized such that theLCD driver 130 may be loaded (block 420). This time, to update thestate icon 310, theLCD driver 130 is called, to indicate that theoperating system 114 is now operational (block 422). In the embodiment ofFIG. 3A , theicon 336 indicates this state. - At some point, the
operating system 114 may be shut down (block 424). TheLCD driver 130 is called, to indicate this new state (block 426). In the embodiment ofFIG. 3A , theicon 338 indicates that theoperating system 114 is shutting down. - Following shut down of the
operating system 114, theoperating system 114 may be halted. Accordingly, theLCD driver 130 is called (block 428). In the embodiment ofFIG. 3A , theicon 340 indicates that theoperating system 114 is halted. Following the update of thestate icon 310, theoperating system 114 is halted (block 430). - The
disk activity icons 312 may also be updated using theLCD driver 130. In one embodiment, theoperating system 114 controls thedisk activity icon 312 using a disk activity driver. The disk activity driver acts as a filter between a file system driver and a disk driver, such as used to control thehard disk drive 112. - In
FIG. 5 , a flow diagram illustrates the operation of the disk activity driver, according to one embodiment. First, access to the disk driver is initiated (block 452), such as by a file system driver. The disk activity driver then calls theLCD driver 130, to update thedisk activity icon 312 so that it is evident that a disk access is occurring (block 454). Following this, the disk activity driver passes the initial request onto the disk driver (block 456). In some embodiments, theLCD driver 130 is not updated if a disk error occurs, despite detection of a disk access by the disk activity driver. - The
operating system 114 may call theLCD driver 130 during other disk activities. For example, should a back up of thehard disk drive 112 occur, theoperating system 114 may call theLCD driver 130 to change thedisk activity icon 312. - To monitor LAN activity, the
operating system 114, in one embodiment, periodically calls a LAN activity service. InFIG. 6 , the operation of the LAN activity service, according to one embodiment, requests the number of successful sends and receives from a NIC driver using an NDIS query to retrieve the transmit and receive counters. - After receiving a count of the transmit and receive packets (block 462), the count is compared to a previous count (diamond 464). In one embodiment, if the number of transmit and receive packets exceeds the prior count, the
LCD driver 130 is called, to indicate that LAN activity is occurring (block 466). If the count does not exceed the previous count, this indicates that no LAN activity is occurring, and accordingly, no update of theLAN activity icon 314 is necessary. - The
operating system 114 also controls updating theWAN activity icon 316. In one embodiment, the operating system invokes a WAN activity driver, which updates theWAN activity icon 316 on thedisplay 124. Like the disk driver, the WAN activity driver acts as a filter driver, intercepting requests intended for a modem driver. - When a requesting driver or application opens a handle and/or initiates a request to the modem driver, the WAN activity driver receives the request instead. When the request is received, the WAN activity drivers sends a request to the
LCD driver 130, so that theWAN activity icon 316 may be updated to indicate WAN activity. The WAN activity driver then passes the original request to the modem driver. Further, when all connections have been closed, the WAN activity driver also removes the WAN activity icon. - In
FIG. 7 , the WAN activity driver according to one embodiment is illustrated. First, access to the modem driver is initiated (block 472). The WAN activity driver then calls the LCD driver 130 (block 474). Then, the original request is passed on to the modem driver (block 476). - The
sensor status icon 318 may be updated by thePOST program 108, by theoperating system program 114, or by other application software, such as diagnostic programs. In one embodiment, thecomputer system 100 includes distinct sensors for monitoring temperature, voltage, operation of the fan, and whether the chassis is opened. Accordingly, in the embodiment ofFIG. 3E , atemperature icon 362, avoltage icon 364, afan icon 366, and a chassis openedicon 368 may be placed in thesensor status icon 318 position of theLCD display 124. - The “please wait”
icon 320 may likewise be used by any power-on routine to indicate that an operation may take an extended period of time. In one embodiment, the “hourglass”icon 370 ofFIG. 3F may be called by theLCD driver 130 or by theBIOS 110 function, display icon. - Thus, in some embodiments a system provides a mechanism for the power-on state as well as other activities of a system to be visibly available to a user. In some embodiments, different icons are available to represent distinct functional portions of the computer system: power-on state, LAN activity, disk activity, WAN activity, and sensor status.
- While the present invention has been described with respect to a limited number of embodiments, those skilled in the art will appreciate numerous modifications and variations therefrom. It is intended that the appended claims cover all such modifications and variations as fall within the true spirit and scope of this present invention.
Claims (21)
1-14. (canceled)
15. A method comprising:
executing a power-on routine;
identifying a portion of the power-on routine with a state;
retrieving an icon from a memory to represent the state; and
sending the icon to a display coupled to a headless server system.
16. The method of claim 15 , further comprising:
identifying a second portion of the power-on routine with a second state;
retrieving a second icon from the memory to represent the second state; and
sending the second icon to the display.
17. The method of claim 15 , wherein sending the icon to the display comprises sending the icon through a display controller of the headless server system to the display, wherein the display is included in the headless server system.
18. The method of claim 15 , further comprising sending the icon to the display before the headless server system has established network access.
19. The method of claim 15 , further comprising sending the icon to an icon region of the display corresponding to the icon.
20. The method of claim 15 , further comprising using a basic input/output system function to send the icon to the display.
21. The method of claim 15 , wherein sending the icon to the display comprises sending the icon to a liquid crystal display.
22. A system comprising:
a processor;
a memory coupled to the processor; and
a medium coupled to the processor including instructions that, when executed enable the system to:
execute a power-on routine;
identify a portion of the power-on routine with a state;
retrieve an icon from the memory to represent the state; and
send the icon to a display of the system, wherein the system comprises a headless server.
23. The system of claim 22 , wherein the instructions, when executed enable the system to:
identify a second portion of the power-on routine with a second state;
retrieve a second icon from the memory to represent the second state; and
send the second icon to the display.
24. The system of claim 22 , wherein the instructions, when executed enable the system to send the icon through a display controller of the headless server to the display.
25. The system of claim 22 , wherein the instructions, when executed enable the system to send a message to the display before the headless server has established network access.
26. The system of claim 22 , wherein the instructions, when executed enable the system to use a basic input/output system function to send the icon to the display.
27. The system of claim 22 , wherein the display comprises a liquid crystal display.
28. The system of claim 27 , wherein the liquid crystal display includes a first region to display a plurality of icons and a second region to display message information.
29. An article comprising a machine-accessible medium including instructions that enable a system to:
execute a power-on routine;
identify a portion of the power-on routine with a state;
retrieve an icon from a memory to represent the state; and
send the icon to a display physically located with the system, wherein the system comprises a headless server.
30. The article of claim 29 , further storing instructions that enable the system to:
identify a second portion of the power-on routine with a second state;
retrieve a second icon from the memory to represent the second state; and
send the second icon to the display.
31. The article of claim 29 , wherein the instructions further enable the system to send the icon through a display controller of the headless server to the display.
32. The article of claim 29 , wherein the instructions further enable the system to send a message to the display.
33. The article of claim 29 , wherein the instructions further enable the system to send the icon to an icon region of the display corresponding to the icon.
34. The article of claim 29 , wherein the instructions further enable the system to use a basic input/output system function to send the icon to the display.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/100,884 US20050198583A1 (en) | 2000-02-25 | 2005-04-07 | State/activity indication using icons on an LCD |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/513,425 US6901557B1 (en) | 2000-02-25 | 2000-02-25 | State/activity indication using icons on an LCD |
US11/100,884 US20050198583A1 (en) | 2000-02-25 | 2005-04-07 | State/activity indication using icons on an LCD |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/513,425 Continuation US6901557B1 (en) | 2000-02-25 | 2000-02-25 | State/activity indication using icons on an LCD |
Publications (1)
Publication Number | Publication Date |
---|---|
US20050198583A1 true US20050198583A1 (en) | 2005-09-08 |
Family
ID=34590110
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/513,425 Expired - Fee Related US6901557B1 (en) | 2000-02-25 | 2000-02-25 | State/activity indication using icons on an LCD |
US11/100,884 Abandoned US20050198583A1 (en) | 2000-02-25 | 2005-04-07 | State/activity indication using icons on an LCD |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/513,425 Expired - Fee Related US6901557B1 (en) | 2000-02-25 | 2000-02-25 | State/activity indication using icons on an LCD |
Country Status (1)
Country | Link |
---|---|
US (2) | US6901557B1 (en) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20060026451A1 (en) * | 2004-07-28 | 2006-02-02 | Voigt Douglas L | Managing a fault tolerant system |
US20130036453A1 (en) * | 2004-08-02 | 2013-02-07 | Microsoft Corporation | System, method and user interface for network status reporting |
US20150169528A1 (en) * | 2006-09-13 | 2015-06-18 | Carl Sjogreen | Calendar information events |
Families Citing this family (19)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2001337812A (en) * | 2000-03-23 | 2001-12-07 | Fujitsu Ltd | Status representation control device and electronic device, and record medium |
JP3563721B2 (en) * | 2001-09-21 | 2004-09-08 | 株式会社東芝 | Information processing apparatus and clock display control method used in the information processing apparatus |
JP4072459B2 (en) * | 2003-05-14 | 2008-04-09 | Necパーソナルプロダクツ株式会社 | Information terminal device and user environment display method using information terminal device |
US7738242B2 (en) * | 2004-01-08 | 2010-06-15 | Hewlett-Packard Development Company, L.P. | System and method for displaying chassis component information |
US20050193104A1 (en) * | 2004-02-27 | 2005-09-01 | Wyse Technology Inc. | User interface for remote computing devices |
US7434171B2 (en) * | 2004-03-25 | 2008-10-07 | Intel Corporation | Performance control apparatus |
KR100678937B1 (en) * | 2004-09-03 | 2007-02-07 | 삼성전자주식회사 | Method and apparatus for providing information in digital device using user-friendly method |
US20060122916A1 (en) * | 2004-10-19 | 2006-06-08 | Peter Kassan | System and method for dynamic e-commerce shopping icons |
AU2005295448A1 (en) * | 2004-10-19 | 2006-04-27 | Peter Kassan | System and method for dynamic e-commerce shopping icons |
US7916487B2 (en) * | 2005-03-30 | 2011-03-29 | Yosef Bitton | Method and apparatus for the enhanced disaster survivability of a networked computer server |
US8341537B2 (en) * | 2006-02-28 | 2012-12-25 | Microsoft Corporation | Indication of delayed content output in a user interface |
US8325485B2 (en) * | 2008-12-30 | 2012-12-04 | Gateway, Inc. | Removable system management information display |
USD667448S1 (en) * | 2011-09-12 | 2012-09-18 | Microsoft Corporation | Display screen with icon |
USD667433S1 (en) * | 2011-09-12 | 2012-09-18 | Microsoft Corporation | Display screen with icon |
USD667434S1 (en) * | 2011-09-12 | 2012-09-18 | Microsoft Corporation | Display screen with icon |
USD667447S1 (en) * | 2011-09-12 | 2012-09-18 | Microsoft Corporation | Display screen with icon |
USD667432S1 (en) * | 2011-09-12 | 2012-09-18 | Microsoft Corporation | Display screen with icon |
CN104765666B (en) * | 2015-04-17 | 2018-04-24 | 南车株洲电力机车研究所有限公司 | The maintaining method that a kind of train display does not start |
CN108845857A (en) * | 2018-06-13 | 2018-11-20 | 郑州云海信息技术有限公司 | A kind of icon management method and device based on cloud platform |
Citations (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5247815A (en) * | 1992-04-17 | 1993-09-28 | Caldwell Michael V | Tire clamp for preventing theft of a vehicle |
US5442740A (en) * | 1993-07-13 | 1995-08-15 | International Business Machines Corporation | Method and apparatus for visual display of program performance trace data |
US5455904A (en) * | 1990-08-02 | 1995-10-03 | Bull S.A. | Method of sizing or moving windows |
US5617526A (en) * | 1994-12-13 | 1997-04-01 | Microsoft Corporation | Operating system provided notification area for displaying visual notifications from application programs |
US5809449A (en) * | 1996-10-30 | 1998-09-15 | Hewlett-Packard Company | Indicator of battery current for portable devices |
US5903269A (en) * | 1995-10-10 | 1999-05-11 | Anysoft Ltd. | Apparatus for and method of acquiring processing and routing data contained in a GUI window |
US5905914A (en) * | 1992-09-17 | 1999-05-18 | Kabushiki Kaisha Toshiba | Portable computer having dedicated register group and peripheral controller bus between system bus and peripheral controller |
US5953010A (en) * | 1997-08-01 | 1999-09-14 | Sun Microsystems, Inc. | User-friendly iconic message display indicating progress and status of loading and running system program in electronic digital computer |
US5956507A (en) * | 1996-05-14 | 1999-09-21 | Shearer, Jr.; Bennie L. | Dynamic alteration of operating system kernel resource tables |
US5958058A (en) * | 1997-07-18 | 1999-09-28 | Micron Electronics, Inc. | User-selectable power management interface with application threshold warnings |
US6014141A (en) * | 1997-03-25 | 2000-01-11 | Micron Electronics, Inc. | Method and apparatus for selectively displaying a parameter in a separate status panel |
US6122746A (en) * | 1997-05-13 | 2000-09-19 | Micron Electronics, Inc. | System for powering up and powering down a server |
US6121967A (en) * | 1998-05-04 | 2000-09-19 | Apple Computer, Inc. | Method and apparatus for controlling media bays in a computer system |
US6732159B1 (en) * | 2000-01-27 | 2004-05-04 | Middle Digital Inc. | Apparatus and method for remote administration of a PC-server |
US20050204392A1 (en) * | 1998-05-06 | 2005-09-15 | Samsung Electronics Co., Ltd. | Apparatus for and method of creating a device page for a device which does not support a predetermined protocol on a home network |
Family Cites Families (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5274815A (en) * | 1991-11-01 | 1993-12-28 | Motorola, Inc. | Dynamic instruction modifying controller and operation method |
-
2000
- 2000-02-25 US US09/513,425 patent/US6901557B1/en not_active Expired - Fee Related
-
2005
- 2005-04-07 US US11/100,884 patent/US20050198583A1/en not_active Abandoned
Patent Citations (16)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5455904A (en) * | 1990-08-02 | 1995-10-03 | Bull S.A. | Method of sizing or moving windows |
US5247815A (en) * | 1992-04-17 | 1993-09-28 | Caldwell Michael V | Tire clamp for preventing theft of a vehicle |
US5905914A (en) * | 1992-09-17 | 1999-05-18 | Kabushiki Kaisha Toshiba | Portable computer having dedicated register group and peripheral controller bus between system bus and peripheral controller |
US5442740A (en) * | 1993-07-13 | 1995-08-15 | International Business Machines Corporation | Method and apparatus for visual display of program performance trace data |
US5617526A (en) * | 1994-12-13 | 1997-04-01 | Microsoft Corporation | Operating system provided notification area for displaying visual notifications from application programs |
US5903269A (en) * | 1995-10-10 | 1999-05-11 | Anysoft Ltd. | Apparatus for and method of acquiring processing and routing data contained in a GUI window |
US5956507A (en) * | 1996-05-14 | 1999-09-21 | Shearer, Jr.; Bennie L. | Dynamic alteration of operating system kernel resource tables |
US5809449A (en) * | 1996-10-30 | 1998-09-15 | Hewlett-Packard Company | Indicator of battery current for portable devices |
US6014141A (en) * | 1997-03-25 | 2000-01-11 | Micron Electronics, Inc. | Method and apparatus for selectively displaying a parameter in a separate status panel |
US6122746A (en) * | 1997-05-13 | 2000-09-19 | Micron Electronics, Inc. | System for powering up and powering down a server |
US5958058A (en) * | 1997-07-18 | 1999-09-28 | Micron Electronics, Inc. | User-selectable power management interface with application threshold warnings |
US5953010A (en) * | 1997-08-01 | 1999-09-14 | Sun Microsystems, Inc. | User-friendly iconic message display indicating progress and status of loading and running system program in electronic digital computer |
US6121967A (en) * | 1998-05-04 | 2000-09-19 | Apple Computer, Inc. | Method and apparatus for controlling media bays in a computer system |
US20050204392A1 (en) * | 1998-05-06 | 2005-09-15 | Samsung Electronics Co., Ltd. | Apparatus for and method of creating a device page for a device which does not support a predetermined protocol on a home network |
US6993785B1 (en) * | 1998-05-06 | 2006-01-31 | Samsung Electronics Co., Ltd. | Apparatus for and method of creating a device page for a device which does not support a predetermined protocol on a home network |
US6732159B1 (en) * | 2000-01-27 | 2004-05-04 | Middle Digital Inc. | Apparatus and method for remote administration of a PC-server |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20060026451A1 (en) * | 2004-07-28 | 2006-02-02 | Voigt Douglas L | Managing a fault tolerant system |
US7299385B2 (en) * | 2004-07-28 | 2007-11-20 | Hewlett-Packard Development Company, L.P. | Managing a fault tolerant system |
US20130036453A1 (en) * | 2004-08-02 | 2013-02-07 | Microsoft Corporation | System, method and user interface for network status reporting |
US20150169528A1 (en) * | 2006-09-13 | 2015-06-18 | Carl Sjogreen | Calendar information events |
Also Published As
Publication number | Publication date |
---|---|
US6901557B1 (en) | 2005-05-31 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20050198583A1 (en) | State/activity indication using icons on an LCD | |
US6763456B1 (en) | Self correcting server with automatic error handling | |
US6487464B1 (en) | Power-on software for robust boot | |
JP4887150B2 (en) | Method and apparatus for monitoring and resetting a coprocessor | |
JP4688821B2 (en) | Method and apparatus for remote correction of system configuration | |
US7577731B2 (en) | System and method for monitoring program code | |
US6691225B1 (en) | Method and apparatus for deterministically booting a computer system having redundant components | |
US7143275B2 (en) | System firmware back-up using a BIOS-accessible pre-boot partition | |
US6324644B1 (en) | Network enhanced bios enabling remote management of a computer without a functioning operating system | |
US6173417B1 (en) | Initializing and restarting operating systems | |
US6189114B1 (en) | Data processing system diagnostics | |
US7111202B2 (en) | Autonomous boot failure detection and recovery | |
US6216226B1 (en) | Method and system for dynamically selecting a boot process within a data processing system | |
US6826710B2 (en) | System and method for providing a fault-resilient boot | |
US6505298B1 (en) | System using an OS inaccessible interrupt handler to reset the OS when a device driver failed to set a register bit indicating OS hang condition | |
US7269768B2 (en) | Method and system to provide debugging of a computer system from firmware | |
US20060168576A1 (en) | Method of updating a computer system to a qualified state prior to installation of an operating system | |
US9985831B2 (en) | Method and apparatus for remote modification of system configuration | |
US6725396B2 (en) | Identifying field replaceable units responsible for faults detected with processor timeouts utilizing IPL boot progress indicator status | |
US7900033B2 (en) | Firmware processing for operating system panic data | |
CN113672250A (en) | Interface and warm reset path for memory device firmware upgrade | |
US20080250268A1 (en) | Method, system, and product for providing extended error handling capability in host bridges | |
US8166152B1 (en) | Architecture and method for monitoring system resources within an enterprise network | |
US20050033952A1 (en) | Dynamic scheduling of diagnostic tests to be performed during a system boot process | |
JP2002215399A (en) | Computer system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |