Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!mcsun!unido!gmdzi!strobl
From: strobl@gmdzi.gmd.de (Wolfgang Strobl)
Newsgroups: comp.windows.ms
Subject: Re: Win3 + Kermit 3.01; .PIF's suggestion
Message-ID: <4113@gmdzi.gmd.de>
Date: 20 Feb 91 23:16:13 GMT
References: <1991Feb19.210758.1519@javelin.es.com>
Organization: GMD, Sankt Augustin, F. R. Germany
Lines: 32

bgeer@javelin.es.com (Bob Geer) writes:

>1)	I'm using MSKermit 3.01 in a Win3 window in 386enhanced mode
>on a 386-20 w/ 5Mb using the .PIF settings shown below.  Anyone got
>any better suggestions?

I use 3.01, too.


>KERMIT.PIF
>	...
>	"x" detect idle time

I have changed this to "do not detect idle time", just to be shure
that Windows doesn't slow down Kermit because of frequent keyboard
polls.


>2)	Kermit 3.01 starts a download with 2000 byte packets for the
>first couple of data xfers (large .gif's), then the packet size drops
>into the low hundreds for the remainder of the xfer.  (Using a
>USRobotics Courier 2400 external.)  No errors are listed on the
>download display.  So, why?  Why doesn't it stick to the large packet
>size?

Perhaps because the other side doesn't like long packets? What kermit
is on the other side? Long packets are a protokol extension of kermit.
If one of both sides doesn't implement it, kermit falls back to 
short packets (i.e. packets shorter than 96 bytes).

Wolfgang Strobl
#include <std.disclaimer.hpp>