Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!think!ames!ucbcad!zen!ucbvax!UCONNVM.BITNET!SEWALL
From: SEWALL@UCONNVM.BITNET
Newsgroups: comp.sys.apple
Subject: Dead Kermit 3.79 (with SSC driver)
Message-ID: <8712021405.aa01868@SMOKE.BRL.ARPA>
Date: Wed, 2-Dec-87 13:31:00 EST
Article-I.D.: SMOKE.8712021405.aa01868
Posted: Wed Dec  2 13:31:00 1987
Date-Received: Sun, 6-Dec-87 07:25:32 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 27

Aha!  That problem sounds familiar.  If Kermit 3.xx has the SSC
driver installed, INTERRUPTS MUST BE ENABLED (SW2-6=ON on a
SuperSerial Card).  If interrupts aren't enabled, the program
will send but not receive (appears to be quite dead when CONNECTED).

If you don't have a real SSC (or you have a clone that doesn't
support interrupts) or, for other reasons, you don't want interrupts
enabled, run the INSTALL program and select the Microtek 622C
driver (works with a SSC card too but expects interrupts disabled).

If the Microtek driver is installed, then you'll lose a character
or two at the beginnings of lines at 1200 baud or faster.  I've used
Kermit 3.79 in this mode as a VT100 and the way our mainframe's
emulator addresses the screen all that disappears are a couple of
characters in the top left corner (the program is quite servicable).
I understand that at least some VAX's have a "null characters" option
that will throw a few pad (nulls) characters on the end of each line
so that what disappears are the nulls which are superfluous anyway
(nulls = 4 ought to do fine at 1200).

When all else fails, read the documenation! (also available from
KERMSRV@CUVMA).

---------------------
ARPA:   sewall%uconnvm.bitnet@cunyvm.cuny.edu       Murphy A. Sewall
BITNET: SEWALL@UCONNVM                          School of Business Admin.
UUCP:   ...ihnp4!psuvax1!UCONNVM.BITNET!SEWALL  University of Connecticut