CDC Cyber Kermit Version 3 Available. 3/19/87 A new version of Kermit is available for CDC Cybers running NOS. It is derived from the U of Texas Fortran 5 Kermit, with NOS/BE and UT2D support removed. It contains the following new features and changes (items 8 through 10 are new for Version 3.3.) 1. Wildcard file names on the SEND command and server GET command. A '*' stands for any 0 or more characters. A '?' stands for any one character. For example: *BUG All files ending in BUG. *DOG* All files containing DOG. F* All files starting with F. F?X* All files whose names start with F and contain X in the the third position, followed by 0 or more characters. 2. Local and permanent file SEND and server GET. If no local files match the request, the user's permanent file catalog is searched. If the specified file name is preceeded by 'L:', only local files are sent. If preceeded by 'P:', only permanent files are sent. 3. A DIRECTORY command and server REMOTE DIRECTORY command. Lists local (by default) or permanent file names. Accepts wildcards and/or L: and P: specifications (above). 4. Automatic recognition of DISPLAY CODE, 6/12 ASCII, and 8/12 ASCII file text modes on SEND. Receives 6/12 ASCII by default. The SET FILE-MODE command allows BINARY and TEXT file types. SET TEXT-MODE allows AUTO to set automatic recognition (above), or DISPLAY, 6/12-ASCII, or 8/12-ASCII to force a specific character translation for TEXT file mode. BINARY file mode stores characters as 7.5 8-bit characters per 60 bit Cyber word. 5. Supports repeated character compression (if the micro Kermit allows). 6. Supports long file transfer packets up to 1000 characters (if the micro Kermit allows). Use the SET RECEIVE PACKET 1000 command within Cyber Kermit to enable long packet receive. To send long packets, enter the above command in your micro Kermit, if it supports long packets. 7. Cyber Kermit no longer affects the parity of your terminal connection. If you have trouble sending or receiving files, check your parity setting. On the Cyber, the parity at login is set to NONE. Note that changing your terminal class (TC parameter) via TRMDEF or %TC=?? will reset your parity setting. 8. ***New for V3.3*** (May, 1987) Kermit will take commands from the file KERMINI at startup time. You may use this to set non-standard parameters, start up an server automatically, etc. Kermit will first look for a local KERMINI, then for a permanent file KERMINI. 9. ***New for V3.3*** There is now a TAKE filename command to direct Kermit to read its commands from a local or permanent file. It searches for local and permanent files like the SEND command, above. 10. ***New for V3.3*** When files are being received by the Cyber, Kermit will now attempt to use up to 3 characters of the micro's filename's extension as part of the Cyber's file name. This allows file transfers of the form LONGNAME.* to proceed with fewer file name conflict problems. Please contact me if you have any problems with Cyber Kermit Version 3. Steve Roseman Lehigh University LUSGR@LEHICDC1.BITNET (215) 758-3987 ------------------------------ Date: Wed, 30 Sep 87 14:15:20 EDT From: op%VIRGINIA.BITNET@CUVMA.COLUMBIA.EDU (Olaf Pors 804-924-0633) Subject: Updates for CDC Cyber NOS Kermit (CD3KER) The files CD3KER.INS and CD3KER.MOD contain feature addition to CDC NOS Kermit (the CD3 Kermit). CD3KER.INS is a replacement for that file on the Kermit distribution. CD3KER.MOD is the only source code you need to upgrade CD3 Kermit from version 3.2 to the one I created (3.3); this file should be added to the rest of the CD3KER files on the distribution, so it can be applied using the CDC UPDATE utility. UPDATE works with a base file (usually quite large) and applies modifications (usually small) to create a file for compilation. This is the way that CDC maintains their system software, and I think CD3 Kermit should be handled this way too; i.e., have a large, unchanging base file and a small modification on the distribution. New changes would be added to the modification file until it gets too unwieldy, at which time a new base file would be created. The CD3KER.INS file I've supplied assumes the (possible) existence of such a modification file. See also the comments in CD3KER.INS. All the documentation needed concerning my enhancements (upward compatible) is at the beginning of the CD3KER.MOD file. [Ed. - Thanks, Olaf! And apologies for taking so long to bring your contribution to public light. Olaf's changes include support for 8/12 ASCII binary files, optional kinds of EOF conversion, and support for CDCNET. Unfortunately, in August 1987 (several months before you submitted this one), Steve Roseman of Lehigh University (LUSGR@LEHICDC1.BITNET) submitted another, different, version 3.3 of this program, announced in Info-Kermit V6 #17. Your files have been put in KER:CD3KER.IN2 (so as not to interfere with Steve's CD3KER.INS), and CD3KER.MOD. Meanwhile, let's hope someone will be able to reconcile the two versions and maybe produce a version 3.4?]