Path: utzoo!censor!geac!maccs!cs4g6ag
From: cs4g6ag@maccs.dcss.mcmaster.ca (Stephen M. Dunn)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Trouble getting files from SIMTEL20
Message-ID: <258AD56C.7260@maccs.dcss.mcmaster.ca>
Date: 16 Dec 89 23:53:15 GMT
References: <4446@ur-cc.UUCP> <14759@boulder.Colorado.EDU> <2584431E.3787@maccs.dcss.mcmaster.ca> <6001@nigel.udel.EDU>
Reply-To: cs4g6ag@maccs.dcss.mcmaster.ca (Stephen M. Dunn)
Distribution: usa
Organization: McMaster University, Hamilton, Ontario
Lines: 20

In article <6001@nigel.udel.EDU> neumann@udel.edu (Brian R. Neumann) writes:
$I had this trouble and then gave up on simtel for a year.  Then someone told
$me a solution to the problem.  On the mainframe,  I invoke kermit by
$kermit -i
$      ^^^^^ to use binary mode. CRC checks are fine, and the programs run fine.

   I received more than one suggestion by e-mail to type in a set command
within Kermit to put it into binary mode.  Alas, our implementation of KErmit
does not have this particular set command, but it _does_ have the -i switch.

   One thing that's puzzling me, though, is why for files of up to 100K or
possibly more it works fine (with my Procomm Plus set to the correct mode,
be it binary or text as required), but once I hit 160-180K it chokes.  I
don't see how this could be related to setting or not setting binary mode.

-- 
Stephen M. Dunn                               cs4g6ag@maccs.dcss.mcmaster.ca
          <std_disclaimer.h> = "\nI'm only an undergraduate!!!\n";
****************************************************************************
    If it's true that love is only a game//Well, then I can play pretend