Getting Started with Windows PE

Total Page:16

File Type:pdf, Size:1020Kb

Getting Started with Windows PE Wes Miller Systems Management GETTING STARTED WITH WINDOWS PE Chances are you don’t know much about the Microsoft Windows Preinstallation Environment, or Windows PE as it’s usually called, even though it shipped the same day as Windows XP. Windows PE was designed to allow Windows setup or a 32-bit imaging program to run on a PC even with Originally, the Windows setup CD included no version of Windows installed. The idea was to make things easier for OEMs. Windows both a prebuilt version of Windows PE and PE has evolved over the years and, as you’ll see, it can make your life easier as well. a toolset that let you create your own build. For quite some time, MS-DOS® played a big part in Windows installation and setup, Today, Windows PE is shipped only as the but eventually that became problematic. As both Windows and hardware grew more so- toolset; you need to build your own copy. phisticated, MS-DOS couldn’t keep up. Its shortcomings as a setup initiator for doing a Eventually, Windows PE spread beyond custom setup were plentiful. Performance the OEM community it was designed for. • The history of Windows PE was a big issue, so was driver availability. ISVs, enterprise, education and government • How Windows PE can stand in for These problems became the key impetus for customers all took advantage of it, and they MS-DOS replacing MS-DOS for OEMs and eventu- used it for far more than the deployment sce- • How to customise Windows PE ally enterprise customers. narios we initially envisioned. They used it • Windows PE Q&A A developer on the Windows setup team for recovery and diagnostics as well. Today, came up with the idea of integrating the dif- Windows PE is available for customers with Wes Miller is the Product Technology Strategist at Winternals ferent components of setup into one solu- Software Assurance, as well as Enterprise AT A GLANCEAT Software in Austin, Texas, where he focuses on all Winternals products, including Protection Manager, the Winternals Enter- tion so that a simple boot CD could provide Agreements, Campus Agreements, and as a prise Security product. Previously, Wes worked at Microsoft as a minimal environment that would let 32- component of several other licensing agree- a Program Manager and Product Manager for Windows enter- bit setup run, eliminating the problems with ments with Microsoft. prise deployment. MS-DOS. With that, Windows PE was born. When running, Windows PE looks like 36 To get your FREE copy of TechNet Magazine subscribe at: www.microsoft.com/uk/technetmagazine Windows PE Q&A Send your Windows PE questions to [email protected] and I’ll answer them as time allows. Doesn’t using Windows PE Qcompletely violate the NTFS secu- rity of Windows? Under Windows PE, the user runs all tasks as System, which is more powerful than local administrator. It turns out this really isn’t Aan issue. Law number 3 of the 10 Immutable Laws of Security says, “If a bad guy has unrestricted physi- Figure 1 Default Configuration of Windows PE Booted to the Command Shell cal access to your computer, it’s not your computer anymore.” (See micro- Figure 1. You’ll note that it doesn’t include not be available. Windows PE users began soft.com/technet/archive/community/columns/secu- Windows Explorer, and as such does not have to regularly request a number of addition- rity/essays/10imlaws.mspx for the complete any of the regular Windows shell available. al features. We were unable to officially en- It’s truly a bare-bones installation. gineer these features into the product, but article). we did provide a script that would allow a The point is that if someone can What You Get Windows PE admin to add ADO connectiv- physically access your computer, As you can see in the sidebar “Windows ity to a Microsoft SQL Server, and HTML there are numerous other methods PE Releases”, there have been a number for Applications (HTA) and Windows Script besides Windows PE (a parallel install of upgrades. The basic functionality of Host (WSH) support to an image. These of Windows, an NTFS-capable install Windows PE was broadly expanded to al- provided a handy framework of tools that of Linux or even Mac OS X, or physical low OEM partners and enterprise custom- have enabled some creative deployment and removal of the drive to another system ers to perform WMI queries on hardware recovery solutions. Windows PE 2.0, which running Windows) to remove or poten- and to initialise classes of devices that no is scheduled to ship with Windows Vista, tially destroy your data. True, Windows one originally had expected would be used will add notable new capabilities. PE makes this more convenient. under Windows PE. Windows PE was ini- To counter this threat—as well as tially designed to boot from CD; network Booting Windows PE boot via PXE was an afterthought, and the When you’re starting with Windows PE, Law number 3 as a whole—you should hard drive method came very late in devel- one of the first considerations is how you either physically secure your system at opment. The intent with Windows PE was want to boot. Over the years the number of all times or use EFS to at least secure always to allow for a 32-bit environment boot mediums supported by Windows PE your data, or a full disk encryption with TCP/IP networking, hard disk access has grown (see Figure 2). product, which will secure your data to enable imaging or scripted installation of Technically, Windows PE can also boot and even your entire system volume. Windows, and basic video support. Windows from an LS-120/LS-240 disk, though I’d nev- This is something you should be do- PE always uses the same basic VESA mode er recommend it due to serious performance ing with your mobile systems anyway video driver regardless of the card in use. issues. USB Flash Drive boot is something if they are storing any sort of confi- This lets it display very good colour depth we worked hard on for Windows PE 1.6. It dential data. and resolution on modern VESA-compliant works very well, though it’s only supported hardware, though some older hardware may by Microsoft when an OEM provides it with Can I PXE-boot Windows PE default to a very unpleasant (though usable) a new system because there’s no reliable way colour depth and resolution. to ensure that systems would have the nec- Qfrom anything besides RIS? From the beginning Windows PE had essary capabilities. This method requires only very basic Win32® API support, mean- BIOS-specific functionality that must be With the RAMDisk boot ca- ing that the Microsoft .NET Framework, provided by the PC manufacturer, as well Apability in Windows PE 2005, yes DirectX®, TAPI/MAPI/SAPI, audio and as USB 2.0 support. you can. many other high-level Windows APIs would Your particular needs will determine how TechNet Magazine October 2006 37 Systems Management you can best use Windows PE. The impor- family) or the one immediately preceding. tant thing to remember is that you can ba- Figure 2 Windows PE Boot Options So for Windows PE 1.5, the build tools will check for either Windows Server 2003 RTM sically reuse the same technology across PXE (Pre-boot eXecution Environment) multiple boot methods, no matter which using RAMDisk boot technology media (either the Standard or Enterprise one(s) you choose. RIS (the Microsoft proprietary Editions) or Windows XP Service Pack 2 Before you begin creating your build of PXE implementation, which is tradition- (SP2) integrated media. Note that the WMI Windows PE, you’ll need to make some de- ally used to launch Windows setup over features in 1.5 require Windows XP SP2, and the network) the RAMDisk and USB Flash Drive features cisions. A key question you’ll need to answer Hard Disk (either directly or via a is who’s in charge? Will this be a self-service RAMDisk) in 1.6 require Windows Server 2003 SP1. reinstallation solution that non-technical CD (or an ISO-formatted DVD) To create a build of Windows PE 1.6, then, users will execute, or will it be used by your RAMDisk (this allows for some very you will want to have the 1.6 build tools technical or IT support staff? interesting scenarios which I’ll describe as well as a copy of Windows Server 2003 in depth in an upcoming article) SP1 integrated media. Launch a command This is a critical question, since it will dic- USB Flash Drive (UFD) tate whether you’ll have corporate brand- prompt and go to the directory where you ing on the user interface, whether you need copied the Windows PE build tools. At the to build protections in to keep users from partitions, getting build information from prompt, type the following (the last four running the installer accidentally, and many SQL Server or a network share, and mix- arguments are optional): other issues. Here roaming user profiles or a ing and matching PXE and CD/DVD boot mkimg.cmd [source] [destination] [ISO Image] separate user data partition for Documents mechanisms. The best part about Windows [/PNP] [/WMI] [/NOWF] and Settings can come in handy. PE is the countless ways in which you can Let’s say your Windows Server 2003 SP1 in- You’ll also need to decide if you’ll build configure it to do your bidding.
Recommended publications
  • Supporting Operating System Installation | 3
    cc01SupportingOperatingSystemInstallation.indd01SupportingOperatingSystemInstallation.indd PagePage 1 08/10/1408/10/14 4:334:33 PMPM martinmartin //208/WB01410/XXXXXXXXXXXXX/ch01/text_s208/WB01410/XXXXXXXXXXXXX/ch01/text_s Supporting Operating LESSON 1 System Installation 70-688 EXAM OBJECTIVE Objective 1.1 – Support operating system installation. This objective may include but is not limited to: Support Windows To Go; manage boot settings, including native virtual hard disk (VHD) and multi-boot; manage desktop images; customize a Windows installation by using Windows Preinstallation Environment (PE). LESSON HEADING EXAM OBJECTIVE Using a Troubleshooting Methodology Viewing System Information Using the Event Viewer Supporting Windows To Go Support Windows To Go Creating and Deploying a Windows To Go Workspace Drive Booting into a Windows To Go Workspace Managing Boot Settings Manage boot settings, including native virtual hard disk (VHD) and multi-boot Using BCDEdit and BCDBoot Configuring a Multi-Boot System Manage boot settings, including native virtual hard disk (VHD) and multi-boot Configuring a Native VHD Boot File Manage boot settings, including native virtual hard disk (VHD) and multi-boot Understanding VHD Formats Installing Windows 8.1 on a VHD with an Operating System Present Installing Windows 8.1 on a VHD Without an Operating SystemCOPYRIGHTED Present MATERIAL Managing Desktop Images Manage desktop images Capturing Images Modifying Images using DISM Customizing a Windows Installation by Using Windows PE Customize a Windows
    [Show full text]
  • Meeting Planner Documentation
    MEETING PLANNER Installation, Configuration, and User Guides Last Updated: April 24, 2018 EMS Software | emssoftware.com/help | 800.440.3994 | © 2018 EMS Software, LLC. All Rights Reserved. Table of Contents CHAPTER 1: Introduction to Meeting Planner 1 Contact Customer Support 1 CHAPTER 2: Network Architecture Diagram 2 2 CHAPTER 3: Hardware & Software Requirements 3 Hardware Requirements 3 1-5,000 active users 3 5,000-30,000 active users 4 30,000+ active users 5 Software Prerequisites 6 End-User Machines 6 Application Server 8 Exchange Server 10 Service Accounts 10 Database Server 11 CHAPTER 4: Hardware & Software Requirements Checklist 13 End user machines 13 Application Server 13 Web Server (Roles) 13 Message Queuing Services 14 Internet Information Services 14 Microsoft .NET Framework 14 Service Accounts 14 Database Server 14 SQL Server 14 CHAPTER 5: Server 2012 Prerequisite Setup 15 Application Server Prerequisite Setup 15 Web Server (Role) 15 Message Queuing Services 19 Internet Information Services (IIS) 19 Microsoft .NET Framework 21 Supporting Microsoft References: 22 Database Server Prerequisite Setup 22 SQL Server 22 CHAPTER 6: Server 2008 R2 Prerequisite Setup 25 Application Server Prerequisite Setup 25 Web Server (Roles) 25 Message Queuing Services 26 Internet Information Services (IIS) 27 Microsoft .NET Framework 28 Supporting Microsoft References: 29 Database Server Prerequisite Setup 29 SQL Server 29 CHAPTER 7: Application Server Installation 31 CHAPTER 8: Database Server Configuration 35 Identify Database 35 Restore Database
    [Show full text]
  • Advanced Windows SIG January 17, 2002 Disk Management Note: Material for Paragraphs 1, 2,And 3 Based on Microsoft Windows XP Inside/Out Chapter 26
    Advanced Windows SIG January 17, 2002 Disk Management Note: material for paragraphs 1, 2,and 3 based on Microsoft Windows XP Inside/Out Chapter 26 If you have mastered hard-disk setup utilities from Windows 98 and Me, prepare to unlearn everything you know. Windows XP offers new capabilities and a new set of tools. 1. Definitions • Disk or hard Disk Î physical disk drive installed on computer o First hard disk drive Î Disk 0 o Second hard disk drive Î Disk 1 o Third hard disk drive Î Disk 2 • Basic Disk Î Contains one or more partitions o A partition Î A portion of a disk that functions as if it were a separate disk o A primary partition Î used for starting Windows - can not be further subdivided o An extended partition Î can be further divided into one or more logical drives each of which can be formatted separately and assigned a drive letter • Volume Î When a partition or logical drive is formatted for a particular file system (FAT, FAT32, or NTFS) and assigned a drive letter, it is called a volume Disk Management rev 1.doc Page 1 of 5 1/16/2002 D R Wright 2. Windows XP Disk Management Utility • Provides tools to manage disks, partitions, volumes and logical drives • Go to Start Î Right click My Computer Î Manage Î Disk Management • Perform the following tasks: o Check size, file system, status o Create partitions, logical drives, and volumes o Assign drive letters to hard disk volumes, removable disk drives, and CD-ROM drives o Changes usually take effect immediately and without need to reboot 3.
    [Show full text]
  • MS Exchange 2016
    MS Exchange 2016 Deployment Guide UPDATED: 23 March 2021 MS Exchange 2016 Copyright Notices Copyright © 2002-2021 Kemp Technologies, Inc. All rights reserved. Kemp Technologies and the Kemp Technologies logo are registered trademarks of Kemp Technologies, Inc. Kemp Technologies, Inc. reserves all ownership rights for the LoadMaster and Kemp 360 product line including software and documentation. Used, under license, U.S. Patent Nos. 6,473,802, 6,374,300, 8,392,563, 8,103,770, 7,831,712, 7,606,912, 7,346,695, 7,287,084 and 6,970,933 kemp.ax 2 Copyright 2002-2021, Kemp Technologies, All Rights Reserved MS Exchange 2016 Table of Contents 1 Introduction 5 1.1 About This Manual 5 1.2 Related Firmware Version 5 1.3 Prerequisites 5 2 Exchange 2016 Overview 7 2.1 Understanding Server Load Balancing 7 2.2 Enable Subnet Originating Requests Globally 8 2.3 100-Continue Handling 9 2.4 Additional L7 Header 9 3 Virtual Service Templates 11 4 Configuring Virtual Services for Exchange 2016 12 4.1 HTTPS Offloaded and Reencrypt without ESP 12 4.1.1 Add SSL/TLS Certificate 12 4.2 HTTPS Offloaded and Reencrypt with ESP 14 4.2.1 Add SSL/TLS Certificate 15 4.2.2 Configure ESP 16 4.3 IMAP and IMAPS Virtual Service 18 4.4 IMAPS Offloaded and IMAP with STARTTLS Virtual Service 19 4.5 POP and POPS Virtual Service 20 4.6 POPS Offloaded and POP with STARTTLS Virtual Service 20 4.7 SMTP and SMTPS Virtual Service 21 kemp.ax 3 Copyright 2002-2021, Kemp Technologies, All Rights Reserved MS Exchange 2016 4.8 SMTPS Offloaded and SMTP with STARTTLS Virtual Service 22 4.9
    [Show full text]
  • Powernet Installation and Troubleshooting Guide
    PowerNet Installation and Troubleshooting Guide revision: 06-13-06-0001 PowerNet Installation and Troubleshooting Guide Table of Contents Implementation Process for PowerNet Products .......................................................3 Customer Requirements and Information Gathering .................................................4 Installation Process……................................................................................................5 Verification of the Installation ......................................................................................6 XP Soft NCU Installation ...............................................................................................7 Appendix A: Preparing Windows 2000 for PowerNet...............................................12 Appendix B: Preparing Windows NT for PowerNet..................................................14 Appendix C: Application Target Hosts ......................................................................16 Appendix D: Information on Access Points ..............................................................17 Appendix E: Mobile Unit Information.........................................................................18 Appendix F: PowerNet OpenAir Server Information ................................................19 Appendix G: PowerNet Twin Client Server Information...........................................20 Appendix H: Non-Interactive Applications User Interface .......................................21 Appendix I: Windows 2000 Telnet Interface..............................................................22
    [Show full text]
  • Windows 95 & NT
    Windows 95 & NT Configuration Help By Marc Goetschalckx Version 1.48, September 19, 1999 Copyright 1995-1999 Marc Goetschalckx. All rights reserved Version 1.48, September 19, 1999 Marc Goetschalckx 4031 Bradbury Drive Marietta, GA 30062-6165 tel. (770) 565-3370 fax. (770) 578-6148 Contents Chapter 1. System Files 1 MSDOS.SYS..............................................................................................................................1 WIN.COM..................................................................................................................................2 Chapter 2. Windows Installation 5 Setup (Windows 95 only)...........................................................................................................5 Internet Services Manager (Windows NT Only)........................................................................6 Dial-Up Networking and Scripting Tool....................................................................................6 Direct Cable Connection ..........................................................................................................16 Fax............................................................................................................................................17 Using Device Drivers of Previous Versions.............................................................................18 Identifying Windows Versions.................................................................................................18 User Manager (NT Only) .........................................................................................................19
    [Show full text]
  • Understand How MAPI Over HTTP Is Changing Your Outlook Introduction
    Understand how MAPI over HTTP is changing your Outlook Introduction MAPI/ HTTP is slowly replacing RPC/ HTTP. Office 365 has already implemented it and Outlook 2016 use this protocol by default. The questions we explored at GSX were: does MAPI impact the end-user performance? How does it change the network’s consumption? Will you have performance tickets when switching from one protocol to another? To best answer these questions, we decided to employ our Robot Users, with different network configurations and the two protocols. Through this article, we will divulge our findings. MAPI over HTTP: features and benefits What is MAPI? MAPI stands for Messaging Application Programming Interface. If we had to describe it simply, it is just a way for a program to call functions on a messaging server. MAPI has been around for a while. In 1991, MAPI 0 was available for MS Mail. At that time, the API was not yet officially called MAPI. First formal release of MAPI was in 1992. Initially, it was designed just to let a local mail client running on Windows talk to a mail server running on Windows as well in the same network. With the first MAPI, the problem was that it was designed to be used exclusively on your network, and it was created even before the current Internet existed. It just defined a series of remote procedure calls (RPC) that are also very old and did not address any security concerns. These problems made it particularly unsafe to make it available on the Internet. Before the most recent release of MAPI, we used RPC over HTTP: It was still MAPI, just first wrapped with RPC and then wrapped with HTTP, resulting in what we know as “Outlook Anywhere”.
    [Show full text]
  • The New York Society Library Presents
    The New York Society Library Presents: Intermediate Computers Ingrid Richter Computer Specialist & Webmaster COMPUTERS I INDEX INTRODUCTION Basic Windows Overview……………………………………………………………………… Page 03 Windows 98, ME, 2000, XP.........................................................….. Page 04 THE BASICS: My Computer........................................................................……… Page 05 Start Menu & Taskbar..........................................................……… Page 06 Control Panel.......................................................................……… Page 07 Windows Setup.....................................................................……… Page 08 FILE ORGANIZATION: Windows Explorer...................................................................... Page 09 SOFTWARE Backup..................................................................................... Page 10 DOS and file extensions………………………………………………………………………. Page 10 Calculator................................................................................. Page 11 HyperTerminal.......................................................................... Page 11 Notepad.................................................................................... Page 12 Wordpad................................................................................... Page 12 Paint......................................................................................... Page 13 TROUBLESHOOTING: Scanning Hard Drive.................................................................
    [Show full text]
  • Enterprise Vault™ Setting up Exchange Server Archiving
    Enterprise Vault™ Setting up Exchange Server Archiving 12.3 Enterprise Vault™: Setting up Exchange Server Archiving Last updated: 2018-03-29. Legal Notice Copyright © 2018 Veritas Technologies LLC. All rights reserved. Veritas, the Veritas Logo, Enterprise Vault, Compliance Accelerator, and Discovery Accelerator are trademarks or registered trademarks of Veritas Technologies LLC or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners. This product may contain third-party software for which Veritas is required to provide attribution to the third party ("Third-party Programs"). Some of the Third-party Programs are available under open source or free software licenses. The License Agreement accompanying the Software does not alter any rights or obligations you may have under those open source or free software licenses. Refer to the Third-party Legal Notices document accompanying this Veritas product or available at: https://www.veritas.com/about/legal/license-agreements The product described in this document is distributed under licenses restricting its use, copying, distribution, and decompilation/reverse engineering. No part of this document may be reproduced in any form by any means without prior written authorization of Veritas Technologies LLC and its licensors, if any. THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. VERITAS TECHNOLOGIES LLC SHALL NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS DOCUMENTATION.
    [Show full text]
  • U3-1033 Ovation Netdde Server
    Ovation NetDDE Server User Guide Section Title Page Summary of Changes Section 1. Introduction 1-1. Overview. 1-1 1-2. NetDDE Server Features. 1-1 1-3. DDE Overview . 1-2 1-3.1. Application or Service Name. 1-2 1-3.2. Topic . 1-2 1-3.3. Item . 1-3 1-3.4. Network DDE . 1-4 1-4. Limitations . 1-5 Section 2. Getting Started 2-1. Section Overview . 2-1 2-2. Requirements . 2-1 2-2.1. System . 2-1 2-2.2. Hardware . 2-1 2-2.3. Software . 2-2 2-2.4. License Server . 2-2 2-3. Setup . 2-4 2-3.1. Environment Variables Required for Setup. 2-5 2-3.2. Linked Libraries. 2-6 2-3.3. Files Installed During Setup. 2-7 2-3.4. Registry Entries . 2-8 2-3.5. Security . 2-10 2-4. Setup Procedure . 2-10 2-5. Configuration . 2-11 2-5.1. Permissions . 2-11 2-6. Un-installation. 2-11 Section 3. Using NetDDE 3-1. Section Overview . 3-1 3-2. Syntax for Calls. 3-1 Glossary Index 12/00 i U3-1033 (Rev 1) Westinghouse Process Control, Inc. Proprietary Class 2C Summary of Changes This revision of “Ovation NetDDE Server User Guide” (U3-1033) reflects the following changes: • System topic has now been changed to wwwdde_system. • DataCreate and DataOriginate topics are removed from the WDPF NetDDE Server. • The machine name must appear when the point information (or Item) link is created on the WDPF NetDDE Server machine or accessed remotely in Excel or any other DDE supported application.
    [Show full text]
  • Recovery Media Creation Guide Based on Active Backup for Business 2.1.1 Table of Contents
    Recovery Media Creation Guide Based on Active Backup for Business 2.1.1 Table of Contents Introduction Method 1: Automatically Create Recovery Media System Requirements and Supported Media Types 4 Create USB Recovery Media 5 Create ISO Recovery Media 7 Cancel Recovery Media or Troubleshoot Failure 9 Method 2: Manually Create Recovery Media System Requirements and Limitations 10 Create Recovery Media with the Windows ADK 11 Pack Recovery Media 13 Boot Recovery Media (ISO Image or USB Drive) 16 Appendix Copy Drivers 17 Install Drivers 17 Configure Resolution 18 Configure Language Settings 18 Add Certificate to WinPE Image 19 2 Introduction Synology Active Backup for Business is a business-wise and all-in-one backup solution that supports backing up physical devices including Windows PCs and Windows servers. With this solution, you can create recovery media to restore an entire device either automatically or manually. Recovery media must be created manually if the device intended to be restored is running a 32-bit version of Windows or contains specific driver versions, time zone, or language. However, recovery media can be created automatically if the device intended to be restored is not running a 32-bit version of Windows and does not contain specific drivers, time zone, and language. We recommend you to create recovery media automatically, if possible, because this method is easier. This Recovery Media Creation Guide details the methods for creating recovery media automatically or manually. Please refer to the following chapters detailing the methods, requirements, limitations, and processes of recovery media creation. 3 Introduction Method 1: Automatically Create Recovery Media Synology Active Backup for Business Recovery Media Creator is a desktop tool affiliated to our business data protection solution — Active Backup for Business.
    [Show full text]
  • Microsoft Windows Resource
    Chapter 13 Troubleshooting Windows 3.1 This chapter provides information about troubleshooting Microsoft Windows for both general users and experts. If you have trouble installing Windows, or if Windows doesn’t run as well as you expected, this chapter will help you find out why and show you how to isolate and solve common problems. Related Information • Windows User’s Guide: Chapter 15, “Maintaining Windows with Setup” See also Chapter 4, “Troubleshooting,” in the Getting Started booklet • Windows Resource Kit: “The Troubleshooting Flowcharts for Windows 3.1” in “Welcome” Contents of this chapter About Troubleshooting.....................................................................................396 Getting Started with Troubleshooting........................................................396 Creating a “Clean Boot” for Troubleshooting ...........................................398 Troubleshooting Setup......................................................................................399 Troubleshooting TSR s During Setup .........................................................400 Troubleshooting MS-DOS Mode Setup......................................................401 Troubleshooting Windows Mode Setup ....................................................402 Troubleshooting Windows Configuration ........................................................403 Troubleshooting the Desktop Configuration .............................................403 Troubleshooting TSR Compatibility Problems ..........................................404
    [Show full text]