Common Preinstallation Environment for Heterogeneous OS
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing methods for installing heterogeneous operating systems, such as Linux, Novell Netware, and Microsoft Windows, face challenges in achieving a uniform and unattended installation process, particularly due to proprietary formats like Boot Configuration Data (BCD) and Windows Imaging (WIM), and require manual intervention for dual-boot configurations, leading to inefficiencies and increased total cost of ownership (TCO).
Innovation Solution
A common preinstallation environment (CPE) is implemented, comprising a host preinstallation environment (HPE) and native preinstallation environments (NPEs), which provides a uniform installation process by determining hardware components, injecting missing drivers, and transitioning control between HPE and NPE to ensure seamless installation of multiple operating systems like Netware, Windows, and Linux variants.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of time
If a pre-execution environment is implemented to load operating systems from remote sources, then installation time is reduced and manual intervention is minimized, but proprietary formats (BCD, WIM) and different installation procedures prevent a uniform installation process for heterogeneous operating systems
Solution Approach 1:
The patent introduces a translation layer that acts as an intermediary between the pre-execution environment and different operating system installation procedures. This translation layer converts uniform installation commands into OS-specific installation actions, enabling a single pre-execution environment to support multiple heterogeneous operating systems (Windows, Linux, Netware) without requiring separate installation processes for each OS type.
Solution Approach 2:
The pre-execution environment is designed with universal functionality to support installation of multiple operating system types through a single unified interface. By implementing OS-agnostic installation procedures that can adapt to different file systems (NTFS, ext3, swap), partitioning schemes, and driver models, the system achieves multi-functionality across heterogeneous platforms while maintaining a consistent user experience.
2Reliability
If different installation procedures are required for different operating systems, then each OS can be installed correctly according to its specific requirements, but the installation process becomes complex and requires manual intervention
Solution Approach 1:
The installation process is segmented into distinct phases: hardware detection, driver loading, partitioning, file system creation, and OS-specific configuration. Each phase is handled by specialized modules that can be independently configured for different operating systems. This segmentation allows the system to maintain a simple unified interface while managing complex OS-specific requirements through modular, interchangeable components.
Solution Approach 2:
The system uses parameter-based configuration to adapt installation behavior for different operating systems. By changing installation parameters (file system type, partitioning scheme, driver model, boot configuration) based on the target OS, the same installation framework can correctly install Windows, Linux, or Netware without requiring different installation procedures. The translation layer automatically adjusts these parameters based on the detected target OS.
3Ease of manufacture
If physical media (floppy disks, CDs, hard disk drives) are used to install operating systems, then installation can be performed, but an operator must be physically present to load the operating system and make configuration choices
Solution Approach 1:
The pre-execution environment implements self-service capabilities by automatically detecting hardware components, selecting appropriate drivers, configuring system parameters, and executing the installation process without human intervention. The system autonomously inventories hardware, loads necessary drivers, creates partitions, formats file systems, and initiates OS installation based on pre-configured preferences or user-specified options, eliminating the need for operators to be physically present during installation.
Solution Approach 2:
Installation configurations, driver selections, and system preferences are predetermined and stored in the pre-execution environment before the actual installation begins. Hardware inventories are pre-established, and installation parameters are pre-configured based on the target operating system type. This preliminary preparation enables the installation to proceed automatically without requiring real-time operator decisions or physical media handling during the installation process.
Data Source
AI summary
A system and method is disclosed for the uniform installation of one or more of a plurality of heterogeneous operating systems (operating systems) on a predetermined information handling system. A common preinstallation environment (CPE) is implemented, comprising a host preinstallation environment (HPE) and one or more native preinstallation environments (NPEs). If an NPE is not required for installation, an HPE comprising a common, bootable kernel generates a bootable operating system image that is installed on the target system. Otherwise, the HPE creates a deployment partition, where it implements the NPE and generates a metafile describing the hardware drivers supported by the NPE. The HPE then inventories the hardware components comprising the target system and compares the results to the metafile. If all required drivers are accessible, the target system boots to the NPE, which begins native installation of the chosen operating system. Otherwise, the HPE injects the missing drivers into the operating system image generated by the NPE and the resulting operating system image is then installed on the target system. If the HPE cannot inject drivers into the NPE, then a stage handler is implemented to relinquish installation control to the NPE which completes a native installation.