DOCSLIB.ORG

Windows Embedded Standard 2009 Prepkit

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Windows Embedded Standard 2009 Prepkit MCTSi Exam 70-577 Windows Embedded Standard 2009 Preparation Kit Certification Exam Preparation Automation Not for resale. ii Table of Contents Contents at a Glance 1 Creating and Customizing the Configuration 2 Managing the Development Environment 3 Integrating Embedded Enabling Features 4Creating Components 5 Generating and Deploying an Image 6 Adding Windows Functionality Chapter 5 Generating and Deploying an Image After you have completed the tasks of designing your run-time image, configuring it with the necessary components and testing the configuration, you can continue with production deployment to your target devices. Production deployment entails reviewing the deployment scenario, preparing the image, and deploying it to devices for a final, retail-ready product. This chapter discusses key deployment scenarios for Internet- connected and unconnected devices including devices that start remotely or start from an onboard booting media. This chapter also covers the configuration dependencies you must complete to prepare your image for distribution. Exam objectives in this chapter: ■ Generate the Pre-First Boot Agent (pre-FBA) image ■ Seal and clone the post-FBA image ■ Prepare target media for deployment ■ Deploy the Post-First Boot Agent (post-FBA) image to the target device ■ Implement a remote boot solution Before You Begin To complete the lessons in this chapter you need the following: ■ Microsoft® Windows® Embedded Studio for Windows Embedded Standard 2009 installed. ■ Completed Chapters 1, 2, 3 and 4. 145 146 Chapter 5 Generating and Deploying an Image Lesson 1: Generate the Pre-FBA Image FBA runs the first time your operating system starts after you configure and build an image. FBA completes the run-time image build process by running a sequence of tasks on the target system, such as Plug and Play (PnP) device detection, security installation, and DLL registration. You can add commands to the FBA process and specify when they will run. You can also add tasks to the FBA process by defining custom resources, referred to as FBA commands, such as RunOnce requests, application shortcuts, and populating the registry with service data. After this lesson, you will be able to: ■ Include a product identification key (PID). ■ Understand the FBA process. ■ Create custom resources to customize the build process. Estimated lesson time: 20 minutes. Run-Time Image Licensing You must enter a PID for your retail image. Otherwise, the image that you create is an evaluation image and will stop working after the evaluation period expires 120 days after deployment. Windows Embedded Standard 2009 product activation does not require online access and is activated in Target Designer when you enter a run-time product key in the Run-time Image Licensing section of the image configuration settings. FBA Phases and Processing Order The Target Designer build process creates the raw system image, creates the necessary directory structure, and copies the files for each component to the specified directories. The build process also creates the registry hives and saves these in the \Windows\System32\Config folder. This raw system image is not ready to run as it is. On the first start of the raw run-time image, FBA runs to complete the build process. FBA performs any run-time tasks that could not be performed offline with Target Designer, including security installation, catalog registration, PnP device detection, network configuration, DLL registration, and profile initialization. The FBA process flows in a predefined, sequential order that is determined by phases and ordinal values to control the timing of various commands. FBA Generic Lesson 1: Generate the Pre-FBA Image 147 Command, FBA DLL/COM Registration, and FBA OC Manager Requests all have ordinal values associated with them. FBA starts at 0 and continues through 65,535. Phases 0 through 8,500 are reserved for use by the system and you should not set a directive to run below 8,500. The phase values are double words, where the high word indicates the FBA phase and the low word indicates the ordinal value within an FBA phase. You can view a log (Fbalog.txt) of the FBA process in the Windows\FBA directory on the target device after FBA has run. If you have a kernel debugger attached while FBA executes, the logging information is forwarded to the debugger as well as written to the log file. Custom Resources You add custom resources to enhance the functionality of a component when you create a component in Component Designer. However, custom resources are also FBA commands, because FBA controls their execution. During first boot, FBA uses these commands to populate the registry, set up application shortcuts, specify replacements for end-of-life components, and perform actions that cannot be done during the building of a configuration, such as Component Object Model (COM) registration. You use Target Designer to add custom resources to a configuration. FBA DLL or COM Registration This resource is required for any component that needs to register a COM InProc server. FBA uses functions from the Win32® application programming interface (API), including LoadLibrary, DllRegisterServer, DllUnregisterServer, and DllInstall, to register and load the DLLs containing the COM objects. Component Branch This resource is used to specify a replacement component for a component that is set to an end-of-life (EOL) state. When an EOL component is replaced by multiple components, one branch resource is added to the EOL component for each replacement component. Branch resources are only used in EOL components. However not all EOL components require replacements—in such a case there is no branch. In other cases there is only one branch which means that the EOL component is replaced by one new component. 148 Chapter 5 Generating and Deploying an Image PnP Device ID This resource is used to insert PnP information into a device component, and is required for PnP device drivers. As already mentioned in Chapter 4, you should not add PnP resources manually to a component, because these are created automatically when you import an INF file into Component Designer. RunOnce Request This resource is used to execute an application during the first start of the run-time image, after first boot, or after every logon. This functionality is added to the run-time image as one of three registry keys: ■ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion \Run. The Run key is processed after every logon. The Explorer shell runs it if present, otherwise either Custom Shell, Command Shell, or Task Manager Shell run it. If FBA processes this key, it does so after every logon, not during first start as it nor- mally would. Typically, this key is used to load system tray applications, launch services in executables, hide auto start applications, or hide background pro- cesses. ■ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion \RunOnce. FBA processes the RunOnce key only once after PnP device enumeration and DLL registration processing have completed. The values of this registry key are deleted from the registry after it is processed, so that it will not run again. Typi- cally, this flag is used when a restart is required, such as for a DLL or OCX reg- istration. ■ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion \RunOnceEx. The RunOnceEx key is processed only once, by the Explorer shell, after the first logon. The values of this registry key are deleted from the registry after it is pro- cessed, so that it will not run again. If the Explorer shell is not present, this key is ignored. Typically, this flag is used for a process that runs only once, and that either cannot be run correctly by FBA or requires the system to be fully opera- tional. Lesson 1: Generate the Pre-FBA Image 149 Service Data This resource is required for components that define a Windows service. Start Menu Shortcuts This resource is used to create shortcuts on the Start menu or on the desktop if these are part of your image. FBA Generic Commands This is a custom resource which is required for a component that needs programs executed during FBA on the run-time image. FBA calls CreateProcess from the Win32 API to run a program and optionally pass it command-line arguments. Prepare for Cloning Before you prepare to clone your image, make sure that the configuration accurately reflects the hardware of your target device and that you have verified its functionality on your target device. Then, add the System Cloning Tool component to your configuration, which is located under Software>System>System Services>Base folder in component browser. After you add it to the configuration, you can configure its settings or leave the default settings. The next lesson covers the settings for the cloning tool. Lesson Summary This lesson introduces the tasks you have to perform before you build and deploy your production image. You need to stamp your image with a PID key for the image to become a production image that does not expire after 120 days. You create all the custom resources you need for FBA to prepare your raw image to function as intended. Finally, you must plan for mass deployment by adding the System Cloning Tool to your configuration. You complete a final dependency check, build your image and save your configuration file. 150 Chapter 5 Generating and Deploying an Image Quick Check 1. What must be done in order to prevent a Windows Embedded Standard 2009 operating system from expiring? 2. Is it safe to run FBA on a development machine, and then transfer the operat- ing system to a different machine for testing? 3. What do you add to your configuration to facilitate cloning of the operating system? Quick Check Answers 1. A retail run-time PID must be entered in Target Designer to prevent the run- time from expiring.
Load more

