home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.apple2
- Path: sparky!uunet!cs.utexas.edu!torn!utzoo!censor!feline!gray
- From: gray@feline.uucp (Kelly Gray)
- Subject: Re: 'send *' in Kermit
- Message-ID: <1993Jan22.180046.29301@feline.uucp>
- Sender: Kelly Gray
- Organization: Humber College Technology Dept.
- References: <9301180227.AA27473@max.ee.lsu.edu>
- Date: Fri, 22 Jan 1993 18:00:46 GMT
- Lines: 35
-
- In article <9301180227.AA27473@max.ee.lsu.edu> mills@MAX.EE.LSU.EDU (John Mills) writes:
- > no, no, no. Kermit DOES do batch transfers. I use it.
- >
- > The problem may be with the Kermit on the host system. On the unix box here
- > all I do is 'kermit send *.bsq' and ALL files with '.bsq' are sent.
- >
- > On PT3.0, select 'receive kermit' and it will d/l each file sent.
- >
- > I know this works... :)
- >
- > -- John M.
- >
- > ===================================
- > INet: mills@max.ee.lsu.edu (pref)
- > AOL: jmills (@aol.com)
- > GEnie: J.MILLS11
- >
- What version of Kermit are you running on your unix box? We have a
- version of Kermit here that uses the sliding windows. I have yet to
- manage a proper download using Kermit from ProTerm 3.0, but Kermit 3.87
- handles things perfectly.
-
- I suspect that the root of the problem is that ProTerm doesn't support
- the latest features from the newer versions of the Kermit protocol.
- I suspect that ProTerm doesn't quite implement the every little detail
- of the Kermit protocol, with the result that ProTerm gets confused by
- the new command packets and gives up, aborting the transfer.
-
-
-
- --
-
- <o_o> Kelly Gray
- gray@feline.uucp (preferred)
- gray@admin.humberc.on.ca
-