Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!husc6!husc4!nakada
From: nakada@husc4.HARVARD.EDU (Paul Nakada)
Newsgroups: comp.sys.apple
Subject: Re: Binscii mess
Message-ID: <1573@husc6.harvard.edu>
Date: 7 Apr 89 12:41:50 GMT
References: <8904062148.aa13319@SMOKE.BRL.MIL>
Sender: news@husc6.harvard.edu
Reply-To: nakada@husc4.UUCP (Paul Nakada)
Organization: Harvard University Science Center, Cambridge MA
Lines: 28


From article <8904062148.aa13319@SMOKE.BRL.MIL>, by SEWALL@UCONNVM.BITNET (Murph Sewall):
>>  Proterm's Kermit sure messed up my Hyper C download -- in BinSCII format,
>>but Executioner format is fine. I've been downloading Executioner format
>>files with Proterm for a long time now.
> 
> Other messages indicate that which version of ProTerm your using makes a
> BIG difference.  It would be helpful if comments referring to ProTerm's
> problems (or lack of them) specified which version is in use.
> 
> Murph Sewall                       Vaporware? ---> [Gary Larson returns 1/1/90]

the key feature of binscii is that kermit is not necessary as far as
transfer protocols are concerned.  A straight binary transfer will
suffice since binscii can deal with different types of line terminators,
(which kermit normally fiddles with).. for users of proterm, i recommend
using any of the binary transfer protocols (xmodem, ymodem) which are
almost always available on your host machines (if not talk to your
system administrator, because they should be)

-paul nakada

 __
|     Paul Nakada  '89   #8-)  |                                          
      North House              |                nakada@husc4.HARVARD.EDU  
      Harvard College          |       seismo>!harvard!husc4!nakada.UUCP  
      Cambridge, MA  02138     |     rutgers/   nakada@husc4.BITNET       
      617/498-6255 || 6264     |                                         __|