Abstract: Embodiments of a method and system for managing a system are disclosed herein. The method and system provides a means to permanently and/or securely store core system configuration information so that the core system configuration information stays with a particular system, such as a computing device or motherboard for example. The method and system provide a means for channel integrators, manufacturers, and technicians to quickly troubleshoot and return a system to full service after receiving the system from a customer as part of an unstable, non-functioning, or other system service event. Other embodiments are described and claimed.

Abstract: An embodiment of the present invention relates generally to computer configuration and, more specifically, to a system and method to seamlessly determine the component configurations of a series of heterogeneous platforms and enable their respective component configurations to be intelligently migrated from one platform to another. In some embodiments, the invention involves generating configuration binaries for a plurality of target platforms. The configuration binaries are used with tools to create configuration directives for the target machines. In at least one embodiment, the configuration directives are sent to the target platforms in a scripting language. In some embodiments, the scripts are automatically generated by a tool using the configuration binaries for various platforms and policy guidance to determine which settings should be set on or off. Other embodiments are described and claimed.

Abstract: A method and apparatus provides hardware-configured wake-up events for a computer operating system compliant with an advanced configuration and power interface (ACPI) protocol without requiring additional hardware. The method and apparatus includes generation of a system management interrupt (SMI) during normal ACPI working-to-sleep transition allowing a basic input-output system (BIOS) circuit to enable additional wake-up events independent of the computer operating system.

Abstract: A startup program for protecting against corruption of firmware resides in multiple blocks of a firmware device in a processor-based system. While the firmware device typically stores code, the device may additionally store data that is accessible to application programs. The startup program confirms that the block from which it executes is a valid startup block. If the block is not a valid startup block, the startup program searches the other blocks in the firmware device for a valid startup block. Upon identifying a valid startup block, the startup program sets an execution address such that subsequent initialization of the processor-based system occurs from the startup block.

Abstract: A method and apparatus for the dynamic inclusion or exclusion of initialization modules within the set of initialization modules designated as recovery initialization modules is described. When a BIOS system is updated through the inclusion of a new initialization module, the algorithm of the present invention dynamically determines if the initialization module is required for recovery. A firmware update utility evaluates new initiation modules to determine if they are designated as recovery or required by core recovery modules. If so, the new module is designated for recovery and stored to a fault-tolerant block within a recovery file volume. The firmware update utility of the present invention allows an initiation module to be automatically designated as recovery only when necessary. Initiation modules, designated as recovery, that subsequently are not required fro recovery may be omitted from the recovery set. Thus the collection of recovery initiation modules is minimized.

Abstract: A startup program for protecting against corruption of firmware resides in multiple blocks of a firmware device in a processor-based system. While the firmware device typically stores code, the device may additionally store data that is accessible to application programs. The startup program confirms that the block from which it executes is a valid startup block. If the block is not a valid startup block, the startup program searches the other blocks in the firmware device for a valid startup block. Upon identifying a valid startup block, the startup program sets an execution address such that subsequent initialization of the processor-based system occurs from the startup block.

Abstract: A system and method for upgrading a boot block of a firmware program is disclosed. A copy of a replacement boot block is transferred to a firmware device, and then the execution address is changed to point to this new location. The replacement boot block is then copied over the original boot block. Once the copying is complete, the execution address is restored to the original location in the firmware program.