DOCSLIB.ORG

This Document Explains How to Copy Ondemand5 Data to Your Hard Drive

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Copying Your Repair DVD Data To Your Hard Drive Introduction This document explains how to copy OnDemand5 Repair data to your hard drive, and how to configure your OnDemand software appropriately. The document is intended for your network professional as a practical guide for implementing Mitchell1’s quarterly updates. The document provides two methods; one using the Xcopy command in a DOS window, and the other using standard Windows Copy and Paste functionality. Preparing your System You will need 8 Gigabytes of free space per DVD to be copied onto a hard drive. Be sure you have the necessary space before beginning this procedure. Turn off screen savers, power down options or any other program that may interfere with this process. IMPORTANT NOTICE – USE AT YOUR OWN RISK: This information is provided as a courtesy to assist those who desire to copy their DVD disks to their hard drive. Minimal technical assistance is available for this procedure. It is not recommended due to the high probability of failure due to DVD drive/disk read problems, over heating, hard drive write errors and memory overrun issues. This procedure is very detailed and should only be performed by users who are very familiar with Windows and/or DOS commands. Novice computers users should not attempt this procedure. Copying Repair data from a DVD is a time-consuming process. Depending on the speed of your processor and/or network, could easily require two or more hours per disk. For this reason, we recommend that you perform the actual copying of data during non-business evening or weekend hours. If swapping DVD disks is an issue Mitchell1 recommends converting to Ondemand5.com. Contact Mitchell1 at 888-724-6742 to speak to a technical support representative if you do not have the WISE system. Copying Data Instructions Using “Xcopy” You will copy each DVD ROM to its own subdirectory on the hard drive you have chosen. Determine the drive letter of your DVD drive and load the first DVD in that drive. This example portrays the DVD ROM as drive E: and our hard drive as drive D: With the first DVD in the E: drive go to a command prompt, usually done by selecting Start / Run and entering ‘CMD’ or ‘Command’ and hitting Enter. With the DOS prompt window open, enter the command Xcopy e: d:\1 /s/i/r/y and hit Enter. DOS window with xcopy command This will create a directory on the D: drive named ‘1’ and copy the contents of the DVD to that folder. Once the copy process is complete, perform similar steps with the remaining discs and change the command appropriately. For example, copy disc two using the command: Xcopy e: d:\2 /s/i/r/y , disc three using the command: Xcopy e: d:\3 /s/i/r/y , etc. You will need to perform this function for all DVD disc, dependant on the number of disc to copy. Configure OnDemand5 When the copy process is complete, view Drive D: from My Computer … My Computer showing folders for OnDemand DVD Data Please start OnDemand5 and proceed with setting up the data location and updating data. Click on the Update Data button to reveal the Update Wizard screen OnDemand5 opening screen In the Update Wizard screen, and put a check mark in the Repair box and click Next. Update Wizard screen Enter ‘ D:\1 ‘ as the drive letter for the OnDemand5 DVD and click on Next. Updating Data – Repair Enter D:\1 thru D:\11 Data Paths and click Next. Data Location Screen Your system will copy the necessary files. Copying Files When the Data Updated window displays, you are ready to configure the remaining workstations on your network. Data Updated Summary If you completed the steps outlined in this section, you are ready to begin accessing OnDemand5 directly from a shared hard drive location, rather than from Data DVDs. Your data lookups will be quicker than ever before. You will also no longer need to support multiple dedicated DVD ROM drives on your network. Be sure and put your Data DVDs in a safe place for re-installation in the case of hard drive crash, or other unforeseen hardware problem. .
Recommended publications
  • Mac Keyboard Shortcuts Cut, Copy, Paste, and Other Common Shortcuts

    Mac Keyboard Shortcuts Cut, Copy, Paste, and Other Common Shortcuts

    Mac keyboard shortcuts By pressing a combination of keys, you can do things that normally need a mouse, trackpad, or other input device. To use a keyboard shortcut, hold down one or more modifier keys while pressing the last key of the shortcut. For example, to use the shortcut Command-C (copy), hold down Command, press C, then release both keys. Mac menus and keyboards often use symbols for certain keys, including the modifier keys: Command ⌘ Option ⌥ Caps Lock ⇪ Shift ⇧ Control ⌃ Fn If you're using a keyboard made for Windows PCs, use the Alt key instead of Option, and the Windows logo key instead of Command. Some Mac keyboards and shortcuts use special keys in the top row, which include icons for volume, display brightness, and other functions. Press the icon key to perform that function, or combine it with the Fn key to use it as an F1, F2, F3, or other standard function key. To learn more shortcuts, check the menus of the app you're using. Every app can have its own shortcuts, and shortcuts that work in one app may not work in another. Cut, copy, paste, and other common shortcuts Shortcut Description Command-X Cut: Remove the selected item and copy it to the Clipboard. Command-C Copy the selected item to the Clipboard. This also works for files in the Finder. Command-V Paste the contents of the Clipboard into the current document or app. This also works for files in the Finder. Command-Z Undo the previous command. You can then press Command-Shift-Z to Redo, reversing the undo command.
  • Powerview Command Reference

    Powerview Command Reference

    PowerView Command Reference TRACE32 Online Help TRACE32 Directory TRACE32 Index TRACE32 Documents ...................................................................................................................... PowerView User Interface ............................................................................................................ PowerView Command Reference .............................................................................................1 History ...................................................................................................................................... 12 ABORT ...................................................................................................................................... 13 ABORT Abort driver program 13 AREA ........................................................................................................................................ 14 AREA Message windows 14 AREA.CLEAR Clear area 15 AREA.CLOSE Close output file 15 AREA.Create Create or modify message area 16 AREA.Delete Delete message area 17 AREA.List Display a detailed list off all message areas 18 AREA.OPEN Open output file 20 AREA.PIPE Redirect area to stdout 21 AREA.RESet Reset areas 21 AREA.SAVE Save AREA window contents to file 21 AREA.Select Select area 22 AREA.STDERR Redirect area to stderr 23 AREA.STDOUT Redirect area to stdout 23 AREA.view Display message area in AREA window 24 AutoSTOre ..............................................................................................................................
  • 1. Xcopy 2. No, You Cannot Use the Xcopy Command in Your Assignment

    1. Xcopy 2. No, You Cannot Use the Xcopy Command in Your Assignment

    Intro to Operating Systems CNET 173 Assignment #4 Windows / LINUX Command Line Commands You are to list twenty-five command line commands of each operating system (WINDOWS and LINUX). That’s twenty- five WINDOWS commands and twenty-five LINUX commands. For each command you are to give: 1. The command a. Description/Attribute of the command b. Syntax of the command and c. A maximum of five Parameters used with the command and a description of the parameter. (If there are less than five parameters, list all parameters associated with the command.) Each command should be numbered and grouped (all WINDOWS commands with WINDOWS commands). Command information should be listed in the 1, a, b, c order listed above (i.e. command, description, syntax and parameters). This assignment must be typed and submitted through CANVAS. It should include a title page consisting of your name, course name, number, day and time, assignment name, instructor’s name, and due date and the assignment instructions. Example listed below. Windows Command Line Commands 1. xcopy a) Description - Copies files and directories, including subdirectories. b) Syntax xcopy Source [Destination] [/w] [/p] [/c] [/v] [/q] [/f] [/l] [/g] [/d[:mm-dd-yyyy]] [/u] [/i] [/s [/e]] [/t] [/k] [/r] [/h] [{/a|/m}] [/n] [/o] [/x] [/exclude:file1[+[file2]][+[file3]] [{/y|/-y}] [/z] c) Parameters /w : Displays the following message and waits for your response before starting to copy files: Press any key to begin copying file(s) /p : Prompts you to confirm whether you want to create each destination file. /c : Ignores errors. /v : Verifies each file as it is written to the destination file to make sure that the destination files are identical to the source files.
  • How to Cheat at Windows System Administration Using Command Line Scripts

    How to Cheat at Windows System Administration Using Command Line Scripts

    www.dbebooks.com - Free Books & magazines 405_Script_FM.qxd 9/5/06 11:37 AM Page i How to Cheat at Windows System Administration Using Command Line Scripts Pawan K. Bhardwaj 405_Script_FM.qxd 9/5/06 11:37 AM Page ii Syngress Publishing, Inc., the author(s), and any person or firm involved in the writing, editing, or produc- tion (collectively “Makers”) of this book (“the Work”) do not guarantee or warrant the results to be obtained from the Work. There is no guarantee of any kind, expressed or implied, regarding the Work or its contents.The Work is sold AS IS and WITHOUT WARRANTY.You may have other legal rights, which vary from state to state. In no event will Makers be liable to you for damages, including any loss of profits, lost savings, or other incidental or consequential damages arising out from the Work or its contents. Because some states do not allow the exclusion or limitation of liability for consequential or incidental damages, the above limitation may not apply to you. You should always use reasonable care, including backup and other appropriate precautions, when working with computers, networks, data, and files. Syngress Media®, Syngress®,“Career Advancement Through Skill Enhancement®,”“Ask the Author UPDATE®,” and “Hack Proofing®,” are registered trademarks of Syngress Publishing, Inc.“Syngress:The Definition of a Serious Security Library”™,“Mission Critical™,” and “The Only Way to Stop a Hacker is to Think Like One™” are trademarks of Syngress Publishing, Inc. Brands and product names mentioned in this book are trademarks or service marks of their respective companies.
  • Creating and Formatting Partitions

    Creating and Formatting Partitions

    Creating and formatting partitions Home Download Docs FAQ Forum Creating and formatting partitions SUNDAY, 14 NOVEMBER 2010 12:27 JAY Creating & formatting partitions in Porteus There are two ways to do things in Porteus. Using a GUI (graphical User Interface) or from a console prompt. If you prefer using a GUI then you can download a module called 'gparted' which takes care of creating and modifying partitions. Double click the module from within Porteus to activate it or place the module in the modules folder if you want it to be available automatically when you boot Porteus. Click here to get gparted. Once activated it should appear in your menu system and you can start it and create your partitions. If it does not exist in the menu then open a console and type: gparted Creating partitions from a console: There is a built in application to modify your partition table in Porteus. It is called cfdisk and gives you a CUI (console user interface) to manage your partition through. Simply open your console and type: cfdisk Another built in function for modifying partitions is called fdisk which also uses a CUI. The benefit of fdisk is that it can be called from a script. You should know the path of your USB device before using this option which you can get from typing: fdisk -l at console. Once you know the path of your USB device you would start fdisk by typing: fdisk /dev/sdb where sdb is the path of your usb. Don't include the number on the end (for example /dev/sdb1) as you will need to modify the entire devices partition table.
  • Configuring Your Login Session

    Configuring Your Login Session

    SSCC Pub.# 7-9 Last revised: 5/18/99 Configuring Your Login Session When you log into UNIX, you are running a program called a shell. The shell is the program that provides you with the prompt and that submits to the computer commands that you type on the command line. This shell is highly configurable. It has already been partially configured for you, but it is possible to change the way that the shell runs. Many shells run under UNIX. The shell that SSCC users use by default is called the tcsh, pronounced "Tee-Cee-shell", or more simply, the C shell. The C shell can be configured using three files called .login, .cshrc, and .logout, which reside in your home directory. Also, many other programs can be configured using the C shell's configuration files. Below are sample configuration files for the C shell and explanations of the commands contained within these files. As you find commands that you would like to include in your configuration files, use an editor (such as EMACS or nuTPU) to add the lines to your own configuration files. Since the first character of configuration files is a dot ("."), the files are called "dot files". They are also called "hidden files" because you cannot see them when you type the ls command. They can only be listed when using the -a option with the ls command. Other commands may have their own setup files. These files almost always begin with a dot and often end with the letters "rc", which stands for "run commands".
  • System Analysis and Tuning Guide System Analysis and Tuning Guide SUSE Linux Enterprise Server 15 SP1

    System Analysis and Tuning Guide System Analysis and Tuning Guide SUSE Linux Enterprise Server 15 SP1

    SUSE Linux Enterprise Server 15 SP1 System Analysis and Tuning Guide System Analysis and Tuning Guide SUSE Linux Enterprise Server 15 SP1 An administrator's guide for problem detection, resolution and optimization. Find how to inspect and optimize your system by means of monitoring tools and how to eciently manage resources. Also contains an overview of common problems and solutions and of additional help and documentation resources. Publication Date: September 24, 2021 SUSE LLC 1800 South Novell Place Provo, UT 84606 USA https://documentation.suse.com Copyright © 2006– 2021 SUSE LLC and contributors. All rights reserved. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or (at your option) version 1.3; with the Invariant Section being this copyright notice and license. A copy of the license version 1.2 is included in the section entitled “GNU Free Documentation License”. For SUSE trademarks, see https://www.suse.com/company/legal/ . All other third-party trademarks are the property of their respective owners. Trademark symbols (®, ™ etc.) denote trademarks of SUSE and its aliates. Asterisks (*) denote third-party trademarks. All information found in this book has been compiled with utmost attention to detail. However, this does not guarantee complete accuracy. Neither SUSE LLC, its aliates, the authors nor the translators shall be held liable for possible errors or the consequences thereof. Contents About This Guide xii 1 Available Documentation xiii
  • Falcon DOS Portable Terminals Advanced User's Guide

    Falcon DOS Portable Terminals Advanced User's Guide

    ! " #$% & " ' ()**%++,,,&% & " !"# $ $ % &' $ % ( ( % )*+ (*,' (% $ )(+ $ - !!. !!/$ 0 1 2 + + 2 3'4 0 5 -../ .+ 0 % &6 (*, % $ & & &/,( % & & ( &/,( 0 &(*, % & ! "#$%#$&#'%#'&( !! ! )!* 0 $ $ 0 3&7 4 8 $ 9 8 % 2 $ : $ 1 0 ; < $ ; * $ , . % $ / ) = ) $ # 0 , $ # 0 ( ( " & > 0 & > ? ! % , < 9 $ ; 0 ++ . 0 + = 0 & 2
  • Service Information

    Service Information

    Service Information VAS Tester Number: AVT-14-20 Subject: VAS Diagnostic Device Hard Disc Maintenance Date: Sept. 24, 2014 Supersedes AVT-12-12 due to updated information. 1.0 – Introduction If persistent diagnostic software or Windows® 7 operating system error messages are displayed while installing or using the diagnostic software, use the Windows CHKDSK utility to check hard disk integrity and fix logical file system errors. CHKDSK can also handle some physical errors and may be able to recover lost data that is readable. We recommend the CHKDSK utility be run on a regular basis on all VAS diagnostic devices in service. Consult with your dealership Systems Administrator or IT Professional about checking the integrity of the hard disk as described below on a regular basis, as well as regular performance of the Windows DEFRAG utility. 2.0 – Procedure Prerequisites: Device plugged into power adapter and booted to Windows desktop 1. Go to Windows Start > Computer 2. Right click/select Local Disk (C:) and select Properties from the dropdown menu: Continued… 2/ Page 1 of 3 © 2014 Audi of America, Inc. All rights reserved. Information contained in this document is based on the latest information available at the time of printing and is subject to the copyright and other intellectual property rights of Audi of America, Inc., its affiliated companies and its licensors. All rights are reserved to make changes at any time without notice. No part of this document may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, nor may these materials be modified or reposted to other sites, without the prior expressed written permission of the publisher.
  • 13 Using the Do-File Editor—Automating Stata

    13 Using the Do-File Editor—Automating Stata

    13 Using the Do-file Editor—automating Stata The Do-file Editor Stata comes with an integrated text editor called the Do-file Editor, which can be used for many tasks. It gets its name from the term do-file, which is a file containing a list of commands for Stata to run (called a batch file or a script in other settings). See [U] 16 Do-files for more information. Although the Do-file Editor has advanced features that can help in writing such files, it can also be used to build up a series of commands that can then be submitted to Stata all at once. This feature can be handy when writing a loop to process multiple variables in a similar fashion or when doing complex, repetitive tasks interactively. To get the most from this chapter, you should work through it at your computer. Start by opening the Do-file Editor, either by clicking on the Do-file Editor button, , or by typing doedit in the Command window and pressing Enter. The Do-file Editor toolbar The Do-file Editor has 15 buttons. Many of the buttons share a similar purpose with their look-alikes in the main Stata toolbar. If you ever forget what a button does, hover the mouse pointer over a button, and a tooltip will appear. New: Open a new do-file in a new tab in the Do-file Editor. Open: Open a do-file from disk in a new tab in the Do-file Editor. Save: Save the current file to disk.
  • Older Operating Systems

    Older Operating Systems

    Older Operating Systems Class Notes # 10 Batch Files (Part 2) October 23, 2003 IF Condition When a given condition is true, the statement is executed. When the given condition is false, the statement is not executed. Figure one illustrates the flow chart for the IF condition. IF entry point No Decision Yes Statement (perform some action) IF exit point Figure 1: IF condition flow chart The IF condition tests the following three conditions: • The ERRORLEVEL of a program • Whether a string is equal to another string • Whether a file exists Using IF to test ERRORLEVEL The syntax for testing the ERRORLEVEL is: IF ERRORLEVEL number command This form of the IF condition determines whether the value of ERRORLEVEL is greater than or equal to a number specified in the number parameter. IF NOT ERRORLEVEL number command This form of the IF condition determines whether the value of ERRORLEVEL is not greater than or equal to a number specified in the number parameter. 1 If the specified condition is true, DOS executes the command specified in the command parameter. Otherwise, DOS skips to the next line in the batch file without executing the command in the command parameter. The only DOS commands that leave an ERRORLEVEL (exit) code are: BACKUP, DISKCOMP, DISKCOPY, FORMAT, GRAFTABL, KEYB, REPLACE, RESTORE, and XCOPY. Many other programs generate exit codes, however. For example, table one contains codes that are generated by the DISKCOPY command. Table one: DISKCOPY codes Code Description 0 The operation was successful. 1 A read/write error occurred that did not terminate the disk copy operation.
  • Tectips: Hidden FDISK(32) Options

    Tectips: Hidden FDISK(32) Options

    WHITE PAPER TecTips: Hidden FDISK(32) Options Guide Previously Undocumented Options of the FDISK Utility Released Under Microsoft Windows95™ OSR2 or Later Abstract 2 Document Conventions 2 Read This First 3 Best-Case Scenario 3 Windows Startup Disk 3 How to apply these options 3 FDISK(32) Options 4 Informational Options 4 Behavioral Options 5 Functional Options 6 February, 2000 Content ©1999 StorageSoft Corporation, all rights reserved Authored by Doug Hassell, In-house Technical Writer StorageSoft White Paper page 2 FDISK(32) Command Line Options Abstract Anyone that remembers setting-up Windows 3.x or the first Win95 release surely knows of the text-based utility, fdisk.exe. Some of those may even be aware of the few, documented switches, such as /status, /x or even the commonly referenced /mbr. Even fewer would be aware of the large table of undocumented command-line options - including automated creation, reboot behavior, and other modifiers - which we will divulge in this document. Note that all options given here are not fully tested, nor are they guaranteed to work in all scenarios, all commands referenced apply to the contemporary release of Win95 (OSR2 - version “B” - or later, including Win98 and the up-and-coming Millennium™ edition). For our recommendation on how to use these swtiches, please refer to the “Read This First” section. Document Conventions In this document are certain references that deserve special recognition. This is done through special text- formatting conventions, described here… v Words and phrases of particular importance will stand-out. Each occurrence of this style will generally indicate a critical condition or pitfall that deserves specific attention.