Abstract: Examples herein disclose a command to control a use of a test key for installation of a test basic input output system (BIOS). The examples validate a command and replace at least a portion of a production BIOS with the test BIOS based on an allowance of the test key.

Abstract: Example embodiments disclosed herein relate to backing up firmware. An operating system can be initialized. During the initialization process, memory can be set. The firmware can be backed up to storage based on the set memory.

Abstract: In response to starting a system including a first non-volatile memory containing system boot code, and a second non-volatile memory, provisioning of the second non-volatile memory is performed. The provisioning includes checking that the second non-volatile memory is uninitialized, and in response to determining that the second non-volatile memory is uninitialized, the system boot code is copied from the first non-volatile memory to the second non-volatile memory.

Abstract: Example embodiments disclosed herein relate to backing up firmware. An operating system can be initialized. During the initialization process, memory can be set. The firmware can be backed up to storage based on the set memory.

Abstract: A BIOS storage device including driver variable records, a corruption detection engine and a corruption remediation engine, wherein the corruption detection engine is to evaluate a plurality of driver variable records stored in an area of a BIOS storage device for corruption, and a corruption remediation engine is to replace a corrupt driver variable record with a last known good version of the driver variable record.

Abstract: Example embodiments disclosed herein relate to backing up firmware. An operating system can be initialized. During the initialization process, memory can be set. The firmware can be backed up to storage based on the set memory.

Abstract: Examples herein disclose a command to control a use of a test key for installation of a test basic input output system (BIOS). The examples validate a command and replace at least a portion of a production BIOS with the test BIOS based on an allowance of the test key.

Abstract: In accordance with at least some embodiments, a system includes a first processor and a second processor. The system also includes a boot task storage medium that can only be accessed by one processor at a time. A boot process of the system has a first stage and a second stage. During the first stage, the first processor fetches and executes boot tasks without assistance from the second processor. During the second stage, boot task execution performed by first processor overlaps with at least one boot task fetch performed by the second processor.

Abstract: In response to starting a system including a first non-volatile memory containing system boot code, and a second non-volatile memory, provisioning of the second non-volatile memory is performed. The provisioning includes checking that the second non-volatile memory is uninitialized, and in response to determining that the second non-volatile memory is uninitialized, the system boot code is copied from the first non-volatile memory to the second non-volatile memory.

Abstract: A BIOS storage device including driver variable records, a corruption detection engine and a corruption remediation engine, wherein the corruption detection engine is to evaluate a plurality of driver variable records stored in an area of a BIOS storage device for corruption, and a corruption remediation engine is to replace a corrupt driver variable record with a last known good version of the driver variable record.

Abstract: Example embodiments disclosed herein relate to backing up firmware. An operating system can be initialized. During the initialization process, memory can be set. The firmware can be backed up to storage based on the set memory.

Abstract: A computer system comprises a Basic Input/Output System (“BIOS”) graphical engine and a BIOS graphics look and feel module. The BIOS graphics look and feel module is separate from the BIOS graphical engine, and comprises a look and feel definition that defines the appearance and behavior of BIOS graphical user interface displays presented to a user before an operating system acquires control of the system. The BIOS graphical engine transforms information to be displayed for a user in accordance with the look and feel definition to provide a uniform appearance and behavior to graphical displays provided to the user.

Abstract: In accordance with at least some embodiments, a system includes a first processor and a second processor. The system also includes a boot task storage medium that can only be accessed by one processor at a time. A boot process of the system has a first stage and a second stage. During the first stage, the first processor fetches and executes boot tasks without assistance from the second processor. During the second stage, boot task execution performed by first processor overlaps with at least one boot task fetch performed by the second processor.

Abstract: An electronic device data access method comprising sharing, by an operating system and a pre-boot environment module, data stored in a hard disk drive in the electronic device and accessing the data using a block location list identifying a storage location for each portion of the stored data.

Abstract: A computer system comprises a Basic Input/Output System (“BIOS”) graphical engine and a BIOS graphics look and feel module. The BIOS graphics look and feel module is separate from the BIOS graphical engine, and comprises a look and feel definition that defines the appearance and behavior of BIOS graphical user interface displays presented to a user before an operating system acquires control of the system. The BIOS graphical engine transforms information to be displayed for a user in accordance with the look and feel definition to provide a uniform appearance and behaviour to graphical displays provided to the user.

Abstract: An electronic device data access method comprising sharing, by an operating system and a pre-boot environment module, data stored in a hard disk drive in the electronic device and accessing the data using a block location list identifying a storage location for each portion of the stored data.