DOCSLIB.ORG

The Kermit File Transfer Protocol

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
The Kermit File Transfer Protocol THE KERMIT FILE TRANSFER PROTOCOL Frank da Cruz February 1985 This is the original manuscript of the Digital Press book Kermit, A File Transfer Protocol, ISBN 0-932976-88-6, Copyright 1987, written in 1985 and in print from 1986 until 2001. This PDF file was produced by running the original Scribe markup-language source files through the Scribe publishing package, which still existed on an old Sun Solaris computer that was about to be shut off at the end of February 2016, and then converting the resulting PostScript version to PDF. Neither PostScript nor PDF existed in 1985, so this result is a near miracle, especially since the last time this book was "scribed" was on a DECSYSTEM-20 for a Xerox 9700 laser printer (one of the first). Some of the tables are messed up, some of the source code comes out in the wrong font; there's not much I can do about that. Also (unavoidably) the page numbering is different from the printed book and of couse the artwork is missing. Bear in mind Kermit protocol and software have seen over 30 years of progress and development since this book was written. All information herein regarding the Kermit Project, how to get Kermit software, or its license or status, etc, is no longer valid. The Kermit Project at Columbia University survived until 2011 but now it's gone and all Kermit software was converted to Open Source at that time. For current information, please visit the New Open Source Kermit Project website at http://www.kermitproject.org (as long as it lasts). -fdc, February 2016. Foreword Page 1 Foreword It's a great pleasure to see computer programs that were written for the sheer love of it, by people who delight in improving the effectiveness of our machines. The rapid growth of Kermit as a near-universal protocol for transferring files between computers is also a convincing demonstration of the advantages of software sharing. The authors of Kermit wisely decided not to keep their ideas proprietary, and they soon found that hundreds of people were willing and able to refine and extend the system. This book is the logical next step: It presents the concepts in tutorial fashion, and gives detailed examples of the subtle pitfalls that were discovered, so that many more people will be able to learn from the accumulated experience of the pioneer Kermit volunteers. Once this knowledge becomes widespread, we can expect further advances in both hardware and software. People often mistakenly believe that low-level considerations of input and output are not part of ``real'' computer science. The truth is just the opposite. Computer scientists have a duty to understand real-world constraints and to deal with them in as ``clean'' a way as possible. Therefore I hope that many readers of this book will be challenged to find high-level concepts and invariant relations by which various versions of the Kermit protocol can be proved correct in a mathematical sense. It will be very interesting to see how this system evolves in the future. Can a de facto standard continue to rely entirely on dedicated voluntary contributions and peer pressure, or will some sort of stricter rules have to be enforced? Will a steady state be reached? And how long will it be before dictionaries of the English language include the new verb, `to kermit'---as in the sentence ``I kermitted ten files during The Muppet Show.'' Donald E. Knuth Stanford University Page 2 The Kermit File Transfer Protocol Preface Page 3 Preface This book is for everyone who needs to move information from one computer to another. It's for the growing number of people who bring work home to personal computers so they can spend more time with their families. It's for university students with microcomputers in their dormitory rooms, and for university computer centers faced with the microcomputer explosion. It's for students, teachers, hobbyists, administrators, authors, farmers, secretaries, scientists, anyone who might want to share and communicate computer data with their friends or coworkers. And it's for hospitals, space flight centers, city agencies, publishing houses, soft drink bottling plants, organizations of every kind with diverse, incompatible computers of all sizes sprouting in every room and department, who feel the same need on a grand scale. Computers are tools that should be used to improve the quality of life on earth; this book presents a tool that can improve the quality of our lives while we use computers. Kermit is a computer file transfer protocol developed at Columbia University. The Kermit protocol has enjoyed increasing popularity in recent years, enough -- I hope -- to warrant publication of this book, which is intended to serve as a compendium of Kermit information, ranging from instructions for basic use to a formal description of the Kermit protocol. I won't try to put Kermit forth as the best of all possible file transfer protocols, only to describe it as it has evolved. I hope that the result is something more -- and less -- than a typical computer software user manual: more, because it supplies the background and motivation usually lacking in manuals; less, because it does not try to describe every command and peculiarity of each and every Kermit program; there are far too many them, and they change too often. I've tried to improve upon earlier Kermit publications [6, 7, 8]1by presenting the material in a more coherent, natural sequence. Tutorial sections have been added to provide background in computing, file organization, and data communications. These are independent from the other material and may be skipped by those who don't need tutoring. Case studies illustrate ways of coping with diverse computer systems and data communications environments. The latter part of the book describes the Kermit protocol in detail, with each facet illustrated by some code from a working Kermit program. At the end are a glossary, appendices, and an index. The book should prove useful to three distinct groups of people: those who wish to use Kermit, those who wish to support its use within an organization, and those who wish to create Kermit programs. Potential Kermit users need no particular experience with computers; any necessary background can be picked up from the tutorials. Potential supporters of Kermit programs should also be able to learn whatever they need from this book, particularly from the case studies. Those who want to create Kermit programs should have a reading knowledge of the C programming language [19] to follow the program examples given in the 1Citations refer to the bibliography on page 00. Page 4 The Kermit File Transfer Protocol protocol specification. This book may also find useful application in data communication or networking courses (Kermit is a degenerate case of networking) as an introductory text or as a case study in coping with a complicated reality. Even experienced protocol designers might pick up a few useful tidbits. After all, Kermit is able to work in environments where other protocols have not been so fortunate. And in the areas where Kermit is wanting, designers can learn from our mistakes. Kermit is more than a file transfer protocol, it is also the process by which the protocol spreads and develops through the cooperation of a wide, diverse, and open international community. Most Kermit programs are written and contributed by volunteers, often working on their own time. The programs can vary markedly in both style and quality, but tend to improve with age, as improvements are added. No document can hope to pin down the Kermit universe for all time; new Kermit programs appear, old ones change, the protocol itself evolves. Even when a program remains the same, changes in the underlying machine, operating system, or communications environment can alter its behavior. This book attempts to describe Kermit as it is today, in terms specific enough to be useful yet general enough to remain valid tomorrow, and maybe even the next day. Acknowledgments Because so many have contributed to the Kermit storehouse, this book has more acknowledgments than an Academy Award acceptance speech. As you flip past these pages, I hope you will come away with a feeling for the scope of the Kermit effort. Thanks and acknowledgments must go to the Columbia University Center for Computing Activities (CUCCA, my employer), which has generously fostered our Kermit development and support efforts even when there was no apparent tangible benefit to itself; to Bill Catchings, the codesigner (with me) of the basic Kermit protocol, who worked out many of the details and wrote several Kermit programs, including the first two (for CP/M and the DECSYSTEM-20), and who suggested and coauthored the 1984 BYTE magazine article [8]; to Daphne Tzoar, who conquered IBM mainframe asynchronous communications and wrote the next two Kermit programs (IBM System/370 VM/CMS and IBM PC), and who tirelessly kept the BITNET Kermit distribution up to date; to Va,ce Kundak,ci, who advised and helped with all IBM mainframe aspects of Kermit design and implementation; to Bruce Gilchrist, director of CUCCA, and Howard Eskin, director of academic computing at CUCCA, who encouraged our early efforts and promulgated and proselytized them beyond the walls of Columbia. Bill, Daphne, and Howard are no longer at Columbia, but Kermit will haunt them long into their new careers. Acknowledgments also to Coleen Markland, Bob Tschudi, Peter Howard, and Robert Story for running the ``Kermit factory,'' and to Christine Gianone, who coordinates all of this while simultaneously
Load more

