DOCSLIB.ORG

Ersatz-11 for Os/2 Pdp-11 Emulator Demo Version 7.3

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Ersatz-11 for Os/2 Pdp-11 Emulator Demo Version 7.3 ERSATZ-11 FOR OS/2 PDP-11 EMULATOR DEMO VERSION 7.3 FOR 30-DAY COMMERCIAL EVALUATION ONLY Copyright c 1993{2017 by Digby's Bitpile, Inc. All rights reserved. Release date: 01-Mar-2017 §¤¤ ¤ ¤¥ ¦¥¥ ¥ D Bit • 139 Stafford Road • Monson, MA • 01057 • USA • www.dbit.com § ¤ ¤¤ Digby's Bitpile, Inc. DBA D Bit ¤¥ 139 Stafford Road Monson, MA 01057 ¦ ¥¥ ¥ USA +1 (413) 267-4600 [email protected] www.dbit.com Copyright c 1993{2017 by Digby's Bitpile, Inc. All rights reserved. The following are trademarks of Digby's Bitpile, Inc.: £ ¡ D Bit E11 Ersatz ¢¡¡ ¡ The following are trademarks or registered trademarks of Digital Equipment Corporation: DEC DECnet DECtape DECwriter DIGITAL IAS MASSBUS PDP PDT P/OS Q-BUS RSTS RSX RT-11 ULTRIX UNIBUS VT The following are trademarks or registered trademarks of S&H Computer Systems, Inc.: TSX TSX-Plus Other product, service, and company names that appear in this document are used for identification purposes only, and may be trademarks and/or service marks of their respective owners. Contents 1 Introduction 1 1.1 Emulated block device types . 2 1.2 Emulated sequential device types . 3 1.3 Emulated serial device types . 3 1.4 Emulated network device types . 4 1.5 Emulated DDCMP device types . 4 1.6 Miscellaneous device types . 4 1.7 PC hardware support . 5 1.8 Device names . 6 1.9 Filenames . 8 1.10 Time durations . 8 1.11 Notes . 9 1.11.1 Interrupts . 9 1.11.2 Host systems . 9 1.11.3 Copyright and licensing . 10 1.12 Acknowledgments . 10 1.13 History . 11 2 Installation and Configuration 13 2.1 System requirements . 13 2.2 Installation . 13 2.3 Configuration . 14 3 Transferring the PDP-11 Operating System to the PC 17 3.1 SCSI disks . 17 3.2 SCSI tapes . 18 3.3 Kermit . 18 3.4 Ethernet . 18 3.5 ASCII serial dump . 19 3.6 System-specific notes . 20 3.7 Utilities . 20 4 Disk Devices 22 4.1 Disk cache . 23 4.2 Padding short volumes . 23 4.3 PC disk devices . 23 4.3.1 Disk image files . 24 4.3.2 Raw floppy disk drives . 25 4.3.3 RAM disk drives . 25 4.3.4 Disks with intentionally bad blocks . 26 4.3.5 Null disk drives . 26 4.4 Emulated PDP-11 disk devices . 27 4.4.1 DB: | RP04, RP05, RP06 . 27 4.4.2 DC: | RC11/RS64 . 28 4.4.3 DD: | DL11/TU58 . 28 4.4.4 DF: | RF11/RS11, DDC DMS-11X/SSDM 100 (called RF: in RT-11) . 29 4.4.5 DK: | RK02, RK03, RK05 DECpack (called RK: in RT-11) . 30 4.4.6 DL: | RL01, RL02 . 30 4.4.7 DM: | RK06, RK07 . 31 4.4.8 DP: | RP02, RP03 . 31 4.4.9 DR: | RM02, RM03, RM05, RM80, RP07 . 32 4.4.10 DS: | RS03, RS04 . 33 4.4.11 DT: | TU55, TU56 DECtape . 33 4.4.12 DU: | MSCP disks . 33 4.4.13 DX: | RX01 . 34 4.4.14 DY: | RX02, \RX03" . 35 4.4.15 FX: | Fox 2/30 \drum" . 36 4.4.16 HD: | Hypothetical disk . 36 4.4.17 PD: | PDT-11/150 RX01 . 37 4.4.18 QX: | Terak 8510/a single-density disk . 37 5 Tape Devices 38 5.1 PC tape devices . 38 5.1.1 Tape image files . 38 5.1.2 RAM tape drives . 39 5.1.3 Null tape drives . 39 5.2 Emulated PDP-11 tape devices . 40 5.2.1 CT: | TU60 DECcassette . 40 5.2.2 MM: | TE16/TU16, TU45, TU77 . 40 5.2.3 MR: | TR79 (HP7970E) . 41 5.2.4 MS: | TK25, TS04, TS05, TU80 . 42 5.2.5 MT: | TS03, TU10 . 42 5.2.6 MU: | TMSCP tapes . 43 6 Serial Lines 44 6.1 PC serial devices . 45 6.1.1 Serial options common to all devices . 45 6.1.2 Video consoles . 45 6.1.3 Line printer emulation using OS-supplied print drivers . 46 6.2 PC serial pseudo-devices . 48 6.2.1 Hayes-compatible dialup modems . 48 6.2.2 Kermit file-transfer protocol . 48 6.2.3 Throttled I/O . 48 6.2.4 Multiple physical ports on one emulated line . ..
Load more

Recommended publications
  • The Linux Kernel Module Programming Guide
    The Linux Kernel Module Programming Guide Peter Jay Salzman Michael Burian Ori Pomerantz Copyright © 2001 Peter Jay Salzman 2007−05−18 ver 2.6.4 The Linux Kernel Module Programming Guide is a free book; you may reproduce and/or modify it under the terms of the Open Software License, version 1.1. You can obtain a copy of this license at http://opensource.org/licenses/osl.php. This book is distributed in the hope it will be useful, but without any warranty, without even the implied warranty of merchantability or fitness for a particular purpose. The author encourages wide distribution of this book for personal or commercial use, provided the above copyright notice remains intact and the method adheres to the provisions of the Open Software License. In summary, you may copy and distribute this book free of charge or for a profit. No explicit permission is required from the author for reproduction of this book in any medium, physical or electronic. Derivative works and translations of this document must be placed under the Open Software License, and the original copyright notice must remain intact. If you have contributed new material to this book, you must make the material and source code available for your revisions. Please make revisions and updates available directly to the document maintainer, Peter Jay Salzman <[email protected]>. This will allow for the merging of updates and provide consistent revisions to the Linux community. If you publish or distribute this book commercially, donations, royalties, and/or printed copies are greatly appreciated by the author and the Linux Documentation Project (LDP).
    [Show full text]
  • Introduction to Linux Kernel Driver Programming
    IntroductionIntroduction toto LinuxLinux kernelkernel driverdriver programmingprogramming Introduction to Linux kernel driver programming The Linux kernel device model Authors and license ● Authors – Michael Opdenacker ([email protected]) Founder of Bootlin, kernel and embedded Linux engineering company https://bootlin.com/company/staff/michael-opdenacker ● License – Creative Commons Attribution – Share Alike 4.0 https://creativecommons.org/licenses/by-sa/4.0/ – Document sources: https://github.com/e-ale/Slides Need for a device model ● For the same device, need to use the same device driver on multiple CPU architectures (x86, ARM…), even though the hardware controllers are different. ● Need for a single driver to support multiple devices of the same kind. ● This requires a clean organization of the code, with the device drivers separated from the controller drivers, the hardware description separated from the drivers themselves, etc. Driver: between bus infrastructure and framework In Linux, a driver is always interfacing with: ● a framework that allows the driver to expose the hardware features in a generic way. ● a bus infrastructure, part of the device model, to detect/communicate with the hardware. Let’s focus on the bus infrastructure for now Device model data structures The device model is organized around three main data structures: ● The struct bus_type structure, which represent one type of bus (USB, PCI, I2C, etc.) ● The struct device_driver structure, which represents one driver capable of handling certain devices on a certain bus. ● The struct device structure, which represents one device connected to a bus The kernel uses inheritance to create more specialized versions of struct device_driver and struct device for each bus subsystem.
    [Show full text]
  • Operating System User's Mannal ~Zilog 03-0072-01 Revision a September 1978
    t_ .' Operating System User's Mannal ~Zilog 03-0072-01 Revision A September 1978 Copyright © 1978 by Zilog, Inc. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior written permission of Zilog. Zilog assumes no responsibility for the use of any circuitry other than circuitry embodied in a Zilog product. No other circuit patent licenses are implied. zaO-RIO Operating System User's Manual September 1978 TABLE OF CONTENTS CHAPTER 1 - INTRODUCTION AND OVERVIEW • 1 1.1 INTRODUCTION •• 1 1.2 SYSTEM OVERVIEW 3 1.2.1 Hardware Configuration • • • • • • 3 1.2.2 File Systems • • • • • • • . • • 3 1.2.3 System Initialization •••.••• 6 1.2.4 Commands • • .• .•..••• 7 1.2.5 I/O • • • . • • • • • . • • • • • . 7 CHAPTER 2 - RIO EXECUTIVE 9 2.1 SYSTEM INITIALIZATION 9 2.2 FILE NAME CONVENTIONS · 10 2.3 MEMORY MANAGEMENT . • • . 12 2.3.1 MEMMGR • . 13 2.4 COMMAND STRING INTERPRETATION · 13 2.5 ERROR HANDLING • • . 15 2.6 PROGRAM EXECUTION OF COMMANDS · 15 CHAPTER 3 - 1/0 STRUCTURE • · 16 3.1 OVERVIEW . • · 16 3.2 I/O REQUESTS - SYSTEM CALLS · 17 3.3 THE 'ASSIGN' I/O REQUEST ••• • 19 - i - 3.4 STANDARD RIO I/O DEVICES • • • 21 3.4.1 ZDOS . • • • . 21 3.4.2 DFS . 21 3.4.3 NULL . • • • . 21 3.4.4 CON . • • • . • • • • • 22 3.4.5 PCON • 27 3.4.6 FLOPPY • • • • • • • • • • 27 3.4.7 DISK • • • • • • 27 CHAPTER 4 - PROGRAM INTERFACE • • 28 4.1 PROGRAM LOCATION • • • • • 28 4.2 PARAMETER STRING ADDRESS · 29 4.3 PROGRAM STACK SPACE • • • 29 4.4 PROGRAM TERMINATION - ERROR HANDLING ••.
    [Show full text]
  • The Linux Device File-System
    The Linux Device File-System Richard Gooch EMC Corporation [email protected] Abstract 1 Introduction All Unix systems provide access to hardware via de- vice drivers. These drivers need to provide entry points for user-space applications and system tools to access the hardware. Following the \everything is a file” philosophy of Unix, these entry points are ex- posed in the file name-space, and are called \device The Device File-System (devfs) provides a power- special files” or \device nodes". ful new device management mechanism for Linux. Unlike other existing and proposed device manage- This paper discusses how these device nodes are cre- ment schemes, it is powerful, flexible, scalable and ated and managed in conventional Unix systems and efficient. the limitations this scheme imposes. An alternative mechanism is then presented. It is an alternative to conventional disc-based char- acter and block special devices. Kernel device drivers can register devices by name rather than de- vice numbers, and these device entries will appear in the file-system automatically. 1.1 Device numbers Devfs provides an immediate benefit to system ad- ministrators, as it implements a device naming scheme which is more convenient for large systems Conventional Unix systems have the concept of a (providing a topology-based name-space) and small \device number". Each instance of a driver and systems (via a device-class based name-space) alike. hardware component is assigned a unique device number. Within the kernel, this device number is Device driver authors can benefit from devfs by used to refer to the hardware and driver instance.
    [Show full text]
  • Operating Systems
    CS101 – Fundamentals of Computer and Information Sciences – LIU 1 of 2 Operating systems OS History We covered a (slightly rambling) story about the history of operating systems. Batch computing Batch systems were extraordinarily large and expensive, so that organizations could afford at most one or two. The machines had a human operator who was responsible for scheduling tasks for the machine, in order to make best use of its (very valuable) time. • Norwich council takes delivery of its first computer –@StuartSumner • Punch cards • IBM ad feat. punched cards • Keypunch machine • IBM 704 with card reader • LEGO Grace Hopper with Univac TODO: scheduling and calculating turn-around time using First-Come First-Served (FCFS) vs. Shortest Job First. (See book section 10.4, pages 350–351.) Time-sharing When mini-computers became available (just the size of a refrigerator, not a whole room), then we could have one for each workgroup or department within an orga- nization. They were powerful enough that multiple users could share the computer at the same time, by connecting multiple terminals (keyboard and monitor) to the same machine. The job of the human operator was now automated, and this was the golden ageof operating systems. Not only did they have to schedule tasks effectively, but they had to switch efficiently among serving different users, protect those users from interfer- ing with each other’s work, and so on. Some of the operating systems developed in this era were Multics, VMS, and UNIX. • PDP-11 with Ken Thompson, Dennis Ritchie • VT-101 terminal • IBM 7090 time-sharing video • Brian Kernighan on Bell Labs (Computerphile video) 2 of 2 Prof.
    [Show full text]
  • IODF Explorer
    The Input/Output Definition File (IODF) is a critical Control Point in the management of the IBM z/Series Platform. IODF Explorer Release 4.0 USER GUIDE Contact us for additional information: NewEra Software Technical Support 800-421-5035 [email protected] www.newera.com Rev: 2009-04-24 IODF Explorer 4.0 ¾ Copyright, Trademark and Legal Notices Copyrights This Getting Started Guide and the related Software Product(s) are protected under a Copyright dated 2009 by NewEra Software, Inc. All rights are reserved. License Agreement This Getting Started Guide describes the installation and operation of Image FOCUS, its environment and applications. It is made available only under the terms of a license agreement between the licensee and NewEra Software Inc. No part of this Guide or the related Software Product(s) may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, for any purpose, without the express written permission of NewEra Software, Inc. Trademarks and Copyrights of Others The following products and/or registered trademarks of International Business Machines Corporation are referenced in this document: MVS, VM, RACF, z/OS, SYSPLEX, JES, VTAM, TSO, ISPF, ICKDSF, DFSMSdss, DF/DSS, and others. 2 NewEra Software, Inc. ‐ Image Control Environment (ICE) Applications IODF Explorer 4.0 ¾ Technical Support Information NewEra Software is dedicated to providing the highest level of technical Around-the-clock- support support to meet our customers’ growing needs. In order to meet these needs, NewEra provides around‐the‐clock technical support, 7 days a week, 24 hours a day.
    [Show full text]
  • Topic 10: Device Driver
    Topic 10: Device Driver Tongping Liu University of Massachusetts Amherst 1 Administration • Today it is the deadline of Project3 • Homework5 is posted, due on 05/03 • Bonus points: ECE570 – 3 points, ECE670-5 points – Design exam questions – Process&threads, scheduling, synchronization, IPC, memory management, device driver/virtualization – Due: 05/01 • Survey project (ECE570/ECE670): 05/12 University of Massachusetts Amherst 2 Objectives • Understanding concepts of device driver, e.g., device number, device file • Understand the difference of kernel modules and device drivers • Learn how to implement a simple kernel module • Learn how to implement a simple device driver University of Massachusetts Amherst 3 Outline • Basic concepts • Kernel module • Writing device driver University of Massachusetts Amherst 4 Device Driver • A special kind of computer program that operates or controls a particular type of device that is attached to a computer University of Massachusetts Amherst 5 Device Driver • A special kind of computer program that operates or controls a particular type of device that is attached to a computer – Needs to execute privileged instructions – Must be integrated into the OS kernel, with a specific format – Interfaces both to kernel and to hardware University of Massachusetts Amherst 6 Whole System Stack Note: This picture is excerpted from Write a Linux Hardware Device Driver, Andrew O’Shauqhnessy, Unix world University of Massachusetts Amherst 7 Another View from OS University of Massachusetts Amherst 8 Type of Devices • Character device – Read or write one byte at a time as a stream of sequential data – Examples: serial ports, parallel ports, sound cards, keyboard • Block device – Randomly access fixed-sized chunks of data (block) – Examples: hard disks, USB cameras University of Massachusetts Amherst 9 Linux Device Driver • Manage data flow between user programs and device • Typically a self-contained kernel module – Add and remove dynamically • Device is a special file in /dev that user can access, e.g.
    [Show full text]
  • Hardware Configuration Definition User's Guide
    z/OS Version 2 Release 3 Hardware Configuration Definition User's Guide IBM SC34-2669-30 Note Before using this information and the product it supports, read the information in “Notices” on page 443. This edition applies to Version 2 Release 3 of z/OS (5650-ZOS) and to all subsequent releases and modifications until otherwise indicated in new editions. Last updated: 2019-02-16 © Copyright International Business Machines Corporation 1994, 2018. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents List of Figures..................................................................................................... xiii List of Tables.....................................................................................................xxiii About this document.......................................................................................... xxv Who this document is for..........................................................................................................................xxv Related information.................................................................................................................................. xxv How to use this document.......................................................................................................................xxvi How this document is organized............................................................................................................. xxvi How to read syntax diagrams................................................................................................................
    [Show full text]
  • Introduction to the New Mainframe: Z/OS Basics
    Front cover Introduction to the New Mainframe: z/OS Basics An introduction to mainframe computing on the IBM zSeries platform z/OS concepts and facilities for students and beginners zSeries hardware and peripheral devices Mike Ebbers Wayne O’Brien Bill Ogden ibm.com/ International Technical Support Organization z/OS Basics March 2005 SG24-6366-00 Note: Before using this information and the product it supports, read the information in “Notices” on page -1. First Edition (March 2005) © Copyright International Business Machines Corporation 2005. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Preface . xvii How this text is organized . xvii How each chapter is organized . xviii Acknowledgements . xix Comments welcome. xxi Part 1. Introduction to z/OS and the mainframe environment Chapter 1. Introduction to the new mainframe . 1-1 1.1 The new mainframe. 1-2 1.2 Evolving architecture . 1-2 1.3 Mainframes in our midst . 1-4 1.4 What is a mainframe? . 1-5 1.5 Who uses mainframe computers?. 1-7 1.6 Factors contributing to mainframe use . 1-8 1.6.1 Reliability, availability, and serviceability. 1-9 1.6.2 Security . 1-10 1.6.3 Scalability . 1-10 1.6.4 Continuing compatibility . 1-11 1.7 Typical mainframe workloads . 1-11 1.7.1 Batch processing. 1-12 1.7.2 Online transactional processing . 1-15 1.8 Roles in the mainframe world . 1-17 1.8.1 Who is the system programmer? . 1-19 1.8.2 Who is the system administrator? .
    [Show full text]
  • Guest OS Compatibility Guide
    Guest OS Compatibility Guide Guest OS Compatibility Guide Last Updated: September 29, 2021 For more information go to vmware.com. Introduction VMware provides the widest virtualization support for guest operating systems in the industry to enable your environments and maximize your investments. The VMware Compatibility Guide shows the certification status of operating system releases for use as a Guest OS by the following VMware products: • VMware ESXi/ESX Server 3.0 and later • VMware Workstation 6.0 and later • VMware Fusion 2.0 and later • VMware ACE 2.0 and later • VMware Server 2.0 and later VMware Certification and Support Levels VMware product support for operating system releases can vary depending upon the specific VMware product release or update and can also be subject to: • Installation of specific patches to VMware products • Installation of specific operating system patches • Adherence to guidance and recommendations that are documented in knowledge base articles VMware attempts to provide timely support for new operating system update releases and where possible, certification of new update releases will be added to existing VMware product releases in the VMware Compatibility Guide based upon the results of compatibility testing. Tech Preview Operating system releases that are shown with the Tech Preview level of support are planned for future support by the VMware product but are not certified for use as a Guest OS for one or more of the of the following reasons: • The operating system vendor has not announced the general availability of the OS release. • Not all blocking issues have been resolved by the operating system vendor.
    [Show full text]
  • ACPI Project for Ecomstation
    The ACPI Project for eComStation David Azarewicz www.88watts.net [email protected] Warpstock USA 2012 About Me • I am primarily a hardware developer. I started my career designing hardware for IBM 360 mainframe clones. • I then joined a small company building Cray compatible computers where I did a little of everything including microcode and embedded systems hardware and software. • Since then I have worked on projects from auto industry process controllers, to home automation, to radiation effects testing for satellite electronics. • I have been using OS/2 and developing software for OS/2 since the beginning. • Being an experienced hardware developer gives me an advantage in writing device drivers. Warpstock USA 2012 - The ACPI Project - David Azarewicz - Page 2 of 20 This Presentation • What is ACPI? • What is the ACPI Project? • What does the ACPI Project software do? • The Big Picture • The benefits and limitations of the ACPI Project software • How to work around problems • Using ACPI in your applications • Questions Warpstock USA 2012 - The ACPI Project - David Azarewicz - Page 3 of 20 What is ACPI? • ACPI stands for Advanced Configuration and Power Interface • ACPI is supplied by your computer vendor and is part of your computer’s BIOS. • ACPI provides a standard interface to your computer’s hardware through a list of objects and methods called the ACPI tables. • Software can use the ACPI tables to learn about what hardware is available • Software can use the ACPI tables to do things in the system. • ACPI is an extremely large and complex topic and is not really the subject of this presentation.
    [Show full text]
  • Evolutionary Sprint 2009/11
    Evolutionary Sprint Evolutionary Sprint 2009/11 Speaker: Eugene Gorbunoff software http://ecomstation.ru Perspectives of eComStation 2008/11 “Build non-sinking constructions” 2007/11 “Change your mind” 2006/11 “OS/2 Village” software http://ecomstation.ru Perspectives of eComStation What is Evolutionary Sprint? ● Evolutionary = don't migrate to other platform ● Sprint = 2-3 years to improve situation (starting from fall 2006) software http://ecomstation.ru Perspectives of eComStation Contents of the presentation: (A) (B) (C) What's new? What is successful eCS? PC in 2010 Roles Make quick changes FAQ eComStation 3.0 We need new software software http://ecomstation.ru Perspectives of eComStation Key slide: #04-00 Sci-tech labs.. development of technologies.. software http://ecomstation.ru Perspectives of eComStation software http://ecomstation.ru Perspectives of eComStation Keep in mind.. eComStation 2.0 was started in 2002!! software http://ecomstation.ru Perspectives of eComStation What's new in 2009? # 05-00 eComStation 2.0 RC7, eComStation 2.0 GA Applications: * OpenOffice.org 3.1 GA * PMView (2009/05) improved for SMP/Panorama VESA * always the latest Thunderbird, Firefox * DFSee 10.0 New technologies: * Flash-player software http://ecomstation.ru Perspectives of eComStation What's new in 2009? # 05-02 ACPI * Poor support of users during 2009 * Intel ACPI source code 2008/12 * ACPI is patching the kernel on-the-fly (suspend/resume) * support of Embedded controller is implemented Hardware support: * CUPS (USB, debugging) software http://ecomstation.ru
    [Show full text]