DOCSLIB.ORG

Undocumented DOS Second Edition a Programmer's Guide to Reserved MS-DOS® Functions and Data Structures

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Undocumented DOS Second Edition a Programmer's Guide to Reserved MS-DOS® Functions and Data Structures \ Undocumented DOS Second Edition A Programmer's Guide to Reserved MS-DOS® Functions and Data Structures Andrew Schulman, Ralf Brown, David Maxey, Raymond J. Michels, and Jim Kyle A . •• Addison-Wesley Publishing Company Reading, Massachusetts Menlo Park, California New York Don Mills, Ontario Wokingham, England Amsterdam Bonn Sydney Singapore Tokyo Madrid San Juan Paris Seoul Milan Mexico City Taipei CONTENTS CHAPTER 1 — Undocumented DOS: The Madness Continues 1 "Cruel Coding" and Tying Arrangements 3 Windows and DR DOS 5 Systems Rivalry and Smoking Guns 6 The Windows AARD Detection Code 7 A Gauntlet of Tests 9 A Gratuitous Gatekeeper 1 3 Does Beta Gode Really Matter? 15 So What? 16 Microsoft's Response 16 Documentation vs. Tying 1 7 Microsoft Windows Uses Undocumented DOS 18 WIN.COM Walks the SFT 20 BlockDevand INT2Fh Function 13h 21 DOSMGR: Windows' Connection to Undocumented DOS 21 CON CON CON CON CON 24 The Undocumented DOSMGR Callout API.:•...: 24 Implementing DOSMGR Functions 30 Patching DOS 32 DOS Knows About Windows 34 DOSMGR and the SDA 35 DOSMGR and the InDOS Flag 35 SYSTEM.INI Settings and Undocumented DOS 36 KRNL386 Grows the SFT 37 - KRNL386 and the PSP 37 Undocumented DOS and the Utilities Wars 38 Undocumented SmartDrive .-. 39 Undocumented DoubleSpace ?.. 40 UndocumentedEMM386.EXE 42 Microsoft Anti-Virus 43 No Problem? '. 45 DOS Documented 48 Why Leave Functionality Undocumented? 50 Documentation and Monopoly 52 Fear of Undocumented DOS 54 Ain't Misbehavin' 55 CHAPTER 2 — Programming for Documented and Undocumented DOS: A Comparison 59 Using Documented DOS Functions 60 DOS Calls from Assembly Language 61 III iv UNDOCUMENTED DOS, Second Edition CHAPTER 2 (continued) DOS Calls from C 62 int86() 62 Inline Assembler 63 Register Pseudo-Variables 64 DOS Library Functions 65 DOS Calls from Turbo Pascal 65 DOS Calls from BASIC 66 Using Undocumented DOS 67 Disassembling DOS 68 Using the Interrupt List 70 No Magic Numbers 70 Undocumented DOS Calls from Assembly Language 72 DOS Versionitis 74 Accessing SysVars 75 Undocumented DOS Calls from C 76 What, No Structures? 78 Undocumented DOS Calls from Turbo Pascal 82 Undocumented DOS Calls from BASIC 84 When Not To Use Undocumented Features 85 Verifying Undocumented DOS 86 Making Modifications 87 An Important Special Case: Novell NetWare 93 Hooking DOS: Application Wrappers 95 On to Protected Mode 99 CHAPTER 3 — Undocumented DOS Meets Windows 101 Calling Undocumented DOS from Windows 103 It Doesn't Really Work! 108 The Dreaded GP Fault 110 A DPMI Shell 11 3 Trying Out Undocumented DOS from DPMISH Programs 11 7 The Windows DOS Extenders 119 Inside the DOSMGR DOS Extender 122 How DOSMGR Handles Undocumented DOS Calls / 126 Do Your Own XLAT .'. 128 DPMI Programming 128 Hiding DPMI .- 131 Fixing SFTWALK ; 138 Inside the DPMI Server in VMM 141 Back to Windows Programming 143 Windows and the SFT 143 Walking the Device Chain 144 Truename 148 Windows and the PSP 151 Peeking at DOS Boxes from a Windows Program 155 A Brief Introduction to VxD Programming 173 Timing DOS Calls 176 Contents v CHAPTER 4 — Other DOSs: From DR DOS and NetWare to MVDMs in OS/2 and Windows NT 179 From CP/M to DR DOS to Novell DOS 181 The DR DOS Version Number 184 Undocumented Novell DOS 185 Watching DR DOS 189 Disassembling DR DOS 189 How Close Is DR DOS to MS-DOS? 190 SysVars, the Current Directory Structure, and the Redirector 191 The System File Tables and SHARE 192 Memory Control Blocks 192 TSRs and the Swappable Data Area 194 Additional DR DOS and Novell DOS Functionality 194 Novell NetWare 195 NETXandlNT21h 196 NetWare 4.0 and the Network Redirector 197 How NETX Changes INT 21 h 198 Undocumented NetWare 204 OS/2 2.x: "A Better DOS Than DOS"? 205 MVDMs and VDDs 207 So What Version of DOS Is This DOS Emulation Pretending To Be?. 208 Loading a Genuine DOS 210 OS/2 2.x and Undocumented DOS 211 New OS/2 Services for Old DOS Programs 213 DOS Emulation Under Windows NT 216 The Client/Server Model 217 NTVDM, NTIO, and NTDOS 218 Magic Pills and Bops 219 WhatisNTVDM.EXE? 220 DOS 5.50 222 Additional NTDOS Functionality 224 Undocumented NT 225 CHAPTER 5 — INTRSPY: A Program for Exploring DOS 229 Why a Script-Driven, Event-Driven Debugger? .- 229 A Guided Tour. L 230 Device Drivers 234 Watching XMS „ 237 Dynamic Hooks !". 238 INTRSPY User's Guide 241 UsinglNTRSPY.EXE 241 UsingCMDSPY.EXE 241 Script Language 241 Syntax 242 INCLUDE Syntax 242 STRUCTURE Syntax 242 INTERCEPT Syntax 243 GENERATE Syntax 245 RUN Syntax 245 REPORT, STOP and RESTART Syntax 246 Vi UNDOCUMENTED DOS, Second Edition CHAPTER 5 (continued) DEBUG Syntax 246 Predefined Constants 247 Error Messages 247 GMDSPY Compilation Messages 247 CMDSPY and INTRSPY In Operation 248 INTRSPY Utility Scripts 248 UNDOC 248 LSTOFLST 251 Log Your Machine's Activity 253 Monitoring Disk I/O 254 MEM 258 Writing a Generic Interrupt Handler 258 The Problem with Intel's INT 260 Changed Implementation in INTRSPY 2.0 261 Implementation 261 Pitfalls I Fell In 262 The Future of INTRSPY 263 CHAPTER 6 — Disassembling DOS 265 What is MS-DOS? 266 Disassembling IO.SYS and MSDOS.SYS s. 267 Interrupt Vectors and Chaining 271 Tracing a DOS INT 21 h Call 280 Unassembling the Get/Set PSP Functions 287 Unassembling INT 21 h AH=33h 288 Examining the Low-Memory Stub for DOS=HIGH 289 Examining the INT 21 h Dispatch Function 291 Examining the INT 21 h Dispatch Table 297 Get SysVars and the Caller's Registers 299 A Very Brief Glance at File I/O 301 Tracing a DOS INT 2Fh Call 301 How Does DEBUG Trace Through an INT? 301 INTCHAIN 302 Examining The INT 2Fh Chain /. 306 The MSDOS.SYS and IO.SYS INT 2Fh Handlers 308 Examining the MSDOS.SYS Handler for INT 2Fh AH=12h 309 Locating the INT 2Fh AH=12h Dispatch Table 310 Really Disassembling DOS :. 313 Using NICEDBG 315 Examining a Few DOS Functions 324 Examining the DOS Lseek Function 326 Other Parts of DOS 332 Am I Going to Jail for This? 333 Use the Source, Luke! 336 Microsoft's DOS OEM Adaptation Kit (OAK) 340 CHAPTER 7 — MS-DOS Resource Management: Memory, Processes, Devices 343 Memory Management 343 Memory Control Blocks 344 The HMA and UMBs 346 Contents vii CHAPTER 7 (continued) Making Use of UMBs., 347 The High Memory Area 349 How To Find the Start of the MCB Chain 350 How To Trace the MCB Chain 351 MCB Consistency Checks 354 A More Detailed UDMEM Program 356 Allocation Precautions 364 RAM Allocation Strategies 365 First-fit Strategy 366 Best-fit Strategy 366 Last-fit Strategy 366 Process Management 367 Program Files and Processes 367 The COM File Format 367 The EXE File Format 367 The PSP: How It Identifies a Process 368 History, Purpose, and Use 369 (Usually) Unique Process Identifier 369 Undocumented Areas of the PSP '. 370 DOS Termination Address 371 Other PSP Fields 372 Spawning Child Processes 373 Locating Parent Processes 373 Locating Ancestors 373 Use of this Capability 373 Device Management 374 Why Device Drivers Exist...., 374 Hardware-Dependent Details 375 Logically Required Functions 375 Congruence of Files and Devices 375 Tracing the Driver Chain 376 Organization of the Device Driver Chain 377 How Drivers Are Initialized ..377 Locating the Start of the Chain {. 378 Tracing It Through 378 Loading Device Drivers from the DOS Command Line 381 How DEVLOD Works f. 382 DEVLOD.C '.. 385 MOVUP.ASM 394 TESTNAME.ASM 395 CO.ASM 396 Make File 396 How Well Does DEVLOD Work? 397 CHAPTER 8 — The DOS File System and Network Redirector 401 A Quick Overview of the System 402 The DOS File System 407 Surfaces, Tracks, and Sectors 407 Partition and Boot Records 408 viii UNDOCUMENTED DOS, Second Edition r | CHAPTER 8 (continued) The Boot Record and BIOS Parameter Block (BPB) 410 Logical Sector Numbers and the Cluster Concept 412 The File Allocation Table (FAT) 41 3 DOS Directory Structure 421 The Drive Parameter Block (DPB) 433 Buffers and Disk Caches 436 The Current Directory Structure (CDS) 443 Contents of the CDS 446 Walking the CDS Array 448 Detecting RAM Disks 449 DoubleSpace Drives 450 Stacker Drives 458 Novell NetWare Drives : 461 Manufacturing and Removing Drive Letters '. 462 System File Tables (SFTs) and ]ob File Table (]FT) 465 How Many FILES? 469 Filename From Handle 472 What Files Are Now Open? 475 Releasing Orphaned File Handles 482 More File Handles 485 System FCBs 489 The SHARE Hooks 490 The MS-DOS Network Redirector 494 Using the Network Redirector Interface 496 Front-End Hooks and Device Drivers vs. Back-End Redirectors 497 What DOS Provides : 498 What a Redirector Must Supply 503 Tracing an Open, Revisited 503 The Phantom 508 Phantom Implementation 509 Initializing the CDS 509 The Redirector INT 2Fh Handler 511 How Do We Know the Call Is for Us? ,: 51 3 Handling a Read 515 The Phantom XMS File System 51 7 Handling an Open 519 Handling Chdir 522 Handling Mkdir 523 Differences Between DOS Versions 525 The Network Redirector Specification 526 Using DOS Internal Functions 534 The Future of the DOS File System 539 CHAPTER 9 — Memory Resident Software: Pop-ups and Multitasking 541 TSR: It Sounds Like a Bug, But It's a Feature 542 Where Does Undocumented DOS Come In? 544 MS-DOS TSRs 547 The Generic TSR 548 Contents ; jx CHAPTER 9 (continued) TSR Programming in Microsoft and Borland C/C++ 550 Keeping a C Program Resident 553 Not Going Resident.... 555 Jiggling the Stack 556 DOS Functions for TSRs 558 MS-DOS Flags 558 Get/Set PSP 560 • Extended Error Information 561 Extended Break Information 563 Interrupt 28h 564 Inside the Generic TSR 565 TSR Command Line Arguments 583 Writing TSRs with the DOS Swappable Data Area 584 TSRs and Task Managers 592 Removing a TSR 601 Sample TSR Programs 604 TSRFILE 604 TSRMEM 605 TSR2E 607 Multitasking TSR 609 Task Switching 610 MULTI Installation 610 Timer Interrupt 610 Idle Interrupt ..611 Keyboard Interrupt 611 Printing .'.
Load more

