The Last Great Commodore 64 Commercial Software Sale
Total Page:16
File Type:pdf, Size:1020Kb
Load more
Recommended publications
-
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. -
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). -
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. -
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 -
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 -
Imperial College of Science and Technology, University of London, Department of Computing
Imperial College of Science and Technology, University of London, Department of Computing. HIGH EFFICIENCY, CHARACTER-ORIENTED, LOCAL AREA NETWORKS by Martin Cripps This thesis is submitted in partial fulfilment of the requirements for the degree of Doctor of Philosophy and the Diploma of Imperial College of Science and Technology, January 1988. For Clare Attempt the end His reasons are as two grains of wheat but never stand to doubt hid in two bushels of chaff. nothing's so hard You shall seek all day ere you find them but search and when you have found them will find it out they are not worth the search. Robert Herrick (1591-1674) William Shakespeare (1564-1616) 1 ABSTRACT This thesis explores the problem of interconnecting character-oriented devices over local area networks by investigating significant aspects of hardware, software, protocol and operational factors. It proposes effective and efficient solutions which were tested during a full-scale experiment The results of that experiment demonstrate convenient, cost-effective and reliable operation. The novelty of this investigation arises from its character-oriented approach. Much work has been carried out by others on local area networks which transfer blocks of data efficiently, however, a large majority of installed devices operate on a character-by-character basis and will continue so to do for some considerable time. This study is approached through analysis of the low efficiency of international standard networks for this class of device which defines the scope of this work. An original analysis of the potential mechanisms which can be used to give high efficiency and low delay for this class of transfer is then derived. -
Server Operating System
Server Operating System ® White Paper Guide to Microsoft® Windows NT® 4.0 Profiles and Policies © 1997 Microsoft Corporation. All rights reserved. The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication. This White Paper is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT. Microsoft, the BackOffice logo, MS-DOS, Windows, and Windows NT are registered trademarks of Microsoft Corporation. Other product or company names mentioned herein may be the trademarks of their respective owners. Microsoft Corporation • One Microsoft Way • Redmond, WA 98052-6399 • USA 0997 Abstract This guide provides information and procedures for implementing Microsoft® Windows NT® 4.0 Profiles and Policies on client workstations and servers. A Microsoft Windows NT 4.0 User Profile describes the Windows NT configuration for a specific user, including the user’s environment and preference settings. A System Policy is a set of registry settings that together define the computer resources available to a group of users or an individual. With the addition of System Policies and the new User Profile structure to Windows NT 4.0, network administrators have a greater ability to control the user environment than they have ever had before. This document provides the details that administrators need to know to implement a rollout of User Profiles and System Policies under Windows NT 4.0. -
Electronic Bulletin Board System for the Federal Depository Library Program
GP 3.2:E1 2 Electronic Bulletin Board System for the Federal Depository Library Program: A Study Library Programs Service U.S. Government Printing Office Superintendent of Documents Washington, D.C. 1991 tr Electronic Bulletin Board System for the Federal Depository Library Program A Study Written by: Marian W. MacGilvray Joseph P. Paskoski John M. Walters Project Director: Joseph C. McClane February 1, 1991 Library Programs Service U.S. Government Printing Office Washington, D.C. U.S. Government Printing Office Robert W. Houk, Public Printer Superintendent of Documents (Vacant) Library Programs Service Bonnie B. Trivizas, Director Library Division Gil Baldwin, Chief Depository Services Staff Joseph C. McClane, Chief Any use of trade, product, or firm names in this publication is for descriptive purposes only and does not imply endorsement by the U.S. Government. Table of Contents Preface , iv I. Executive Summary and Recommendations 1 II. Introduction A. Federal Depository Library Program 2 B. Basis of the Study 2 C. Scope of the System 2 D. Study Methodology 2 III. Bulletin Board Systems - General Characteristics 3 IV. FDLP Bulletin Board System - System Description A. File Characteristics and Size 4 B. Usage Characteristics 7 C. Staffing 7 D. Telecommunications . 7 E. System Configuration Options and Costs 8 F. Implementation Schedule 11 Bibliography 13 Appendix A. Recommendations, Depository Library Council 14 Appendix B. List of Consultants 15 Appendix C. Suggestions for File Content 18 Appendix D. Alternate Technologies 20 Appendix E. Hardware and Software 25 iii Preface A preliminary draft of "Electronic Bulletin Board • the system will be beta tested with the 54 System for the Federal Depository Library Program: A regional depositories before being made Study" was completed on October 15, 1990 and available to all depository libraries. -
Copying Files with XMODEM What Is XMODEM
Copying Files With XMODEM What Is XMODEM XMODEM is a simple file transfer protocol which became extremely popular in the early bulletin board system (BBS) market, largely because it was so simple to implement. XMODEM was later replaced by….you guessed it: YMODEM* and then ZMODEM. XMODEM is an old, slow transfer protocol. So why would we ever use it? *We’ll use XMODEM in this lesson, but YMODEM is also available on Cisco devices. I am unsure if YMODEM has any advantage over XMODEM for our purposes. Transferring files via the console port You can used XMODEM to transfer files to a Cisco device when you do not have access to an FTP or TFTP server – but you do have access to the console port -and need to copy files to a Cisco device. There may be emergency situations where this may be your best – or only – method of getting files on a Cisco device. Requirements You’ll need: A terminal emulator which supports XMODEM(or YMODEM) transfers. SecureCRT(shown), Hyperterminal*, and Tera Term Pro all support XMODEM**. Access to the console port of the Cisco device. A PC with the files you want to transfer. * Microsoft – in their infinite wisdom – no longer packages Hyperterminal with Vista and Windows 7. ** I may be wrong, but I don’t believe that Putty supports XMODEM SecureCRT Tera Term Pro HyperTerminal Setting the console port speed By default the console port’s speed is 9600 baud: 2610#sh line con 0 | i Baud Baud rate (TX/RX) is 9600/9600, no parity, 2 stopbits, 8 databits You can change this with the ‘speed’ command under the console line: 2610(config)#line con 0 2610(config-line)#speed ? <0-4294967295> Transmit and receive speeds 2610(config-line)#speed 115200 Très important: You MUST match the console line speed with a speed that your terminal emulator is capable of providing. -
Command Line Interface User's Guide
Dell™ OpenManage™ Server Administrator Version 5.2 Command Line Interface User's Guide www.dell.com | support.dell.com Notes and Notices NOTE: A NOTE indicates important information that helps you make better use of your computer. NOTICE: A NOTICE indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. ____________________ Information in this document is subject to change without notice. © 2006 Dell Inc. All rights reserved. Reproduction in any manner whatsoever without the written permission of Dell Inc. is strictly forbidden. Trademarks used in this text: Dell, the DELL logo, PowerEdge, and OpenManage are trademarks of Dell Inc.; Microsoft, Windows, Windows Server, MS-DOS, and Windows NT are registered trademarks of Microsoft Corporation; SUSE is a registered trademark of Novell, Inc. in the United States and other countries; Red Hat and Red Hat Enterprise Linux are registered trademarks of Red Hat, Inc.; Intel, Pentium, and Itanium are registered trademarks and Intel386 is a trademark of Intel Corporation; AMD, AMD Opteron, AMD-V, and AMD PowerNow! are trademarks of Advanced Micro Devices, Inc.; VESA is a registered trademark of Video Electronic Standards Association; UNIX is a registered trademark of The Open Group in the United States and other countries; OS/2 is a registered trademark of International Business Machines Corporation. Other trademarks and trade names may be used in this document to refer to either the entities claiming the marks and names or their products. Dell Inc. disclaims any proprietary interest in trademarks and trade names other than its own. December 2006 Contents 1 Introduction . -
File Transfer by Xmodem Protocol Using UART Module
File Transfer by XModem Protocol Using UART Module V1.3 - Dec 22, 2006 English Version 19, Innovation First Road • Science Park • Hsin-Chu • Taiwan 300 • R.O.C. Tel: 886-3-578-6005 Fax: 886-3-578-4418 E-mail: [email protected] http://www.sunplusmcu.com http://mcu.sunplus.com File Transfer by XModem Protocol Using UART Module Important Notice SUNPLUS TECHNOLOGY CO. reserves the right to change this documentation without prior notice. Information provided by SUNPLUS TECHNOLOGY CO. is believed to be accurate and reliable. However, SUNPLUS TECHNOLOGY CO. makes no warranty for any errors which may appear in this document. Contact SUNPLUS TECHNOLOGY CO. to obtain the latest version of device specifications before placing your order. No responsibility is assumed by SUNPLUS TECHNOLOGY CO. for any infringement of patent or other rights of third parties which may result from its use. In addition, SUNPLUS products are not authorized for use as critical components in life support systems or aviation systems, where a malfunction or failure of the product may reasonably be expected to result in significant injury to the user, without the express written approval of Sunplus. © Sunplus Technology Co., Ltd. PAGE 1 V1.3 - Dec 22, 2006 File Transfer by XModem Protocol Using UART Module Revision History Page Revision Date Translated By Remark Number(s) V1.3 2006/12/22 Qin Haiyan Proofreading Translate ‘File Transfer by XModem V1.2 2006/03/28 Qin Haiyan Protocol Using UART Module V1.2, Chinese version’ © Sunplus Technology Co., Ltd. PAGE 2 V1.3 - Dec 22, 2006 File Transfer by XModem Protocol Using UART Module Table of Content PAGE 1 System Design Summary ................................................................................................................. -
X/84 Documentation Release 2.0.15
x/84 Documentation Release 2.0.15 Jeff Quast Jun 17, 2020 Contents 1 Introduction 3 1.1 Quickstart................................................3 1.2 Documentation, Support, Issue Tracking................................4 2 Project Details 5 2.1 Compatible Clients............................................5 2.2 Binding to port 23............................................6 2.2.1 Linux..............................................6 2.2.2 Solaris 10............................................6 2.2.3 BSD...............................................6 2.2.4 Other..............................................6 2.3 Other Telnet BBS Systems........................................7 2.3.1 How x/84 compares.......................................7 2.4 History..................................................8 2.5 What does x/84 mean?..........................................8 2.6 Future Directions.............................................8 3 Running a message server 11 3.1 Configuring a hub............................................ 11 3.2 Configuring a leaf node......................................... 12 3.3 Authorship................................................ 12 4 Doors 13 4.1 Dosemu.................................................. 14 5 Web server 15 5.1 Starting a web server........................................... 15 5.2 Lookup path............................................... 16 5.3 Serving static files............................................ 16 5.4 Writing a web module.......................................... 16 5.4.1