Abstract: A method and an information handling system (IHS) provide hierarchical failure recovery for firmware components of the information handling system. According to one aspect, a hierarchical recovery and learning module (HRLM) detects firmware component failure. The HRLM initiates a hierarchical failure recovery by executing recovery sequences from a set of hierarchically ordered recovery sequences. The HRLM determines whether the detected failure was corrected by executing the recovery sequence. If the HRLM further determines that the failure is not corrected by executing the set of hierarchically ordered recovery sequences, the HRLM dynamically generates a new recovery sequence(s) using commands selected from at least one of the previously executed recovery sequences and executes the new recovery sequence(s). If the failure is corrected by a new recovery sequence, the HRLM forwards the particular recovery sequence to a customer support site for use by other systems in addressing similar or identical failures.

Abstract: A method and an information handling system (IHS) provide hierarchical failure recovery for firmware components of the information handling system. According to one aspect, a hierarchical recovery and learning module (HRLM) detects firmware component failure. The HRLM initiates a hierarchical failure recovery by executing recovery sequences from a set of hierarchically ordered recovery sequences. The HRLM determines whether the detected failure was corrected by executing the recovery sequence. If the HRLM further determines that the failure is not corrected by executing the set of hierarchically ordered recovery sequences, the HRLM dynamically generates a new recovery sequence(s) using commands selected from at least one of the previously executed recovery sequences and executes the new recovery sequence(s). If the failure is corrected by a new recovery sequence, the HRLM forwards the particular recovery sequence to a customer support site for use by other systems in addressing similar or identical failures.

Abstract: Loading software on a plurality of processors is presented. A processing unit (PU) retrieves a file from system memory and loads it into its internal memory. The PU extracts a processor type from the file's header which identifies whether the file should execute on the PU or a synergistic processing unit (SPU). If an SPU should execute the file, the PU DMA's the file to the SPU for execution. In one embodiment, the file is a combined file which includes both PU and SPU code. In this embodiment, the PU identifies one or more section headers included in the file which indicates embedded SPU code within the combined file. In this embodiment, the PU extracts the SPU code from the combined file and DMA's the extracted code to an SPU for execution.

Abstract: Loading software on a plurality of processors is presented. A processing unit (PU) retrieves a file from system memory and loads it into its internal memory. The PU extracts a processor type from the file's header which identifies whether the file should execute on the PU or a synergistic processing unit (SPU). If an SPU should execute the file, the PU DMA's the file to the SPU for execution. In one embodiment, the file is a combined file which includes both PU and SPU code. In this embodiment, the PU identifies one or more section headers included in the file which indicates embedded SPU code within the combined file. In this embodiment, the PU extracts the SPU code from the combined file and DMA's the extracted code to an SPU for execution.

Abstract: A processing unit (PU) retrieves a file from system memory and loads it into its internal memory. The PU extracts a processor type from the file's header which identifies whether the file should execute on the PU or a synergistic processing unit (SPU). If an SPU should execute the file, the PU DMA's the file to the SPU for execution. In one embodiment, the file is a combined file which includes both PU and SPU code. In this embodiment, the PU identifies one or more section headers included in the file which indicates embedded SPU code within the combined file. In this embodiment, the PU extracts the SPU code from the combined file and DMA's the extracted code to an SPU for execution.

Abstract: The field of invention relates to a method, means, and device for acquiring user input by a computer and, more particularly, a new and improved method of customizing a user interface to each specific task performed by a user such that the user interface customizes itself without the user having to modify multiple sets of preferences.

Abstract: A method and system for efficiently handling events occurring in an environment in a data processing system. The data processing system includes multiple environments and objects that may be used in different environments. Each object includes an action that is triggered in response to an event. An event manager object is created for handling events from different environments. Events are registered for the objects. An action is triggered using the event manager object in response to detecting an event occurring in the data processing system, wherein events occurring in an environment are efficiently handled.

Abstract: A method and system for invoking a subroutine from within an object and an object oriented system. The object oriented system is executing on a data processing system and includes a plurality of subroutines and classes. A subroutine may be called from within the object using an address for the subroutine. Callback arrays are employed within the object, wherein each callback array belongs to different class within the plurality of classes. Additionally, each object includes at least one slot identified by an integer. Each slot includes an address for one of the subroutines. A class identifier is accepted to identify one of the callback arrays within the object. An integer is employed to select a slot within the array identified by the class identifier. The address located within the selected slots of the identified array is employed to call a subroutine, wherein the complexity of managing callbacks are reduced.

Abstract: An object model-based visual builder is provided which includes proxy objects at build time, each corresponding to a target object at runtime. Each such proxy object has associated therewith several items of information, including the class of the target object corresponding to the proxy object, presentation information, properties and how they are mapped to IDL attributes and operations, events available on the target object, and operations supported by the target object. A portion of such information is stored in an Interface Repository, such as the System Object Model (SOM) Interface Repository, in easily changeable form, with the necessary knowledge for retrieving such information from the Interface Repository being contained in the proxy object itself. The information stored in the Interface Repository may be changed without altering or recompiling the source code which implements the proxy object itself.

Abstract: A system and method whereby the cursor displayed by a data processing system on a monitor is automatically moved to a preselected location on the desktop, called the parking area, whenever it has been inactive for a predetermined amount of time. If the window focus is dependent on the location of the cursor, the parking area can be located within a specified window.

Abstract: A system and method are provided for implementing an improved visual builder. A proxy tree comprised of proxy objects is visually built. Each proxy object corresponds to a target object in a runtime hierarchical target object tree. Proxy object interfaces, as seen by the user, are decoupled or separately and independently defined from the interfaces of the target objects. Accordingly, arbitrary mapping of proxy properties and operations to IDL attributes and operations is provided for. Visibility and grouping control is also provided to proxy properties and operations whereby the visual builder is not forced to present the exact attributes and operations of the target objects dictated by a given object definition which may be less user-friendly, inappropriate, or unnecessary in a visual builder environment.