Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!cs.utexas.edu!uunet!coplex!disk!crazyrat
From: crazyrat@disk.uucp (@jap)
Newsgroups: comp.sys.amiga.datacomm
Subject: Re: Kermit for JrComm?
Summary: problematic kermit vax AT&T ISN life fish etc
Message-ID: <1991Apr19.230557.6361@disk.uucp>
Date: 19 Apr 91 23:05:57 GMT
References: <22147@shlump.nac.dec.com>
Distribution: na
Organization: Digital Information Systems of KY
Lines: 32

In article <22147@shlump.nac.dec.com>, kendrix_j@mims.enet.dec.com (John R. Kendrix) writes:
> 
> In article <791.280868f6@zodiac.rutgers.edu>, amatthews@zodiac.rutgers.edu writes...
> >I think Jr-Comm is the nicest term out there, but unfortunately I
> >find that I am unable to use it.  The reason for this is that I
> >use a term program mostly to get on the nets, and whenever I want
> 
> Kermit is a real dog for transfering files.  Reason being that it transmits
> it's packets in 128 byte blocks.  Xmodem I believe uses a bit larger package,
> while Zmodem will use 1024 byte pages for transmitting data.  
> 

Unfortunately for a mass of us, Zmodem is not an option on our vax.  It seems
that more of the Vax installations these days are operating with an ISN 
network developed by AT&T.  This ISN network does not conform to standards
and thus does not do nice things to 'sliding packet' protocol programs
(such as Z,X,Y modem).  Kermit, btw, has had no problems in these aspects.

Our version of Vax Kermit has no problem sending and receiving at 1k packets
and there is a version on our IBM 3090 that supports 2k and 3k packets.  I'm
waiting patiently for these to be added (hopefully) to the vax.

Otherwise, I sit and wait...

@jap

-----------------------------------------------------------------------------
/The waiting pickle/

-- 
Joel C. Justen      Crazyrat Productions Ltd.
CRAZYRAT@DISK.UUCP  JCJUST01@ulkyvx.BITNET