DOCSLIB.ORG

Preparing for and Dealing with Windows NT Start-Up Problems

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Preparing for and Dealing with Windows NT Start-Up Problems Preparing for and Dealing With Windows NT® Start-up Problems Agilent ChemStation Products "Success depends on preparation." Read this document now; schedule regular backups and perform disk maintenance regularly. Create and maintain a current ERD (see below). The following procedure assumes you have some knowledge of Windows, and you have determined that you need to repair or restore a Windows NT system. You should always maintain a current backup of all critical data from the hard disk you wish to save, before using this procedure. It is the ChemStation User's responsibility to ensure that all critical computer files are backed up on a routine basis, as determined by your business environment. Working with the Microsoft Windows NT “Blue Screen” halt. The text mode STOP messages or “Blue Screens” are used to identify and debug hardware and software problems that occur while loading or running Windows NT. When a mission critical operating system fails, NT will generate the Blue Screen consisting of a STOP message, the text translation, the address of the violating call, and the drivers loaded at the time of the STOP screen. Each time Windows NT boots up and a user successfully logs on, the registries are backed up into a compressed file. If any drivers or programs are changed that cause the system to halt with the dreaded Blue Screen, try rebooting. During the boot process, Windows NT gives you the opportunity to “Hit the Spacebar for the Last Known Good Configuration”. Hitting the spacebar will find the compressed backup of the registries from the last successful logon, and copy these files back to the registries. This will fix many problems caused by configuration changes or incompatible drivers. If the Windows NT boot files have become corrupted, or deleted, the Blue Screen will appear without giving an opportunity to “hit the spacebar….” In this case, the boot files must be restored. This can be done using the Emergency Repair Disk (ERD). This document is believed to be accurate and up-to-date. However, Agilent Technologies, Inc. cannot assume responsibility for the use of this material. The information contained herein is intended for use by informed individuals who can and must determine its fitness for their purpose. a05308.doc http:// www.chem.agilent.com Page 1 of 8 *NOTE* All bundled systems purchased from Agilent, where the Instrument and ChemStation are purchased together are shipped with an Emergency Recovery Kit (see Appendix A). This kit consists of: 1 (one) CD labeled Emergency Recovery CD - This CD contains an image of the NT operating system, along with a folder called i386, which contains the standard Microsoft NT install files. 2 (two) floppy Disks - 1 disk labeled Emergency Boot Floppy and a second floppy disk labeled Emergency Repair Disk (ERD). This ERD is not the current ERD, which you must create and update regularly. This kit can be used if the operating system cannot be recovered as previously noted. NOTE: If you do not have these disks, you will need to find and/or purchase replacements before you will be able to restore your system. AFTER THE SYSTEM IS INSTALLED, AND WHENEVER THE SYSTEM IS UPGRADED, UPDATED, OR SIGNIFICANTLY CHANGED, DO THE FOLLOWING: Creating and using the Windows NT Emergency Repair Disk (ERD) The ERD is used to take a snapshot of your system’s configuration. The ERD is not bootable, and is used in conjunction with the NT Startup Disks. The ERD mentioned above that ships with the standard Agilent bundles, needs to be updated once you have the entire system installed and updated, or any time after you install new programs or modify system settings. !!!IT IS VERY IMPORTANT TO KEEP THE ERD DISK CURRENT!!! If you are not sure if your ERD is current, create or update it before installing any software or hardware updates. You can use the emergency repair disk to: Inspect the Registry files Inspect the Startup environment Verify the NT system files Inspect the boot sector If any of your boot files are missing or corrupt, you can repair the failure through the emergency repair disk, or by using a NT Boot Disk (See below). To repair boot files, you need the three NT setup disks and the ERD. To create/update your NT Emergency Repair Disk (ERD) a05308.doc hhttp://ttp:// www.chem.agilent.com Page 2 of 8 This option can only be performed when your system is working properly. If you do not complete this step before a failure, then you have a poor chance of successfully repairing your NT system after a failure. Click on Start-Programs-Command Prompt - the Windows NT Command Prompt should appear. At the C:\> prompt type: RDISK /s (then press <Enter> key.) The Saving Configuration window appears. This stores the information to the hard drive. When prompted, select 'Yes' to also save the information to a floppy. You will need to insert a new floppy at this point. The program will format the disk and store the ERD to it. Label the disk and store it in a secure area. You should avoid using an ERD from another computer if you plan on repairing the registry. Nor should you use this one on another computer!! *Note* The /s switch used with the RDISK command, forces RDISK to backup the SAM and SECURITY hives to the hard drive \winnt\repair folder, along with the rest of the registry. Without the /s, these hives aren't backed up by RDISK Preparing a NT bootable floppy disk It is essential that you prepare an NT boot disk, this is a 3 1/2" floppy formatted under NT. You can boot from this disk later if any of your NT startup files become corrupt or missing. Prepare this disk as listed below. If you suspect one or more of the startup files is bad, insert this floppy into your floppy disk drive with the computer shut down. Turn on the computer and allow the normal startup process to proceed. If successful, your computer will read from the floppy and then continue booting the NT system from the hard drive. You should be able to logon as usual. You can now restore the individual NT boot files from this floppy to your hard drive. Use the NT Explorer to restore these files. This step may save you from having to run through the NT SETUP/ERD process. Create an NT bootable floppy disk: 1. Format floppy in NT Explorer (A disk formatted on DOS or Win9x will not work!!) On a working NT machine, format a floppy diskette (You MUST format the disk on NT; even if you're using a pre-formatted diskette, format it again on NT.) Before formatting the disk, ensure that the “Quick Format” option is not selected, or there will be no NT boot sector written to the formatted floppy. Or from the Command Prompt in NT type: format a: 2. You need to copy some files to this diskette from the root directory of the boot partition for NT on the system for which you are creating these disks. Make sure hidden & system files are displayed in the NT Explorer. To do this, open NT Explorer, click View...Options and click the radio button to "Show All Files", and unselect “Hide file extensions for known file types”. Select OK to close the window. You should see the following files: NTLDR - Loads NT operating system for Intel based computers BOOT.INI - Builds the boot loader operating system menu NTDETECT.COM - Only used on Intel machines, Detects HW, passes to ntldr. BOOTSECT.DOS - Run for all non-NT Op Systems, used to boot MS-DOS. NTBOOTDD.SYS - SCSI hard drives on Intel machines with BIOS disabled adapter. *Note if you don't find the file, your machine probably does not use it. The first 4 files are most important! Copy all of these files to your newly formatted floppy disk. YOU NOW HAVE AN NT BOOT FLOPPY!! a05308.doc hhttp://ttp:// www.chem.agilent.com Page 3 of 8 Creating the 3 (three) NT setup floppy disks If you purchased an Agilent ChemStation bundle, you will have to create the 3 NT install setup disks. You can use either the First or the Second choices below. First choice: On a running ChemStation Bundle system, select Start, Run, and enter: \i386\winnt32.exe /ox Second choice: 1. With the system shut down, insert the Emergency Boot Floppy and Emergency Recovery CD. Then turn on your computer. The system should boot from the floppy and stop at the a:\> prompt. 2 Type at the prompt: a:\> d: (then press <Enter> key) Only type (d:). This assumes that d: is the drive letter assigned to the CD-ROM drive. Substitute the correct letter for your system. 3. Now your prompt should be: D:\>. Type the following: cd i386 Press <Enter> key. 4. At the d:\i386> prompt, type: winnt /ox *Note* This will start the NT installation program. The /ox option forces winnt to only create the 3 installation floppies. Follow the prompts and label the floppies accordingly. Saving Data needed to restore ChemStation(GC, LC, A/D, UV & LC/MSD only) 1. With ChemStation sessions closed, select one of the following based on your revision: Before A.08.0x: START-PROGRAMS-HP CHEMSTATIONS-HP CONFIGURATION EDITOR A.08.0x: START-PROGRAMS-CHEMSTATIONS-CONFIGURATION EDITOR UV-VIS: START-PROGRAMS-UV-VISIBLE CHEMSTATIONS 2. Select File, Print and choose All Instruments. Print and save the configuration in a safe place. 3. Make sure you have all Software License Numbers.
Load more

