Xref: utzoo comp.sys.ibm.pc:14327 comp.unix.questions:6519
Path: utzoo!mnetor!uunet!apctrc!zjat02
From: zjat02@apctrc.UUCP (Jon A. Tankersley)
Newsgroups: comp.sys.ibm.pc,comp.unix.questions
Subject: Re: kermit
Message-ID: <475@apctrc.UUCP>
Date: 10 Apr 88 04:29:05 GMT
References: <715@btnix.UUCP>
Reply-To: zjat02@apctrc.UUCP (Jon A. Tankersley)
Organization: Amoco Production Co, Tulsa Research Center
Lines: 18
Keywords: msdos kermit unix

I have successfully used Ckermit with ProComm(sp?) and a few others,
even CMS kermit.  A couple of things to watch out for.
	1) some kermit implementation don't synchronize properly.  Ckermit
	   displays SF.....E(?) for a transfer.  ?, Q, N are all miscellaneous
	   error packets - N for Nack.  If it doesn't get past the F it is
	   probably a sync problem.  Another problem is the translation
	   character set.  Kermit HAS to have the same ASCII translations.
	   It uses an incremental character as a packet counter.
	2) Try it out of server mode.  Some server implementations don't work
	   very well.  A simple send/receive transmission might work.  It isn't
	   pleasant, but it gets the job done.  CMS Kermit (old version) would
	   often fail in server mode, getting 2 breaks in quick succession
	   would drop CMS into CP mode, no ifs, ands, or buts.
	3) try reversing the transfer if possible.
	4) Get Xmodem,Ymodem,Zmodem for UNIX and the PC.  They also work most
	   of the time.

-tank-