Automated Boot Sequence for Alternative OS on Removable Media

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Modern computers, particularly those certified for Microsoft's Windows 8 OS and higher, face challenges in reliably booting alternative operating systems from removable devices, as existing technologies like UEFI-based methods are not generic and can be unreliable.

Innovation Solution

A method utilizing a dedicated application (RFMS) that applies a sequence of automated and manual booting techniques, including Direct HDD UEFI booting, USB UEFI booting, Bcdedit-based booting, Grub4Dos-based booting, and BIOS-based manual booting, to maximize the likelihood of successfully booting an alternative operating system from a removable device, avoiding custom firmware and prioritizing techniques based on the computer's specifications.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If UEFI-based booting techniques are used for alternative operating systems, then booting capability is provided, but reliability is poor and the solution is not generic

Engineering Contradiction:
Improvebooting capabilityVSAvoidbooting reliability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent segments the booting process into multiple distinct techniques (UEFI booting, Legacy booting, Grub4Dos booting, boot.ini booting) and applies them in a systematic sequence. Each technique is isolated as an independent attempt, allowing the system to methodically try different approaches until success, thereby resolving the reliability issue while maintaining adaptability across different computer systems.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If custom firmware User Interface is used in Windows 8 and higher, then booting from removable devices is supported, but the solution is not generic and requires custom firmware

Engineering Contradiction:
Improvebooting supportVSAvoidfirmware complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a universal booting application that works across multiple Windows versions (XP, Vista, 7, 8, and higher) and multiple booting techniques without requiring custom firmware for each version. The application universally applies a sequence of booting techniques that are compatible with different Windows versions and computer systems, eliminating the need for version-specific custom firmware solutions.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Reliability

If multiple booting techniques are applied in sequence, then success rate increases, but the process becomes more complex

Engineering Contradiction:
Improvebooting success rateVSAvoidbooting process complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements a self-service automated application that independently determines the computer's specifications, selects the appropriate sequence of booting techniques, executes each technique automatically, and monitors the booting process without requiring user intervention. This automation hides the complexity of multiple techniques from the user while maintaining high success rates through systematic application of different booting methods.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS11392390B2Method and system for automatically booting a computer to run from a removable device
Publication Date: 2022.07.19 FIXMESTICK TECH INC
  • US11392390B2 patent drawing
  • US11392390B2 patent drawing

AI summary

A removable device and method for automatically booting a computer running a standard operating system (OS) into an alternative OS. The method comprises a user inserting the removable device into the computer, and the user launching an application stored on the removable device for booting guidance. The user directs the application to boot the computer into the alternative OS, whereupon the application determines a first booting technique to be used on the computer and configures the computer accordingly. The application restarts the computer in an attempt to boot into the alternative OS. If booting the alternative OS fails, the computer boots back into the standard OS, whereupon the application determines a next best booting technique and configures the computer accordingly. This process continues until the alternative OS is successfully booted, or, failing that, the user is given manual booting direction.