Recommended publications
  • Boot Mode Considerations: BIOS Vs UEFI
    Boot Mode Considerations: BIOS vs. UEFI An overview of differences between UEFI Boot Mode and traditional BIOS Boot Mode Dell Engineering June 2018 Revisions Date Description October 2017 Initial release June 2018 Added DHCP Server PXE configuration details. The information in this publication is provided “as is.” Dell Inc. makes no representations or warranties of any kind with respect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a particular purpose. Use, copying, and distribution of any software described in this publication requires an applicable software license. Copyright © 2017 Dell Inc. or its subsidiaries. All Rights Reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be the property of their respective owners. Published in the USA [1/15/2020] [Deployment and Configuration Guide] [Document ID] Dell believes the information in this document is accurate as of its publication date. The information is subject to change without notice. 2 : BIOS vs. UEFI | Doc ID 20444677 | June 2018 Table of contents Revisions............................................................................................................................................................................. 2 Executive Summary ............................................................................................................................................................ 4 1 Introduction ..................................................................................................................................................................
    [Show full text]
  • Active@ Boot Disk User Guide Copyright © 2008, LSOFT TECHNOLOGIES INC
    Active@ Boot Disk User Guide Copyright © 2008, LSOFT TECHNOLOGIES INC. All rights reserved. No part of this documentation may be reproduced in any form or by any means or used to make any derivative work (such as translation, transformation, or adaptation) without written permission from LSOFT TECHNOLOGIES INC. LSOFT TECHNOLOGIES INC. reserves the right to revise this documentation and to make changes in content from time to time without obligation on the part of LSOFT TECHNOLOGIES INC. to provide notification of such revision or change. LSOFT TECHNOLOGIES INC. provides this documentation without warranty of any kind, either implied or expressed, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. LSOFT may make improvements or changes in the product(s) and/or the program(s) described in this documentation at any time. All technical data and computer software is commercial in nature and developed solely at private expense. As the User, or Installer/Administrator of this software, you agree not to remove or deface any portion of any legend provided on any licensed program or documentation contained in, or delivered to you in conjunction with, this User Guide. LSOFT.NET logo is a trademark of LSOFT TECHNOLOGIES INC. Other brand and product names may be registered trademarks or trademarks of their respective holders. 2 Active@ Boot Disk User Guide Contents 1.0 Product Overview ..........................................................................................................
    [Show full text]
  • 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]
  • Illustrated Tutorial: Creating a Bootable USB Flash Drive for Windows XP
    Illustrated tutorial: Creating a bootable Version 1.0 February 15, 2007 USB flash drive for Windows XP By Greg Shultz The ability to boot Windows XP from a USB Flash Drive (UFD) offers endless possibilities. For example, you might make an easy-to-use troubleshooting tool for booting and analyzing seemingly dead PCs. Or you could transport your favorite applications back and forth from home to work without having to install them on both PCs. However, before you can create a bootable UFD, you must clear a few hurdles. You saw that one coming didn’t you? The first hurdle is having a PC in which the BIOS will allow you to configure the USB port to act as a bootable device. The second hurdle is having a UFD that that will work as a bootable device and that’s large enough and fast enough to boot an operating system such as Windows XP. The third hurdle is finding a way to condense and install Windows XP on a UFD. If you have a PC that was manufactured in the last several years, chances are that its BIOS will allow you to configure the USB port to act as a bootable device. If you have a good qual- ity UFD that’s at least 512 KB and that was manufactured in the last couple of years, you’ve probably cleared the second hurdle. And once you’ve cleared those first two hur- dles, the third one is a piece of cake. All you have to do is download and run some free soft- ware to create the bootable UFD.
    [Show full text]
  • Volatility: Part 2 – Malware in Hiberfil.Sys
    Patrick Leahy Center for Digital Investigation (LCDI) Volatility: Part 2 – Malware in hiberfil.sys Written by Dan Doonan and Catherine Stamm Researched by Dan Doonan, Connor Hicks, David Leberfinger, and Catherine Stamm The Senator Patrick Leahy Center for Digital Investigation Champlain College December 4, 2012 Version: 0.1 – Volatility: – Review Date: 12/4/2012 Page 1 of 6 Patrick Leahy Center for Digital Investigation (LCDI) Disclaimer: This document contains information based on research that has been gathered by employee(s) of The Senator Patrick Leahy Center for Digital Investigation (LCDI). The data contained in this project is submitted voluntarily and is unaudited. Every effort has been made by LCDI to assure the accuracy and reliability of the data contained in this report. However, LCDI nor any of our employees make no representation, warranty or guarantee in connection with this report and hereby expressly disclaims any liability or responsibility for loss or damage resulting from use of this data. Information in this report can be downloaded and redistributed by any person or persons. Any redistribution must maintain the LCDI logo and any references from this report must be properly annotated. Contents 1 Introduction ................................................................................................................................3 1.1 Background .........................................................................................................................3 1.2 Research Questions ..............................................................................................................3
    [Show full text]
  • Chapter 3. Booting Operating Systems
    Chapter 3. Booting Operating Systems Abstract: Chapter 3 provides a complete coverage on operating systems booting. It explains the booting principle and the booting sequence of various kinds of bootable devices. These include booting from floppy disk, hard disk, CDROM and USB drives. Instead of writing a customized booter to boot up only MTX, it shows how to develop booter programs to boot up real operating systems, such as Linux, from a variety of bootable devices. In particular, it shows how to boot up generic Linux bzImage kernels with initial ramdisk support. It is shown that the hard disk and CDROM booters developed in this book are comparable to GRUB and isolinux in performance. In addition, it demonstrates the booter programs by sample systems. 3.1. Booting Booting, which is short for bootstrap, refers to the process of loading an operating system image into computer memory and starting up the operating system. As such, it is the first step to run an operating system. Despite its importance and widespread interests among computer users, the subject of booting is rarely discussed in operating system books. Information on booting are usually scattered and, in most cases, incomplete. A systematic treatment of the booting process has been lacking. The purpose of this chapter is to try to fill this void. In this chapter, we shall discuss the booting principle and show how to write booter programs to boot up real operating systems. As one might expect, the booting process is highly machine dependent. To be more specific, we shall only consider the booting process of Intel x86 based PCs.
    [Show full text]
  • 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]
  • Linux Boot Loaders Compared
    Linux Boot Loaders Compared L.C. Benschop May 29, 2003 Copyright c 2002, 2003, L.C. Benschop, Eindhoven, The Netherlands. Per- mission is granted to make verbatim copies of this document. This is version 1.1 which has some minor corrections. Contents 1 introduction 2 2 How Boot Loaders Work 3 2.1 What BIOS does for us . 3 2.2 Parts of a boot loader . 6 2.2.1 boot sector program . 6 2.2.2 second stage of boot loader . 7 2.2.3 Boot loader installer . 8 2.3 Loading the operating system . 8 2.3.1 Loading the Linux kernel . 8 2.3.2 Chain loading . 10 2.4 Configuring the boot loader . 10 3 Example Installations 11 3.1 Example root file system and kernel . 11 3.2 Linux Boot Sector . 11 3.3 LILO . 14 3.4 GNU GRUB . 15 3.5 SYSLINUX . 18 3.6 LOADLIN . 19 3.7 Where Can Boot Loaders Live . 21 1 4 RAM Disks 22 4.1 Living without a RAM disk . 22 4.2 RAM disk devices . 23 4.3 Loading a RAM disk at boot time . 24 4.4 The initial RAM disk . 24 5 Making Diskette Images without Diskettes 25 6 Hard Disk Installation 26 7 CD-ROM Installation 29 8 Conclusions 31 1 introduction If you use Linux on a production system, you will only see it a few times a year. If you are a hobbyist who compiles many kernels or who uses many operating systems, you may see it several times per day.
    [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]
  • S.Ha.R.K. Installation Howto Tools Knoppix Live CD Linux Fdisk HD
    S.Ha.R.K. Installation Tools HowTo • Linux fdisk utility • A copy of Linux installation CD • A copy of Windows® installation CD Tullio Facchinetti University of Pavia - Italy • Some FreeDOS utilities • A copy of S.Ha.R.K. S.Ha.R.K. Workshop S.Ha.R.K. Workshop Knoppix live CD Linux fdisk Command action a toggle a bootable flag Download ISO from b edit bsd disklabel c toggle the dos compatibility flag d delete a partition http://www.knoppix.org l list known partition types m print this menu n add a new partition o create a new empty DOS partition table p print the partition table q quit without saving changes • boot from CD s create a new empty Sun disklabel t change a partition's system id • open a command shell u change display/entry units v verify the partition table • type “su” (become root ), password is empty w write table to disk and exit x extra functionality (experts only) • start fdisk (ex. fdisk /dev/hda ) Command (m for help): S.Ha.R.K. Workshop S.Ha.R.K. Workshop HD partitioning HD partitioning 1st FreeDOS FAT32 FreeDOS must be installed Primary 2nd Windows® FAT32 into the first partition of your HD or it may not boot 3rd Linux / extX Data 1 FAT32 format data partitions as ... Extended FAT32, so that you can share Data n FAT32 your data between Linux, last Linux swap swap Windows® and FreeDOS S.Ha.R.K. Workshop S.Ha.R.K. Workshop 1 HD partitioning Windows ® installation FAT32 Windows® partition type Install Windows®..
    [Show full text]
  • DOS Technical Reference
    -------- - ---- Personal Computer - ---- - --- ------ - . - Programming Family DOS Technical Reference 6138536 Preliminary First Edition (February 1985) The following paragraph does not apply to the United Kingdom or any country where such provisions are inconsistent ~ith local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES TIllS PUBLICATION "AS IS" wrrnom WARRANTY OF ANY KIND, EmlER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, 1HE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. lbis publication could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and!or changes in the product(s) and/or the program(s) described in this pUblication at any time. It is possible that this publication may contain reference to, or information about, IBM products (machines and programs), programming, or services that are not announced in your country. Such references or information must not be construed to mean that IBM intends to announce such IBM products, programming, or services in your country. Products are not stocked at the address below. Requests for copies of this publication and for technical information about IBM Personal Computer products should be made to your authorized IBM Personal Computer dealer, IBM Product Center, or your IBM Marketing Representative. The following paragraph applies only to the United States and Puerto Rico: A Reader's Comment Form is provided at the back of this publication. If the form has been removed.
    [Show full text]
  • Flashboot User Manual
    FlashBoot User Manual © 2015 Mikhail Kupchik Contents 3 Table of Contents Foreword 0 Part I Introduction 5 1 Product................................................................................................................................... Overview 5 2 Why USB................................................................................................................................... Flash Disks? 5 3 Why FlashBoot?................................................................................................................................... 6 4 System................................................................................................................................... Requirements 7 5 Limitations................................................................................................................................... of Demo Version 8 6 Demo Version................................................................................................................................... -> Full Version 8 7 Support................................................................................................................................... & Feedback 8 Part II CD/DVD to USB conversions 9 1 Install ...................................................................................................................................full Win8/8.1/10 -> USB [BIOS mode] 9 2 Install................................................................................................................................... full
    [Show full text]