3-Oct-84 00:15:54-EDT,5823;000000000001 Return-Path: Received: from amelia.ARPA (AMELIA-EC.ARPA.#Internet) by CU20B.ARPA with TCP; Wed 3 Oct 84 00:15:36-EDT Date: Tue, 2 Oct 84 21:17:19 pdt From: Dave Tweten Message-Id: <8410030417.AA02739@amelia.ARPA> Received: by amelia.ARPA; Tue, 2 Oct 84 21:17:19 pdt To: +outgoing@AMES-NAS-GW.ARPA, INFO-KERMIT@CU20B.ARPA Subject: 170Kermit on NOS 2.3, Bug Fixes Cc: Knutson@UT-NGP.ARPA, Russel@NYU.ARPA In a selfish attempt to get Kermit implemented on a machine I occasionally use, some time back I gave a copy of the latest 170Kermit to a friend at CDC's Sunnyvale installation, Ted Brown. I succeeded beyond my greatest expectation. Not only does it work well on the Sunnyvale CDC machines, but Ted offered to let me relay what he learned about 170Kermit back to Info-Kermit. If you wish to communicate to Ted through the net (CDC Sunnyvale isn't connected), feel free to relay the message through me. What follows is Ted's message: Date: 2 October 1984 To: Info-Kermit@CU20B.ARPA Knutson@UT-NGP.ARPA Russel@NYU.ARPA From: Ted Brown, Control Data Corporation Subject: Corrections to Kermit-170 Version 2.2 for NOS I recently received a copy of Kermit-170 Version 2.2 and encountered some problems when installing and executing it in the standard release of NOS Version 2.3 (PSR Level 617). Following is a description of each problem, and attached to this letter is a NOS CCL procedure that properly installs Kermit-170 with corrections for all the problems. The procedure assumes the existence of a direct access permanent file named KERMITS that contains the UPDATE source for the Kermit PL in the first logical record and the source for the AZLIB PL in the second. 1. The installation instructions in the documentation file are missing some parameters and control statements. 2. Assembly errors occur due to incorrect usage of quotation marks and apostrophes in micro definitions. 3. The default data mode (DISPLAY) is inconvenient. ASCII would be more appropriate for the majority of file transfers. 4. The terminal parameters for PW, PG, and EB are not restored after terminating binary mode. Although it is not possible to determine their original values, they could be set to something with less negative impact for the majority of users. 5. Subroutine CONBUFF aborts if Kermit is not compiled with OPT=0 due to an instruction that is overwritten by subroutine CFE when it clears the FET that is adjacent to CONBUFF's entry point. 6. Single-character inputs are incorrectly processed. Specifically, a question mark for help is not recognized due to a parsing error in subroutine CONBUFF. Please feel free to contact me if you have any questions about my code. Thank you very much for the excellent job that you are doing to support and distribute Kermit! Ted Brown Central Software Support Control Data Corporation 215 Moffett Park Drive Sunnyvale, California 94089 408/744-5521 800/328-9567 ________________________________________________________________________ .PROC,KERMITI. ASSIGN,MS,OUTPUT. ATTACH,KERMITS. ATTACH,KERMIT/M=W. UPDATE,I=KERMITS,N=KERMUPL. UPDATE,I=KERMITS,N=AZLBUPL. UPDATE,F,P=AZLBUPL,I=KERMITM. COMPASS,I,S=PSSTEXT,S=SYSTEXT,A. LIBGEN,P=AZLIB. UPDATE,F,P=KERMUPL,I=KERMITM. REWIND,LGO. FTN5,I,S=PSSTEXT,S=SYSTEXT,OPT=2. FTN5,I,S=PSSTEXT,S=SYSTEXT,B=LIBREL,OPT=2. LIBGEN,F=LIBREL,P=KERMLIB. LDSET,MAP=SBEX. LOAD,LGO. NOGO,KERMIT. DAYFILE,,KERMITI. RENAME,KERMITL=OUTPUT. REVERT.KERMITI. EXIT. DAYFILE,,KERMITI. RENAME,KERMITL=OUTPUT. REVERT,ABORT.KERMITI. .DATA,KERMITM. *ID EWB840918 */ */ EXCHANGE QUOTES AND APOSTROPHES THAT CAUSED ASSEMBLY ERRORS */ *D MACREL.947 ^%S'MCS1 MICRO 1,, S *D MACREL.950 ^%S'MCS1 MICRO 1,, T *D MACREL.954 ^%S'MCS2 MICRO 1,, S *D MACREL.957 ^%S'MCS2 MICRO 1,, T *D MACREL.960 RJ =X"^%S'MCS1"X"^%S'MCS2"> *D MACREL.1048 ^%S'MCS1 MICRO 1,, S *D MACREL.1051 ^%S'MCS1 MICRO 1,, T *D MACREL.1055 ^%S'MCS2 MICRO 1,, S *D MACREL.1058 ^%S'MCS2 MICRO 1,, T *D MACREL.1061 RJ =X"^%S'MCS1"X"^%S'MCS2"> .EOR. *ID EWB840918 */ */ DEFINE STANDARD NOS SYSTEM */ *DF NOS *DF OTHER *DF 642CSET *DF OVCAP *ID EWB840930 */ */ CHANGE DEFAULT DATA MODE FROM DISPLAY TO ASCII */ *D KERMIT.709 DATA DSKCSET / DSKNOS8 / *D KERMIT.1207 +INS 8-BIT ^A^S^C^I^I DATA. ^THE DEFAULT IS ^A^S^C^I^I.\N\N') *D KERMLIB.2513 INTEGER NOSITM(5), NOSTTM(3), NOSFULL, NOSHALF, */ */ RESTORE PW, PG, AND EB PARAMETERS AFTER TERMINATING BINARY MODE */ *D KERMLIB.2517 C SET PW=0,CI=0,LI=0,PG=N,UBL=15,UBZ=200,EB=EL,FA=Y,CP=N,LK=Y *D KERMLIB.2524 C SET PW=80,PG=Y,EB=EB,FA=N,CP=Y,LK=N *D KERMLIB.2526 DATA NOSTTM / O"00164043412040454001", O"41014002406740004107", + O"40014040400000000000" / *D KERMLIB.2636 CALL WRITEW(FETS(0,STDOUT),NOSTTM, 3) *ID EWB841001 */ */ ELIMINATE RUNTIME ABORT THAT OCCURRED IF NOT COMPILED WITH OPT=0 */ *D KERMLIB.3701 CFEA BSSZ 5 FAKE FET */ */ CORRECTLY PROCESS ALL SINGLE-CHARACTER INPUTS (E.G., QUESTION MARK) */ *D KERMLIB.3765 LPS = 12 .EOR. *ID DEBUG */ */ TEMPORARY CHANGES FOR TESTING PURPOSES */ *D KERMIT.7 *D KERMIT.568,KERMIT.572 *D KERMLIB.3710 DATA CONBUG / .TRUE. / ________________________________________________________________________ That's the end of Ted's message. Let me add that if you accept Ted's proposed change of the default character code, a change will be required in the documentation for SET DATA-MODE. 13-Feb-86 07:14:35-EST,1603;000000000001 Return-Path: Received: from ngp.UTEXAS.EDU by CU20B.COLUMBIA.EDU with TCP; Thu 13 Feb 86 07:14:30-EST Posted-Date: Wed, 12 Feb 86 12:08:33 cst Received: from walt.UTEXAS.EDU by ngp.UTEXAS.EDU (4.22/4.22) id AA18990; Wed, 12 Feb 86 12:10:36 cst Received: from huey.UTEXAS.EDU by walt.UTEXAS.EDU (2.0/4.22) id AA20790; Wed, 12 Feb 86 12:10:11 cst Date: Wed, 12 Feb 86 12:08:33 cst From: knutson@huey.UTEXAS.EDU (Jim Knutson) Message-Id: <8602121808.AA09452@huey.UTEXAS.EDU> Received: by huey.UTEXAS.EDU (2.0/4.22) id AA09452; Wed, 12 Feb 86 12:08:33 cst To: info-kermit@cu20b.ARPA Subject: THE FROG for 64-bit CDC's? I am no longer working with Cybers anymore so my support of Cyber Kermit has become rather limited. I would like to see support for it continue on a "real" Cyber site (not this homegrown OS stuff). Basically, the support needed is finish server support and be willing to write tapes for other CDC sites. Perhaps a general cleanup of all the nasty conditional code is in order also. Anyone willing to take this on should contact me to obtain all the materials I have. It is interesting to see that other sites are writing Kermits to run on CDC equipment. I can understand writing in Pascal but writing one in Compass makes me shudder. I have had to support several Compass programs in the past and it is a nightmare when trying to make mods. I wish them all the luck in the world in that endeavor. Jim Knutson ARPA: knutson@ngp.UTEXAS.EDU UUCP: {ihnp4,seismo,kpno,ctvax}!ut-sally!ut-ngp!knutson Phone: (512) 471-3241 Date: Fri, 19 Sep 86 00:34:12 edt From: Don Barry To: info-kermit@CU20B.COLUMBIA.EDU In response to your request for evaluations of the existing cyber 170 series kermits, we have installed both kermits at this site (running cdc 855 and 990 m machines). The fortran kermit (from UT) is specific to their system in many ways because they run a homebrew operating system (taurus) instead of NOS. this even has a unique character set, posing formidable conversion tasks. it was done here, but the results were not impressive - inefficient in speed, occasional bugs. A systems programmer wrote a kermit for local use in CDC CYBIL (a high level systems programming language) but it is bug-ridden and of comparable efficiency to UT kermit. If you'd like a copy, he can probably be persuaded to part with one - his address on bitnet is CC100td TD at GITVM1. Overall, the clear winner is Manchester KERMIT in CDC COMPASS. THis is very well written, modular, commented well, and 5 times faster than either of the previous CDC kermits. Its only deficiency is requirement of parity specification at compile time and inability to do 8-bit transfers without quoting. These should be easy enough to add - even without, it is far and above the best-designed kermit for CDC equipment. The CYBIL version, after appropriate debugging and efficiency enhancement, will prove eventually worth supporting, as it will run under NOS/VE without major change, whereas the assembly version will be useless. Don Barry (Chemistry Dept) CSnet: cmpbsdb%gitpyr.GTNET@gatech.CSNET Georgia Institute of Technology BITNET: CMPBSDB @ GITVM1 Atlanta, GA 30332 ARPA: cmpbsdb%gitpyr.GTNET%gatech.CSNET@csnet-relay.ARPA UUCP: ...!{akgua,allegra,amd,hplabs,ihnp4,seismo,ut-ngp}!gatech!gitpyr!cmpbsdb 1-Oct-86 18:35:35-EDT,1494;000000000001 Return-Path: Received: from ngp.UTEXAS.EDU by CU20B.COLUMBIA.EDU with TCP; Wed 1 Oct 86 18:35:31-EDT Posted-Date: Tue, 30 Sep 86 10:46:01 cdt Received: from huey.cc.utexas.edu by ngp.UTEXAS.EDU (4.22/4.22) id AA16558; Wed, 1 Oct 86 16:59:07 cdt Date: Tue, 30 Sep 86 10:46:01 cdt From: knutson@huey.cc.UTEXAS.EDU (Jim Knutson) Message-Id: <8609301546.AA13674@huey.cc.utexas.edu> Received: by huey.cc.utexas.edu (2.2/4.22) id AA13674; Tue, 30 Sep 86 10:46:01 cdt To: SY.FDC@CU20B.COLUMBIA.EDU Subject: Re: [Christine M Gianone : [Don Barry :]] Cc: reeder@ngp.UTEXAS.EDU I haven't used any of the other Cyber Kermits. I do admit that the FORTRAN version is fairly slow (~50% of the baud rate) and that it has lots of system dependencies in it. However, it is/has been ported to NOS/BE, NOS 1.x, NOS 2.x, and UT-2D and it contains conversion code for several of the character sets that CDC has chosen to inflict upon its users. The draw back is that I haven't been working on a Cyber (or Cyber Kermit) for over a year now. The person that has been handling the requests we get for Cyber Kermit is William Reeder (reeder@ngp.utexas.edu). I'm not sure if he is supporting it beyond writing tapes for distribution. In terms of support and ease of porting, the COMPASS version may be best for other CDC sites with "standard" operating systems. Jim Knutson 11-Aug-87 14:41:36-EDT,1425;000000000001 Mail-From: SY.KEN created at 11-Dec-86 15:05:35 Return-Path: Received: from ngp.utexas.edu by CU20B.COLUMBIA.EDU with TCP; Thu 11 Dec 86 15:05:58-EST Posted-Date: Thu, 11 Dec 86 14:02:15 cst Received: by ngp.utexas.edu (5.51/5.51) id AA01452; Thu, 11 Dec 86 14:06:04 CST Date: Thu, 11 Dec 86 14:02:15 cst From: knutson@huey.cc.utexas.edu (Jim Knutson) Message-Id: <8612112002.AA12834@huey.cc.utexas.edu> Received: by huey.cc.utexas.edu (2.2/4.22) id AA12834; Thu, 11 Dec 86 14:02:15 cst To: SY.FDC@cu20b.columbia.edu Subject: Re: [Steve Roseman : More on Multiple CDC Kermits] Cc: LUSGR%LEHICDC1.BITNET@wiscvm.wisc.edu Personally, I feel that the CDC versions of kermit for the version I wrote (the fortan version), should probably be split into seperate versions. The code for trying to manage several operating systems and approximately 5 different character sets is horrendous. I would be in favor of ripping out all non-nos code (that means NOS/BE and, sniff, UT-2D). A NOS/VE version will probably have to be done seperately because of the word size differences and all. I have not had many calls from NOS/BE sites lately and very few calls from NOS/VE sites as well. However, I must say that I really haven't been maintaining the Cyber version of Kermit for quite a while now so perhaps my suggestions should be tempered by that.