Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!usc!nic.csu.net!csun!aurora!swalton
From: swalton@aurora.csun.edu (Stephen Walton)
Newsgroups: comp.sys.amiga.datacomm
Subject: Re: Extended packet size with Handshake Kermit
Summary: setenv XPRKERMIT "OP500,B3"
Message-ID: <1991Feb17.023922.23786@csun.edu>
Date: 17 Feb 91 02:39:22 GMT
References: <21080@know.pws.bull.com>
Sender: news@csun.edu (News Administrator)
Organization: California State Univ., Northridge
Lines: 25

In article <21080@know.pws.bull.com> emcphers@fox.cs.vt.edu (Frank McPherson) writes:
>
>Is it possible to convince the Kermit in Handshake 2.20c to receive extended
>packet lengths?  If so, how?  

Assuming that Handshake supports the usual XPR conventions, you should be
able to select an "XPR Setup" menu item, or maybe send a setup string to
the XPR.  Sending a string starting with O to XPR Kermit means you are
setting options;  "OP500" sets packet length to 500, for example.

Before startup of your program, you should also be able to set the XPRKERMIT
environment variable to the desired setup string.  "OP500,B3,TY" will
/ss/set/p
/pacc/s//pac/p
/pacck
/pacck
/pacck/
/op500
/OP500/
set the default options to Packets of 500 bytes, Block check of 3, and
Text file mode to Yes (On).
-- 
-------------------------------
Stephen Walton, Dept. of Physics & Astronomy, Cal State Univ. Northridge
   I am srw@csun.edu no matter WHAT the stupid From: line says!