Abstract:
A method for registering and initiating a pre-boot environment for enabling partitions. The method provides a basic input output system (CIOS) with an application program interface (API) that accesses a Logical Clock Address (LCA) sector number when a boot configuration flag is set, the LCA sector number stores an operating environment manager which then boots the information handling system to an appropriate partition.

Description:
BACKGROUND OF THE INVENTION 
   1. Field of the Invention 
   The present invention relates to the field of registering and initiating pre-boot environments and more particularly to registering and initiating pre-boot environments in a Windows Vista type operating system for enabling partitions. 
   2. Description of the Related Art 
   As the value and use of information continues to increase, individuals and businesses seek additional ways to process and store information. One option available to users is information handling systems. An information handling system generally processes, compiles, stores, and/or communicates information or data for business, personal, or other purposes thereby allowing users to take advantage of the value of the information. Because technology and information handling needs and requirements vary between different users or applications, information handling systems may also vary regarding what information is handled, how the information is handled, how much information is processed, stored, or communicated, and how quickly and efficiently the information may be processed, stored, or communicated. The variations in information handling systems allow for information handling systems to be general or configured for a specific user or specific use such as financial transaction processing, airline reservations, enterprise data storage, or global communications. In addition, information handling systems may include a variety of hardware and software components that may be configured to process, store, and communicate information and may include one or more computer systems, data storage systems, and networking systems. 
   It is known to provide information handling systems with a plurality of partitions. For example, it is known to provide MediaDirect and System Restore (PC Restore) solutions. These solutions are designed to boot into their respective partitions using some form of dynamic modifications done to a master boot record (MBR) every time a customer tries to boot into one of these partitions. 
   For example,  FIG. 1 , labeled prior art, shows an example implementation of booting into a MediaDirect partition for an XP type operating system. More specifically,  FIG. 1  shows an example of booting into a MediaDirect partition from either a sleeping state (S 4 ) or a soft-off state (S 5 ) of an advanced Configuration and Power Interface (ACPI) compliant information handling system. 
   When a user actuates a MediaDirect button located on the information handling system from either the S 4  or S 5  state, the basic input output system (BIOS) of the information handling system sets a Simple Boot Flag (which may be stored within the configuration memory (e.g., the CMOS memory) of the information handling system) indicating the information handling system was powered on by the MediaDirect button. The information handling system boots to the hard drive, which is initiated by execution of the MBR boot code. The updated MBR boot code detects the Simple Boot Flag in the configuration memory and executes (i.e., jumps to) an Extended MBR Boot Code residing in unused sectors on track  0  of hard drive  0 . The jump to command is executed from a bootstrap section of MBR. The Extended MBR Boot Code, using the MediaDirect MBR stored in track  0 , unlocks the MediaDirect partition and boots to this partition. Thus, a MediaDirect installer program modifies the Master Boot Record (MBR). The MBR is modified so that the operating system on the MediaDirect partition is booted when the user starts the system by pressing the media button. 
   There are a plurality of issues relating to the use of this mechanism, especially with respect to a Windows Vista type operating system. For example, a Windows Vista type operating system may prohibit any custom version of the Master Boot Record. Therefore, if this were the case, a MediaDirect installer would be unable to modify the MBR on systems with Windows Vista. If the operating system is one that prohibits custom versions of the Master Boot Record, then it is desirable to provide an alternate mechanism to continue enabling booting to MediaDirect and System Restore partitions stored on the information handing system. 
   Additionally, MBR modifications may account for potential quality issues. It is often the case that errors in the execution of a PC Restore partition are due to MBR related issues. Additionally, MBR modifications can also cause booting difficulty (e.g., blue screen issues) with certain information handling systems. 
   Accordingly, it is desirable to provide a method for registering and initiating a pre-boot environment for enabling partitions. 
   SUMMARY OF THE INVENTION 
   In accordance with the present invention, a method for registering and initiating a pre-boot environment for enabling partitions is set forth. The method provides a BIOS with an application program interface (API) that accesses a Logical Block Address (LBA) sector number when a boot configuration flag is set, the LBA sector number stores an operating environment manager which then boots the information handling system to an appropriate partition. 
   The operating environment manager may be called either during the manufacturing process or in the field by the API of the BIOS to provide the BIOS with the LBA sector number which is stored within a boot drive. In certain embodiments, the LBA sector number includes a 64-bit LBA address which is stored within the BIOS. 
   The operating environment manager code is stored within predetermined sectors of the boot drive during manufacture or field service of the information handling system. In certain embodiments, the first sector (assuming more than one, but not necessarily) binary also includes the LBA address so that operating environment manager code can locate additional sectors that contain the continuation of the operating environment manager code (again, assuming more than one sector is required to store the operating environment code). 
   When customer actuates a button such as the MediaDirect button, BIOS detects that a MediaDirect mode is desired. The BIOS then reads the LBA address that was previously stored and, if set, reads that sector into memory. The BIOS may either separately maintain a flag that indicates MediaDirect/No-MediaDirect, or use the LBA address value itself as the flag. E.g., if 0 is not a valid LBA address, then 0 would indicate MediaDirect off. 
   Next, the BIOS verifies that the sector loaded into memory contains an operating environment manager signature. If no operating environment manager signature is present, then the BIOS boots to a customer operating system MBR as normal (i.e., the BIOS ignores the MediaDirect event). If an operating environment manager signature is present, then the BIOS jumps to the operating environment manager code (i.e., the BIOS causes the operating environment manager code to start executing). 
   The operating environment manager code takes over control of the information handling system and loads the MediaDirect Partition. This method allows an information handling system manufacturer to change boot code on the fly without having to synchronize changes to the boot code with BIOS release schedules. Additionally, this method also allows for the operating environment manager code to be stored anywhere on the drive of the information handling system (e.g., somewhere other than Track  0 , if that truly became as issue with certain operating systems). Additionally, this method allows placement of the operating environment manager code in reserved sectors inside an actual MediaDirect partition, thus making the MediaDirect solution self contained. 
   Additionally, this method functions with a standard MBR, where a call to the operating environment manager (via e.g., the API) is added to the BIOS of information handling systems that support MediaDirect. Additionally, updates to the operating environment manager would not require BIOS updates 

   
     BRIEF DESCRIPTION OF THE DRAWINGS 
     The present invention may be better understood, and its numerous objects, features and advantages made apparent to those skilled in the art by referencing the accompanying drawings. The use of the same reference number throughout the several figures designates a like or similar element. 
       FIG. 1 , labeled prior art, shows a flow chart of the operation of a method for accessing a MediaDirect partition using a custom MBR. 
       FIG. 2  shows a system block diagram of an information handling system. 
       FIG. 3  shows a flow chart of the operation of a method for accessing a MediaDirect partition via an operating environment manager. 
   

   DETAILED DESCRIPTION 
   Referring briefly to  FIG. 2 , a system block diagram of an information handling system  200  is shown. The information handling system  200  includes a processor  202 , input/output (I/O) devices  204 , such as a display, a keyboard, a mouse, and associated controllers, memory  206  including volatile memory such as random access memory and non volatile memory such as a hard disk and drive, and other storage devices  206 , such as an optical disk and drive and other memory devices, and various other subsystems  210 , all interconnected via one or more buses  212 . 
   The information handling system  200  also includes a basic input output system (BIOS)  220  stored on the memory  206  as well as an operating system partition  230 , a MediaDirect partition  232  and a system restore partition  234 . The information handling system  200  also includes an operating environment manager  240  stored on the memory  206 . 
   The operating environment manager  240  may be called either during the manufacturing process or in the field by the API of the BIOS  220  to provide the BIOS  220  with the LBA sector number which is stored within a boot drive. In certain embodiments, the LBA sector number includes a 64-bit LBA address which is stored within the BIOS  220 . 
   The operating environment manager  240  is stored within predetermined sectors of a boot drive during manufacture or field service of the information handling system  200 . In certain embodiments, the first sector (assuming more than one, but not necessarily) binary also includes the LBA address so that operating environment manager  240  can locate additional sectors that contain the continuation of the operating environment manager  240  (again, assuming more than one sector is required to store the operating environment code). 
   For purposes of this disclosure, an information handling system may include any instrumentality or aggregate of instrumentalities operable to compute, classify, process, transmit, receive, retrieve, originate, switch, store, display, manifest, detect, record, reproduce, handle, or utilize any form of information, intelligence, or data for business, scientific, control, or other purposes. For example, an information handling system may be a personal computer, a network storage device, or any other suitable device and may vary in size, shape, performance, functionality, and price. The information handling system may include random access memory (RAM), one or more processing resources such as a central processing unit (CPU) or hardware or software control logic, ROM, and/or other types of nonvolatile memory. Additional components of the information handling system may include one or more disk drives, one or more network ports for communicating with external devices as well as various input and output (I/O) devices, such as a keyboard, a mouse, and a video display. The information handling system may also include one or more buses operable to transmit communications between the various hardware components. 
     FIG. 3  shows a flow chart of the operation of a method for accessing a MediaDirect partition via an operating environment manage  240 . More specifically, when a customer actuates a button such as a MediaDirect button at step  310 , BIOS  220  detects that a MediaDirect mode is desired and sets a media direct (MD) flag (e.g., within the CMOS) so indicating at step  312 . The BIOS  220  then reads an LBA address that was previously stored and, if set, reads that sector into memory at step  314 . The BIOS may either separately maintain a flag that indicates MediaDirect/No-MediaDirect, or use the LBA address value itself as the flag. E.g., if 0 is not a valid LBA address, then 0 would indicate MediaDirect off. When a customer actuates a power button at step  316 , then the BIOS  220  clears the MD flag at step  318  and proceeds to boot to the bootable device, which in this case is the operating system partition  230 , at step  319 . 
   Next, the BIOS verifies that the sector loaded into memory contains an operating environment manager checksum at step  320 . If no operating environment manager checksum is present, then the BIOS  220  boots to a customer operating system MBR as normal (i.e., the BIOS ignores the MediaDirect event) at step  319 . If an operating environment manager checksum is present, then the BIOS invokes the operating environment manager  240  (i.e., the BIOS  220  causes the operating environment manager code to start executing) at step  330 . 
   The operating environment manager  240  takes over control of the information handling system  200  and loads the MediaDirect Partition. More specifically, the operating environment manager  240  first determines whether a utility partition (UP) flag is active (indicating that system should boot to a license agreement portion) at step  340 . If the utility partition is active, then the operating environment manger boots to a utility partition/end user license agreement (UP/EULA) portion at step  342 . 
   If the UP flag is not active, then the operating environment manager  240  determines whether a media direct boot flag is set at step  350 . If the media direct boot flag is not set, then the media direct partition is hidden at step  352  and the operating environment manger  240  boots to the primary operating system stored within the operating system partition  230  (e.g., the XP operating system) at step  354 . If the media direct boot flag is set, then access to the media direct partition  232  is allowed (i.e., the media direct partition  232  is made visible) at step  360  and the information handling system  200  boots to the media operating system (e.g., the XPe operating system) stored within the media direct partition  232  at step  362 . 
   This method allows an information handling system manufacturer to change boot code on the fly without having to synchronize changes to the boot code with BIOS release schedules. Additionally, this method also allows for the operating environment manager code to be stored anywhere on the drive of the information handling system (e.g., somewhere other than Track  0 , if that truly became as issue with certain operating systems). Additionally, this method allows placement of the operating environment manager code in reserved sectors inside an actual MediaDirect partition, thus making the MediaDirect solution self contained. 
   Additionally, this method functions with a standard MBR, where a call to the operating environment manager (via e.g., the API) is added to the BIOS of information handling systems that support MediaDirect. Additionally, updates to the operating environment manager would not require BIOS updates 
   The present invention is well adapted to attain the advantages mentioned as well as others inherent therein. While the present invention has been depicted, described, and is defined by reference to particular embodiments of the invention, such references do not imply a limitation on the invention, and no such limitation is to be inferred. The invention is capable of considerable modification, alteration, and equivalents in form and function, as will occur to those ordinarily skilled in the pertinent arts. The depicted and described embodiments are examples only, and are not exhaustive of the scope of the invention. 
   For example, the above-discussed embodiments include software modules that perform certain tasks. The software modules discussed herein may include script, batch, or other executable files. The software modules may be stored on a machine-readable or computer-readable storage medium such as a disk drive. Storage devices used for storing software modules in accordance with an embodiment of the invention may be magnetic floppy disks, hard disks, or optical discs such as CD-ROMs or CD-Rs, for example. A storage device used for storing firmware or hardware modules in accordance with an embodiment of the invention may also include a semiconductor-based memory, which may be permanently, removably or remotely coupled to a microprocessor/memory system. Thus, the modules may be stored within a computer system memory to configure the computer system to perform the functions of the module. Other new and various types of computer-readable storage media may be used to store the modules discussed herein. Additionally, those skilled in the art will recognize that the separation of functionality into modules is for illustrative purposes. Alternative embodiments may merge the functionality of multiple modules into a single module or may impose an alternate decomposition of functionality of modules. For example, a software module for calling sub-modules may be decomposed so that each sub-module performs its function and passes control directly to another sub-module. 
   Also for example, the operating environment manager may be stored as an operating environment manager module within the BIOS  220 . In this embodiment, when the BIOS  220  detects actuation of the MediaDirect button, the BIOS  220  executes the operating environment manager module stored within the BIOS to boot to the MediaDirect partition. The operating environment manager module would virtualize a master boot record in memory so as to not effect the master boot record that is stored on the hard drive (e.g., stored at track  0 /sector  1 ). The operating environment manager would know where the MediaDirect MBR (as well as all associated MediaDirect logic) is stored (e.g., at track  0 /sector  3 ). Such a method would thus operate much like the master boot record method used by the Microsoft operating systems. However, updates to the operating environment manager module would need to be distributed across all of the different instantiations of the BIOS used across every system produced by an information handling system manufacturer. Additionally, with this method drive replacements in the field would need a fixer tool to restore the MediaDirect MBR to track  0 /sector  3 . 
   Also for example, the operating environment manager could be stored in a non-volatile memory portion (e.g., a non-volatile random access memory) within the BIOS  220 . With this method, the BIOS could be updated with a call which loads operating environment manager out of NVRAM and jump to the operating environment manager when the MediaDirect button is actuated. The operating environment manager could be stored in the NVRAM during a factory install process when the information handling system is fabricated. Such a method would thus operate much like the master boot record method used by the Microsoft operating systems. Additionally, only the loader call needs to be added to the various instantiations of the BIOS used by the information handling system manufacturer, which is a smaller BIOS code change. Additionally, updates to the operating environment manager would not require BIOS updates. However, such a method would require a BIOS to include a writable portion. 
   Consequently, the invention is intended to be limited only by the spirit and scope of the appended claims, giving full cognizance to equivalents in all respects.