Recommended publications
  • Macwise Version 19 User's Manual
    [email protected] www.CarnationSoftware.com www.MacWise.com MacWise Version 19 User's Manual You can use Command F to find what you are looking for in this document. Introduction Terminal Emulation MacWise emulates ADDS Viewpoint, Wyse 50, Wyse 60, Wyse 370, Televideo TV 925, DEC VT100, VT220 and Prism terminals. Supports ANSI color. Esprit III color is also supported in Wyse 370 mode. MacWise allows a Macintosh to be used as a terminal -- connected to a host computer directly, by modem, or over the Internet. The emulators support video attributes such as dim, reverse, underline, 132-column modes, protected fields and graphic characters sent from the host computer, as well as enhanced Viewpoint mode. Features include phone list and dialer for modems, on-screen programmable function keys, connection scripts and more. Connectivity 1. Built in Modem 2. Telnet / TCP/IP 3. SSH Secure Shell 4. Serial ports via USB to Serial adaptor . 5. Also communicates directly with the Mac unix shell Telnet Telnet settings are under the Connection Menu. Select "Telnet" to enable telnet. Select "Telnet Connection..." to enter your Host IP address, port number and terminal type. =============================== KERMIT ================================ NOTE: If you are running Mac OS 10.13 or later, you need to also use Kermit. (There should be a check mark on "Kermit" under the Connection Menu.) Kermit is installed automatically when Mac OS 10.13 or later is detected. You can re-install kermit any time by selecting Kermit Installer from the Help Menu in MacWise. Echo Kermit Characters ( under the Connection Menu ) This is normally enabled when Kermit is enabled.
    [Show full text]
  • Technical Details of the Elliott 152 and 153
    Appendix 1 Technical Details of the Elliott 152 and 153 Introduction The Elliott 152 computer was part of the Admiralty’s MRS5 (medium range system 5) naval gunnery project, described in Chap. 2. The Elliott 153 computer, also known as the D/F (direction-finding) computer, was built for GCHQ and the Admiralty as described in Chap. 3. The information in this appendix is intended to supplement the overall descriptions of the machines as given in Chaps. 2 and 3. A1.1 The Elliott 152 Work on the MRS5 contract at Borehamwood began in October 1946 and was essen- tially finished in 1950. Novel target-tracking radar was at the heart of the project, the radar being synchronized to the computer’s clock. In his enthusiasm for perfecting the radar technology, John Coales seems to have spent little time on what we would now call an overall systems design. When Harry Carpenter joined the staff of the Computing Division at Borehamwood on 1 January 1949, he recalls that nobody had yet defined the way in which the control program, running on the 152 computer, would interface with guns and radar. Furthermore, nobody yet appeared to be working on the computational algorithms necessary for three-dimensional trajectory predic- tion. As for the guns that the MRS5 system was intended to control, not even the basic ballistics parameters seemed to be known with any accuracy at Borehamwood [1, 2]. A1.1.1 Communication and Data-Rate The physical separation, between radar in the Borehamwood car park and digital computer in the laboratory, necessitated an interconnecting cable of about 150 m in length.
    [Show full text]
  • A Kermit File Transfer Protocol for the Apple II Series Personal Computers : John Patrick Francisco Lehigh University
    Lehigh University Lehigh Preserve Theses and Dissertations 1986 A Kermit file transfer protocol for the Apple II series personal computers : John Patrick Francisco Lehigh University Follow this and additional works at: https://preserve.lehigh.edu/etd Part of the Electrical and Computer Engineering Commons Recommended Citation Francisco, John Patrick, "A Kermit file transfer protocol for the Apple II series personal computers :" (1986). Theses and Dissertations. 4628. https://preserve.lehigh.edu/etd/4628 This Thesis is brought to you for free and open access by Lehigh Preserve. It has been accepted for inclusion in Theses and Dissertations by an authorized administrator of Lehigh Preserve. For more information, please contact [email protected]. A KERMIT FILE TRANSFER PROTOCOL FOR THE APPLE II SERIES PERSONAL COMPUTERS (Using the Apple Pascal Operating system) by John Patrick Francisco A Thesis Presented to the Graduate Committee of Lehigh University in Candidacy for the Degree of Master of Science 1n• Computer Science Lehigh University March 1986 This thesis is accepted and approved in partial fulfillment of the requirements for the degree of Master of science.• (date) Professor in Charge -------------- --------------- Chairman of the Division Chairman of the Department • • -11- ACKNOWLEDGEMENTS It would be somewhat of an understatement to say this project was broad in scope as the disciplines involved ranged from Phychology to Electrical Engineering. Since the project required an extensive amount of detailed in­ formation in all fields, I was impelled to seek the help, advice and opinion of many. There were also numerous t friends and relatives upon whom I relied for both moral and financial support.
    [Show full text]
  • THE PROVISION of WIDE-AREA NETWORKING FACILITIES Dr
    - 240 - THE PROVISION OF WIDE-AREA NETWORKING FACILITIES Dr Barrie J Charles Joint Network Team of the Computer Board and Research Councils, c/o Rutherford Appleton Laboratory, CHILTON, Didcot, Oxon 0X11 OQX, UK ABSTRACT The academic community in the United Kingdom is currently engaged in an extensive programme to provide comprehensive networking facilities within and among the 47 universities and numerous research institutions in the British Isles. The programme is described and the possible provision of similar facilities on an international scale discussed. 1. INTRODUCTION Since the 1960s, funds for large scale computers in universities and academic research institutes in the United Kingdom have been provided centrally through organisations reporting to the Department of Education and Science. This central funding made possible the establishment of national or regional facilities designed to handle the needs of users which could not be met by an institution's local computing equipment. The distance between these users and the central machines encouraged the early establishment of data communication facilities. Today the primary requirements for wide-area networks are seen as: access to large national or regional centres; facility or resource sharing between sites; database access; electronic mail; software distribution; a tool for multi-site scientific collaborations; a means for the itinerant worker to access his home base. Many of these activities are also now becoming practical internationally and local networks are seen as satisfying similar requirements on a smaller geographical scale. - 241 - HISTORY During the early to mid 1970s many separate networks were set up in the UK academic community. These were based either on the packet- switching techniques made popular by the advent of the ARPA network in the United States or on proprietary RJE protocols such as IBM HASP, CDC 200UT or ICL 7020.
    [Show full text]
  • Information Technology: Applications DLIS408
    Information Technology: Applications DLIS408 Edited by: Jovita Kaur INFORMATION TECHNOLOGY: APPLICATIONS Edited By Jovita Kaur Printed by LAXMI PUBLICATIONS (P) LTD. 113, Golden House, Daryaganj, New Delhi-110002 for Lovely Professional University Phagwara DLP-7765-079-INFO TECHNOLOGY APPLICATION C-4713/012/02 Typeset at: Shubham Composers, Delhi Printed at: Sanjay Printers & Publishers, Delhi SYLLABUS Information Technology: Applications Objectives: • To understand the applications of Information technology in organizations. • To appreciate how information technology can help to improve decision-making in organizations. • To appreciate how information technology is used to integrate the business disciplines. • To introduce students to business cases, so they learn to solve business problems with information technology. • To introduce students to the strategic applications of information technology. • To introduce students to the issues and problems involved in building complex systems and organizing information resources. • To introduce students to the social implications of information technology. • To introduce students to the management of information systems. S. No. Topics Library automation: Planning and implementation, Automation of housekeeping operations – Acquisition, 1. Cataloguing, Circulation, Serials control OPAC Library management. 2. Library software packages: RFID, LIBSYS, SOUL, WINISIS. 3. Databases: Types and generations, salient features of select bibliographic databases. 4. Communication technology: Fundamentals communication media and components. 5. Network media and types: LAN, MAN, WAN, Intranet. 6. Digital, Virtual and Hybrid libraries: Definition and scope. Recent development. 7. Library and Information Networks with special reference to India: DELNET, INFLIBNET, ERNET, NICNET. Internet—based resources and services Browsers, search engines, portals, gateways, electronic journals, mailing 8. list and scholarly discussion lists, bulletin board, computer conference and virtual seminars.
    [Show full text]
  • CS5865 Laboratory #1 Notes File Transfer Protocols
    1 CS5865 Laboratory #1 Notes File Transfer Protocols - An Overview Dr. B.J. Kurz XMODEM (Ward Christensen, 1970), one of the earliest ‘industry standard’ file transfer protocols in the public domain. HDX operation, character (byte)-oriented, fixed-length 128-byte blocks, 8-bit characters (bytes), 8-bit BCC = sum-mod256, stop-wait ARQ, block counts, binary data capability. Poor error detection capability, typically 95%. data block format: SOH/count/1’s compl. count/ user data/BCC control block format: ACK or NAK (or C), EOT Several later versions of XMODEM are in use: XMODEM-CRC same as regular XMODEM above except uses 8-bit BCC = CRC-8 (some implementations use 16-bit BCC = CRC-16). Better error detection capability, typically 99.97% (for CRC-8). Some versions negotiate the error character generation method: the sender first tries sum- mod256 BCC, then switches to CRC-8 BCC after three unsuccessful attempts indicated by NAKs from the receiver. XMODEM-1K same as XMODEM-CRC except uses 1024-byte blocks for better throughput (fewer line- turn-arounds), but slightly degraded error detection performance. WXMODEM a sliding-window version of XMODEM. Group size is fixed as 4 blocks. Much improved throughput. FDX capable lines needed if continous-ARQ error recovery used. YMODEM (Chuck Forsberg) a variation of XMODEM-1K. Supports two block lengths of 128 bytes and 1024 bytes, uses 2-byte CRC-16, excellent error detection capability, typically 99.99%. KERMIT (Frank de Cruz, Columbia Univ. Comp. Center, N.Y), most popular file transfer protocol, copyrighted, over 200 implementations for various systems. This is a comprehensive 2 remote communications package including terminal emulators, storage-to-storage transfer, not only a file transfer protocol.
    [Show full text]
  • Altair CP/M 2.2AT Ver 1.1 IOBYTE Implementation
    Altair CP/M 2.2AT Ver 1.1 CP/M 2.2AT supports an Altair 8800 computer with both an Altair and Tarbell floppy controller installed. Drives A & B are Altair drives 0 & 1. Drives C & D are Tarbell drives 0 & 1. The boot drive is always Altair drive 0. The Altair controller can be either the 8" or the 5.25" (mini-disk) controller as selected by conditional assembly. The BIOS uses track buffering to improve disk performance. Compared to a non-buffered BIOS, perfor- mance of program with substantial disk I/O improves by 25% to 75%. For the Altair drives, the same disk layout used by the original versions of Altair CP/M 1.4 and 2.2 is used. For the Tarbell controller, the standard IBM SSSD soft-sectored format is used. This BIOS provides full IOBYTE support to allow use of a variety of standard Altair I/O boards. See IOBYTE below. During cold boot, the BIOS looks for a Teletype on the console port and if detected (based on baud rate), subsequently follows any CR to the console device with a NULL to give the Teletype carriage time to reach the left margin. The send null flag (SNDNULL) is located immediately following the MODE and IOBYTE in memory so it can be over-ridden if needed. This BIOS adds a disk select timeout for the Altair 8" floppy so if a non-present or empty drive is select- ed, it will eventually timeout. To still allow the operator time to insert a disk, close the door, and wait for the drive enable one-shot to expire, the default timeout is set to seven seconds.
    [Show full text]
  • Flow Control and ARQ Media Access Physical
    Data Link Layer The Data Link layer can be further subdivided into: Computer Networks application 1. Logical Link Control (LLC): provides flow and error control transport • different link protocols may provide different services, e.g., Ethernet doesn’t provide reliable network delivery (error recovery) Lecture 26: 2. Media Access Control (MAC): framing and LLC MAC Flow Control and ARQ media access physical Link Layer Services Flow Control Flow Control: What is flow control? • pacing between adjacent sending and receiving nodes • receiver telling sender to slow down Error Control: Why do you need flow control? • errors caused by signal attenuation, noise • ARQ: receiver detects presence of errors and asks sender for retransmission Flow control protocols at data link layer (single hop): • FEC: receiver identifies and corrects bit error(s), • XON/XOFF without resorting to retransmission • Stop & Wait Protocol • Sliding Window Protocol Reliable delivery between adjacent nodes • seldom used on low bit error links (fiber, some twisted pair) Similar issues and mechanisms apply at the • plays an important role in wireless links with high error rates transport layer (end-to-end) • Q: why do we need both link-level and end-end reliability? XON/XOFF Stop and Wait (S&W) Protocol ! : propagation After sending a packet, sender must wait for delay SR acknowledgment (ACK) before sending the next packet sender receiver Sender Receiver S R round-trip Algorithm: time (rtt) t • S sends stream of data Time ! : propagation • R sends XOFF, S stops transmission pkt
    [Show full text]
  • Effect of Sliding Window Techniques Over a Performance of Tcp/Ip Networks
    EFFECT OF SLIDING WINDOW TECHNIQUES OVER A PERFORMANCE OF TCP/IP NETWORKS ABBAS ABEDI JANUARY, 2018 EFFECT OF SLIDING WINDOWS TECHNIQUES OVER A PERFORMANCE OF TCP/IP NETWORKS A THESIS SUBMITTED TO THE GRADUATE SCHOOL OF NATURAL AND APPLIED SCIENCES OF CANKAYA UNIVERSITY BY ABBAS ABEDI IN PARTIAL FULLFILLMENT OF a REQUIREMENTS FOR THE DEGREE OF MASTER OF SCIENCE IN THE DEPARTMENT OF ELECTRONICS AND COMMUNICATION ENGINEERING JANUARY, 2018 ABSTRACT EFFECT OF SLIDING WINDOWS TECHNIQUES OVER A PERFORMANCE OF TCP/IP NETWORKS ABEDI, Abbas M.Sc., Department of Electronics and Communication Engineering Supervisor: Asst. Prof. Dr. Barbaros PREVEZE January 2018 The communication channels have a variety of features in the communication system and networks, particularly wireless channels. It is used in transmissions between two nodes and deals with high error rates. Such errors that occur frequently which are not easy to be avoided, have the greatest effect on the performance of a network. So, it must be concluded that error rates are for different network conditions with use of different types of sliding windows techniques. In this thesis, error correcting techniques have been investigated based on a retransmission technique they used. One of the famous retransmission techniques is sliding windows technique, which it has three sub-algorithms called: stop and wait, selective repeat, and go back N. In this work, selective repeat and go back N algorithms were taken into account, but a stop and wait algorithm was not considered since it doesn’t use any window structure in their retransmissions. Also, it always has a high delay amount with less performance compared to the selective repeat and go back N techniques.
    [Show full text]
  • Download, Including1 17N REU, Ramlink Partition, Jimymon-64 (ML Monitor)
    C 0 T E T S ISSUE Published June 1996 COMMODORE WORLD 6 Wheels-Laying More Than A Patch THE NEWS MAGAZINE FOR COMMODORE 64 » 1'■ I 1J',[ K1. Bruce Thonuu 14 GOFA-A Modulap- Pcogpamming System Fob The Coeimodore 64 http://wviw.cmiweb.am/cwhtme.hlml George Flanagan General Manager Chinks ft Christiansen ♦ Editor Review; Doug Cot Ion ♦ 24 Software: Centipede 126 E>r Gaelwe R. Gasson Advegtisinq Sales A Look ai ihe Newesi Commodore I2S BBS Program Charles A. Christiansen (413) 525-0023 ♦ Graphic Acts Doug Cotton .UMN! '♦ 26 Jusr Fob Starters by Jason Compton Electronic Pre-Press & Pointing Maiuir/Holden Helpful Hints for Handling Disk Drives ♦ 30 Graphic Interpretation by Bruce Thomas Cover Design by Doug Cotton GEOS: For ti Good lime... 32 Carrier Detect by Gaelyne B. Gasson Tclecommunicationi News & Updates 36 S16 Beat by Mark Fellows Things to Look Out For When Program/Hint- the 65X16 Commodore1" and [he respective Commodore producl names are trademarks or registered trademarks of Commodore, a 38 Over The Edge by Jeffrey L. Jones division of Tulip Compulers. Commodore World is in no way aftiliated wilrtthe owner n! ".he Commodore logo ana technology. Commodore Programming in a SuperCPU World Commodore Worla (ISSN 1078-2515) is published 8 limos annually by Creative Micro Designs. Inc.. 15 Benton Drive, Easl Longrneadow MA 01028-0646. Secono-Class Postage Paid at EasL Longmeaflow MA. (USPS «)n-801| Annual subscnpiion rale is USS29.95 fci U.S. addresses. USS35.95(orC3nada0'Maiico.USSJS.95!orallECCounlnB5. Department paymanlsmusl be provided in U S. Dollars. Mail subscriptions 2 From the Editor to CW Subscriptions, do Crestiva Micro Designs.
    [Show full text]
  • Courier V.Everything External Modem: Getting Started
    Courier V.Everything External Modem: Getting Started FINAL 4/96 p/n 1.024.492 1996 U.S. Robotics Access Corp. 8100 North McCormick Blvd. Skokie, IL 60076-2999 All Rights Reserved U.S. Robotics and the U.S. Robotics logo are registered trademarks of U.S. Robotics Access Corp. V.Fast Class and V.FC are trademarks of Rockwell International. Any trademarks, tradenames, service marks or service names owned or registered by any other company and used in this manual are the property of their respective companies. 1996 U.S. Robotics Access Corp. 8100 N. McCormick Blvd. Skokie, IL 60076-2999 USA Table of Contents About This Manual iii We Welcome Your Suggestions.............................................................iii Chapter 1 The Courier 1-1 Courier Controls, Displays, and Connectors.....................................1-3 Status Indicators ....................................................................................1-4 Features...................................................................................................1-5 Chapter 2 Installing the Courier 2-1 What You Need......................................................................................2-1 Package Contents...................................................................................2-3 Installing the Courier ............................................................................2-4 Setting the DIP Switches.......................................................................2-4 Powering On the Courier .....................................................................2-6
    [Show full text]
  • Configuration Parameters
    Good news, everyone! User Documentation Version: 2020-01-01 M. Brutman ([email protected]) http://www.brutman.com/mTCP/ Table of Contents Introduction and Setup Introduction..............................................................................................................................................................8 What is mTCP?...................................................................................................................................................8 Features...............................................................................................................................................................8 Tested machines/environments...........................................................................................................................9 Licensing...........................................................................................................................................................10 Packaging..........................................................................................................................................................10 Binaries.....................................................................................................................................................................10 Documentation..........................................................................................................................................................11 Support and contact information.......................................................................................................................11
    [Show full text]