home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
cdccyber
/
cd3ker.bwr
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
8KB
Date: 10 MAR 1987 09:36 EST
To: Frank da Cruz <SY.FDC@CU20B.COLUMBIA.EDU>
From: Steve Roseman <LUSGR@LEHICDC1.BITNET>
Subject: CD3KERM.BWR
Frank,
Please place the following note in CD3KERM.BWR. Thanks.
I have been using the new Cyber Kermit for more than 2 months, but didn't
discover a serious bug until the day it became public. It's like software
that works perfectly until the customer shows up for a demo.
The command SEND P:ABCDEFG truncated the parameter at 7 characters before
removing the P: instead of after. Place the following 2 lines in the file
KERMODS, which the install proc already looks at for mods.
*D,KERMIT.927
CALL SETVAL(FILESTR,'S',IRET,9,0,0,HLPSNFN,.TRUE.)
Sorry for the inconvenience.
Steve Roseman
Lehigh Univ.
------------------------------
Date: 09 MAY 1988 09:49 EST
From: Steve Roseman <LUSGR%LEHICDC1.BITNET@CUVMA.COLUMBIA.EDU>
Subject: Error in CD3KER, CDC Cyber NOS Kermit
There is an error in CD3KER, the CDC Cyber NOS Kermit (the Fortran one),
which prevents its use with V2.31 of MS-Kermit. CD3KER's response to an 'F'
packet contains the wrong length, which didn't bother V2.30, but does upset
V2.31. The following code fixes the problem. Please replace the current
CD3KER.BWR with this message, since the current .BWR file is out-of-date.
Thanks.
*IDENT,MAY0688
*D,KERMLIB.3426
CALL SNDPACK(Y, NUM, SLEN(FILESTR), FILESTR)
On a related note, I will be negotiating with Olaf Pors of Univ of
Virginia about who gets to incorporate his mods from last September (V7 #3),
into the standard CD3KER. I don't really have the time, but I will if
necessary.
Steve Roseman
Lehigh University Computing Center
LUSGR@LEHICDC1
------------------------------
Date: Mon, 9 May 88 16:47:20 EDT
From: Olaf Pors <op@bigfoot.acc.virginia.edu>
Subject: CDC Kermit
Keywords: CDC Cyber Kermit
I just took a look at the Kermit distribution and noticed that the CD3KER.IN2
and CD3KER.MOD files were the ones that conflicted with Steve Roseman's 3.3
version of Kermit. Late last year I downloaded Roseman's 3.3 version and
upgraded my mod to correspond (producing version 3.4), and I thought I sent
you the upgraded stuff.
In case something got dropped, here are the two files again. The first one
should be put in place of CD3KER.INS (get rid of CD3KER.IN2). The second
should be put in place of CD3KER.MOD. There's also an updated CD3KER.HLP.
Olaf Pors, University of Virginia
[Ed. - Thanks, Olaf. The updated files have been put in right places.]
------------------------------
Date: Fri, 27 May 88 14:00:48 -0800
From: ames!tis.llnl.gov!lll-tis!lll-crg!lll-winken!uunet!convex!otto!-
jimi!unsvax.uucp!bartlett@ucbvax.Berkeley.EDU
Subject: Bug in CD3KER vs. 3.4, CDC Cyber Nos Kermit
I have been installing the latest Kermit distribution for CD3KER version 3.4
for the CDC Cyber NOS systems and I discovered an error in the CD3KER.MOD
file. The problem concerns the fact that the modified array SETTYP must be
in alphabetical order for the Fortran subroutine MATCH to work correctly.
To fix the file CD3KER.MOD replace the following four lines -
*D 1041
+ 'TEXT-MODE', BIN-MODE', 'EOR-EOF-MODE' /
*D 1046
GO TO (20,30,40,10,50,70,75,80,90,100,110,120), INDX
with the following six lines -
*D 1039,1041
DATA SETTYP / 'BIN-MODE', 'DEBUG', 'DELAY', 'DUPLEX',
+ 'EOR-EOF-MODE', 'FILE-MODE', 'INIT-RETRY', 'RECEIVE',
+ 'RDELAY', 'RETRY', 'SEND', 'TEXT-MODE' /
*D 1046
GO TO (110,20,30,40,120,10,50,70,75,80,90,100), INDX
I should add that I have installed CD3KER vs. 3.4 on an older Cyber NOS
l647 and everthing seems to work except for the CDCNET versus NPU test
in Program KRM0100.
Dave Bartlett
UNS Computing Services
bartlett@unsvax.uns.edu, bartlett@uns-helios.uns.edu,
or via BITNET as AC34U05@UNEV
------------------------------
Date: Tue, 30 Aug 88 15:40:09 EDT
From: kobus@nadc.arpa (D. Kobus)
To: kermit@cunixc.cc.columbia.edu
Subject: CDC CYBER KERMIT Version 3.4
1. I'm having trouble installing the subject KERMIT on our cybers. Having taken
the cd3*.* files from kermit/d, I transferred these files notitably kermsrc and
kermins on to our machine, executed the kermins procedure file, and encountered
compilation errors which I saved via the log session command. The compilation
errors are included at the end of this message.
2. Last year I successfully transferred Version 3.2 and have been frequently
using the older version without problems. I even recompiled the older version
using the older kermins and kermsrc file again without incident to double
check my compilation method.
3. Could someone review my log session and provide any suggestions to
successfully compile Version 3.4? The log session follows.....
Dave Kobus
..........................................................................
GET,KERMSRC,KERMINS
/-,KERMINS
1 FTN 5.1+650 88/08/30. 15.09.45 PAGE 1
SUBROUTINE KERMAIN 74/74 OPT=2,ROUND= A/ S/ M/-D,-DS
508 BOOLEAN FETS(0:FETL-1,MAXFILE)
>>>> COMCKER 238
FATAL * ILLEGAL USE OF OPERATOR / OPERAND -- _0 _
(hundreds of similar messages omitted)
------------------------------
Date: 12 Sep 1988 12:27 EST
From: Steve Roseman <LUSGR%LEHICDC1.BITNET@cuvmb.cc.columbia.edu>
Subject: CD3 Problems
The problem installing CD3 was due to differences in the character sets of
the CD3KER files. Most of the files are what is known in the NOS world as
6/12 ASCII files (where most characters are 6 bits long, but some, like
lower-case characters, are a pair of 6-bit characters.) However, CD3KERM.SRC
and CD3KERM.MOD are DISPLAY CODE, where all characters are 6 bits. The
problem is the caret (^), at (@), and colon (:), characters are different
between the 2 sets. So, these 2 files must be converted before compilation if
received in NOS ASCII (like most mail is.) CD3KERM.MSG contains a passing
reference to the different file formats, but I definitely not obvious enough.
I should get all the CD3KERM auxiliary files cleaned up.
So, if CD3KERM.SRC and CD3KERM.MOD are received in ASCII, it is necessary
to do an
FCOPY(P=KERMSRC,N=NEWSRC,PC=ASCII,NC=DIS,R)
and
FCOPY(P=KERMOD1,N=NEWMOD,PC=ASCII,NC=DIS,R)
and replace the KERMxxx files with the NEWxxx files.
Steve Roseman
Lehigh University
------------------------------
Date: Tue, 20 Mar 90 11:32:43 EST
From: Richter%GNOS.NIST.GOV@cuvmb.cc.columbia.edu
(Gale Richter, Computer Services Division, 975-2873)
Subject: CYBER NOS Kermit 3.4
Please add the following message to the CYBER NOS Kermit 3.4 beware
file:
CYBER NOS Kermit 3.4 developed a problem with CDCNET release 7606(16).
The problem occurred when CYBER Kermit was in server mode and several
GET commands were issued. The first GET would work as expected, but the
second GET would fail. The reason for the failure was that CDCNET was
no longer in transparent mode after the completion of the first GET.
The second GET command was not getting across to the CYBER Kermit correctly.
CYBER Kermit sets CDCNET transparent mode to Forward_Terminate and also
sets the Transparent_Forward_Character and Transparent_Terminate_Character
to <CR>. This, by the way, is now an illegal combination. The TFC and TTC
must now be set to different characters. Since each packet ends in a
single <CR>, CDCNET was exiting transparent mode with each packet. However,
CYBER Kermit was setting it back to transparent mode with each packet it
sent. The problem only became apparent when 2 packets were sent to the
CYBER Kermit without an intervening packet coming from the CYBER
(i.e., two GET commands in a row).
To solve this problem local code was added to CYBER Kermit to change
TTC to DEL (7F or FF hex.) A PSR has also been filed with CDC to report
the problem with the Forward_Terminate mode.
------------------------------