Recommended publications
  • Operating System Boot from Fully Encrypted Device
    Masaryk University Faculty of Informatics Operating system boot from fully encrypted device Bachelor’s Thesis Daniel Chromik Brno, Fall 2016 Replace this page with a copy of the official signed thesis assignment and the copy of the Statement of an Author. Declaration Hereby I declare that this paper is my original authorial work, which I have worked out by my own. All sources, references and literature used or excerpted during elaboration of this work are properly cited and listed in complete reference to the due source. Daniel Chromik Advisor: ing. Milan Brož i Acknowledgement I would like to thank my advisor, Ing. Milan Brož, for his guidance and his patience of a saint. Another round of thanks I would like to send towards my family and friends for their support. ii Abstract The goal of this work is description of existing solutions for boot- ing Linux and Windows from fully encrypted devices with Secure Boot. Before that, though, early boot process and bootloaders are de- scribed. A simple Linux distribution is then set up to boot from a fully encrypted device. And lastly, existing Windows encryption solutions are described. iii Keywords boot process, Linux, Windows, disk encryption, GRUB 2, LUKS iv Contents 1 Introduction ............................1 1.1 Thesis goals ..........................1 1.2 Thesis structure ........................2 2 Boot Process Description ....................3 2.1 Early Boot Process ......................3 2.2 Firmware interfaces ......................4 2.2.1 BIOS – Basic Input/Output System . .4 2.2.2 UEFI – Unified Extended Firmware Interface .5 2.3 Partitioning tables ......................5 2.3.1 MBR – Master Boot Record .
    [Show full text]
  • Server Support Interview Questions and Answers Guide
    Server Support Interview Questions And Answers Guide. Global Guideline. https://www.globalguideline.com/ Server Support Interview Questions And Answers Global Guideline . COM Server Support Job Interview Preparation Guide. Question # 1 Tell me where are cluster logs stored? Answer:- Please share your answers. Read More Answers. Question # 2 What are the Logical / Physical Structures of the AD Environment? Answer:- Active Directory Logical components are Forests, Trees, Domains, OUs and Objects. Active Directory Physical components are Domain Controllers, Sites and subnets. Read More Answers. Question # 3 What applications or services use AD application partitions? Name a couple? Answer:- Application partition contains the information of application data and other data related to application as well. But it does not contain any data related AD object such as USER, COMPUTER and GROUP. The saved data will be replicated to some of the particular DC not to all the DCs. Read More Answers. Question # 4 What are the types of hard disks used in servers? Answer:- Mostly we use scsi hardrive in server due few reason to it, high scalability & flexibility in raid array, faster from other type of hdd interface like-sata,ata,ide also it reliable & compatible with older scsi devices Read More Answers. Question # 5 What are some of the command-line tools available for managing a Windows 2003 Server/Active Directory environment? Answer:- Command Line Tools 1) GPupdate 2) Where 3) SystemInfo 4) CSVDE 5) LDIFDE 6) CMDCONS 7) Ipconfig 8) RoboCopy 9) CMDHere 10) PathPing Read More Answers. Question # 6 What if a FSMO server role fails? Answer:- FSMO roles are important role in server .
    [Show full text]
  • How Will You Troubleshoot the Issue? What Are the Steps to Followed? A
    1. A user in a corporate network contacts service desk saying he/she has lost network connectivity: How will you troubleshoot the issue? What are the steps to followed? A. First I will check the network cable is plugged in or not. Then check the network connections and the ip address is assigned or not. Then check connecting to website or not. IP conflict. 2. A User calls in and complains that her computer and network is running very slow. How would go about troubleshooting it? A. 3. How would you create an email account for a user already in AD? A. Open Microsoft Outlook if you are using office 2000, and click on "Tools" tab. Go to "Email Accounts". There you can find two option like Email and Directory. Click on "Add a new Account" and click next. If you are using Exchange Server then click over there, this depends on that particular Organization. According to the their setup you have to choose. And if you are using POP3 server then next popup will come along with your name, email address POP3 and SMTP IP address, Password etc. and after that click on Next and finish it..... 4. A PC did not receive an update from SMS. What steps would we take to resolve this? A. If SMS not updated in client system. 1. Need to check system getting IPaddress or not. 2. Need to check system in domain or not 3.Ensure that windows firewall should be off. 5. How do you set the IP address by using the command prompt A.
    [Show full text]
  • Boot Problem Solutions B 102/1
    B102.qxp_July 2018 25/05/2018 10:00 Page 23 BcdEdit: Boot Problem Solutions B 102/1 If Windows Goes on Strike while Booting Up: Use BcdEdit to Take Back Control Using the information given in this article you will be able to: Edit your Windows system’s boot configuration, Remove an old operating system from the boot menu, Restore a faulty boot sector using BootRec. On Windows XP, you could change the boot menu and configure the process simply by editing the BOOT.INI file. This was especially useful if you had a multi- boot system, and needed to quickly change the options displayed in the menu when you start up your PC. With the introduction of Windows 7, everything changed, and modifying your boot menu became much more complicated than editing a single file. That’s because Microsoft replaced the BOOT.INI file with the BCD (Boot Configuration Data) database. Unfortunately, this data could no longer be edited with a text editor and now it is only possible to make configuration changes using the BcdEdit tool. In this article, I’ll show you how to use the BcdEdit program in order to add operating systems to the boot configuration data, or remove entries from the list of displayed operating systems. • BcdEdit: The New Boot File Editor in Windows .... .......... B 102/2 • BcdEdit: The Boot Configuration Data Editor .... ............. B 102/4 • You Should Know these BcdEdit Parameters ..... ............. B 102/5 • Manage Multi-boot Systems Using BcdEdit .... ............... B 102/8 • How to Rescue Windows 10, 8.1 & 7 Multi-boot Systems ..
    [Show full text]
  • Windows Embedded Standard 2009 Prepkit
    MCTSi Exam 70-577 Windows Embedded Standard 2009 Preparation Kit Certification Exam Preparation Automation Not for resale. ii Published by Microsoft Corporation One Microsoft Way Redmond, Washington 98052-6399 This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS DOCUMENT. The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publica- tion. Information in this document, including URL and other Internet Web site references, is subject to change with- out notice. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmit- ted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any pur- pose, without the express written permission of Microsoft Corporation. Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property. Copyright © 2009 Microsoft Corporation. All rights reserved. Internet Explorer, Microsoft, MS-DOS, Visual Studio, Win32, Windows and Windows Vista are trademarks of the Microsoft group of companies.
    [Show full text]
  • The Evolution of TDL: Conquering X64
    The Evolution of TDL: Conquering x64 Revision 1.1 Eugene Rodionov, Malware Researcher Aleksandr Matrosov, Senior Malware Researcher 2 2 CONTENTS 3 INTRODUCTION ..................................................................................................................................................... 4 1 INVESTIGATION ............................................................................................................................................. 5 1.1 GANGSTABUCKS ............................................................................................................................................... 6 2 INSTALLATION ............................................................................................................................................. 11 2.1 INFECTING X86 SYSTEMS .................................................................................................................................. 11 2.2 INFECTING X64 SYSTEMS .................................................................................................................................. 13 2.3 THE DROPPER’S PAYLOAD ................................................................................................................................ 14 2.4 COMPARISON WITH TDL3/TDL3+..................................................................................................................... 15 3 THE BOT .....................................................................................................................................................
    [Show full text]
  • [ [ [ {[email protected]}
    UNDERSTANDING WINDOWS 2K SOURCES (part 1) Written By: AndreaGeddon [www.andreageddon.com] [www.reteam.org] [www.quequero.org] {[email protected]} :: INTRO :: This is the first of a series of articles in which I will deal a little bit in detail with the windows 2000 kernel. In particular I will refer to the stolen sources that have been published. For obvious causes I shall not write the code directly in this article, but I will make precise references to the files I will describe, so if you have the sources you will find easy it easy to understand this text. :: REQUIREMENTS :: Well, first of all it would be good if you have the sources, if you don’t have them you can read the article the same as it will have a quite generic stamp. Second, you have to know hardware x86 architecture basics, infact I will not deal with things like IDT etc, so get your Intel manuals and study them! Last, I will assume you have some basic knowledge about an operating system, that is you know what is a file system, what is a scheduler and so on. Now we can begin. :: BIBLIOGRAPHY :: Here are some books on the argument that I advise you to read: • The Windows 2000 Device Driver Book - Art Baker, Jerry Lozano • Inside Windows 2000 - Russinovich, Solomon (sysinternals) • Windows driver model - Oney • Windows NT Native Api - Gary Nebbett • Undocumented Windows NT - Dabak, Phadke, Borate • Windows NT File SYstem Internals - Nagar • Windows NT Device Driver Development - Viscarola :: THE BEGINNING :: The source leak is dated on the first ten days of february, with the direct responsibility for it, being Mainsoft; an old partner of Microsoft.
    [Show full text]
  • Review NTFS Basics
    Australian Journal of Basic and Applied Sciences, 6(7): 325-338, 2012 ISSN 1991-8178 Review NTFS Basics Behzad Mahjour Shafiei, Farshid Iranmanesh, Fariborz Iranmanesh Bardsir Branch, Islamic Azad University, Bardsir, Iran Abstract: The Windows NT file system (NTFS) provides a combination of performance, reliability, and compatibility not found in the FAT file system. It is designed to quickly perform standard file operations such as read, write, and search - and even advanced operations such as file-system recovery - on very large hard disks. Key words: Format, NTFS, Volume, Fat, Partition INTRODUCTION Formatting a volume with the NTFS file system results in the creation of several system files and the Master File Table (MFT), which contains information about all the files and folders on the NTFS volume. The first information on an NTFS volume is the Partition Boot Sector, which starts at sector 0 and can be up to 16 sectors long. The first file on an NTFS volume is the Master File Table (MFT). The following figure illustrates the layout of an NTFS volume when formatting has finished. Fig. 5-1: Formatted NTFS Volume. This chapter covers information about NTFS. Topics covered are listed below: NTFS Partition Boot Sector NTFS Master File Table (MFT) NTFS File Types NTFS File Attributes NTFS System Files NTFS Multiple Data Streams NTFS Compressed Files NTFS & EFS Encrypted Files . Using EFS . EFS Internals . $EFS Attribute . Issues with EFS NTFS Sparse Files NTFS Data Integrity and Recoverability The NTFS file system includes security features required for file servers and high-end personal computers in a corporate environment.
    [Show full text]
  • Windows Embedded Standard 2009 Prepkit
    MCTSi Exam 70-577 Windows Embedded Standard 2009 Preparation Kit Certification Exam Preparation Automation Not for resale. ii Table of Contents Contents at a Glance 1 Creating and Customizing the Configuration 2 Managing the Development Environment 3 Integrating Embedded Enabling Features 4Creating Components 5 Generating and Deploying an Image 6 Adding Windows Functionality Chapter 3 Integrating Embedded Enabling Features This chapter discusses Microsoft® Windows Embedded Standard 2009 Embedded Enabling Features (EEFs), which are components that address scenarios specific to embedded devices, such as deploying run-time images on read-only media, managing and updating your device remotely, and mass deployment. Exam objectives in this chapter: ■ Implement Device Update Agent (DUA) ■ Implement a USB Boot solution ■ Implement Enhanced Write Filter (EWF) ■ Implement File Based Write Filter (FBWF) ■ Implement Message Box Default Reply Before You Begin To complete the lessons in this chapter you need the following: ■ Windows Embedded Studio for Windows Embedded Standard 2009 installed. ■ Completed Chapters 1 and 2. ■ The configuration you created in Chapter 1. 73 74 Chapter 3 Integrating Embedded Enabling Features Lesson 1: Implement DUA The DUA component enables you to remotely update the run-time image of your Windows Embedded Standard 2009 devices. It is a service that runs on your device and processes a script that performs update and maintenance operations. DUA is useful for updating Windows Embedded Standard 2009 images, and is a small component with few dependencies. With DUA, you can update applications or application data, deploy new binaries and device drivers, make registry changes, and automate cleanup and management tasks. After this lesson, you will be able to: ■ Add and configure DUA in your image configuration.
    [Show full text]
  • Major System Files, and Their Purpose: Windows 9X –Specific Files • IO.SYS the Io.Sys File Is an MS-DOS and Windows 9X
    Major System Files, and their purpose: Windows 9x –specific files IO.SYS The io.sys file is an MS-DOS and Windows 9x hidden system file that is used to load the operating system each time the computer boots. The file is not editable using normal text editors. MSDOS.SYS The MSDOS.SYS file is a hidden system file created on the root of the boot drive. To edit this file, type edit msdos.sys. The PC boot environment can be changed by changing the file contents. Given below is a typicalMSDOS.SYS file: Below is a sample MSDOS.SYS File [Paths] WinDir=C:\WINDOWS WinBootDir=C:\WINDOWS HostWinBootDrv=C [Options] BootGUI=1 Network=1 BootMulti=1 ; ;The following lines are required for compatibility with other programs. ;Do not remove them (MSDOS.SYS needs to be >1024 bytes). AUTOEXEC.BAT An AUTOEXEC.BAT file contains DOS commands that are executed automatically when a PC boots. The file is usually located in the root directory of the hard drive of the computer. The AUTOEXEC.BAT file is used to set defaults and to run programs that should be executed during startup. Example: PROMPT $P$G Use the PROMPT command to alter the default DOS prompt. The above command makes the DOS prompt display the current path and drive, and is very useful. COMMAND.COM 1. It does: The file contains internal command set and error messages 2. Default Attributes: Nil 3. Is it required for OS Start up: YES 4. Responsible for displaying the command prompt in a DOS based computer.
    [Show full text]
  • Start Linux from the Windows XP Bootloader
    Start Linux from the Windows XP bootloader The idea is to do the same as Windows XP does automatically if installed after Windows 98. It copies the MBR (see http://en.wikipedia.org/wiki/Master_boot_record) made by Windows 98 in a file usually named bootsect.dos and add a line in the Windows XP bootloader (NTLDR) configuration file C:\boot.ini similar to C:\BOOTSECT.DOS="Microsoft Windows". Then, the Windows XP installer replaces the MBR with what it needs and so on. And when you start your computer and choose the entry "Microsoft Windows" on the Windows XP bootloader menu, it launches the code in C:\BOOTSECT.DOS and lets it play as if wants. Therefore, for Linux, we need to capture the MBR made by Linux (with : dd if=/dev/hda of=/bootsect.lnx bs=512 count=1 on Linux in root or with dskprobe on Windows in Administrator : d'abord ouvrir le handle du disque, puis lire de 0 à 16) in a file bootsect.lnx, install Windows XP, put bootsect.lnx on C:\ and add a line C:\BOOTSECT.LNX="Linux" at the end of the C:\Boot.ini file (be sure to remove the read-only attribute and enable the view of hidden and system files in Windows folder options to be able to edit it). This will probably also work with Vista and Seven if you add an entry with bcdedit to handle NTLDR. Note : You can restore at any time the MBR made by XP with the command FIXMBR on the Windows XP recovery console, or with the tool bootsect (type bootsect /nt52 C: /mbr) from Windows Seven or a Windows PE CD or USB key.
    [Show full text]
  • Guide to Computer Forensics and Investigations Fourth Edition
    Guide to Computer Forensics and Investigations Fourth Edition Chapter 6 Working with Windows and DOS Systems Objectives • Explain the purpose and structure of file systems • Describe Microsoft file structures • Explain the structure of New Technology File System (NTFS) disks • List some options for decrypting drives encrypted with whole disk encryption Guide to Computer Forensics and Investigations 2 Objectives (continued) • Explain how the Windows Registry works • Describe Microsoft startup tasks • Describe MS-DOS startup tasks • Explain the purpose of a virtual machine Guide to Computer Forensics and Investigations 3 Understanding File Systems • File system – Gives OS a road map to data on a disk • Type of file system an OS uses determines how data is stored on the disk • A file system is usually directly related to an OS • When you need to access a suspect’s computer to acquire or inspect data – You should be familiar with the computer’s platform Guide to Computer Forensics and Investigations 4 Understanding the Boot Sequence • Complementary Metal Oxide Semiconductor (CMOS) – Computer stores system configuration and date and time information in the CMOS • When power to the system is off • Basic Input/Output System (BIOS) – Contains programs that perform input and output at the hardware level Guide to Computer Forensics and Investigations 5 Understanding the Boot Sequence (continued) • Bootstrap process – Contained in ROM, tells the computer how to proceed – Displays the key or keys you press to open the CMOS setup screen • CMOS should
    [Show full text]