Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!lll-crg!styx!mordor!sri-spam!sri-unix!hplabs!cae780!tektronix!tekgvs!keithe From: keithe@tekgvs.tek.com (Keith Ericson;6276042;50-383;LP=A;) Newsgroups: comp.sys.amiga Subject: Re: Problem with Kermit in vt100 v2.2 Message-ID: <9511@tektronix.UUCP> Date: Fri, 14-Nov-86 17:55:13 EST Article-I.D.: tektroni.9511 Posted: Fri Nov 14 17:55:13 1986 Date-Received: Sun, 16-Nov-86 00:03:32 EST References: <576@cubsvax.UUCP> <51@uw-atm.UUCP> Sender: news@tektronix.UUCP Reply-To: keithe@tekgvs.UUCP (Keith Ericson) Distribution: net Organization: Tektronix, Inc., Beaverton, OR. Lines: 48 In article <51@uw-atm.UUCP> james@uw-atm.UUCP (James M Synge) writes: >In article <576@cubsvax.UUCP>, dss@cubsvax.UUCP (David Silver) writes: >> I found that I couldn't send multiple files by doing a kermit r on >> a remote machine and kermit send * on the vt100 kermit. > >It went away because it had done what you asked: it had received a single file. >Kermit had SERVERs added to the protocol to handle just this problem. Um, er, ah... NO. The UNIX kermit we have on our VAX has the following identifying strings buried in the executable: C-Kermit, 4D(060) 18 Apr 86 C-Kermit functions, 4D(049) 4 Jun 86 C-Kermit Protocol Module 4C(030), 19 Mar 86 I have exercised this version with the VT-100 v2.2 Kermit on my Amiga and with IBM-PC MS-Kermit V2.29 26 May 86. For the first experiment I started the UNIX Kermit with the instruction kermit -r MS-Kermit will successfully transfer multiple files to the Unix Kermit whereas the VT-100 v2.2 Kermit will "hang" after (successfully) sending only the first file. VT-100 v2.2 TRIES to send the subsequent file but it never gets past the status line that says File: [filename] Pckt: S Pckt No: 0 Retrn: 5 Bytes: 0 Stat: TMOUT To regain control of the Amiga I had to terminate the host (Unix) login session at which time the local (Amiga) Kermit aborted and control was returned to me. The UNIX Kermit had terminated. I then ran the MS-Kermit and the VT-100 v2.2 Kermit into a UNIX Kermit that had the logging turned on. This time I started UNIX Kermit with just the command "kermit" which invokes the interactive mode. After requesting that the packets, debugging, session and transaction information be logged into files I gave Kermit the "receive" instruction. The transaction.log for the VT-100 v2.2 did not have any mention of an attempt to negotiate the transmission of a second file, in contrast to the transaction.log for the MS-Kermit transfer which showed that indeed the UNIX Kermit had been prompted to negotiate for and receive a second file. If anyone is trying to fix this I hope this helps. keith ericson at teklabs