DOCSLIB.ORG

Installation Guide

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Installation Guide ATA Hard Drive Installation Guide Copyright © 2002 Maxtor Corporation. All rights reserved. Changes are periodically made to the information herein which will be incorporated in revised editions of this publication. Maxtor may make changes or improvements to the product(s) described in this publication at any time and without notice. MaxBlast is a trademark and Maxtor is a registered trademark of Maxtor Corporation. All other brands or products are trademarks or registered trademarks of their respective holders. FCC Declaration of Conformance This device complies with part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) this device may not cause harmful interference, and (2) this device must accept any interference received including interference that may cause undesired operation. Maxtor Corporation Part Number 500 McCarthy Blvd., Milpitas, California 95035 USA 20186800/A P/N: 20186800/A Contents 1 Getting Started . 1 Handling the Hard Drive. 1 Operating System Requirements . 1 Back Up Your Data . 2 Important Capacity Notice . 2 2 Installing the Hard Drive. 3 Removing the System Cover. 3 Setting the Jumpers . 4 Mounting the Hard Drive . 7 Attaching the Cables . 9 Configuring the System BIOS . 12 3 Formatting the Hard Drive . 15 Installing Hard Drive as a Boot Drive. 16 Installing Hard Drive to Replace Existing Hard Drive. 20 Installing Hard Drive as an Additional Hard Drive . 21 4 Getting Help . 23 Installation Troubleshooting . 23 Frequently Asked Questions . 25 5 Glossary . 27 Maxtor Product Warranty. 30 Getting Started 1 Thank you for selecting a Maxtor hard drive storage product. This installation guide will lead you through the installation of your hard drive. The Maxtor Hard Drive Retail Kit includes the components shown in Figure 1. Your computer may need some or all of these parts to complete the installation. You will also need ATA Interface Cable Maxtor ATA Hard Drive the tools shown in Figure 2 on page 2 to install the hard drive in your computer. Max•BlastTM Plus II Handling the Hard Drive Hard Drive Installation Software MaxBlast Plus II Your hard drive should be handled with care during unpacking and installation. Damage to Installation Disk hard drives is typically caused by rough handling, shock, vibration, or electrostatic discharge (ESD). Be aware of the following precautions when unpacking and handling your hard drive: MaxBlast Plus II Installation CD • Save the packing materials in case you need to return your hard drive. • Allow the hard drive to reach room temperature before opening the anti-static bag. Installation Guide • Handle the hard drive by its sides. Do not touch the circuit board electronics on the bottom (not included with all kits) of the hard drive. Mounting Screws • Do not connect or disconnect any hard drive cables when the system is powered on. • Do not drop, jar, or bump the hard drive. Operating System Requirements 5.25-inch Mounting Brackets (not included with all kits) Quick Start Poster A full version of your operating system is required to install a new hard drive. Figure 1. Included in this Kit Windows 98, ME, NT, 2000 and XP (before SP1), and Mac OS operating systems do not properly support the full capacity of an internal hard drive larger than 137 GB. See “Formatting the Hard Drive” on page 15 for more information. Getting Started 1 Back Up Your Data 1 Protect your data by backing up existing hard drives before installing your new Maxtor System Manual hard drive. Important Capacity Notice System User Manual If you are installing this hard drive without an Ultra/ATA PCI adapter card, be sure that your computer meets the system requirements printed on the Maxtor box. Some older systems require the use of an ATA card to fully recognize higher capacity hard drives. If you are installing this hard drive with an Ultra/ATA PCI adapter card, use the ATA card documentation to install the card before installing the hard drive. Operating System Maxtor recommends that all customers use the MaxBlast™ Plus II installation software, rather CD and/or Boot Disk than FDISK, to partition and format the hard drive. See “Frequently Asked Questions” on page 25 for more information on the MaxBlast Plus II formatting utility. Phillips Screwdriver Small Needle-Nose Pliers Figure 2. Required Tools 2 Getting Started Installing the Hard Drive This chapter describes how to physically install the hard drive in your computer. The installation steps are as follows: • Remove the system cover. 2 • Set the jumpers. • Mount the hard drive in your computer. • Attach the cables. • Configure the BIOS (Windows-based systems only). Removing the System Cover For Macintosh systems, refer to the documentation that came with your system or go to www.apple.com/support for information about opening your system case. 1. Turn your computer off. Leave the computer powered off and plugged into an electrical outlet to keep the system grounded. 2. Remove the cover from your system case. Refer to your computer system user manual for instructions on removing the cover, or obtain the services of a qualified installation technician. 3. Attach a grounding strap or touch a metal portion of your computer case. This will ground you to minimize the risk of exposing the hard drive to electrostatic discharge. Figure 3. Removing the System Cover Installing the Hard Drive 3 Setting the Jumpers A jumper is a small plastic piece that slides over a pair of configuration pins. (See Figure 4.) The next step in the installation process is to set the jumpers on the back of your hard drive so your system can identify the hard drive. 2 The following definitions describe the jumper settings: Figure 4. A Jumper Master. This setting can be used if you will be using the new hard drive as a primary master boot drive or a secondary master additional storage drive. The hard drive should be connected to the black (master) connector at the end of the ATA cable. Slave. This setting can be used if you will be using the new hard drive for additional storage only and is not typically used for boot devices on Windows-based systems. The hard drive should be connected to the gray (middle) connector on the ATA cable. Cable Select. This setting is an alternate method of hard drive identification that can be used instead of the master and slave settings. With cable select enabled, all hard drives positioned on the black (master) connector of the ATA cable will identify as master, and all hard drives positioned on the gray (middle) connector will identify as slave. To properly configure cable select, all devices on the same ATA cable must use the cable select jumper setting and be connected with an 40-pin Ultra ATA cable like the one included. Before installing a new hard drive, Maxtor recommends that you check to see if any device currently attached to the ATA cable you wish to use is configured as cable select. You may need to consult the documentation for this device or its manufacturer for jumper configuration information. Older systems that do not support Ultra ATA/66 speeds or are dated prior to November " 1998 may not be able to use the cable select jumper option. If you are uncertain whether your system can use the cable select option, use the master/slave settings instead. 4 Installing the Hard Drive Determining the Correct Jumper Setting The correct jumper setting for your hard drive depends on your current system configuration and how you want to use the new hard drive. The recommended jumper settings below will work on many, but not all, systems. • If you are building a new system, use the cable select setting on all ATA devices to make it easier to configure your system. • If you have an existing system, check the jumper settings on your current boot drive and C O R P O R O R A T T X I O A N M • • H Y A T R I D L A D U I S Q K • D R E I V Capacity 80GB Firmware: M206B Level MP your CD-ROM drive. If these drives are using master/slave jumper settings, use the master/ P/N: 127351 slave jumper settings on your new hard drive. If your current boot drive and CD-ROM drive are using the cable select setting, use cable select on the new hard drive. " Internal CD-ROM, DVD, Zip, and Jaz drives with an ATA interface are known as ATAPI- Jumper Style A compliant devices. If the new hard drive is being attached to a cable to which an ATAPI drive is already attached, you should configure the hard drive as master and the ATAPI device as slave OR both devices as cable select, with the ATAPI device attached to the Jumper Stylesor B & C gray connector on the ATA cable. To avoid potential issues with hard drive detection and performance, Maxtor does not recommend attaching a hard drive as a slave on the same To determinecable as anyour ATAPI hard device. drive (For cable configuration, see “Existing System 3” on page 11.) Figure 5. Determine Jumper Style 1. 2 Remove the hard drive from its anti-static bag. 2. Locate the jumper block on the back of hard drive. the right of the ATA connector on the hard drive. See Figure 5. 3. Match the jumper block to jumper’s stylejumper A, B,style or C shown in Figure 5. determine if you have jumper style C, look for model number D740X or D540X-4K on the label located on the top of the hard drive.
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]
  • 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]
  • 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]
  • Unit V Algorithm for Booting the UNIX System
    Unit V Algorithm for booting the UNIX system : As we’ve noted, the boot process begins when the instructions stored in the computer’s permanent, nonvolatile memory (referred to colloquially as the BIOS, ROM,NVRAM, and so on) are executed. This storage location for the initial boot instructions is generically referred to as firmware (in contrast to “software,” but reflecting the fact that the instructions constitute a program[2]). These instructions are executed automatically when the power is turned on or the system is reset, although the exact sequence of events may vary according to the values of stored parameters.[3] The firmware instructions may also begin executing in response to a command entered on the system console (as we’ll see in a bit). However they are initiated, these instructions are used to locate and start up the system’s boot program , which in turn starts the Unix operating system. The boot program is stored in a standard location on a bootable device. For a normal boot from disk, for example, the boot program might be located in block 0 of the root disk or, less commonly, in a special partition on the root disk. In the same way, the boot program may be the second file on a bootable tape or in a designated location on a remote file server in the case of a network boot of a diskless workstation. There is usually more than one bootable device on a system. The firmware program may include logic for selecting the device to boot from, often in the form of a list of potential devices to examine.
    [Show full text]
  • Bootloader and Startup Feature Overview and Configuratoin Guide
    TechnicalTTechnicalechnical GuideGuidGuidee Bootloader and Startup Feature Overview and Configuration Guide The AlliedWare Plus™ Bootloader Every switch has a startup process. The end result of the startup is that the unit is running a specific version of the operating system software, with the features configured according to a specific startup configuration file. The startup process goes through two main phases: First, the switch boots up off a dedicated bootloader software image, which initializes core functionality of the unit. Then, the bootloader launches the main operating software image, and passes control over to this operating system. The bootloader is the executable code responsible for setting up the system and loading the operating system software. The bootloader is the software that runs the unit when it first powers up, performing basic initialization and executing the product software release. As part of the startup process of the switch, the bootloader allows you various options before running the product operating system software. C613-22004-00 x REV A alliedtelesis.com Products and software version that apply to this guide This guide applies to all AlliedWare Plus products, running version 5.4.4 or later. However, not all features in this guide are supported on all products. To see whether a product supports a particular feature or command, see the following documents: The product’s Datasheet The AlliedWare Plus Datasheet The product’s Command Reference These documents are available from the above links on our website at alliedtelesis.com. Feature support may change in later versions. For the latest information, see the above documents. Content The AlliedWare Plus™ Bootloader ....................................................................................
    [Show full text]
  • Using the OMAP-L132/L138 Bootloader
    Application Report SPRAB41F–January 2014–Revised January 2019 Using the OMAP-L132/L138 Bootloader Joseph Coombs ABSTRACT This application report describes various boot mechanisms supported by the OMAP-L132/L138 bootloader read-only memory (ROM) image. Topics covered include the Application Image Script (AIS) boot process, an AISgen tool used to generate boot scripts, protocol for booting the device from an external master device, a UART Boot Host GUI for booting the device from a host PC, and any limitations, default settings, and assumptions made by the bootloader. Project collateral discussed in this application report can be downloaded from the following URL: http://www.ti.com/lit/zip/sprab41. Contents 1 Introduction ................................................................................................................... 3 2 Boot Modes................................................................................................................... 3 3 Non-AIS Boot Modes........................................................................................................ 3 4 Application Image Script (AIS) Boot....................................................................................... 6 5 AISgen: Tool to Generate Boot Script (AIS Image).................................................................... 11 6 Master Boot – Booting From a Slave Memory Device ................................................................ 19 7 Slave Boot – Booting From an External Master Host ................................................................
    [Show full text]
  • Using the OMAP-L1x7 Bootloader Urmil Parikh and Joseph Coombs
    Application Report SPRAB04G– June 2012 Using the OMAP-L1x7 Bootloader Urmil Parikh and Joseph Coombs ABSTRACT This application report describes various boot mechanisms supported by the OMAP-L1x7 bootloader read- only memory (ROM) image. Topics covered include the Application Image Script (AIS) boot process, an AISgen tool used to generate boot scripts, protocol for booting the device from an external master device, a UART Boot Host GUI for booting the device from a host PC, and any limitations, default settings, and assumptions made by the bootloader. Project collateral discussed in this application report can be downloaded from the following URL: http://www.ti.com/lit/zip/SPRAB04. Contents 1 Introduction .......................................................................................................................................................... 2 2 Boot Modes .......................................................................................................................................................... 3 3 Non-AIS Boot Modes ........................................................................................................................................... 3 4 Application Image Script (AIS) Boot ..................................................................................................................... 5 5 AISgen: Tool to Generate Boot Script (AIS image) ........................................................................................... 11 6 Master Boot – Booting From a Slave Memory Device
    [Show full text]
  • How to Boot Linux in One Second …Why Userland Is a Waste of Time ;)
    How to boot Linux in one second …why userland is a waste of time ;) Jan Altenberg Linutronix GmbH Jan Altenberg Linutronix GmbH 1 from zero… Jan Altenberg Linutronix GmbH 2 to hero… Jan Altenberg Linutronix GmbH 3 Overview 1. Basics Motivation Some technical basics 2. Optimizations Bootloader Kernel Filesystem Application 3. Example Optimizing an ARMv5 based device Optimizing the test system Jan Altenberg Linutronix GmbH 4 Motivation 1. Basics Motivation Some technical basics 2. Optimizations Bootloader Kernel Filesystem Application 3. Example Optimizing an ARMv5 based device Optimizing the test system Jan Altenberg Linutronix GmbH 5 • solution: power-off instead of suspending • BUT: Users are not used to wait Motivation Motivation ''marketing'' automotive applications energy saving Jan Altenberg Linutronix GmbH 6 • BUT: Users are not used to wait Motivation Motivation ''marketing'' automotive applications energy saving • solution: power-off instead of suspending Jan Altenberg Linutronix GmbH 6 Motivation Motivation ''marketing'' automotive applications energy saving • solution: power-off instead of suspending • BUT: Users are not used to wait Jan Altenberg Linutronix GmbH 6 Some technical basics 1. Basics Motivation Some technical basics 2. Optimizations Bootloader Kernel Filesystem Application 3. Example Optimizing an ARMv5 based device Optimizing the test system Jan Altenberg Linutronix GmbH 7 Some technical basics First step: Define your requirements!!!! What's the limit for the boot time? Which functionality should be available? Speed
    [Show full text]
  • Linux Booting Procedure How Linux Boot?
    Linux Booting Procedure How Linux boot? 2 What is “boot”? • boot (n.) [1] http://en.wikipedia.org/wiki/Boot 4 Brief etymology[2] • Phrase “pull oneself up by one’s bootstraps” • Misattributed (at latest in 1901!) to “The Surprising Adventures of Baron Munchausen” (1781, Rudolf Erich Raspe) : The baron pulls himself out of a swamp by his hair (pigtail). • The use of this phrase is found in 1834 in the U.S. • “[S]omeone is attempting or has claimed some ludicrously far-fetched or impossible task” • In the 20th century, the “possible bootstrap[3] task” meaning has appeared • “To begin an enterprise or recover from a setback without any outside help; to succeed only on one's own effort or abilities” 5 [2] http://en.wiktionary.org/wiki/pull_oneself_up_by_one%27s_bootstraps [3] http://en.wikipedia.org/wiki/Bootstrapping Bootstrapping (in Computer) • The process of loading the basic software (typically, operating systems) into the main memory from persistent memory (HDD, flash ROM, etc.) • “Boot” is an abbreviation for “bootstrap(ping)” Boostrapping Code 6 System startup Booting sequence 1. Tern on 2. CPU jump to address of BIOS (0xFFFF0) 3. BIOS runs POST (Power-On Self Test) 4. Find bootale devices 5. Loads and execute boot sector form MBR 6. Load OS 5 BIOS (Basic Input/Output System) BIOS refers to the software code run by a computer when first powered on The primary function of BIOS is code program embedded on a chip that recognises and controls various devices that make up the computer. BIOS on board BIOS on screen 6 How computer startup? Booting is a bootstrapping process that starts operating systems when the user turns on a computer system A boot sequence is the set of operations the computer performs when it is switched on that load an operating system 4 Boot loader MBR (Master Boot Record) OS is booted from a hard disk, where the Master Boot Record (MBR) contains the primary boot loader The MBR is a 512-byte sector, located in the first sector on the disk (sector 1 of cylinder 0, head 0) After the MBR is loaded into RAM, the BIOS yields control to it.
    [Show full text]
  • VPC100 All-In-One PC! the VPC100 All-In-One PC Is Engineered for Powerful Computing Performance
    ® - User Guide ViewSonic - Guide de l’utilisateur - Bedienungsanleitung VPC100 - Guía del usuario All-in-One PC - Pyководство пользователя - Οδηγός χρηστών - 使用手冊(繁中) - 使用手冊(简中) - 사용자 안내서 Model No. : VS12489 Table of Contents Preface................................................................................................... iv Compliance Information ..................................................................................... iv Important Safety Instructions ............................................................................. vi Declaration of RoHS Compliance ..................................................................... vii Copyright Information ........................................................................................viii U.S. Patent Numbers ........................................................................................viii Product Registration........................................................................................... ix Specifications ......................................................................................................x Chapter 1: Getting Started .................................................................... 1 Package Contents ...............................................................................................2 Features ..............................................................................................................3 System Overview ................................................................................................4
    [Show full text]
  • Booting from On-Chip ROM (Esdhc Or Espi)
    Freescale Semiconductor Document Number: AN3659 Application Note Rev. 2, 06/2012 Booting from On-Chip ROM (eSDHC or eSPI) This document describes on-chip ROM booting from an Contents SD card/MMC or from an EEPROM under a Linux 1. What does the on-chip ROM do? . 2 2. Building a Cconfiguration file . 2 operating system on the following devices: 3. Building a RAM-based U-Boot under Linux . 15 • MPC8536E 4. Preparing the image using boot_format . 18 5. Required POR configurations for booting from on-chip ROM • MPC8569E 20 6. Booting from on-chip ROM on an MPC8536DS . 21 • P2020 7. Booting to Linux from an SD card/MMC . 25 • P1011 8. Revision history . 28 • P1012 • P1013 • P1020 • P1021 • P1022 NOTE The term ‘EEPROM’ refers to a serial flash or an EEPROM memory device with an SPI interface in this document. © 2012 Freescale Semiconductor, Inc. All rights reserved. What does the on-chip ROM do? 1 What does the on-chip ROM do? The on-chip ROM includes both an eSDHC device driver and an eSPI driver. The driver code copies data from either an SD card/MMC or from an EEPROM with an SPI interface to a temporary memory location (see Section 2.4, “Choosing the temporary memory location”). The on-chip ROM is internally mapped to 0xFFFF_E000 when booting from either an SD card/MMC or from an EEPROM.The on-chip boot ROM code uses the information from the SD card/MMC or the EEPROM to configure a temporary memory, such as the L2 cache or a DDR, before it copies a U-Boot image to this temporary memory.
    [Show full text]
  • Secure Boot on Embedded Sitara™ Processors
    Secure boot on embedded Sitara™ processors Amrit Mundra Security architect and systems engineer Texas Instruments Hong Guan Security application engineer Texas Instruments Executive summary The security of an embedded system should not be an afterthought, an after-the- fact add-on or a nice-to-have feature. Either security is designed into the embedded processor so that the device operates as intended from the time power is first supplied, or it’s not. And if it’s not, there may be problems. Of course, when an issue as complex as security comes up, usually the first question a designer will ask is where to begin? Without a strong foundation, the security subsystem of an embedded system will be built on sand. Every security feature or capability in the system will be only as strong and as effective as the foundation upon which it is built. Building a powerful security foundation begins when the system boots. This white paper explains how the secure boot process has been designed into TI Sitara™ processors, as well as their supporting infrastructures, and how these design features provide the root-of-trust upon which designers can begin to build security subsystems to meet their desired security objectives. What is secure boot? say that in the absence of a secure boot process, there is no root-of-trust established in the system. The system booting process occurs every time a So, to secure the boot process, the boot firmware system is reset or power is applied to an unpowered stored in memory must be certifiably secure and system.
    [Show full text]