Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!lll-crg!rutgers!sri-unix!hplabs!cae780!tektronix!uw-beaver!uw-june!geops!uw-atm!james From: james@uw-atm.UUCP (James M Synge) Newsgroups: comp.sys.amiga Subject: Re: Problem with Kermit in vt100 v2.2 Message-ID: <51@uw-atm.UUCP> Date: Thu, 13-Nov-86 09:25:12 EST Article-I.D.: uw-atm.51 Posted: Thu Nov 13 09:25:12 1986 Date-Received: Fri, 14-Nov-86 06:02:33 EST References: <576@cubsvax.UUCP> Distribution: net Organization: Dept. of Atmospheric Sciences, U. of Washington Lines: 21 Summary: Place your remote machine in SERVER mode! 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. The first file > got transfered, the remote kermit went away, and the vt100 kermit sat > there trying to send the rest of the files to noone. Any ideas? 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. They allow the remote host to handle multiple transactions with out "intervention" for every transaction. Thus you could send 3 files, receive 1, send 1 more, then quit, all this with only one command type to the server. Of course you would be typing the names of several files on the Amiga, but it cann't guess the files! james. -- --------------------------------------------------------------------------- James M Synge, Department of Atmospheric Sciences, University of Washington VOX: 1 206 543 0308 (Work) 1 206 455 2025 (Home) UUCP: uw-beaver!geops!uw-atm!james ARPA: geops!uw-atm!james@beaver.cs.washington.edu