In article <1994Apr19.074113.24557@miavx1>, [log in to unmask]
(Kent Covert) writes:
> In article <1994Apr17.114030.24475@miavx1>, [log in to unmask]
writes:
>>         I Have a couple of questions about using kermit.  I have been using
>> it for a while to transfer files to my pc.  I am able to get throughput of
>> about 800-900 cps using the following settings:
>> SET XFER CANCELLATION OFF
>> SET FLOW-CONTROL XON/XOFF
>> SET WINDOW-SIZE 31
>> SET BUFFERS 9024 9024
>> SET FILE TYPE BIN
>> SEND FILENAME
>>
>>         I am using Crosstalk for Windows on an Intel 14.4 modem.  I have
>> checked all my kermit settings for Crosstalk and they seem to match, but I
am
>> never able to finish transfers greater than 200,000 bytes or so.  The screen
>> stops showing the transfer and I get an error message saying that the host
has
>> cancelled the transfer.  Is there some wayto prevent this from happening.
>
> There are a couple of problems here.
>
> 1) There was a problem with our configuration of Kermit.  Kermit on the VAX
> was set to default to no parity.  It appears that Kermit normally
> nogotiates this at the beginning of the transfer and therefore usually
> isn't a problem.  But, this negotiation was not taking place if all of the
> following conditions are true:
>     1) You are using MS-Kermit 3.11 (or a look-alike such as Crosstalk),
>     2) you are not using server mode, and
>     3) you try to download a VMS file of type STREAM_LF (which is the file
>         type of files ftp'ed in binary mode).
> We fixed this problem this morning by setting the default parity to even.
>
> 2) When using the SET FILE TYPE BINARY command, VMS actually tries to guess
> the type of the file (This seems counter-intuitive, but that's what the
> manual says).  For STREAM_LF type files, the system guesses that they're
> actually of type TEXT and will download them as such.  To tell the system
> that you REALLY mean binary mode, use the command SET FILE TYPE IMAGE.
 
Also,
3) Don't forget to issue the command SET BLOCK-CHECK 2 or SET BLOCK-CHECK 3
when using large packets (> 100 bytes).
 
--
                                     Kent Covert, Software Coordinator
                                     Miami Computing and Information Services
                                     Miami University, Oxford, OH
                                     [log in to unmask]  (internet)
                                     kacovert@miavx1                 (bitnet)