Inhaltsverzeichnis 5

Total Page:16

File Type:pdf, Size:1020Kb

Inhaltsverzeichnis 5 Inhaltsverzeichnis 5 Inhaltsverzeichnis Vorwort 13 Vorwort zur 2. Auflage 15 1 Einführung 17 1.1 Das Speicherabbild der 8086/8088-Prozessören 17 1.2 Die Segment:Offset-Notation 18 1.3 Die Speicheraüfteilung durch Intel 19 1.4 Die Speicherbelegung durch MS-DOS 21 1.5 Die Aufteilung des 640-Kbyte-MS-DC)S-RAM-Bereiches 23 1.6 Die MS-DOS-Interrupt-Vektor-Tabelle 24 1.7 Der BIOS-Datenbereich 30 1.8 Der DOS-Datenbereich 35 1.9 Die Funktion des Programmes IO.SYS (IBMBIO.COM) 36 1.10 Die Funktion des Programmes MSDOS.SYS (IBMDOS.COM) 39 1.11 Die Funktion des Programmes COMMAND.COM 39 2 Die BIOS-Funktionen 41 2.1 Print-Screen-Funktion (INT 5) 41 2.2 B [OS-Bildschirmausgabe (INT 10) 41 2.3 Hardwarekonfiguration (INT 11) 52 2.4 Speichergröße ermitteln (INT 12) 53 2.5 Disketten- und Festplatten-Steuerung (INT 13) 53 2.6 Serielle Schnittstelle (INT 14) 71 2.7 (INT 15) 76 2.8 Tastatur abfragen (INT 16) 88 2.9 Druckerschnittstelle (INT 17) 92 2.10 ROM-Basic (INT 18) 93 2.11 Bootstrap (INT 19) 93 2.12 Systemzeit (INT 1A) 93 2.13 Tastatur-Break (INT 1B) 96 2.14 Timer-Interrupt (INT IC) 96 http://d-nb.info/900868430 6 Inhaltsverzeichnis 2.15 Bildschirm-Initialisierung (INT 1D) 96 2.16 Disk-Parameter (INT IE) 97 2.17 Grafik-Tabelle (INT 1F) 98 3 Die MS-DOS-Interrupts 99 3.1 Program Terminate (INT 20) 101 3.2 MS-DOS-Funktionsdispatcher (INT 21) 101 3.3 Terminate Process Exit Address (INT 22) 102 3.4 Control-C Exit Handler Address (INT 23) 102 3.5 Critical Error Handler Address (INT 24) 103 3.6 Absolute Disk Read (INT 25) 108 . • 3.7 Absolute Disk Write (INT 26) 112 3.8 Terminate But Stay Resident (INT 27) 114 3.9 Start a Resident Process (INT 28 undokumentiert) 115 3.10 Screen Output (INT 29 undokumentiert) 116 3.11 Microsoft Netzwerk-Session Layer Interrupt (INT 2A undok.) 117 3.12 Start a Child Process (INT 2E undokumentiert) 119 3.13 Multiplexer-Interrupt (INT 2F undokumentiert) 120 3.14 Der Maus-Treiber-Interrupt (INT 33) 147 3.15 INT 34 bis INT 3E 159 3.16 Overlay Manager (INT 3FH) 159 3.17 Disktreiber (INT 40) 160 3.18 Parametertabelle Festplatte (INT 41, INT 42) 160 3.19 EGA-Videostatus (INT 42) 161 3.20 EGA-Grafikzeichensatz (INT 43) 161 3.21 EGA-Interrupt (INT 44) 161 3.22 Timer-Alarm (INT 4A, INT 50) 161 3.23 GSS Computer Graphic Interface (INT 59H) 162 3.24 NETBIOS Interface (INT 5CH) 162 3.25 PC/TCP Packet Driver (INT 60H) 162 3.26 EMS-Treiber (INT 67H) 162 3.27 DOS 3.2 Realtime Clock Update (INT 6CH) 162 3.28 VGA-Interrupt (INT 6DH) 163 3.29 HP ES-12 Extended BIOS (INT 6FH) 163 4 Die MS-DOS-Funktionen (INT 21) 164 4.1 Terminate Program (Funktion 00H, DOS 2.0-4.x) 169 4.2 Read Keyboard and Echo (Funktion 01H, DOS 2.0-4.x) 169 4.3 Display Character (Funktion 02H, DOS 2.0-4.x) 170 4.4 Auxiliary Input (Funktion 03H, DOS 2.0-4.x) 170 4.5 Auxiliary Output (Funktion 04H, DOS 2.0-4.x) 171 4.6 Print Character (Funktion 05H, DOS 2.0-4.X) 171 4.7 Direct Console I/O (Funktion 06H, DOS 2.0-4.x) 171 Inhaltsverzeichnis 7 4.8 Direct Console Input (Funktion 07H, DOS 2.0-4.x) 172 4.9 Read Keyboard (Funktion 08H, DOS 2.0-4.x) 172 4.10 Display String (Funktion 09H, DOS 2.0-4.x) 172 4.11 Buffered Keyboard Input (Funktion OAH, DOS 2.0-4.x) 173 4.12 Check Keyboard Status (Funktion OBH, DOS 2.0-4.x) 174 4.13 Flush Buffer, Read Keyboard (Funktion OCH, DOS 2.0-4.x) 174 4.14 Reset Disk (Funktion ODH, DOS 2.0-4.x) 175 4.15 Select Disk (Funktion OEH, DOS 2.0-4.x) 175 4.16 Open File (Funktion OFH, DOS 2.0-4.x) 176 4.17 Close File (Funktion 10H, DOS 2.0-4.x) 177 4.18 Search for First Entry (Funktion 11H, DOS 2.0-4.XJ 177 4.19 Search for Next Entry (Funktion 12H, DOS 2.0-4.x) 178 4.20 Delete File (Funktion 13H, DOS 2.0-lx) 179 4.21 Sequential Read (Funktion 14H, DOS 2.0-4.x) 179 4.22 Sequential Write (Funktion 15H, DOS 2.0-4.x) 180 4.23 Create File (Funktion 16H, DOS 2.0-4.x) 181 4.24 Rename File (Funktion 17H, DOS 2.0-4.x) 181 4.25 Get Current Disk (Funktion 19H, DOS 2.0-4.x) 182 4.26 Set Disk Transfer Address (Funktion IAH, DOS 2.0-4.x) 182 4.27 Get Default Drive Data (Funktion 1BH, DOS 2.0-4.x) 183 4.28 Get Drive Data (Funktion ICH, DOS 2.0-4.x) 184 4.29 Get Default Disk Parameter Block (Funktion 1FH, undokumentiert) 184 4.30 Random Read (Funktion 21H, DOS 2.0-4.x) 186 4.31 Random Write (Funktion 22H, DOS 2.0-4.x) 187 4.32 Get File Size (Funktion 23H, DOS 2.0-4.x) 188 4.33 Set Relativ Record (Funktion 24H, DOS 2.0-4.x) 188 4.34 Set-Interrupt-Vektor (Funktion 25H, DOS 2.0-4.x) 189 4.35 Create New PSP (Funktion 26H, DOS 2.0-4.x) 189 4.36 Random Block Read (Funktion 27H, DOS 2.0-4.x) 190 4.37 Random Block Write (Funktion 28H, DOS 2.0-4.x) 191 4.38 Parse File Name (Funktion 29H, DOS 2.0-4.x) 191 4.39 Get Date (Funktion 2AH, DOS 2.0-4.x) 193 4.40 Set Date (Funktion 2BH, DOS 2.0-4.x) 194 4.41 Get Time (Funktion 2CH, DOS 2.0-4.x) 194 4.42 Set Time (Funktion 2DH, DOS 2.0-4.x) 194 4.43 Set/Reset Verify Flag (Funktion 2EH, DOS 2.0-4.x) 195 4.44 Get Disk Transfer Address (Funktion 2FH, DOS 2.0-4.x) 195 4.45 Get MS-DOS Version Number (Funktion 30H, DOS 2.0-4.x) 196 4.46 Keep Process (Funktion 31H, DOS 2.0-4.x) 196 4.47 Get Disk Parameter Block (Funktion 32H, DOS 2.0-4.X, undok.) 197 4.48 Control-C Check (Funktion 33H, DOS 2.0-4.X) 199 4.49 Get DOS Critical Interval Flag (Funktion 34H, DOS 2.0-4.x) 201 4.50 Get Interrupt-Vektor (Funktion 35H, DOS 2.0-4.x) 202 8 Inhaltsverzeichnis 4.51 Get Free Disk Space (Funktion 36H, DOS 2.0-4.x) 202 4.52 Get/Set Switch Character (Funktion 37H, DOS 2.0-4.x) 203 4.53 Get/Set Country Data (Funktion 38H) 204 4.53.1 Get Country Data (Funktion 38H, DOS 2.x) 205 4.53.2 Get Country Data (Funktion 38H, DOS 3.0-4.x) 206 4.53.3 Set Country Data (Funktion 38H, DOS 3.0-4.x) 209 4.54 Create Directory (Funktion 39H, DOS 2.0-4.x) 210 4.55 Remove Directory (Funktion 3AH, DOS 2.0-4.x) 210 4.56 Change Current Directory (Funktion 3BH, DOS 2.0-4.x) 211 4.57 Create Handle (Funktion 3CH, DOS 2.0-4.x) 212 4.58 Open Handle (Funktion 3DH) 212 4.58.1 Open Handle (Funktion 3DH, DOS 2.x) 213 4.58.2 Open Handle (Funktion 3DH, DOS 3.0-4.x) 213 4.59 Close Handle (Funktion 3EH, DOS 2.0-4.x) 217 4.60 Read from a File or Device (Funktion 3FH, DOS 2.0-4.x) 217 4.61 Write to a File or Device (Funktion 40H, DOS 2.0-4.x) 218 4.62 Delete (Unlink) Directory Entry (Funktion 41H, DOS 2.0-4.x) 219 4.63 Move File Pointer (Funktion 42H, DOS 2.0-4.x) 219 4.64 Get/Set File Attributes (Funktion 43H, DOS 2.0-4.x) 220 4.65 IOCTL Data (Funktion 44H, DOS 2.0-4.x) 221 4.65.1 IOCTL Data (Funktion 44H, Code 0 und 1, DOS 2.0-4.x) 222 4.65.2 IOCTL Character (Funktion 44H, Code 2 und 3, DOS 2.0-4.x) 225 4.65.3 IOCTL Block (Funktion 44H, Code 4 und 5, DOS 2.0-4.x) 225 4.65.4 IOCTL Status (Funktion 44H, Code 6 und 7, DOS 2.0-4.x) 226 4.65.5 IOCTL is Changeable (Funktion 44H, Code 8, DOS 3.0-4.x) 227 4.65.6 IOCTL is Redirected Block (Funktion 4409H, DOS 3.l^.x) 227 4.65.7 IOCTL is Redirected Handle (Funktion 440AH, DOS 3.l-4.x) 228 4.65.8 IOCTL Retry (Funktion 44H, Code 0BH, DOS 3.0-4.x) 229 4.65.9 Generic IOCTL Handle Request (Funktion 440CH, DOS 3.3-4.x) 230 4.65.10 Generic IOCTL Request (Funktion 44H, Code 0DH, DOS 3.2-4.x) 237 4.65.11 I/O Control for Device (Funktion 440EH, DOS 3.2-4.x) 244 4.65.12 Set Logical Drive (Funktion 440FH, DOS 3.2-3.3) 245 4.66 Duplicate File Handle (Funktion 45H, DOS 2.0-4.x) 245 4.67 Force Duplicate File Handle (Funktion 46H, DOS 2.0-4.x) 246 4.68 Get Current Directory (Funktion 47H, DOS 2.0-4.x) 247 4.69 Allocate Memory (Funktion 48H, DOS 2.0-4.x) 247 4.70 Free Allocated Memory (Funktion 49H, DOS 2.0-4.x) 248 4.71 Set Block (Funktion 4AH, DOS 2.0-4.x) 249 4.72 Load or Execute a Program (Funktion 4BH, DOS 2.0-4.x) 249 4.72.1 Load and Execute (AL = 0) 249 4.72.2 Load (AL = 1 undokumentiert) 252 4.72.3 Load Overlay (AL = 3) 253 4.73 Terminate a Process (Funktion 4CH, DOS 2.0-4.x) 253 Inhaltsverzeichnis 9 4.74 Get Returncode (Funktion 4DH, DOS 2.0-4.x) 254 4.75 Find First Matching File (Funktion 4EH, DOS 2.0-4.x) 254 4.76 Find Next File (Funktion 4FH, DOS 2.0-4.x) 255 4.77 Set Active PSP (Funktion 50, DOS 2.0-4.X, undokumentiert) 256 4.78 Get Active PSP (Funktion 51, DOS 2.0-4.x, undokumentiert) 256 4.79 Get DOS Data Address (Funktion 52, DOS 2.0-4.X, undokumentiert) 257 4.80 Set Disk Parameter Block (Funktion 53, DOS 2.0-4.X, undok.) 258 4.81 Get Verify State (Funktion 54H, DOS 2.0-4.X) 258 4.82 Install New Process (Funktion 55H, DOS 2.0-4.X, undok.) 258 4.83 Rename File (Funktion 56H, DOS 2.0-4.x) 259 4.84 Get/Set File Date and Time (Funktion 57H, DOS 2.0-4.x) 260 4.85 Get/Set Allocation Strategie (Funktion 58H, DOS 2.0-4.x) 260 4.86 Get Extended Error (Funktion 59H, DOS 3.0-4.x) 261 .
Recommended publications
  • 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]
  • Memory Management
    University of Mississippi eGrove American Institute of Certified Public Guides, Handbooks and Manuals Accountants (AICPA) Historical Collection 1993 Memory management American Institute of Certified Public Accountants. Information echnologyT Division Follow this and additional works at: https://egrove.olemiss.edu/aicpa_guides Part of the Accounting Commons, and the Taxation Commons Recommended Citation American Institute of Certified Public Accountants. Information echnologyT Division, "Memory management" (1993). Guides, Handbooks and Manuals. 486. https://egrove.olemiss.edu/aicpa_guides/486 This Book is brought to you for free and open access by the American Institute of Certified Public Accountants (AICPA) Historical Collection at eGrove. It has been accepted for inclusion in Guides, Handbooks and Manuals by an authorized administrator of eGrove. For more information, please contact [email protected]. INFORMATION TECHNOLOGY DIVISION BULLETIN AICPA American Institute of Certified Public Accountants TECHNOLOGY Notice to Readers This technology bulletin is the first in a series of bulletins that provide accountants with information about a particular technology. These bulletins are issued by the AICPA Information Technology Division for the benefit of Information Technology Section Members. This bulletin does not establish standards or preferred practice; it represents the opinion of the author and does not necessarily reflect the policies of the AICPA or the Information Technology Division. The Information Technology Division expresses its appreciation to the author of this technology bulletin, Liz O’Dell. She is employed by Crowe, Chizek and Company in South Bend, Indiana, as a manager of firmwide microcomputer operations, supporting both hardware and software applications. Liz is an Indiana University graduate with an associate’s degree in computer information systems and a bachelor’s degree in business management.
    [Show full text]
  • Microsoft Windows for MS
    Month Year Version Major Changes or Remarks Microsoft buys non-exclusive rights to market Pattersons Quick & Dirty Operating System from December 1980 QDOS Seattle Computer Products (Developed as 86-DOS) (Which is a clone of Digital Researches C P/M in virtually every respect) Microsoft buys all rights to 86-DOS from Seattle Computer Products, and the name MS-DOS is July 1981 86-DOS adopted for Microsoft's purposes and IBM PC- DOS for shipment with IBM PCs (For Computers with the Intel 8086 Processor) Digital Research release CP/M 86 for the Intel Q3 1981 CP/M 86 8086 Processer Pre-Release PC-DOS produced for IBM Personal Mid 1981 PC-DOS 1.0 Computers (IBM PC) Supported 16K of RAM, ~ Single-sided 5.25" 160Kb Floppy Disk OEM PC-DOS for IBM Corporation. (First August 1982 PC-DOS 1.1 Release Version) OEM Version for Zenith Computer Corporation.. (Also known as Z-DOS) This added support for September 1982 MS-DOS 1.25 Double-Sided 5.25" 320Kb Floppy Disks. Previously the disk had to be turned over to use the other side Digital Research release CP/M Plus for the Q4 1982 CP/M Plus Intel 8086 Processer OEM Version For Zenith - This added support for IBM's 10 MB Hard Disk, Directories and Double- March 1983 MS-DOS 2.0 Density 5.25" Floppy Disks with capacities of 360 Kb OEM PC-DOS for IBM Corporation. - Released March 1983 PC-DOS 2.0 to support the IBM XT Microsoft first announces it intention to create a GUI (Graphical User Interface) for its existing MS-DOS Operating System.
    [Show full text]
  • Older Operating Systems
    Older Operating Systems Class Notes # 14 Computer Configuration November 20, 2003 The default configuration of DOS, which may be adequate for many users, is intended to work with the greatest number of systems. DOS also allows users to take full advantage of their computers features. We could configure our computer to operate more efficiently. There are two general ways of making our computers efficient: • Add or replace hardware • Use software to attain an optimal configuration for existing hardware resources DOS falls in the second category. With DOS we can manage our memory more efficiently and we can also use special device drivers and utility programs to enhance the performance of our hardware and software. Device Drivers Device drivers are software programs, which is used by DOS to control hardware devices. Most device drivers are loaded at boot time by including the device driver in your CONFIG.SYS. The DEVICE command tells DOS to load a device driver and uses the following syntax: DEVICE = driver /switches The driver is the actual software for the device, and the /switches are any switches that the device driver software needs. For example, the mouse device driver (MOUSE.SYS) is loaded in the CONFIG.SYS file with this command: DEVICE = C:\DRIVERS\MOUSE.SYS The DEVICE = command tells DOS that the program file name MOUSE.SYS stored in the \DRIVERS directory on drive C is a TSR needed to drive the mouse device. You may also load certain device drivers in AUTOEXEC.BAT. For example, the mouse device driver can also be loaded from the AUTOEXEC.BAT file.
    [Show full text]
  • Ramcram.Txt MEMORY MANAGEMENT for CD-ROM WORKSTATIONS
    ramcram.txt MEMORY MANAGEMENT FOR CD-ROM WORKSTATIONS by Peter Brueggeman Scripps Institution of Oceanography Library University of California San Diego "Memory management for CD-ROM workstations, Part II", CD-ROM PROFESSIONAL, 4(6):74-78, November 1991. "Memory management for CD-ROM workstations, Part I", CD-ROM PROFESSIONAL, 4(5):39-43, September 1991. The nature of the memory in IBM compatible microcomputers can be confusing to understand and worse to manage. If you are lucky, everything runs fine on the CD-ROM workstation or network and an article on memory management will be interesting but lack immediacy. Try to load other software concurrent with CD-ROM software or to implement network access and you may be due for a crash course in DOS memory, its limitations, and management. Running CD-ROM software usually demands considerable memory resources. Software in general has become more memory-hungry with time, and CD-ROM software have a reputation for being very hungry. Many CD-ROM products state that 640K RAM memory is required; this is not the exact memory requirement of the CD-ROM software. The CD-ROM software itself uses some of the 640K RAM as does DOS. Rarely will the exact memory requirement of a CD-ROM software be readily accessible. Sales representatives usually will not know it and only experienced technical support staff may know. CD-ROM workstation/network managers should try to learn the exact memory requirement of their CD-ROM software. Knowing their memory requirement helps greatly in selecting the level of solution(s). Addressing memory shortfalls may involve considerable tinkering and patience and involve seemingly endless rebooting.
    [Show full text]
  • Datalight BIOS to TRANSFER Files by Means of the Console, in Cases Where the Console Is Implemented by Means of a Serial Port
    Datalight ROM-DOS Version 7.1 User’s Guide Printed: April 2002 Datalight ROM-DOS User’s Guide Copyright © 1993 - 2002 by Datalight, Inc. All Rights Reserved Datalight, Inc. assumes no liability for the use or misuse of this software. Liability for any warranties implied or stated is limited to the original purchaser only and to the recording medium (disk) only, not the information encoded on it. THE SOFTWARE DESCRIBED HEREIN, TOGETHER WITH THIS DOCUMENT, ARE FURNISHED UNDER A SEPARATE SOFTWARE OEM LICENSE AGREEMENT AND MAY BE USED OR COPIED ONLY IN ACCORDANCE WITH THE TERMS AND CONDITIONS OF THAT AGREEMENT. Datalight, the Datalight logo, FlashFX and ROM-DOS are trademarks or registered trademarks of Datalight, Inc. Microsoft and MS-DOS are registered trademarks of Microsoft Corporation. All other trademarks are the property of their respective holders. Part Number: 3010-0200-0306 Contents Chapter 1, Introduction...........................................................................................................1 Conventions Used in this Manual .......................................................................................1 Terminology Used in this Manual.......................................................................................1 Random Access Memory (RAM) ................................................................................2 Read Only Memory (ROM).........................................................................................2 Disks and Disk Drives.........................................................................................................2
    [Show full text]
  • Datalight ROM-DOS™
    Datalight ROM-DOS Developer’s Guide Created: April 2005 Datalight ROM-DOS Developer’s Guide Copyright © 1999-2005 by Datalight, Inc . Portions copyright © GPvNO 2005 All Rights Reserved. Datalight, Inc. assumes no liability for the use or misuse of this software. Liability for any warranties implied or stated is limited to the original purchaser only and to the recording medium (disk) only, not the information encoded on it. U.S. Government Restricted Rights. Use, duplication, reproduction, or transfer of this commercial product and accompanying documentation is restricted in accordance with FAR 12.212 and DFARS 227.7202 and by a license agreement. THE SOFTWARE DESCRIBED HEREIN, TOGETHER WITH THIS DOCUMENT, ARE FURNISHED UNDER A SEPARATE SOFTWARE OEM LICENSE AGREEMENT AND MAY BE USED OR COPIED ONLY IN ACCORDANCE WITH THE TERMS AND CONDITIONS OF THAT AGREEMENT. Datalight and ROM-DOS are registered trademarks of Datalight, Inc. FlashFX ® is a trademark of Datalight, Inc. All other product names are trademarks of their respective holders. Part Number: 3010-0200-0715 Contents Chapter 1, Introduction..................................................................................................................5 About ROM-DOS ......................................................................................................................5 ROM-DOS Target System Requirements...........................................................................6 ROM-DOS Development System Requirements................................................................6
    [Show full text]
  • IPI, Programming and Configuration S/W Pkg, V5.02, GFK-1177
    April 4, 1995 GFK-1177 IMPORTANT PRODUCT INFORMATION READ THIS INFORMATION FIRST Product: Programming and Configuration Software Package, Version 5.02 IC641SWP736A – 3.5-inch 2DD (Standard Serial COM Port Version) IC641SWP733A – Demonstration Package (Standard Serial COM Port Version) CE641SWP731B – Sequential Function Chart (SFC) Programmer Read this document before installing or attempting to use the IC641 programming and configuration software with your programmable controller system. For more information, refer to the Programming Software User’s Manual, the Programmable Controller Reference Manual, the Sequential Function Chart Programming Language User’s Manual, or the README.TXT file on the master diskette. Release 5.02 of the programming and configuration software provides logic programming and configuration for programmable logic control systems. Release 5.02 is compatible with Release 5.0 and earlier CPUs. If a Bus Controller (IC66*) is used with this release of IC641 software, the Bus Controller must be Release 3.0 or later. In addition, Release 5.02 corrects problems that existed in Release 5.00 or earlier software. These problems are listed in section 5, “Problems Resolved by Release 5.02.” Operational Notes 1. System Requirements: A. The IC641 programming and configuration software requires either a minimum of 590K (604,160) bytes of available MS-DOS application memory, or 545K (558,080) bytes of MS-DOS application memory plus an additional 49K of High Memory Area (HMA), Upper Memory Blocks (UMB), or Expanded Memory (EMS) for the communications driver. For more information, refer to the Programming Software User’s Manual. A minimum 1024K of Lotus/Intel/Microsoft Expanded Memory (LIM EMS 3.2 or higher) is required for optimum performance.
    [Show full text]
  • IPI, Logicmaster 90-70 S/W Pkg, V5.0 Pgmr and Conf, GFK-0350P
    March 25, 1994 GFK-0350P IMPORTANT PRODUCT INFORMATION READ THIS INFORMATION FIRST Product: Logicmastert 90-70 Software Package, Version 5.00 Programmer and Configurator IC641SWP701M– 3.5-inch 2DD, 5.25-inch 2S/HD (WSI Version) IC641SWP706E – 3.5-inch 2DD, 5.25-inch 2S/HD (Standard Serial COM Port Version) IC641SWP703G – Demonstration Package (Standard Serial COM Port Version) IC641SWP731A – Sequential Function Chart (SFC) Programmer Read this document before installing or attempting to use Logicmastert 90-70 programmer and configurator software with your Series 90t-70 PLC system. For more information, refer to GFK-0263, GFK-0265, GFK-0854, or the README.TXT file on the master diskette. Release 5.00 of the Logicmaster 90-70 programmer and configurator software packages provides logic programming and configuration for the Series 90-70 PLC. Beginning with Release 5.00, Sequential Function Chart programming capability is available by ordering the desired Logicmaster 90-70 communications version and the SFC Programmer Option diskette (IC641SWP731A). For more information, refer to “New Features Introduced in Release 5.00.” Release 5.00 of Logicmaster 90-70 software is compatible with Release 5.0 and earlier CPUs. However, some new features found in Release 5.00 of Logicmaster 90-70 software require an upgrade of CPU firmware to Release 5 to be fully available. If a Genius Bus Controller is used with this release of Logicmaster 90-70 software, the Genius Bus Controller must be Release 3.0 or later. For more information, refer to “Using Release 5 Software with a Release 5 or Earlier CPU.” 2 Important Product Information GFK-0350P Operational Notes 1.
    [Show full text]
  • Datalight ROM-DOS User's Guide
    Datalight ROM-DOS User’s Guide Created: April 2005 Datalight ROM-DOS User’s Guide Copyright © 1999-2005 by Datalight, Inc . Portions copyright © GpvNO 2005 All Rights Reserved. Datalight, Inc. assumes no liability for the use or misuse of this software. Liability for any warranties implied or stated is limited to the original purchaser only and to the recording medium (disk) only, not the information encoded on it. U.S. Government Restricted Rights. Use, duplication, reproduction, or transfer of this commercial product and accompanying documentation is restricted in accordance with FAR 12.212 and DFARS 227.7202 and by a license agreement. THE SOFTWARE DESCRIBED HEREIN, TOGETHER WITH THIS DOCUMENT, ARE FURNISHED UNDER A SEPARATE SOFTWARE OEM LICENSE AGREEMENT AND MAY BE USED OR COPIED ONLY IN ACCORDANCE WITH THE TERMS AND CONDITIONS OF THAT AGREEMENT. Datalight and ROM-DOS are registered trademarks of Datalight, Inc. FlashFX ® is a trademark of Datalight, Inc. All other product names are trademarks of their respective holders. Part Number: 3010-0200-0716 Contents Chapter 1, ROM-DOS Introduction..............................................................................................1 About ROM-DOS ......................................................................................................................1 Conventions Used in this Manual .......................................................................................1 Terminology Used in this Manual ......................................................................................1
    [Show full text]
  • MORPH-II, a Software Package for the Analysis of Scanning-Electron-Micrograph Images for the Assessment of the Fractal Dimension of Exposed Stone Surfaces
    MORPH-II, a software package for the analysis of scanning- electron-micrograph images for the assessment of the fractal dimension of exposed stone surfaces by Victor G. Mossotti1 and A. Raouf Eldeeb2 Open-File Report 00-013 2000 This report is preliminary and has not been reviewed for conformity with U.S. Geological Survey editorial standards. Any use of trade, product, or firm names is for descriptive purposes only and does not imply endorsement by the U.S. Government. Although this program has been used by the U.S. Geological Survey, no warranty, expressed or implied, is made by the USGS as to the accuracy and functioning of the program and related program material, nor shall the fact of distribution constitute any such warranty, and no responsibility is assumed by the USGS in connection therewith. U.S. DEPARTMENT OF THE INTERIOR U.S. GEOLOGICAL SURVEY ________________________ 1345 Middlefield Road, MS 901, Menlo Park, CA 94025 2508 Cheyenne Drive, Sunnyvale, CA 94087 This report is available online at http://geopubs.wr.usgs.gov/open-file/of00-013/. CONTENTS Page Introduction -----------------------------------------------------------------------------------------------1 Overview of software functions ---------------------------------------------------------------------1 Overview of image analysis programs --------------------------------------------------------------1 Image generation------------------------------------------------------------------------------------------1 Sample preparation -----------------------------------------------------------------------------------2
    [Show full text]
  • Chapter 5 Windows 3.1 and Memory Management
    Chapter 5 Windows 3.1 and Memory Management This chapter contains information about how Microsoft Windows 3.1 interacts with memory. You can use this information to manage memory while running Windows and to troubleshoot various problems related to memory management. For specific information about optimizing your system configuration, see Chapter 6, “Tips for Configuring Windows 3.1.” Related information ••• Windows User’s Guide: Chapter 5, “Control Panel,” and Chapter 14, “Optimizing Windows” ••• Windows Resource Kit: Chapter 7, “Setting Up Non-Windows Applications,” and Chapter 13, “Troubleshooting Windows 3.1” ••• Glossary terms: Expanded Memory Specification, Extended Memory Specification, multitasking, page frame, protected mode, virtual memory Contents of this chapter About Memory .................................................................................................228 Types of Memory: An Overview..............................................................228 The Windows 3.1 Memory Device Drivers...............................................230 Expanded Memory: A Technical Discussion ...........................................230 Windows Standard Mode and Memory............................................................235 Extended Memory and Standard Mode .....................................................236 Expanded Memory and Standard Mode ....................................................237 Windows 386 Enhanced Mode and Memory....................................................238 WINA20.386 and 386 Enhanced
    [Show full text]