External Boot Device Driver Interface for Automatic Hardware Detection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing technologies for starting a computer installation from an external device face challenges in automatically detecting and activating hardware and software elements, limiting the choice of host operating systems that can be used, and complicating the startup process, especially when the user wants to use a specific operating system and environment.
Innovation Solution
A portable device with a connection interface and a data carrier containing executable codes for a host operating system, configured for automatic detection and activation of hardware and software elements, along with a driver software interface to present computer drivers as generic drivers, and a control software interface for managing hardware and software elements using these generic drivers, allowing for a wide choice of operating systems and environments.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If the portable device stores a host operating system configured for automatic detection of hardware elements and activation of computer drivers, then the ease of operation is improved, but the device complexity increases
Solution Approach 1:
The patent introduces a driver software interface as an intermediary layer between the host operating system and the guest operating system. This interface translates hardware-specific driver calls into generic driver interfaces, enabling automatic hardware detection and driver activation without requiring the guest OS to directly interface with specific hardware. This mediator resolves the contradiction by providing automated hardware compatibility (improving ease of operation) through a structured translation layer that manages complexity centrally.
Solution Approach 2:
The driver software interface implements universality by presenting all computer drivers as predetermined generic computer drivers to the guest operating system. This universal interface allows any guest OS to access hardware resources through a standardized abstraction layer, eliminating the need for hardware-specific knowledge in the guest OS while maintaining full hardware compatibility. This multi-functional approach improves ease of operation across different OS types while concentrating complexity in the universal interface layer.
2Adaptability or versatility
If the user can freely choose the host operating system to be stored in the portable external boot device, then the adaptability is improved, but the difficulty of detecting and measuring hardware elements increases
Solution Approach 1:
The driver software interface serves as a mediator that translates hardware detection requirements into generic driver interface calls. When a user selects a guest OS, the system automatically invokes the driver software interface to detect hardware elements and activate corresponding drivers, presenting them as generic interfaces to the guest OS. This intermediary layer resolves the contradiction by enabling OS freedom (improving adaptability) while centralizing hardware detection complexity in the mediator layer.
Solution Approach 2:
The host operating system performs self-service by automatically detecting hardware elements and activating computer drivers without requiring manual configuration or hardware-specific knowledge from the user or guest OS. The driver software interface autonomously translates hardware requirements into generic driver calls, enabling the system to adapt to any selected guest OS while automatically handling hardware compatibility through self-service detection and activation.
3Ease of manufacture
If the portable device uses predetermined generic computer drivers for all hardware elements, then the ease of manufacture is improved, but the reliability of hardware-specific driver activation decreases
Solution Approach 1:
The driver software interface acts as a mediator that bridges generic driver interfaces and hardware-specific requirements. It presents a uniform generic driver interface to the guest OS for ease of manufacture and operation, while simultaneously activating the appropriate hardware-specific drivers in the background. This intermediary layer resolves the contradiction by maintaining generic driver simplicity (improving ease of manufacture) while ensuring reliable hardware-specific driver activation through the mediator's translation function.
Solution Approach 2:
The driver activation process is segmented into two independent stages: first, the driver software interface activates hardware-specific drivers based on detected hardware elements; second, the guest OS accesses hardware through generic driver interfaces. This segmentation allows the system to manufacture with generic drivers (improving ease of manufacture) while maintaining reliable hardware-specific functionality through the first stage of driver activation, resolving the contradiction between manufacturing simplicity and operational reliability.
Data Source
Figure 1~2
Figure 3~4
AI summary
The device (20) has a data medium including data and executable code (22b, 24b) of a piloting software interface configured to present informatic controls activated by a host operating system in the form of predetermined generic informatic control. The medium has data and executable code (22c, 24c) of a guest operating system activated by the interface and configured for management of hardware and/or software elements e.g. motherboard (12), Internal hard disk (14) and connection interface (16), of a computer installation (10) using the predetermined informatic control. An independent claim is also included for a method for external starting of a computer installation.