Recommended publications
  • Optimizing and Protecting Hard Drives ‐ Chapter # 9
    Optimizing and Protecting Hard Drives ‐ Chapter # 9 Amy Hissom Key Terms antivirus (AV) software — Utility programs that prevent infection or scan a system to detect and remove viruses. McAfee Associates’ VirusScan and Norton AntiVirus are two popular AV packages. backup — An extra copy of a file, used in the event that the original becomes damaged or destroyed. boot sector virus — An infectious program that can replace the boot program with a modified, infected version of the boot command utilities, often causing boot and data retrieval problems. buffer — A temporary memory area where data is kept before being written to a hard drive or sent to a printer, thus reducing the number of writes to the devices. chain — A group of clusters used to hold a single file. child, parent, grandparent backup method — A plan for backing up and reusing tapes or removable disks by rotating them each day (child), week (parent), and month (grandparent). cross-linked clusters — Errors caused when more than one file points to a cluster, and the files appear to share the same disk space, according to the file allocation table. defragment — To “optimize” or rewrite a file to a disk in one contiguous chain of clusters, thus speeding up data retrieval. differential backup — Backup method that backs up only files that have changed or have been created since the last full backup. When recovering data, only two backups are needed: the full backup and the last differential backup. disk cache — A method whereby recently retrieved data and adjacent data are read into memory in advance, anticipating the next CPU request.
    [Show full text]
  • 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]
  • SUCCESS STORY. Security Software Porting from Netware to Novell Linux
    SUCCESS STORY. >_ >_ Security Software Porting From Netware To Novell >_ Linux About the The Client is a leader in the development of real-time monitoring, auditing and computer forensics Client technologies for Windows and Novell networks. Its ⧄agship product is used to secure the assets of the world’s largest corporations, banks, and government agencies, educational and healthcare institutions. Business The Client had a signi⣴cant install base for its ⧄agship software on Novell Netware OS. Novell’s Challenge adoption of Linux as the migration path for Netware OS created both an opportunity and a challenge for the Client. To continue supporting its Netware user base through Linux migration, the client wanted to port its monitoring and auditing solution to support SUSE Linux, Novell eDirectory and NSS (Novell Storage Services). The Client did not have in-house Linux Systems programming expertise, especially with ⣴le systems & security knowledge and approached Silicus. Silicus The software had two parts – the agent (client) and the server. The agent was a module that was Solution installed on the PC’s to be audited, and sends information on PC activities to a server installed at a centralized location. Termination of Netware required the agent to be re-developed/ported to Linux. Silicus commenced a feasibility study to address a few unknowns in the project: • Identify the auditing modules available on SuSE Linux • XML libraries that could be used • Multi-threading architecture to be used for agent development Silicus created a software architecture and design for the remote management agent. The agent was developed leveraging 3rd party tools to perform the auditing, monitoring of the Linux systems and communication with the remote server.
    [Show full text]
  • Installation and Performance
    Installation and Performance Welcome Thank you for purchasing Visual Reality software. Visual Reality is designed to offer an easy but extremely powerful, three dimensional environment in which full color still images and 3D animations can be created. Visual Reality 2.0 includes: Renderize Live. Load 2D and 3D models from a variety of drawing and modeling programs or drag and drop from Visual Model and Visual Font and compose unique scenes in an intuitive 3D environment using a wide variety of material, lighting and camera effects. Load bitmap images from a variety of common file formats for backgrounds in scenes and as color, bump or reflection maps in material definitions. Render your compositions as full-color photorealistic images at any resolution. Animate just about anything with just a few button clicks. Objects, camera views, color intensity and location of lights and the bump height of materials can all be set in motion or transformed. Rotoscoping allows you to create moving water and flickering fire. Bend, twist, stretch and morph objects over time. An advanced channel editor gives you precise time line control of every attribute, for every element or object. The 'Ease to' and 'Ease from' functions and hierarchical linking of objects give your animations a natural feel with smooth, fully controllable motion. Visual Font. Load Windows TrueType fonts and create 3D text objects by defining extrusion and bevel properties. Load extruded text into Renderize Live for inclusion in 3D scenes. Visual Image. Load and modify bitmap images from a wide variety of file formats. Work on individual images, or use the powerful layering tools to create digital collages.
    [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]
  • Novell Management Tools
    04 0789729849_ch03.qxd 11/10/03 12:43 PM Page 91 CHAPTER 3 Novell Management Tools Using ConsoleOne ConsoleOne is a Java-based tool for managing your network and its resources. It can be launched by running CONSOLEONE.EXE from where it was installed (default: SYS:PUBLIC\MGMT\CONSOLEONE\1.2\BIN). By default, it lets you manage Novell eDirectory objects, schema, parti- tions, and replicas and NetWare server resources. If you install other Novell products, the appropriate management capabil- ities are automatically snapped into the version of ConsoleOne installed on that server. ConsoleOne is installed during the NetWare 6.5 installation, but can also be re-installed or installed locally from the Novell client’s CD. ConsoleOne also supports remote server console access through a Java applet called RConsoleJ. To access the NetWare 6.5 server console remotely, launch ConsoleOne and browse to the desired server. Select Tools, and then Remote Console. Accessing Web Manager Web Manager is a Web-based “home page” for accessing most of the NetWare 6.5 Web-based tools and services. To access Web Manager, open your Web browser and enter your Web server’s domain name or IP address, followed by a colon and the Web Manager port, which by default is 2200. For example: 04 0789729849_ch03.qxd 11/10/03 12:43 PM Page 92 92 PART I Getting Started https://www.quills.com:2200 or https://137.65.192.1:2200 Accessing iManager iManager provides role-based management of your NetWare network, together with a nearly comprehensive set of administrative tools.
    [Show full text]
  • Novell Cluster Services,. for Linux. and Netware
    Novell Cluster Services,. for Linux. and NetWare. ROB BASTIAANSEN SANDER VAN VUGT Novell PRESS. Novell. Published by Pearson Education, Inc. 800 East 96th Street, Indianapolis, Indiana 46240 USA Table of Contents Introduction 1 CHAPTER 1: Introduction to Clustering and High Availability 5 Novell Cluster Services Defined 5 Shared Disk Access 6 Secondary IP Addresses 7 Clustering Terminology 8 High-Availability Solutions Overview 12 Novell Cluster Services 12 Business Continuity Clustering 13 PolyServe Matrix Server 15 Heartbeat Subsystem for High-Availability Linux 16 When Not to Cluster Applications 16 Availability Defined 18 High Availability Defined 18 Calculating Average Downtime 21 Avoiding Downtime 22 Hardware 22 Environment 23 Software 23 Procedures 24 Novell Cluster Services Requirements 24 Hardware Requirements 24 Software Requirements 26 CHAPTER 2: Examining Novell Cluster Services Architecture 27 Novell Cluster Services Objects and Modules 27 Cluster eDirectory Objects 28 Cluster Modules 31 IH Novell Cluster Services for Linux and NetWare Heartbeats, Epoch Numbers, and the Split Brain Detector 35 Removing a Failing Slave Node 36 Removing a Failed Master Node 37 Summary 37 CHAPTER 3: Clustering Design 39 Cluster Design Guidelines 39 How Many Nodes to Choose 39 Using a Heartbeat LAN or Not 40 Use NIC Teaming 41 Choosing Storage Methods 42 Mirror the Split Brain Detector Partition 48 Selecting Applications to Run in a Cluster 48 eDirectory Cluster Guidelines 50 Creating a Failover Matrix 52 Application-Specific Design Guidelines
    [Show full text]
  • Install Guide
    THIS BOX CONTAINS: • (1) CD (your game!) • Install Guide (16 pp.) with quick installation instructions, directions for creating a floppy boot disk, configurations for a variety of memory management systems and Troubleshooting answers to possible problems. • Playguide (24 pp.) covering movement, fighting, interaction and so on. • Reference Card lists keyboard commands for a single-glance reminder. • Top Line — news brief, courtesy of the World Economic Consortium. • Anti-Terrorist Site Security — guide to keeping your WEC installation safe from armored, gun-toting turncoats and other menaces, annotated by General Maxis. • Resistance Handbook — written briefing for new rebel recruits. • Registration Card — please tell us who you are! CRUSADER: NO REMORSE ™ INSTALL GUIDE Welcome to Crusader: No Remorse. This guide includes quick installation instructions for users more familiar with the process, and a detailed, step-by- step guide to installing the game. If you experience any difficulty, consult Troubleshooting (page 9). To avoid compatibility or memory problems, please take a moment to confirm that your machine matches the System Require- ments described on page 2. Remember, you may safely stop at any time during installation and return to DOS with q, except when files are being copied. QUICK INSTALLATION Note: If you are running a disk cache such as SMARTDrive, you need to disable it to ensure a clean installation. (This only affects the installation of the game. SMARTDrive will work normally during gameplay.) Refer to your SMARTDrive documentation or make a system boot disk as described in Boot Disks (page 4) to disable this cache. 1. Turn on your computer and wait for the DOS prompt.
    [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]
  • Wavetek 488RT Manual
    Full-service, independent repair center -~ ARTISAN® with experienced engineers and technicians on staff. TECHNOLOGY GROUP ~I We buy your excess, underutilized, and idle equipment along with credit for buybacks and trade-ins. Custom engineering Your definitive source so your equipment works exactly as you specify. for quality pre-owned • Critical and expedited services • Leasing / Rentals/ Demos equipment. • In stock/ Ready-to-ship • !TAR-certified secure asset solutions Expert team I Trust guarantee I 100% satisfaction Artisan Technology Group (217) 352-9330 | [email protected] | artisantg.com All trademarks, brand names, and brands appearing herein are the property o f their respective owners. Find the Rockwell / Allen-Bradley 1784-T45 at our website: Click HERE WAVETEK WaveTese Runtime 488-RT WAVETE ST SOFTyARE PREFACE WaveTest Runtime (488-R1) enables you to run already developed and debugged automatic test programs. Clear. easy-to -use screens with pull-down menus guide you through program execu- tion. Programs developed with WaveTest (488) can be loaded and exe- cuted. The operator will have available all of the operator dialogs and runtime output that have been included in the test program. There are no editing capabilities. Chapter 1. Configuring Chapter 1 tells you how to setup WaveTest Runtime. This in- cludes ways to automatically load and run a test program. Chap- ter 1 also has useful information regarding how to effectively use the runtime environment of Windows. Chapter 2. Reference Chapter 2 describes the windows and menus available for access- ing test programs and controlloing their execution. Chapter 2 is not meant to be read through, but rather referred to for help with questions as they arise.
    [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]
  • Computing :: Operatingsystems :: DOS Beyond 640K 2Nd
    DOS® Beyond 640K 2nd Edition DOS® Beyond 640K 2nd Edition James S. Forney Windcrest®/McGraw-Hill SECOND EDITION FIRST PRINTING © 1992 by James S. Forney. First Edition © 1989 by James S. Forney. Published by Windcrest Books, an imprint of TAB Books. TAB Books is a division of McGraw-Hill, Inc. The name "Windcrest" is a registered trademark of TAB Books. Printed in the United States of America. All rights reserved. The publisher takes no responsibility for the use of any of the materials or methods described in this book, nor for the products thereof. Library of Congress Cataloging-in-Publication Data Forney, James. DOS beyond 640K / by James S. Forney. - 2nd ed. p. cm. Rev. ed. of: MS-DOS beyond 640K. Includes index. ISBN 0-8306-9717-9 ISBN 0-8306-3744-3 (pbk.) 1. Operating systems (Computers) 2. MS-DOS (Computer file) 3. PC -DOS (Computer file) 4. Random access memory. I. Forney, James. MS-DOS beyond 640K. II. Title. QA76.76.063F644 1991 0058.4'3--dc20 91-24629 CIP TAB Books offers software for sale. For information and a catalog, please contact TAB Software Department, Blue Ridge Summit, PA 17294-0850. Acquisitions Editor: Stephen Moore Production: Katherine G. Brown Book Design: Jaclyn J. Boone Cover: Sandra Blair Design, Harrisburg, PA WTl To Sheila Contents Preface Xlll Acknowledgments xv Introduction xvii Chapter 1. The unexpanded system 1 Physical limits of the system 2 The physical machine 5 Life beyond 640K 7 The operating system 10 Evolution: a two-way street 12 What else is in there? 13 Out of hiding 13 Chapter 2.
    [Show full text]