Disk Operating System

Total Page:16

File Type:pdf, Size:1020Kb

Disk Operating System - -------- ---- --- Personal Computer -------_.---- - - --- Computer Language Series Disk Operating System Second Edition (May 1982) Version 1.10 Changes are periodically made to the information herein; these changes will be incorporated in new editions of this publication. Products are not stocked at the address below. Requests for copies of this product and for technical information about the system should be made to your authorized IBM Personal Computer Dealer. A Product Comment Form is provided at the back of this publication. If this form has been removed, address comment to: IBM Corp., Personal Computer, P.O. Box 1328-C, Boca Raton, Florida 33432. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligations whatever. © Copyright International Business Machines Corporation 1981 Preface This reference manual explains how to use the IBM Personal Computer Disk Operating System (DOS). It provides information on how to issue commands to DOS to create, edit, link, debug, and execute programs. Prerequisite Publication Regardless of your background or previous programming experience, you should look at the Guide to Operations before reading this manual. The chapter on "Using DOS" should be especially helpful to you before you approach the more detailed information that appears in this manual. Organization of this manual This manual has six chapters and six appendixes. Chapter I has some introductory information about DOS and files. Chapter 2 contains information about starting DOS, as well as directions on how to use the control keys and DOS editing keys. Chapter 3 contains detailed descriptions of the commands you can issue to DOS. These commands enable you to manage files, maintain diskettes, and create and execute programs. Chapter4 describes how to use the Line Editor (EDLIN) program to create , alter, and display source language files and text files. Chapter 5 describes how to use the linker (LINK) program to link programs together before execution. Chapter 6 describes how the DEBUG program provides a controlled test environment so you can monitor and . cnntrol the execution of a program to be debugged; by altering, displaying., and.executing6bject files. iii Appendix A lists messages generated by the programs described in this manual. Appendix B contains general technical information, and introduces the technical information in Appendixes C-E. Appendix C describes allocation of space on diskettes. Appendix D describes the system interrupts and fun cti on calls. Appendix E describes control blocks and work areas, including a Memory Map, Program Segment, and File Control Block. Appendix F contains detailed information about .EXE file structure and loading. Data Security The IBM Personal Computer is a powerful and useful tool to help you with your personal and business information processing needs. (As with any information system, inadvertent errors may occur and information may be misused.) We suggest that when processing sensitive or highly valuable information, you take steps to ensure your data and programs are protected from accidental or unauthorized disclosure, modification, destruction, or misuse. Simple measures, such as: removing diskettes when not in use, keeping backup copies of valuable information, or installing the equipment in a secure facility, can go a long way to maintain the integrity and privacy of your information. iv Summary of Changes This manual includes the following DOS Release 1.10 enhancemen ts: • Revisions to the linker (LINK) program (Chapter 5). • Support for an intermix of single sided and dual sided diskette drives (Chapter 2 and wherever applicable in Chapter 3 and Appendixes B and C). Commands of special interest include: - FORMAT - DISKCOMP - DISKCOPY • DEBUG can now load files longer than 64K and includes a command to com pare two blocks of memory (Chapter 6). • A new command, EXE2BIN, converts .EXE files to .COM format programs (Chapter 3). • The MODE command now includes the capability to set the speed and protocol for the Asynchronous Communications Adapter, as well as redirecting parallel printer output to an Asynchronous Communications Adapter (Chapter 3). • Several new messages have been added (Appendix A), as well as new prompts or screens for: - DATE - TIME - FORMAT - CHKDSK - ERASE v • Tables of values for single sided and dual sided diskette maps are included (Appendix C). • The COpy command provides support for concatenation (that is, combining) of files (Chapter 3). • Directory entries include the time, as well as the date, when each file was last written to (Chapter 3). CAUTION The DOS 1.10 commands should never be executed when you are running DOS 1.00, and the DOS 1.00 commands should never be executed under DOS 1.10. Because of the internal changes required for DOS 1.10, any attempt to run Level 1.00 commands on a 1.10 system (or vice versa) may result in the loss of data. vi CONTENTS Preface ............. iii Prerequisite Publication . iii Organization of this manual iii Data Security . iv Summary of Changes . v CHAPTER 1. INTRODUCTION 1-1 What is DOS? . 1-3 What Are the Parts of DOS? . 1-3 A Few Words about Files . 1-5 What Is a File? . 1-5 What Can I Name My Files? 1-5 How Many Files Can I Have? 1-6 How Does DOS Keep Track of My Files? . 1-6 Why Is This Information Important to Me? 1-6 Formatting Your Diskettes ........ 1-7 Why You Should Back Up Your Diskettes 1-7 CHAPTER 2. STARTING DOS . 2-1 How to Start DOS ......... 2-3 If Your Computer Power Is Off 2-3 If Your Computer Power Is Already On 2-4 What Happens When You Start DOS? 2-4 How to Enter the Date and Time . 2-5 Specifying the Defaul t Drive . 2-6 Automatic Program Execution . 2-7 Important Notes about Diskette and Drive Compatibility . 2-8 Single-Drive Systems ........... 2-9 Control Keys . 2-11 DOS Editing Keys ............ 2-16 Examples of Ways to Use DOS Editing Keys . 2-20 To Start EDLIN 2-20 Example 1 2-22 Example 2 2-23 Example 3 2-24 Example 4 2-25 Example 5 2-26 vii Example 6 . 2-27 Example 7 . 2-28 To Stop the Editing Session 2-30 CHAPTER 3. DOS COMMANDS 3-1 Introduction ....... 3-3 Types of DOS Commands 3-4 Format Notation . 3-5 DOS Command Parameters 3-6 Reserved Device Names 3-8 Global Filename Characters 3-9 Detailed Descriptions of the DOS Commands 3-12 Information Common to All DOS Commands . 3-1 2 Batch Processing ........... 3-14 The AUTOEXEC.BAT File ... 3-15 Creating a .BA T File With Replaceable Parameters . 3-17 Executing a .BAT File With Replaceable Parameters . 3-18 CHKDSK (Check Disk) Command 3-19 COMP (Compare Files) Command 3-21 COpy Command 3-23 DATE Command . 3-32 DEL Command . 3-34 DIR (Directory) Command 3-35 DISKCOMP (Compare Diskette) Command 3-39 DISKCOPY (Copy Diskette) Command 3-42 ERASE Command 3-45 EXE2BIN Command 3-47 FORMAT Command 3-50 MODE Command . 3-53 PAUSE Command 3-58 REM (Remark) Command 3-59 RENAME (or REN) Command 3-60 SYS (System) Command . 3-61 TIME Command ...... 3-62 TYPE Command ...... 3-64 Summary of DOS Commands 3-65 CHAPTER 4. THE LINE EDITOR (EDLIN) 4-1 Introduction ........... 4-3 How to Start the ED LIN Program 4-4 The ED LIN Command Parameters 4-6 The ED LIN Commands . 4-9 Information Common to All EDLIN Commands . 4-9 viii Append Lines Command 4-11 Delete Lines Command 4-1 2 Edit Line Command 4-16 End Edit Command . 4-18 Insert Lines Command 4-19 List Lines Command . 4-22 Quit Edit Command 4-26 Replace Text Command 4-27 Search Text Command . 4-30 Write Lines Command 4-33 Summary of EDLIN Commands 4-34 CHAPTER 5. THE LINKER (LINK) PROGRAM 5-1 Introduction 5-3 Files ...... 5-4 Input Files . 5-4 Output Files 5-4 YM.TMP (Temporary File) 5-5 Definitions . 5-6 Segment 5-6 Group . 5-7 Class . 5-7 Comlnand Prompts 5-8 Detailed Descriptions of the Comlnand Prompts . 5-10 Object Modules [.OBJ]: . 5-10 Run File [filespec.EXE] : 5-11 List File [NUL.MAP)]: 5-11 Libraries [.LIB] : 5-12 Linker Parameters . 5-13 How to Start the Linker Program 5-1 7 Before You Begin . 5-17 Option 1 - Console Responses 5-17 Option 2 - Command Line . 5-18 Option 3 - Automatic Responses 5-20 Example Linker Session ....... 5-22 Load Module Memory Map ... 5-26 How to Determine the Absolute Address of a Segment 5-27 Messages . 5-28 CHAPTER 6. THE DEBUG PROGRAM 6-1 fu troduction ........... 6-3 How to Start the DEBUG Program 6-4 The OEBUG Command Parameters 6-6 ix The DEBUG Commands ........ 6-11 Information Common to All DEBUG Commands . 6-11 Compare Command . 6-13 Dump Command . 6-14 Enter Command . 6-17 Fill Command 6-20 Go Command .. 6-21 Hexarithmetic Command 6-24 Input Command 6-25 Load Command . 6-26 Move Command 6-29 Name Command 6-30 Output Command 6-32 Quit Command . 6-33 Register Command 6-34 Search Command . 6-39 Trace Command 6-40 Un assemble Command 6-42 Write Command 6-45 Summary of DEBUG Commands 6-49 APPENDIX A. MESSAGES . A-3 APPENDIX B. DOS TECHNICAL INFORMATION B-1 DOS Structure ..... B-1 DOS Initialization . B-2 The Command Processor B-3 Replacing the Command Processor B-4 Available DOS Functions .... B-5 Diskette/File Management Notes B-6 The Disk Transfer Area (DTA) B-7 Error Trapping ........ B-7 General Guidelines ...... B-8 Example of Using DOS Functions B-9 APPENDIX C. DOS DISKETTE ALLOCATION C-l DOS Diskette Directory .......
Recommended publications
  • Windows Command Prompt Cheatsheet
    Windows Command Prompt Cheatsheet - Command line interface (as opposed to a GUI - graphical user interface) - Used to execute programs - Commands are small programs that do something useful - There are many commands already included with Windows, but we will use a few. - A filepath is where you are in the filesystem • C: is the C drive • C:\user\Documents is the Documents folder • C:\user\Documents\hello.c is a file in the Documents folder Command What it Does Usage dir Displays a list of a folder’s files dir (shows current folder) and subfolders dir myfolder cd Displays the name of the current cd filepath chdir directory or changes the current chdir filepath folder. cd .. (goes one directory up) md Creates a folder (directory) md folder-name mkdir mkdir folder-name rm Deletes a folder (directory) rm folder-name rmdir rmdir folder-name rm /s folder-name rmdir /s folder-name Note: if the folder isn’t empty, you must add the /s. copy Copies a file from one location to copy filepath-from filepath-to another move Moves file from one folder to move folder1\file.txt folder2\ another ren Changes the name of a file ren file1 file2 rename del Deletes one or more files del filename exit Exits batch script or current exit command control echo Used to display a message or to echo message turn off/on messages in batch scripts type Displays contents of a text file type myfile.txt fc Compares two files and displays fc file1 file2 the difference between them cls Clears the screen cls help Provides more details about help (lists all commands) DOS/Command Prompt help command commands Source: https://technet.microsoft.com/en-us/library/cc754340.aspx.
    [Show full text]
  • File Formats
    man pages section 4: File Formats Sun Microsystems, Inc. 4150 Network Circle Santa Clara, CA 95054 U.S.A. Part No: 817–3945–10 September 2004 Copyright 2004 Sun Microsystems, Inc. 4150 Network Circle, Santa Clara, CA 95054 U.S.A. All rights reserved. This product or document is protected by copyright and distributed under licenses restricting its use, copying, distribution, and decompilation. No part of this product or document may be reproduced in any form by any means without prior written authorization of Sun and its licensors, if any. Third-party software, including font technology, is copyrighted and licensed from Sun suppliers. Parts of the product may be derived from Berkeley BSD systems, licensed from the University of California. UNIX is a registered trademark in the U.S. and other countries, exclusively licensed through X/Open Company, Ltd. Sun, Sun Microsystems, the Sun logo, docs.sun.com, AnswerBook, AnswerBook2, and Solaris are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the U.S. and other countries. Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc. The OPEN LOOK and Sun™ Graphical User Interface was developed by Sun Microsystems, Inc. for its users and licensees. Sun acknowledges the pioneering efforts of Xerox in researching and developing the concept of visual or graphical user interfaces for the computer industry. Sun holds a non-exclusive license from Xerox to the Xerox Graphical User Interface, which license also covers Sun’s licensees who implement OPEN LOOK GUIs and otherwise comply with Sun’s written license agreements.
    [Show full text]
  • User Guide Ty Pe S 8143, 8144, 8146 Ty Pe S 8422, 8423, 8427
    ThinkCentre™ User Guide Ty pe s 8143, 8144, 8146 Ty pe s 8422, 8423, 8427 ThinkCentre™ User Guide Ty pe s 8143, 8144, 8146 Ty pe s 8422, 8423, 8427 Note Before using this information and the product it supports, be sure to read the “Important safety information” on page v and Appendix D, “Notices,” on page 43. Second Edition (June 2004) © Copyright International Business Machines Corporation 2004. All rights reserved. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Important safety information . .v Erasing a lost or forgotten password (clearing Conditions that require immediate action. .v CMOS) . .24 General safety guidelines . .vi Replacing the cover and connecting the cables. .25 Service . .vi Power cords and power adapters . .vi Chapter 2. Using the IBM Setup Utility Extension cords and related devices . vii program . .27 Plugs and outlets . vii Starting the IBM Setup Utility program . .27 Batteries . vii Viewing and changing settings . .27 Heat and product ventilation . viii Using passwords . .27 CD and DVD drive safety . viii Password considerations . .27 Additional safety information . .ix User Password . .28 Lithium battery notice . .x Administrator Password . .28 Modem safety information. .x IDE Drive User Password . .28 Laser compliance statement . .xi IDE Drive Master Password . .28 Setting, changing, and deleting a password. .29 Overview . xiii Using Security Profile by Device . .29 Information resources. xiii Selecting a startup device. .29 Selecting a temporary startup device . .30 Chapter 1. Installing options . .1 Changing the startup sequence . .30 Features . .1 Exiting from the IBM Setup Utility program . .30 Available options .
    [Show full text]
  • Introduction to MS-DOS
    1.Introduction to MS-DOS : MS-DOS (Microsoft Disk Operating System) was the Microsoft-marketed version of the first widely-installed operating system in personal computers. It was essentially the same operating system that (Bill Gates's) young company developed for IBM as Personal Computer - Disk Operating System in 1981. Most users of either DOS system simply referred to their system as Disk Operating System. Like PC-DOS, MS-DOS was (and still is) a non-graphical line-oriented command- driven operating system, with a relatively simple interface but not overly "friendly" user interface. Its prompt to enter a command looks like this: C:\> MS-DOS does not care about anything called an icon, wallpaper or screen saver. Rather than being considered as a Graphical User Interface (GUI) MS-DOS is what is known as a command-line interface. You type commands on what is called the command line. MS-DOS is a single-user, single-tasking computer operating system. In spite of its very small size and relative simplicity, it is one of the most successful operating systems that has been developed to date. In DOS, a file name consists of eight character followed by a 3 character file extension. The size of a file is restricted to a 4 byte file descriptor, which limits a file’s maximum size to approximately 4 billion characters. The first release of DOS could not read or write to disk drives so users could only read and write to a floppy disc. DOS was not a state of the art operating system, even for its time.
    [Show full text]
  • Chapter 1. Origins of Mac OS X
    1 Chapter 1. Origins of Mac OS X "Most ideas come from previous ideas." Alan Curtis Kay The Mac OS X operating system represents a rather successful coming together of paradigms, ideologies, and technologies that have often resisted each other in the past. A good example is the cordial relationship that exists between the command-line and graphical interfaces in Mac OS X. The system is a result of the trials and tribulations of Apple and NeXT, as well as their user and developer communities. Mac OS X exemplifies how a capable system can result from the direct or indirect efforts of corporations, academic and research communities, the Open Source and Free Software movements, and, of course, individuals. Apple has been around since 1976, and many accounts of its history have been told. If the story of Apple as a company is fascinating, so is the technical history of Apple's operating systems. In this chapter,[1] we will trace the history of Mac OS X, discussing several technologies whose confluence eventually led to the modern-day Apple operating system. [1] This book's accompanying web site (www.osxbook.com) provides a more detailed technical history of all of Apple's operating systems. 1 2 2 1 1.1. Apple's Quest for the[2] Operating System [2] Whereas the word "the" is used here to designate prominence and desirability, it is an interesting coincidence that "THE" was the name of a multiprogramming system described by Edsger W. Dijkstra in a 1968 paper. It was March 1988. The Macintosh had been around for four years.
    [Show full text]
  • 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.
    [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]
  • Files and Processes (Review)
    Files and Processes (review) Files and Processes (review) 1/61 Learning Objectives Files and Processes (review) I Review of files in standard C versus using system call interface for files I Review of buffering concepts I Review of process memory model I Review of bootup sequence in Linux and Microsoft Windows I Review of basic system calls under Linux: fork, exec, wait, exit, sleep, alarm, kill, signal I Review of similar basic system calls under MS Windows 2/61 Files Files and I Recall how we write a file copy program in standard C. Processes (review) #include <stdio.h> FILE *fopen(const char *path, const char *mode); size_t fread(void *ptr, size_t size, size_t nmemb, FILE *stream); size_t fwrite(const void *ptr, size_t size, size_t nmemb, FILE *stream); int fclose(FILE *fp); I We can also use character-based functions such as: #include <stdio.h> int fgetc(FILE *stream); int fputc(int c, FILE *stream); I With either approach, we can write a C program that will work on any operating system as it is in standard C. 3/61 Standard C File Copy Files and Processes (review) I Uses fread and fwrite. I files-processes/stdc-mycp.c 4/61 POSIX/Unix Files Files and Processes (review) I "On a UNIX system, everything is a file; if something is not a file, it is a process." I A directory is just a file containing names of other files. I Programs, services, texts, images, and so forth, are all files. I Input and output devices, and generally all devices, are considered to be files.
    [Show full text]
  • The Application of File Identification, Validation, and Characterization Tools in Digital Curation
    THE APPLICATION OF FILE IDENTIFICATION, VALIDATION, AND CHARACTERIZATION TOOLS IN DIGITAL CURATION BY KEVIN MICHAEL FORD THESIS Submitted in partial fulfillment of the requirements for the degree of Master of Science in Library and Information Science in the Graduate College of the University of Illinois at Urbana-Champaign, 2011 Urbana, Illinois Advisers: Research Assistant Professor Melissa Cragin Assistant Professor Jerome McDonough ABSTRACT File format identification, characterization, and validation are considered essential processes for digital preservation and, by extension, long-term data curation. These actions are performed on data objects by humans or computers, in an attempt to identify the type of a given file, derive characterizing information that is specific to the file, and validate that the given file conforms to its type specification. The present research reviews the literature surrounding these digital preservation activities, including their theoretical basis and the publications that accompanied the formal release of tools and services designed in response to their theoretical foundation. It also reports the results from extensive tests designed to evaluate the coverage of some of the software tools developed to perform file format identification, characterization, and validation actions. Tests of these tools demonstrate that more work is needed – particularly in terms of scalable solutions – to address the expanse of digital data to be preserved and curated. The breadth of file types these tools are anticipated to handle is so great as to call into question whether a scalable solution is feasible, and, more broadly, whether such efforts will offer a meaningful return on investment. Also, these tools, which serve to provide a type of baseline reading of a file in a repository, can be easily tricked.
    [Show full text]
  • And PC 750 (Type 6887)
    Technical Information Manual PC 730 (Type 6877) and PC 750 (Type 6887) Technical Information Manual IBM PC 730 (Type 6877) and PC 750 (Type 6887) Note Before using this information and the product it supports, be sure to read the general information under Appendix B, “Notices and Trademarks” on page 65. First Edition (June 1996) The following paragraph does not apply to the United Kingdom or any country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE 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. This 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. Requests for technical information about IBM products should be made to your IBM reseller or IBM marketing representative. IBM may have patents or pending patent applications covering subject matter in this document.
    [Show full text]
  • MS-DOS Lecture
    MS-DOS 2017 University of Babylon College of Engineering Electrical Department Learning Basics of MS-DOS Assis. Lec. Abeer Abd Alhameed | 1 MS-DOS 2017 Outcomes: By the end of this lecture, students are able to: Define the MS-DOS system Log in MS-DOS commands system Display MS-DOS information on your computer Type basic commands of MS-DOS system (view directory contents, change directory, make directory) Assis. Lec. Abeer Abd Alhameed | 2 MS-DOS 2017 Learning of MS-DOS Basics: Definition - What does Microsoft Disk Operating System (MS- DOS) mean? The Microsoft Disk Operating System (MS-DOS) is an operating system developed for PCs (personal computers) with x86 microprocessors. It was the first widely-installed operating system in personal computers. It is a command-line-based system, where all commands are entered in text form and there is no graphical user interface. The Command Prompt: When you first turn on your computer, you will see some information flash by. MS-DOS displays this information to let you know how it is configuring your computer. You can ignore it for now. When the information stops scrolling past, you'll see the following: C:\> This is called the command prompt or DOS prompt. The flashing underscore next to the command prompt is called the cursor. The cursor shows where the command you type will appear. Typing a Command: This section explains how to type a command at the command prompt and demonstrates the "Bad command or file name" message. • To type a command at the command prompt 1. Type the following at the command prompt (you can type the command in either uppercase or lowercase letters): nul If you make a typing mistake, press the BACKSPACE key to erase the mistake, and then try again.
    [Show full text]
  • Befehlsverzeichnis Zu MS-DOS 3.3 Ansi.Sys Assign Attrib Autoexec.Bat
    117 Befehlsverzeichnis zu MS-DOS 3.3 Beschreibung der Befehle (bis Version 3.3 einschlieBlich.) in drei Punkten: J) Be/ehlswort: Befehlszweck, Befehlsart (interner oder externer Befehl). 2) Allgemeilles Format: Klammerangaben wahlfrei, ( .. ) fOr beliebig wiederholbaren Begriff, / fOr entweder-oder, d: fOr Laufwerksangabe. 3) Beispiele: mit Befehlsaufrufen zu typischen Anwendungen. append (ab DOS 3.3) Auf Dateien zugreifen (extern) append d:Pfad (;( d:)Pfad ... ) append (/ x)( I e) ansi.sys Tastatur-Treiber (fur device) device=ansi.sys assign Zugriff umleiten (extern) assign (x( = )y( .. )) attrib Dateianderungsattribut (extern) attrib (+r / -r)(+a/ -a) (d:)(Pfad)(Dateiname(.erw) (/ s) autoexec.bat Spezielle Stapeldatei backup Daten von Platte sichern (extern) backup d:(Pfad)(Dateiname(.erw)) d:(s)( / m)( / a)( / d:u.mm.jj) break Abbruch Strg-C prufen (intern) break (on/ off) buffers Pufferanzahl (fur config.sys) buffers=x cd Verzeichnis wechseln (intern) cd (d:)(Pfad) chcp (ab DOS 3.3) Zeichensatztabelle (intern) chcp (nnn) Gewahlte Zeichen8at~tabelle nnn. 118 chdir Wie cd: (intern) chkdsk Speicherstatusbericht (extern) chkdsk(d:)(Pfad)(Dateiname(.erw))( If)( Iv) f=Fehler. v=Anzeigen cis Bildschirm IOschen (intern) command Befehlsprozessor rufen (extern) command (d:)(Pfad)(/p)(/c Zeichenfolge) (/e:xxxxx) comp Dateiinhalt vergleichen (extern) comp (d:)(Pfad)(Dateiname(.erw)) (d:)(Pfad)( Dateiname(.erw)) copy Dateil Datei2 Dateien kopieren (intern) copy (d:)(Pfad)Dateiname(.erw) (d:)(Dateiname(.erw))( Iv) copy Dateil + Datei2 ... Datei Dateien zusammenfiigen (intern) copy (d:)(Pfad)Dateiname(.erw) (+( d:)(Pfad)Dateiname(.erw) ... ) (d: )(Plad)(Dateiname( .erw) )(/v) copy Eingabeeinheit Datei Eingabe von Einheit aus (intern). copy Datei Ausgabeeinheit Datei drucken (intern) country Linderanpassung (fiir config.sys) country=xxx mit xxx=049 fur Deutschland.
    [Show full text]