Boot Engineering Extension Record (B.E.E.R.) By Curtis E. Stevens.

Slides:



Advertisements
Similar presentations
DIT314 ~ Client Operating System & Administration CHAPTER 4 CONFIGURING HARDWARE DEVICES AND STARTUP PROCESS Prepared By : Suraya Alias.
Advertisements

计算机系 信息处理实验室 Lecture 5 Startup and Shutdown
Chapter 3 Understanding the Boot Process and Command Line.
Installing Windows XP Professional Using Attended Installation Slide 1 of 35Session 9 Ver. 1.0 CompTIA A+ Certification: A Comprehensive Approach for all.
MCDST : Supporting Users and Troubleshooting a Microsoft Windows XP Operating System Chapter 8: Troubleshooting Storage Devices and Display Devices.
11 INSTALLING WINDOWS XP Chapter 2. Chapter 2: Installing Windows XP2 INSTALLING WINDOWS XP  Prepare a computer for the installation of Microsoft Windows.
EET 450 Chapter 2 – How hardware and Software Work Together.
1 Chapter Overview CD-ROM and DVD Drives Advanced Hard Disk Drives SCSI Drives.
Operating Systems Operating System
Tel : 同济大学软件学院 UEFI 与固件程序设计.
How Hardware and Software Work Together
Chapter 5 Basic Input/Output System (BIOS)
Basic Input Output System
Hands-On Microsoft Windows Server 2008
Guide to Linux Installation and Administration, 2e1 Chapter 3 Installing Linux.
A+ Guide to Managing and Maintaining Your PC Fifth Edition Chapter 15 Installing and Using Windows XP Professional.
1 UCR Firmware Attacks and Security introduction.
Chapter Fourteen Windows XP Professional Fault Tolerance.
Understanding and Troubleshooting Your PC. Chapter 5: Understanding, Installing, and Troubleshooting Disk Drives2 Chapter Objectives  In this chapter,
From UEFI Shell to Linux - UEFI Linux BootLoader Zhang Rui Software Engineer Sep 28 th 2011.
How Hardware and Software Work Together
PC Maintenance: Preparing for A+ Certification Chapter 10: Introduction to Disk Storage.
Hardware Boot Sequence. Vocabulary BIOS = Basic Input Output System UEFI = Unified Extensible Firmware Interface POST= Power On Self Test BR = Boot Record.
MCTS Guide to Microsoft Windows Vista Chapter 4 Managing Disks.
Windows NTFS Introduction to Operating Systems: Module 15.
Hard disk drives It is a non volatile mass storage device. It consists of platters made of aluminum alloy or glass ceramic composite material. Platters.
14 Step-by-Step Instructions for an Upgrade Installation n Prepare for the installation Verify that all devices and applications are Windows 2000 compatible.
Chapter 3 Partitioning Drives using NTFS and FAT32 Prepared by: Khurram N. Shamsi.
Setting the BIOS BIOS – Part 3 Richard L. Goldman March 2000.
Chapter Thirteen Booting Windows XP. Objectives Understand the Windows XP boot process Understand the Windows XP boot process Troubleshoot system restoration.
11 INSTALLING AND MANAGING HARDWARE Chapter 6. Chapter 6: Installing and Managing Hardware2 INSTALLING AND MANAGING HARDWARE  Install hardware in a Microsoft.
Basic Input/Output System (BIOS). 5.1Introduction to BIOS Basic Input / Output System (BIOS) boot the computer by providing a basic set of instructions.
Copyright © Genetic Computer School 2008 Computer Systems Architecture SA 8- 0 Lesson 8 Secondary Management.
Adding a Hard Drive. BIOS / UEFI The Unified Extensible Firmware Interface (UEFI) defines a software interface between an operating system and platform.
IT Essentials 1 v3 Module 4 JEOPARDY IT Essentials 1 RouterModesWANEncapsulationWANServicesRouterBasicsRouterCommands RouterModesWANEncapsulationWANServicesRouterBasicsRouterCommands.
Hands-On Microsoft Windows Server 2008 Chapter 7 Configuring and Managing Data Storage.
Review ATA - IDE Project name : ATA – IDE Training Engineer : Minh Nguyen.
1 Remote Installation Service Windows 2003 Server Prof. Abdul Hameed.
Dual Boot Systems with Ubuntu Michael Frey Engineering Manager OEM Services, Canonical.
NT1110 Computer Structure and Logic Unit 8 (Module 5A) COMPUTER OPERATION AND SECURITY.
Computer Viruses Author: Alyse Allen.
Why VT-d Direct memory access (DMA) is a method that allows an input/output (I/O) device to send or receive data directly to or from the main memory, bypassing.
Chapter Objectives In this chapter, you will learn:
Guide to Linux Installation and Administration, 2e
Chapter 2 Memory and process management
ES C263 Microprocessor Programming and Interfacing
Disks and Formatting Ch 3.
Credits: 3 CIE: 50 Marks SEE:100 Marks Lab: Embedded and IOT Lab
Chapter 12: File System Implementation
5.0 : Windows Operating System
Introduction to Operating System (OS)
Introduction to Computers
CS-401 Computer Architecture Assembly Language Programming
CONFIGURING HARDWARE DEVICE & START UP PROCESS
Plug-and-Play.
Booting Up 15-Nov-18 boot.ppt.
Starting the computer. Every day we are using an operating system and most specifically a Windows operating system but most of us are not aware of the.
Chapter 9: IOS Images and Licensing
Chapter 2: System Structures
Chapter Overview CD-ROM and DVD Drives Advanced Hard Disk Drives
Nathan Obr, Jack Creasey Microsoft Corporation
Files Management – The interfacing
Modern PC operating systems
TPM, UEFI, Trusted Boot, Secure Boot
The bios.
Chapter 11 Processor Structure and function
Department of Computer Science
Introduction to BIOS Prof. Shamim Ahmad Hakim
WINDOW 7 INSTALLATION Prepared By:- Mr. Pawan Kumar
Presentation transcript:

