DOCSLIB.ORG

CP/M Plus™ (CP/M Version 3) CP/M 3 Operating System

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

CP/M Plus™ (CP/M Version 3) CP/M 3 Operating System User's Guide Copyright © 1982 Digital Research P.O. Box 579 160 Central Avenue Pacific Grove, CA 93950 (408) 649-3896 TWX 910 360 5001 All Rights Reserved COPYRIGHT Copyright © 1982 by Digital Research. All rights reserved. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any language or compu ter language, in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual or otherwise, without the prior written permission of Digital Research, Post Office Box 579, Pacific Grove, California, 93950. DISCLAIMER Digital Research makes no representations or warranties with respect to the contents hereof and specifically disclaims any implied warranties of merchantability or fitness for any particular purpose. Further, Dig i tal Research reserves the right to revise this publication and to make changes f rom time to time in the content hereof wi thout obligation of Digital Research to notify any person of such revision or changes. TRADEMARKS CP/M is a registered trademark of Digital Research. CP/M 3, SID, MAC, and R~C are trademarks of Digital Research. The CP/M 3 Operating System User I s Guide was prepared using the Digital Research TEX Text Formatter and pr inted in the United States of America by Commercial Press/Monterey. ********************************** * Preliminary: November 1982 * ********************************** Final Technical Review Complete In Production for Final Edit and Graphics CP/M 3 and its utility programs are distributed on two floppy disks. The system disk contains the operating system and the most commonly used utility programs. A second disk contains additional utilities. How To Use CP/M 3 Documentation The CP/M 3 documentation includes three manuals: • CP/M 3 Operating System User's Guide • CP/M 3 Operating System Programmer's Guide • Programmer's Utilities Guide The CP/M 3 Operating System User's Guide introduces you to the CP/M 3 operating system and tells you how to use it. The User's Guide assumes that the version of CP/M 3 on your distribution disk is ready to run on your computer. To use this manual, you must be familiar with the parts of your computer, know how to set it up and turn it on, and how to handle, insert, and store disks. However, you do not need a great deal of experience with comp~ters. The CP/M 3 Operating System Programmer's Guide presents information for application programmers who are creating or adapting programs to run under CP/M 3. The Programmer's Utilities Guide includes information on the CP/M assemblers and debuggers that experienced programmers use to create new CP/M 3 programs. Bow This Guide is Organized This guide begins with simple examples, proceeds with basic concepts, then presents a detailed reference section on commands. The first four sections describe CP/M 3 operation for the first-time user. Section 1 introduces CP/M 3 and tells you how to start the operating system, enter commands, edit the command line, and create a back-up copy of your distribution disks. Section 2 discusses files, disks, and drives. Section 3 describes how you can use CP/M 3 to manage your pr inter and console. Section 4 develops the concepts you need to use CP/M 3 commands. If you are new to CP/M, read the first four sections carefully to get a general understanding of how to use CP/M 3 before you proceed to the specific command descriptions. Section 5 provides detailed information on each CP/M 3 utility program, arranged alphabetically for easy reference. Many of these are programming utilities that you will not use until you start writing your own CP/M 3 programs. Section 6 tells you how to use ED, the CP/M 3 file editor. With ED, you can create and edit program, text; and data files. Appendix A lists the messages CP/M 3 displays when it encounters special condi tions I and descr ibes correc tive action where necessary. Appendix B provides an ASCII to hexadecimal conversion iv vi TABLE OF CONTENTS 1 Introduction 1.1 How to Start CP/M 3 1 1.2 The Command Line .• 1 1.3 Why You Should Back Up Your Files 3 1.4 How to Make Copies of Your CP/M 3 Disks 4 2 Files, Disks, and Drives 2.1 What is a File? 7 2.2 How Are Files Created? . 7 2.3 Naming Files--What's in a Name? 8 2.4 Accessing Files--Do You Have the Correct Drive? 9 2.5 Accessing Files--User Numbers 10 2.6 Accessing More Than One File. 11 2.7 How to Protect Your Files 12 2.7.1 File Attributes •••. 12 2.7.2 Time and Date Stamping 13 2.7.3 Passwords • • . • • . 13 2.8 How Are Files Stored on a Disk? 14 2.9 Changing Floppy Disks 14 2.10 Protecting a Drive 15 3 Console and Printer 3.1 Controlling Console Output · · · . 17 3.2 Controlling Printer Output · · · 17 3.3 Console Line Editing . · · . 18 3.3.1 Line Editing in Nonbanked CP/M 3 · · 18 3.3.2 Line Editing in Banked CP/M 3 . · · . 19 vii TABLE OF CONTENTS (continued) 3.4 Redirecting Input and Output 22 3.5 Assigning Logical Devices 24 4 CP/M 3 Command Concepts 4.1 Two Kinds of Commands 25 4.3 Transient Utility Commands. 26 4.4 How CP/M 3 Searches for Program and Data Files. 28 4.4.1 Finding Data Files 28 4.4.2 Finding Program Files 28 4.5 Executing Multiple COIT~ands 30 4.6 Terminating Programs • 31 4.7 Getting Help 32 5 Command Summary 5.1 Let's Get Past the Formalities . 33 5.2 How Commands Are Described 36 The DATE Command . 42 Set the Date and Time 42 The DEVICE COTIl!nand . 44 Display Device Characteristics and Assignments . 45 Assign a Logical Device • • • • • . 46 Set Attributes of a Physical Device .•• • • • 47 Display or Set the Current Console Screen Size 47 The DIR Command 48 Display Directory 48 Display Directory with Options 50 The DUMP Command . 57 The ED Command 58 The ERASE Command 65 viii TABLE OF CONTENTS (continued) The GENCOM Command 67 Attach RSX Files to a COM File • • • . 67 Generate a COM File Using only RSX Files • • 68 Restore a File with Attached RSXs 68 Update (Add or Replace) RSX Files 68 The GET Command • • 70 Get Console Input from a File 70 Terminate Console Input from a File 71 The HELP Command 73 Display Information 73 Add Your Own Descriptions to the HELP.HLP File 74 The HEXCOM Command 77 The INITDIR Command . 78 The LIB Command · 80 The LINK Command 83 The MAC Command · 86 PIP Command . · . 89 Single File Copy • • 89 Multiple File Copy • 92 Combining Files •• • • 93 Copy Files to and from Auxiliary Devices • • 94 Multiple Command Mode •••.•• 96 Using ~ptions with PIP •••••• 96 The PUT Command • • • • • • • 102 Direct Console Output to a File 102 Put Printer Output to a File ••• 103 Terminate Console Output to a File • 104 Terminate Printer Output to a File • 104 The RENAME Command 105 The RMAC Command 107 ix TABLE OF CONTENTS (continued) The SET Co~~and • • 109 Assign a Label to the Disk . 109 Assign Password to the Label . 109 Enable/Disable Password Protection for Files • 110 Assign Passwords to Files •••• 111 Set Password Protection Mode for Files • 111 Assign a Default Password 112 Set Time Stamp Options on Disk • 112 Set File Attributes .•.. 114 Set Drive Attribute .•••••••. 116 Additional SET Examples 116 The SETDEF Command 117 Display the Program Loading Search Definitions • 117 Assign the Drive for Temporary Files ••••. 117 Define the Disk Drive Search Order 118 Define the File Type Search Order 118 Turn On/Off System Display Mode 119 The SHOW Command 121 Display Access Mode and Disk Space Available • 121 Display Disk Label • • • • • 121 Display User Number Information • • • • 122 Display Number of Free Directory Entries • 123 Display Drive Characteristics 123 The SID Command • • • 124 SID Utilities 128 The SUBMIT Command 130 Program Input Lines in a SUB File 131 The SUB File •••• 132 Executing the SUBMIT Command • • 132 The PROFILE.SUB Start-up File 133 The USER Command 136 The XREF Command 137 6 ED, The CP/M 3 Context Editor 6.1 Introduction to ED 139 6.2 Starting ED 139 x TABLE OF CONTENTS (continued) 6.3 ED Oper a tion • • 140 6.3.1 Appending Text into the Buffer 142 6.3.2 ED Exit. 143 6.4 Basic Editing Commands ••. 144 6.4.1 Moving the Character Pointer •• 146 6.4.2 Displaying Memory Buffer Contents • • 147 6.4.3 Deleting Characters •.• 148 6.4.4 Inserting Characters into the Memory Buffer • 150 6.4.5 Replacing Characters 151 6.5 Combining ED Commands 152 6.5.1 Moving the Character Pointer 152 6.5.2 Displaying Text . • . • • 153 6.5.3 Editing . • • • . • • • • 154 6.6 Advanced ED Commands .• 154 6.6.1 Moving the CP and Displaying Text . • . 154 6.6.2 Finding and Replacing Character Strings 156 6.6.3 Moving Text Blocks •.• .• .•• . 159 6.6.4 Saving or Abandoning Changes: ED Exit 161 6.7 ED Error Messages 162 xi APPENDIXES A CP/M 3 Messages • • • 163 B ASCII and Hexadecimal Conversions • 193 C Filetypes 197 D CP/M 3 Control Character Summary 199 E . User's Glossary •••••••.. 203 xii Foreword Welcome to the world of microcomputers opened to you by your eight-bit microprocessor.
Recommended publications
  • Adaptive Android Kernel Live Patching

    Adaptive Android Kernel Live Patching

    Adaptive Android Kernel Live Patching Yue Chen Yulong Zhang Zhi Wang Liangzhao Xia Florida State University Baidu X-Lab Florida State University Baidu X-Lab Chenfu Bao Tao Wei Baidu X-Lab Baidu X-Lab Abstract apps contain sensitive personal data, such as bank ac- counts, mobile payments, private messages, and social Android kernel vulnerabilities pose a serious threat to network data. Even TrustZone, widely used as the se- user security and privacy. They allow attackers to take cure keystore and digital rights management in Android, full control over victim devices, install malicious and un- is under serious threat since the compromised kernel en- wanted apps, and maintain persistent control. Unfortu- ables the attacker to inject malicious payloads into Trust- nately, most Android devices are never timely updated Zone [42, 43]. Therefore, Android kernel vulnerabilities to protect their users from kernel exploits. Recent An- pose a serious threat to user privacy and security. droid malware even has built-in kernel exploits to take Tremendous efforts have been put into finding (and ex- advantage of this large window of vulnerability. An ef- ploiting) Android kernel vulnerabilities by both white- fective solution to this problem must be adaptable to lots hat and black-hat researchers, as evidenced by the sig- of (out-of-date) devices, quickly deployable, and secure nificant increase of kernel vulnerabilities disclosed in from misuse. However, the fragmented Android ecosys- Android Security Bulletin [3] in recent years. In ad- tem makes this a complex and challenging task. dition, many kernel vulnerabilities/exploits are publicly To address that, we systematically studied 1;139 An- available but never reported to Google or the vendors, droid kernels and all the recent critical Android ker- let alone patched (e.g., exploits in Android rooting nel vulnerabilities.
  • Digital Vision Network 5000 Series BCM Motherboard BIOS Upgrade

    Digital Vision Network 5000 Series BCM Motherboard BIOS Upgrade

    Digital Vision Network 5000 Series BCM™ Motherboard BIOS Upgrade Instructions October, 2011 24-10129-128 Rev. – Copyright 2011 Johnson Controls, Inc. All Rights Reserved (805) 522-5555 www.johnsoncontrols.com No part of this document may be reproduced without the prior permission of Johnson Controls, Inc. Cardkey P2000, BadgeMaster, and Metasys are trademarks of Johnson Controls, Inc. All other company and product names are trademarks or registered trademarks of their respective owners. These instructions are supplemental. Some times they are supplemental to other manufacturer’s documentation. Never discard other manufacturer’s documentation. Publications from Johnson Controls, Inc. are not intended to duplicate nor replace other manufacturer’s documentation. Due to continuous development of our products, the information in this document is subject to change without notice. Johnson Controls, Inc. shall not be liable for errors contained herein or for incidental or consequential damages in connection with furnishing or use of this material. Contents of this publication may be preliminary and/or may be changed at any time without any obligation to notify anyone of such revision or change, and shall not be regarded as a warranty. If this document is translated from the original English version by Johnson Controls, Inc., all reasonable endeavors will be used to ensure the accuracy of translation. Johnson Controls, Inc. shall not be liable for any translation errors contained herein or for incidental or consequential damages in connection
  • Guide to Enterprise Patch Management Technologies

    Guide to Enterprise Patch Management Technologies

    NIST Special Publication 800-40 Revision 3 Guide to Enterprise Patch Management Technologies Murugiah Souppaya Karen Scarfone C O M P U T E R S E C U R I T Y NIST Special Publication 800-40 Revision 3 Guide to Enterprise Patch Management Technologies Murugiah Souppaya Computer Security Division Information Technology Laboratory Karen Scarfone Scarfone Cybersecurity Clifton, VA July 2013 U.S. Department of Commerce Penny Pritzker, Secretary National Institute of Standards and Technology Patrick D. Gallagher, Under Secretary of Commerce for Standards and Technology and Director Authority This publication has been developed by NIST to further its statutory responsibilities under the Federal Information Security Management Act (FISMA), Public Law (P.L.) 107-347. NIST is responsible for developing information security standards and guidelines, including minimum requirements for Federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of appropriate Federal officials exercising policy authority over such systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130, Section 8b(3), Securing Agency Information Systems, as analyzed in Circular A- 130, Appendix IV: Analysis of Key Sections. Supplemental information is provided in Circular A-130, Appendix III, Security of Federal Automated Information Resources. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on Federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, Director of the OMB, or any other Federal official.
  • Introduction to MS-DOS

    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.
  • Chapter 1. Origins of Mac OS X

    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.
  • Operating System User's Mannal ~Zilog 03-0072-01 Revision a September 1978

    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 ••.
  • IODF Explorer

    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.
  • Android 10 OS Update Instruction for Family of Products on SDM660

    Android 10 OS Update Instruction for Family of Products on SDM660

    Android 10 OS Update Instruction for Family of Products on SDM660 1 Contents 1. A/B (Seamless) OS Update implementation on SDM660 devices ................................................................................................... 2 2. How AB system is different to Non-AB system ............................................................................................................................... 3 3. Android AB Mode for OS Update .................................................................................................................................................... 4 4. Recovery Mode for OS Update ........................................................................................................................................................ 4 5. Reset Packages and special recovery packages ................................................................................................................................ 4 6. OS Upgrade and Downgrade ............................................................................................................................................................ 5 7. OS Upgrade and Downgrade via EMMs .......................................................................................................................................... 6 8. AB Streaming Update ....................................................................................................................................................................... 7 9. User Notification for Full OTA package
  • Hardware Configuration Definition User's Guide

    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................................................................................................................
  • Patch My PC Microsoft Intune Setup Guide Document Versions

    Patch My PC Microsoft Intune Setup Guide Document Versions

    Patch My PC Microsoft Intune Setup Guide Document Versions: Date Version Description February 07, 2020 1.0 Initial Release March 03, 2020 1.1 User Interface Update August 18, 2020 1.2 Intune Update Feature September 24, 2020 1.3 Grammar and App Registration permission cleanup January 22, 2021 1.4 Update App Registration Permissions February 1, 2021 1.5 Clarified WSUS RSAT prerequisite March 4, 2021 1.6 Updated App Registration permission requirement for GroupMember.Read.All March 17, 2021 1.7 Updated text for Group.Read.All API permission March 26, 2021 1.8 Updated screenshot for new Application Manager Utility location Patch My PC – Publishing Service Setup Guide (Microsoft Intune) 1 System Requirements: • Microsoft .NET Framework 4.5 • Supported Operating Systems o Windows Server 2008 o Windows Server 2012 o Windows Server 2016 o Windows Server 2019 o Windows 10 (x64) – Microsoft Intune only Prerequisites: • WSUS Remote Server Administration Tools (RSAT) to be installed Download the latest MSI installer of the publishing service using the following URL: https://patchmypc.com/publishing- service-download Start the installation by double- clicking the downloaded MSI. Note: Depending on user account control settings, you may need to run an elevated command prompt and launch the MSI from the command prompt. Click Next in the Welcome Wizard Click Next in the Installation Folder Dialog Optionally, you can change the installation folder by clicking Browse… Click Install on the Ready to Install dialog. Note: if user-account control is enabled, you will receive a prompt “Do you want to allow this app to make changes to your device?” Click Yes on this prompt to allow installation Patch My PC – Publishing Service Setup Guide (Microsoft Intune) 2 If you are configuring the product for Intune Win32 application publishing only, you can check Enable Microsoft Intune standalone mode When this option is enabled, prerequisite checks related to WSUS and Configuration Manager are skipped.
  • Patch Management for Redhat Enterprise Linux

    Patch Management for Redhat Enterprise Linux

    Patch Management for RedHat Enterprise Linux Supported Versions BigFix provides coverage for RedHat updates on the following platforms: • RedHat Enterprise Linux 5 • RedHat Enterprise Linux 4 • RedHat Enterprise Linux 3 BigFix covers the following RedHat updates on these platforms: • RedHat Security Advisories • RedHat Bug Fix Advisories • RedHat Enhancement Advisories Patching using Fixlet Messages To deploy patches from the BigFix Console: 1. On the Fixlet messages tab, sort by Site. Choose the Site Patches for RedHat Enterprise Linux. 2. Double-click on the Fixlet message you want to deploy. (In this example, the Fixlet message is RHSA-2007:0992 - Libpng Security Update - Red Hat Enterprise 3.0.) The Fixlet window opens. For more information about setting options using the tabs in the Fixlet window, consult the Console Operators Guide. 3. Select the appropriate Action link. © 2007 by BigFix, Inc. BigFix Patch Management for RedHat Enterprise Linux Page 2 A Take Action window opens. For more information about setting options using the tabs in the Take Action dialog box, consult the Console Operators Guide. 4. Click OK, and enter your Private Key Password when asked. Using the Download Cacher The Download Cacher is designed to automatically download and cache RedHat RPM packages to facilitate deployment of RedHat Enterprise Linux Fixlet messages. Running the Download Cacher Task BigFix provides a Task for running the Download Cacher Tool for RedHat Enterprise Linux. 1. From the Tasks tab, choose Run Download Cacher Tool – Red Hat Enterprise. The Task window opens. © 2007 by BigFix, Inc. BigFix Patch Management for RedHat Enterprise Linux Page 3 2. Select the appropriate Actiont link.
  • Microsoft Plays Hardball: Use of Exclusionary Pricing and Technical

    Microsoft Plays Hardball: Use of Exclusionary Pricing and Technical

    Antitrust Bulletin, XL:2, Summer 1995, 265-315 MICROSOFT PLAYS HARDBALL: The Use of Exclusionary Pricing and Technical Incompatibility to Maintain Monopoly Power in Markets for Operating System Software† by KENNETH C. BASEMAN* FREDERICK R. WARREN-BOULTON* and GLENN A. WOROCH** May 1995 ___________________ * Principals, MiCRA: Microeconomic Consulting and Research Associates, Inc., Washington, DC. ** University of California, Berkeley. † Forthcoming, Antitrust Bulletin, June 1995. We would like to express our appreciation for helpful comments and other assistance to Sturge Sobin, Linnet Harlan, Paul Dennis and the participants at the Columbia Business School's Institute for Tele-Information's Seminar on Sustaining Competition in Network Industries through Regulating and Pricing Access, especially Janusz Ordover and Bobby Willig. TABLE OF CONTENTS I. INTRODUCTION AND SUMMARY ................................... 1 II. BACKGROUND .................................................... 3 A. THE MARKET FOR PERSONAL COMPUTER OPERATING SYSTEMS ............................................................ 3 TABLE: NEW SHIPMENTS OF PERSONAL COMPUTER OPERATING SYSTEMS .............................................. 8 B. MICROSOFT'S PRACTICES ..................................... 9 III. FIRST-DEGREE PRICE DISCRIMINATION vs. INEFFICIENT SUBSTITUTION ................................................... 15 A. FIRST-DEGREE PRICE DISCRIMINATION ........................ 16 B. INEFFICIENT SUBSTITUTION ................................. 20 IV. ANTIFRAUD AND ANTIPIRACY