Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!ut-sally!stevew
From: stevew@ut-sally.UUCP (Steve Williams)
Newsgroups: comp.sys.mac
Subject: Re: RedRyder & Kermit
Message-ID: <8457@ut-sally.UUCP>
Date: Thu, 9-Jul-87 15:35:25 EDT
Article-I.D.: ut-sally.8457
Posted: Thu Jul  9 15:35:25 1987
Date-Received: Sun, 12-Jul-87 06:23:03 EDT
References: <7014@shemp.UCLA.EDU> <434@osupyr.UUCP>
Distribution: na
Organization: U. Texas CS Dept., Austin, Texas
Lines: 23
Summary: Red Ryder's Kermit is )_*@#$

In article <434@osupyr.UUCP>, czei@osupyr.UUCP (Michael S Czeiszperger) writes:
> I've had similar problems using kermit running on a VMS vax.  (I'm
> going to assume that's what operating system your VAX was using,
> you didn't say.)  I tracked the problem down to the way that VMS
> kermit stores the data.  My transfers kept bombing when a file
> over a certain size was sent, which just happened to be the same
> size as a system parameter limiting maximum record sizes.  It would
> appear that VMS kermit tries to store transfered files in one huge
> record.  If you're still having problems check the record size
> limitations of the operating system.
This was in response to an earlier note about Kermit transfers with the program
Red Ryder.

Yes, the Vax is indeed trying to store everything in one record!  Red Ryder's
Kermit module is a piece of crap.   It doesn't do the proper CR -> CR/LF
mapping that is needed during Kermit text file transfers.  Since the Vax 
ever sees a CR/LF pair (Kermit's end of record marker) it never puts an end
of record in the file!  It is NOT the VMS Kermit's fault.  It is NOT VMS's
fault. It is Red Ryder's fault!

As I have said before:  GET MAC KERMIT!!!!!!

Steve Williams