Boot Engineering Extension Record (B.E.E.R.) By Curtis E. Stevens

Agenda  Introduction to Booting  Why BEER?  BEER and Booting  BEER and Runtime Services  BEER and SETUP  Summary

Introduction to Booting

System Initialization  Enable ISA and PCI devices  Detect ATAPI/ATAPI devices  Phoenix proprietary  Uses Floating Bus Test, Device Diagnostics, and sometimes reads/writes cylinder registers when device remains busy too long  Wait up to 31 seconds for ~BSY  Save ATAPI signature...  Wait up to 31 seconds for RDY

System Initialization  Issue ID Device or ATAPI ID Device as necessary (uses much shorter timeout)  Continue the boot process  Configure the devices and interfaces for their operational modes  Includes PIO, DMA, UDMA, etc.  Continue the boot process  Execute INT 19 initial boot load

BIOS Booting  Real Mode  INT 13 based  Load sector at CHS=0,0,1 or LBA 0 to system memory 7C0h:0  Clear registers to 0  Set DL = boot drive (00h or 80h)  Jump to 7C0h:0

MBR Booting  Code in MBR is written by various OS manufacturers  Can be by any OS installed on the system  Good virus target because there is actually no owner  Scans the partition table looking for an active partition  Loads the first sector of the partition into memory and jumps to it  Generally at 7C0h:0 as well.

Process Drawbacks  No MBR Owner  Lots of different programs manipulating the same data structure  Partition types are out of control and conflicting  System information is assumed  Code is INT 13 based  If INT 13 changes data structures become invalid  No good way to detect error conditions

Enter SETMAX  Custom uses for this space are already happening  Now there are multiple applications looking to use this area  New area of expansion has no defined owner  New area of expansion needs organization!!  Big Big mess 1-2 years from now...

Why BEER?

BEER  Provides BIOS readable information regarding drive formatting  Resides in protected area  Some degree of protection from viruses  Provides centralized organization as systems move towards supporting multiple operating environments  Allows for the authentication of data before it is placed in protected areas

BIOS readable information  INT 13 parameters and ID Device parameters used to make calculations  BIOS useable vs reported sectors/drive  Last INT 13 device number assigned to drive  Device name  Can be manufacturer ID  Can also be other things

More BIOS Readable Information  Self describing service areas  Eliminates the need for interpretive code  Allows the user to pick and choose from something that makes sense  Allows several uses for the “SETMAX” area including  Diagnostics/Recovery  Suspend to Disk  Other protected BIOS level data storage

BEER Formatted Disk Normal User Space Managed SETMAX Space BEER Sector

SETMAX Space Diagnostics BIOS Utilities BEER Sector Managed Space Suspend Information

BEER and Booting

Booting Assumptions  No effect on non-BEER drives  Normal booting process continues to function  BEER booting enabled when a BEER sector is present  BEER capabilities are enabled by user intervention  Keypress during post  Integration with boot menu feature

BIOS Booting Changes  If BEER is available and there are no user boot requests  Load parameters from the Service Area with the last boot flag set  Issue SETMAX to the end of the Service Area  Load the first sector of the Service Area to 7C0h:0  Jump to 7C0h:0

More Booting Changes  If BEER is available and there ARE user boot requests  Load parameters from the Service Area selected by the user or BIOS  Issue SETMAX to the end of the Service Area  Load the first sector of the Service Area to 7C0h:0  Jump to 7C0h:0

Boot Selection  Can be OEM platform specific  For instance, systems can have a watchdog function, if windows fails to boot the system automatically boots to diagnostics the next time.  Can be general at the same time  POST or SETUP option for selecting the next service to boot

BEER and Runtime Services

Runtime Services  Only INT 13 changes  Fn 8/48  Parameters are generated from the Directory of Services (DOS)  Only the current service area is reported  All media access functions  Add the Service Area Start to the media address  SETMAX limits the high end of the media access

Advantages of this method  No ATA protocol changes required  Works with drives shipping today  BIOS changes are minimal  Supports all DOS based applications as written  Limits exposure to viruses

Disadvantages Of This Method  Applications that provide proprietary disk interfaces will fail  Possible drive corruption  Code overhead to the BIOS  New technology  Need to protect SETMAX Command

BEER and SETUP

What’s Necessary  A method for selecting the alternate boot capability. An entry like “Boot to Diagnostics” would probably suffice  Could easily be made to perform the function for one boot only  If the system is not field updateable, the drive can be preconfigured and no other SETUP changes are necessary

Field Updates Scenario #1  Need a drive maintenance mode  Prepares new drives by creating the BEER sector  Updates existing drives by adding entries to the directory of services  Can transfer data from other devices into the directory of services  May authenticate the data

Field Updates Scenario #2  Need a drive maintenance mode  Prepares new drives be creating the BEER sector  Updates existing drives by adding entries to the directory of services  Enables a service area  Boot from floppy or other device and the BIOS presents the service area as an empty device  Use normal DOS utilities to format the space

In Summary  BEER is a management data structure controlled by the BIOS for allowing several Operating Systems to co-exist on a disk drive, but only 1 OS to execute  There is a lot of room for product differentiation  There is a lot of room to expand this capability

If system manufacturers are interested in the concept presented here Interaction of INT 13 and INT 19 with BEER can be added to the specification Other capabilities can be added to BEER