Columbia Kermit/kermit.zip/e/mail.86a

Text File | 2020-01-01 | 383KB | 9,129 lines

 6-Jan-86 16:37:34-EST,18350;000000000001
Mail-From: SY.FDC created at  6-Jan-86 16:36:44
Date: Mon 6 Jan 86 16:36:44-EST
From: Frank da Cruz <[e-mail]>
Subject: Info-Kermit Digest V4 #1
To: [e-mail]
Reply-To: Info-Kermit@CU20B
Queries-To: Info-Kermit-Request@CU20B
Message-ID: <[e-mail]>

Info-Kermit Digest         Mon,  6 Jan 1986       Volume 4 : Number  1

Departments:

  MS-DOS KERMIT -
    New C-Kermit with Sliding Windows for PC-DOS
    Revised Modules for MS-Kermit 2.28 jrd
    Re: Fast PC/AT Kermit
    My Two Cents on the MS-Kermit 2.28 jrd "Display Problem"
    MS-DOS Kermit Terminal Emulation Query

  MISCELLANY -
    Apple DOS Kermit Bug
    Kermit for NCR Decision-Mate V?

----------------------------------------------------------------------

Date: Fri 20 Dec 85 00:05:05-EST
From: Jan van der Eijk <[e-mail]>
Subject: New C-Kermit with Sliding Windows for PC-DOS
Keywords: C-Kermit, Sliding Windows, MS-DOS Kermit

I just finished a C version of Kermit for the IBM PC/XT/AT and DOS.  It
supports the following:

    Server
    Dial command
    Script files
    Sliding window (full duplex only)
    File Attributes
    and the majority of the features from the Unix C-Kermit.

The file is called WKERMIT.EXE and the current version is 012.  The sliding
windows part is not widely supported yet but the following systems/programs
do:

     PRO-YAM      Communication package for the PC
     The SOURCE   Public info
     TCOMM        Unattended bulletin board system.

Any updates will be posted on the following TCOMM system:

   data only [phone]

If you have any questions direct them to OC.JAN@CU20B or to JAN VANDEREYK on
the previous mentioned TCOMM BBS.  To upload WKERMIT to this system took
an effective rate of 63 CPS, while using sliding windows it would have been
around 100 CPS.

[Ed. - This is the first implementation of Kermit with windows that we have
received at Columbia.  It is based on a previous release of C-Kermit,
version 4.2, edit number unknown; the current version of C-Kermit is
4C(057).  Windows-Kermit is compiled in Lattice C and uses the Greenleaf
communication libraries (which do not support XON/XOFF).  The source, .EXE,
and .BOO files are in PS:<KERMIT-W>, available via anonymous FTP from CU20B,
for evaluation only.  You may use the .BOO or .EXE file even if you don't
have the Greenleaf libraries or Lattice C.

This is not a polished product -- it needs to be integrated with the
"mainstream" C-Kermit, the DOS interface fixed up a bit, and so on.  The
reason for this posting is to get some experience and data on the windowing
option, especially when used over public networks like Telenet (which is the
normal way of getting to The Source, whose Kermit also does windows).  I'd
be very interested in any performance measurements -- e.g. the transfer of a
particular file with and without windowing, over direct or dial connections
vs over public networks, with various window sizes, etc (the baud rate, the
size of the file in bytes, and the elapsed time required to transfer it in
each case).

I would appreciate it if everyone would refrain from fixing or changing the
program on the source level until a coherent release of C-Kermit can be
produced covering not only MS-DOS, but also Unix, the Macintosh, and VMS.
Also, an up-to-date version of the windowing specification and some
supporting documentation is available in PS:<KERMIT-W>KW*.*.]

------------------------------

Date: 2 JAN 86 13:15-MST
From: JRD@USU
Subject: Revised Modules for MS-Kermit 2.28 jrd
Keywords: MS-DOS Kermit

         Updates to MS Kermit 2.28 jrd/2 as of the end of Dec 1985
                            From Joe R. Doupnik
                        CASS and EE, Utah State Univ
               [phone] (days) Bitnet user JRD node USU

    MS Kermit 2.28 jrd has undergone some internal and external upgrading
since its original posting to Columbia Univ in late November.  The responses
of numerous people testing it have helped a lot.  Thanks guys.  The significant
changes are listed below.  Oh, yes.  Files have renamed to current standards:

  mssdef.h, and the .asm files msscmd,msscom,mssfil,mssker,mssrcv,msssen,
  mssser,mssset,msxibm,msyibm,mssfin. (mssdmb.asm is gone.)

1. The single character command, C for Connect, is back.
   Also fixed the parser to allow keywords within Kermit to be in mixed case.

2. X-packet problems -- fixed, I hope.

3. Interrupting reception of a file by typing ^C, at last, deletes or keeps
   incomplete files as it should.

4. SET End-of-Line # command has been fixed to remove the suprious message
   of "?Not confirmed"; the command actually worked despite the message.

5. A bug in server mode's (lack of) use of repeat prefixes has been fixed.

6. RUN whatever now displays a leading cr/lf before DOS's response.

7. The server mode display screen has been freed of stray messages and
   retry counts, or so I hope.

[Ed. - One big problem with the MS-DOS Kermit server is that the DOS
programs it invokes -- and often DOS itself -- will put a message on the
screen and wait for the user to reply from the Keyboard; a disk problem will
evoke the familar "Abort, Retry, Ignore?" message, CHKDSK will ask you if you
want it to repair your disk if it finds something wrong (and REMOTE SPACE
invokes CHKDSK).  So if the server hangs, it's probably stuck in this
manner, and there's not much one can do about it if the server is unattended.]

8. Filenames are not automatically expanded to be ???????.??? by typing the
   escape key since the complete filename string is now a rather complicated
   object (drive and path fields, etc).

9. Half duplex systems (eg, IBM mainframes) had a problem of not hearing a
   packet if it were received too quickly after its own last transmission
   (such as an EOF response).  A new workaround waits 3 millisec (adjustable in
   the code) before sending any packet in the hope of giving the other end time
   to switch contexts from send to receive.

[Ed. -- 3 msec is about 3 character times at 9600 baud; this should be more
than adequate -- it certainly made the problem disappear for us, with our
own IBM mainframe.  Ideally, the delay should be adjustable, and should be
zero for full duplex connections.]

10. A much more serious I/O problem has been displayed (machines going poof
   or worse especially when Connecting).  My best guess is timing problems in
   the serial port interrupt handling code.  This has been revised and
   tightened considerably.

11. How to build Kermit from sources with various versions of MASM and
   LINK.  Worry no more; Kermit handles that now.  Brief tutorial (yawn):
   Kermit uses three program sections, CODE, CSTACK (was STACK), and DATAS.
   My simple changes were to rename the old STACK section to be CSTACK (sorts
   to later than CODE and earlier than DATAS) and place references to each,
   arranged alphabetically, in the assembler header file, MSSDEF.H, where they
   will be seen before any other code and hence also be in the desired
   order-of-encounter.

   One may link Kermit modules in any order at all, provided that MSSFIN is
   mentioned last.  A typical Link command file might look like this:

        msscmd+msscom+mssfil+mssker+mssrcv+msssen+
        mssser+mssset+msster+msxibm+msyibm+mssfin
        kermit;      or     kermit/map, kermit.map;

12. Internally, code for the "% completed" message has been rewritten to
   run more accurately and to work with files as large as 32 MB. Number of
   Packets still turns over at 64586; that's a lot of packets.

13. The LOG command will now supply a filename of KERMIT.LOG if you don't
   specify one, and logging now appends to the desired file (won't destroy
   old text).  One small comment on this version of Kermit is that in the
   confusion of sending stuff hither and yon I apparently did both

        Kermit> Log Prn (OK by itself), and
        Control-PrtSc (ditto)

   while within VMS Mail. My printer went into grahpics mode and slept hence
   forth.  Seems like both VMS and double printing is not a good combination.
   Mail does bad things by itself due to the escape sequences emitted, but
   double printing certainly is bad news for unknown reasons.

14. All filename handling has been strengthened.  When attempting to write
   to disk all read-only, hidden (system), and volume label files are "fully
   protected" from Kermit.

15. Get and SEND. I have had to back off a little on GET's command line to
   accomodate various filename constructions.  We are back to the manual
   whereby Get can have just one filename on its command line and that name
   can have embedded whitespace and other printable characters. If a local
   override filename is wanted invoke Get with an empty command and then
   remote and local filenames will be requested by prompts. SEND, however, has
   been modified slightly to also prompt for both names if its command line is
   empty. For both commands, the remote name has leading whitespace trimmed,
   but trailing whitespace is retained, and local filenames get full local
   inspection.

   GET and SEND permit the first character of a string to be a wild card by
   saying "#" rather than "?"; the "#" will be translated to a "?". After the
   first character of a string a "?" can be used as needed.

16. Disk I/O buffer sizes have been moved to the header file so you can
   easily change them to suit local conditions.  The logging (capture) buffer
   is set to 256 bytes, up from 128, but the main data disk buffer ("buff") is
   left at 128 bytes to keep the "% completed" display lively; note that DOS
   does full sector buffering anyway.

17. An item of note. Giving the command REM DEL B:\JUNK to an MSDOS remote
   server can lead to trouble if JUNK is a subdirectroy rather than a file.
   DOS interprets this to mean DEL B:\JUNK\*.* (oops!) and asks the server
   "Are you sure?". At this point the server Kermit hangs displaying the
   message above and the server's operator must say something on the keyboard.
   If he/she says N then DOS leaves the user in subdirectory B:\JUNK.  It's a
   DOS "feature" in at least version 2.11.  On the other hand, simply sending
   another file also named JUNK on B: results in a new file named B:\JUNK0001
   if WARNING is on or a complaint if WARNING is off.

18. Z100 backspace bug fixed in MSXZ10.ASM.

19. A new version of the IBM screen handling module, MSYIBM, updated by Bob
   Bolch for operation of Kermit under IBM's TopView has been heavily used by
   me for a while with no problems. However, I don't have TopView (IBM's TV
   demo disk works fine here).  My system is a Zenith 151 PC and a composite
   video monochrome monitor.

[Ed. - MSYIBM.TOP -- please try this if you use TopView, or even if you
don't, to make sure it does no harm on ordinary DOS systems.  TopView setup
parameters are documented in MSVIBM.TOP.]

20. I haven't yet obtained a copy of Purdue's VT100 emulator package so this
   version of Kermit still uses the Heath-19 emulation.  A VT100 module which
   works like a real VT100 sure would be nice!

                    Joe Doupnik
                                        JRD on Bitnet node USU

[Ed. - This message has been considerably shortened for the digest.  The
complete text, along with the new modules and any files mentioned above, are
in PS:<KERMIT-MS> on CU20B, available via anonymous FTP.  Sorry, they are
not available on BITNET via KERMSRV -- after one or two further go-rounds,
the final result of all this will be installed as the official version
(probably 2.29) in all of the normal Kermit distribution areas.

The source files (ASCII text) are in PS:<KERMIT-MS>MSSS*.*.  The object
files (8-bit binary) are in PS:<KERMIT-MS>MSSS*.OBJ.  Documentation, in
the form of the messages we've had from Joe D., are in PS:<KERMIT-MS>MSA*.*.
8-bit binary .EXE files for the IBM PC/XT/AT are in PS:<KERMIT-MS>MSV*.EXE,
and corresponding ASCII .BOO files (decodable with KER:MSBPCT.BAS) are in
PS:<KERMIT-MS>MSV*.BOO.  If you have trouble FTPing the .EXE or .OBJ files,
then either get the source and build from that, or else get the file
KER:AANETW.HLP, which gives hints about FTP'ing binary files from CU20B.

If you have other MS-DOS systems, like the HP-110 or -150, Wang PC, TI Pro,
Z-100, etc, please get the source files and try building and testing the
resulting .EXE, and pointing me at the .EXE if you can put it in a place I
can FTP it from.  Copies of all the MSX*.ASM and MSY*.ASM modules have been
placed in PS:<KERMIT-MS>, but no object files yet.

Finally, I've added the fix for CR at column 80 that Joe added to MSYIBM
to the file MSYIBM.TOP.  Therefore, I'd appreciate it if anyone who is using
TopView could try this module in place of MSYIBM.ASM and report if/how it
works, both under TopView and "up front".  Is the performance any worse than
the TopView-less version?  Should this become the regular terminal emulation
module for the IBM PC/XT/AT?

Thanks again to Joe Doupnik for the tremendous amount of work he's put in
and generously contributed.]

------------------------------

Subject: Re: Fast PC/AT Kermit
Date: 24 Dec 85 16:26:33 EST (Tue)
From: [e-mail]
Keywords: MS-DOS KERMIT

I don't know what you're talking about.  I regularly use MS-KERMIT on an AT
running DOS 3.1 with an 18.4mhz crystal (yielding an effective rate of
9.2mhz.)  I haven't yet seen any problems related to this.  I might mention
that my COM1: is located on the IBM serial/parallel card.

[Ed. - There seems to be a difference of opinion about whether Kermit
works on a souped-up AT.  Can anyone suggest why it works for some people
and not others?]

------------------------------

Date: Tue, 24 Dec 85 22:01 EST
From: Larry Afrin <[e-mail]>
Subject: My Two Cents on the MS-Kermit 2.28 jrd "Display Problem"
Keywords: MS_DOS Kermit

   I saw in the Digest a couple of msgs, one from Kathleen <last name?> and
one from Mike Iglesias, re "display problems" with MS-Kermit 2.28 jrd on old
(16K/64K motherboard) and Compaqs.  I don't know about the Compaq side of
the issue, but I'm also running 2.28 jrd on a 16K/64K vintage 1981 IBM PC,
and I have had no hint of any display problems since I first assembled and
installed the program.  For what it's worth, I'm running PC-DOS 3.10 with
ANSI.SYS installed, and I assembled 2.28 jrd with MASM 1.0 along with that
trick I documented in a msg you included in the Digest one or two issues
back.  Maybe the display problems have something to do with how 2.28 jrd is
assembled and/or linked.  (Hey, for a shot in the dark, it ain't so bad an
idea!)  Oh, I'm also running a monochrome monitor off the standard IBM
monochrome monitor/ parallel printer adapter card.

                                        -- Larry Afrin
                                           Dept. of Computer Science
                                           Clemson University

[Ed. - Another difference of opinion; "jrd/2" should link and assemble the
same way for everybody.  Can someone pinpoint the problem?]

------------------------------

Date: Tue 31 Dec 85 13:39:13-EST
From: Frank da Cruz <[e-mail]>
Subject: MS-DOS Kermit Terminal Emulation Query
Keywords: MS-DOS Kermit

If a forthcoming release of MS-DOS Kermit were to include VT-100 emulation,
would anyone have any objection to removing the Heath-19 emulation?  If so,
would the objections disappear if a VT-102 (with character insert and delete
functions) were emulated?  Since code has been written at several sites to
make Kermit emulation a VT-10x, the question is whether to include it
alongside the H19 code, or to replace the H19 code altogether.  In the
former case, the program would be that much bigger, and the implication
would be that other sites are invited to add emulation for still other kinds
of terminals (DG Dasher, IBM 3101 have already been suggested).  I have a
vague preference for emulating only one kind of terminal, and allowing
others to be supported by turning Kermit's emulation off and loading a
console driver to emulate the desired terminal.  What does everyone else
think?

------------------------------

Date: 30 DEC 85 AT 11:23:27
From: <[e-mail]>
Subject: Apple DOS Kermit Bug
Keywords: Apple II Kermit

 Well my fears are confirmed.  File xfer doesnt care what the checksum
received is. I dont know how this bug has continued this long either we
usually have very good com lines or nobody is using this kermit.

 The bug is "very little attention is being paid to false returns from rpak"
In the case of received data no attention is being paid. Sigh!

The fix:

the stmt after label "rdat2" should be "beq rdat2d" since false is zero.
the 3 stmts starting with label "rdat2c" should be removed but the label
should be retained.

 After looking at all the returns from "rpak" I am supprised that
the packet is used befor checking the checksum. It seems to me that the
whole packet is suspect if the checksum is in error. Anyway you probably
know more about this than I do.
                                     Ted
                                     milnet address "medin@nosc"

[Ed. - This message, and some further, more detailed information, has been
passed along to the Apple Kermit maintainers to see, and has been appended
to the Apple Kermit "beware" file, KER:APPLE.BWR.]

------------------------------

Date: Fri 3 Jan 86 14:09:50-CST
From: Bob Paver <[e-mail]>
Subject: Kermit for NCR Decision-Mate V?
Keywords: NCR

I'm looking for a version of Kermit that will run on a NCR Decision-Mate V.
This system runs MS-DOS, but uses a 2651 UART rather than the more standard
8251.  (MSGENER assumes the presence of the 8251 UART.)

Any help would be appreciated.

Happy New Year!

Bob Paver    [phone]

Microelectronics and Computer Technology Corp. (MCC)
9430 Research Blvd, Echelon Building #1
Austin, TX  78759-6509

ARPA:  [e-mail]
UUCP:  {ihnp4,seismo,harvard,gatech}!ut-sally!im4u!milano!paver

------------------------------

End of Info-Kermit Digest
*************************


-------
 8-Jan-86 09:48:12-EST,7671;000000000001
Mail-From: SY.FDC created at  8-Jan-86 09:46:05
Date: Wed 8 Jan 86 09:46:04-EST
From: Frank da Cruz <[e-mail]>
Subject: Info-Kermit Digest V4 #2
To: [e-mail]
Reply-To: Info-Kermit@CU20B
Queries-To: Info-Kermit-Request@CU20B
Message-ID: <[e-mail]>

Info-Kermit Digest         Wed,  8 Jan 1986       Volume 4 : Number  2

Departments:

  MS-DOS KERMIT -
        Feedback on H19 vs VT102 Support in Kermit-MS (several messages)

  MISCELLANY -
    C-Kermit VMS
    IBM VM/CMS Kermit vs VM Optimizer
    Kermit for Epson HX-20?

----------------------------------------------------------------------

Date: 7-Jan-1986
From: [e-mail]
Subject: H19 Support
Keywords: Terminal Emulation
Cross-Ref: H-19, VT-100, VT-102 (see also Terminal Emulation)

H19 and vt102's -- The consensus here [at the University of Toledo] is that
since there are no H19's on campus H19 support would not be missed.  In
light of the s/1, 7171 and VAX TPU support of vt1xx's and the lack therein
of h19 support, my users would certainly prefer vt1xx emulation.

brian

------------------------------

Date: Tue 7 Jan 86 13:16:53-EST
From: D. M. Rosenblum <[e-mail]>
Subject: Re: MS-DOS Kermit Terminal Emulation Query
Keywords: Terminal Emulation

Personally, I prefer H-19 emulation.  But I'm not much of a heavy MS-DOS
Kermit user these days.  My reasons may nevertheless be of some interest.

If VT1xx emulation is fast enough to avoid the incessant XON/XOFFing that
goes on with real VT1xx's (or, e.g., PRO/350's running PRO/Kermit or
PRO/Communications and emulating VT102s), then I have no objections.  But
there's some software that isn't too kind to XON/XOFF flow control, notably
old versions of Gosling emacs on VAX/VMS's, which we run here at C-MU.  If
the VT1xx emulation tended to generate lots of XON/XOFFs, this could be a
problem.  H-19 emulation doesn't do this any more than real H-19s do, so it
might be good to keep H-19 emulation around.

On the other hand, though, as should be clear, I've had no experience working
with VT1xx emulators, so my concerns may be about non-existent problems.

Daniel M. Rosenblum,
Ph.D. candidate
School of Urban and Public Affairs
Carnegie-Mellon University

------------------------------

Date: Tue 7 Jan 86 14:48:35-EST
From: [e-mail]
Subject: KERMIT terminal emulations
Keywords: Terminal Emulation

In reply to your request for comments re KERMIT terminal emulation:

I would like to see a single terminal with character/line/block
insert/delete capability as the emulation standard in all KERMIT vanilla
issues.  Ideally, this capability could be supplemented with an option to
load any one of a number of independent terminal emulation drivers (residing
separately on disk) either via a switch at initial KERMIT load time or via
an internal KERMIT subcommand.  The capability to switch among
(text/graphics) terminals while KERMIT is loaded would truly be a luxury.

/Farhad

------------------------------

Date: Mon, 6 Jan 86 17:06:35 pst
From: "Scott Weikart" <cdp!scott@glacier>
Subject:  Re: MS-DOS Kermit Terminal Emulation Query

We definitely want insert/delete line/character; we use kermit a lot for
dialup access.  I'd be happy to give up H-19 for VT102, but not for VT100.
Actually, I'd prefer VT102 over H19 (VT102 is more verbose, but more
standard).  I don't have strong feelings about whether there should be one
or n terminal emulators built in.

-scott

------------------------------

Date: Tue, 7 Jan 86 17:02 EST
From: [e-mail]
Subject: Re: your digested query about dropping H-19 and adding VT102

Go for it!  I say drop the Heath-19 emulation like hot lead and replace it
with a good VT102 emulator.  If we're going to do something, let's do it
right, so choose the VT102, not the namby-pamby VT100.  As for including a
bunch of different emulators in Kermit, forget it.  The VT102 is so standard
nowadays that if you connect to a system that doesn't understand what a
VT102 is, then you're connected to either (1) a system that should have been
scrapped so long ago that the gold on its circuit boards is worth more than
it is, or (2) an IBM mainframe (not including the 1 or 2 of such beasts
which run that IBM abomination of UNIX), or (3) both (1) and (2).

A VT102 is all the emulation capability Kermit will need for the forseeable
future.  ("Forseeable" in this industry being <= 10 years (maybe 5).)

                                        -- Larry Afrin
                                           Dept. of Computer Science
                                           Clemson University

[Ed. - I wouldn't be quite so hard on the H19 -- it does most of what the
VT102 does, and it did it first, and it does it more simply and without all
the XON/XOFF craziness.  It's just too bad it never "caught on" in the sense
that popular operating systems (other than Berkeley Unix) or front ends
support it as a standard terminal type.  Are there any setups where dropping
Heath emulation in favor of VT102 (assuming it didn't send XOFFs all the
time) would do serious damage?]

------------------------------

Date: Mon 6 Jan 86 21:14:45-EST
From: Jin Au Kong <[e-mail]>
Subject: Feedback on MS-DOS Kermit 2.28 and C-kermit VMS

Since VT100 is industrial standard, I would support VT100 emulation
in various implementations.

On VMS C-Kermit:

 1) Terminal response is faster than Kermit-32, and requires less
    BYTLM quota.   We have Kermit-32 v3.1066 and C-kermit 4C present
    on our system.  While C-kermit suffer from data overrun problem
    more often, one cannot type too fast when "connect"ed through
    Kermit-32, or it will kick you back to kermit prompt level.

 2) I like the script feature provided by C-Kermit.  We have
    implemented fileserver and printer server between two 750's
    with this feature.  Wish to learn of some other applications, such
    as mailserver.

 3) It would be great if somebody can incorporate a better
    interruption capability for C-Kermit.  Quite often we have user
    tied up the line because of an incorrect operation in C-Kermit.

[Ed. - The VMS support was added to C-Kermit by some volunteers at DEC who
probably don't have time to do much more with it.  I'm sure that C
compilers are pretty common at VMS sites (much more common, at least than
Bliss compilers), so VMS experts are more than welcome to add whatever
improvements they like to the VMS system-dependent modules.]

------------------------------

Date: 7-Jan-1986
From: [e-mail]
Subject: IBM VM/CMS Kermit vs VM Optimizer

The systems group for the IBM system here recently installed a package from
BMC Corp. called VM Optimizer, one feature of which is compression of data
to 3270 type terminals.  Using this will cause CMS S/1 Kermit to fail.  If
something like this is used, it should be disabled for 7171 and S/1 lines.

brian

[Ed. - Swell, I hope it comes with instructions about how to do that...]

------------------------------

Date: 8 Jan 86  9:26:00 EST
From: Frank da Cruz <SY.FDC@CU20B>
Subject: Kermit for Epson HX-20?

Does anyone have Kermit running on an Epson HX-20?  I assume (but don't know
for sure) that this is a CP/M-80 machine (and if it is, I don't know if it
runs CP/M 2.2 or 3.0).  I would be very grateful for information about this
system, or better still, a pointer to where to find Kermit for it, or still
better, an Epson HX-20 diskette with Kermit on it!

------------------------------

End of Info-Kermit Digest
*************************
-------
13-Jan-86 12:10:24-EST,12945;000000000001
Mail-From: SY.FDC created at 13-Jan-86 12:08:58
Date: Mon 13 Jan 86 12:08:58-EST
From: Frank da Cruz <[e-mail]>
Subject: Info-Kermit Digest V4 #3
To: [e-mail]
Reply-To: Info-Kermit@CU20B
Queries-To: Info-Kermit-Request@CU20B
Message-ID: <[e-mail]>

Info-Kermit Digest         Mon, 13 Jan 1986       Volume 4 : Number  3

Departments:

  ANNOUNCEMENTS -
    Bitnet Files Updated

  MS-DOS KERMIT -
    H19 vs VT102 Emulation (many messages)
    Kermit under MS Windows

  MISCELLANY -
    Looking for Apple II CP/M Kermit Diskette
    XON/XOFF Deadlock between vt100 and Hayes Modem
    Bug fix for Prime Kermit server mode

----------------------------------------------------------------------

Date: Mon 13 Jan 86 11:22:40-EST
From: Christine Gianone <[e-mail]>
Subject: Bitnet Files Updated

    The Bitnet Files have finally been updated.  The Kermsrv File
Server on CUVMA should now be able to supply Bitnet Users with
up to date Kermit Files.  JRD's MS-DOS Kermit is still an
exception;  it will be installed on Bitnet when it becomes the
real MS-DOS Kermit.

    The way to get started with Kermsrv is to issue the following
command to CMS:  "SMSG RSCS MSG CUVMA KERMSRV HELP".  If you
haven't used Kermsrv for a while, you may notice that some recent
improvements have been made.

------------------------------

Date: 9 Jan 86 00:24:09 EST
From: John McNamee <[e-mail]>
Subject: H19 and VT10x emulation

VT10x emulation would be nice, but not at the expense of H19. When you're
talking to a host at 1200 baud the goal is to reduce the number of characters
sent. VT10x is so verbose that operation at low speeds is painful. So go
ahead and add VT10x emulation, but leave H19 for those of us still using
dialup lines.

------------------------------

Date: Thu, 9 Jan 86 12:25:20 EST
From: Ivan Auger <[e-mail]>
Subject: VT102 vs H19 support...

I never use kermit's H19 support, instead I use a VT102 emulator that allows
me to run kermit without exiting the program.  So, if H19 support is dropped,
we won't suffer at all.  (By the way, I also use emacs and haven't had any
trouble with VT100 emulators except that it is a good program to find bugs
in this emulators).
Ivan Auger, NYS Dept. of Health

------------------------------

Date:     Thu, 9 Jan 86 19:11 EST
From:     [e-mail]
Subject:  More on VT102 emulation in MS-Kermit

Hmmmm... Just read the latest digest.  Seems I came out sounding more
vehement than I intended.  Now that I've had a chance to put my brain in
gear *first* (before my fingers take off), I can say what I meant to say in
my previous msg: MS-Kermit would be much better off with the VT102's set of
capabilities rather than the H-19's set.  Uh, that means "conceptual set,"
as in, "Make the Kermit emulator do what DECL claims the VT102 can do
*minus* all the implementation deficiencies in DEC's VT102, such as the
XON/XOFF problem."  I was unaware that the XON/XOFF business is a problem to
some users, and now that I am aware of it, I have to agree that if the
Kermit implementation of VT102 is going to include deficiencies such as
that, then we're better off with H-19.

There!  Doesn't that sound nicer?

                                        -- Larry Afrin
                                           Dept. of Computer Science
                                           Clemson University

------------------------------

From: Roy Stehle <stehle@sri-tsc>
Date: 10 Jan 1986 1519-PST (Friday)
Subject: h19 support necessary

I would like to request that h19 support remain in MS-Kermit.

I am working on a VAX running 4.2 BSD UNIX.  The text editor that I use (e)
does not have a termcap for the VT-10X.  There may be some time in the
future that the editor will be enhanced to use the standard UNIX termcap,
but I can't count on that.

We have many h19 terminals in our company and rely heavily on their
compatibility with existing software.

------------------------------

Date: Fri, 10 Jan 86 15:31:02 pst
From: gould9![e-mail] (Joel West @ CACI)
Subject: MS-Dos terminal emulation

VT100 is fine.  VT102 is better, and the standard for Terminal emulators.
Junk the H-19.  Any system that can handle it can handle the VT100, but not
vice versa.

If only a partial emulation is done, make sure it is an innocuous one.  The
MacKermit 0.8 is unreadable when switched to "bold"; fortunately, most
systems don't use this.

Also, for VMS users, a VT100-style keypad mapping would be real handy.  I
have a public domain Macintosh desk accessory (off the net) for those times
I need one under VMS.

    Joel West     CACI, Inc. Federal, La Jolla
PS:

> Date: Tue, 24 Dec 85 22:01 EST
> From: Larry Afrin <[e-mail]>
> Subject: My Two Cents on the MS-Kermit 2.28 jrd "Display Problem"
>
>    I saw in the Digest a couple of msgs, one from Kathleen <last name?> and
> one from Mike Iglesias, re "display problems" with MS-Kermit 2.28 jrd on old
> (16K/64K motherboard) and Compaqs.  I don't know about the Compaq side of
> the issue, but I'm also running 2.28 jrd on a 16K/64K vintage 1981 IBM PC,
> and I have had no hint of any display problems since I first assembled and
> installed the program.

This is probably what we have on our Compaq 286, and it's no figment of our
imagination.  We used the straight IBM .exe (nothing to do with source)
under MSDOS 3.x, and other than that, have no problems.

------------------------------

Date: Sun, 12 Jan 86 20:11:04 PST
From: [e-mail] (David Ragozin)
Subject: H19 emulation in ms-dos kermit

Although I can't speak for the comuputing center here at the University of
Washington, I can say that our instructional computing system is heavily
dependent on h19 and z-29 terminals.  Most instructional computing uses a
screen editor, which has been optimized for this h19 environment.  As a
result, the h19 emulation in kermit has been a very appealing aspect.

Although I personally think the vt102 emulation would be quite nice to have,
and it is desired by our Engineering College computing group, I would hope
that some options could be maintained.  The idea of having some generic
terminal emulator modules, which could then hook into specific terminal
emulator modules at compile time might be a way to go.

As you also may recall, some of our staff created a very bare bones
tektronics 4010 emulator which is invoked when heath mode is off, and the
tektronics graphics code is received.  I forwarded this code to you some
time ago. Hopefully we will be able, without too much change, to repeat this
graphics terminal extention with whatever new version you release.

------------------------------

Date: Thu, 9 Jan 86 16:45:32 PST
From: [e-mail]
Subject: Kermit under MS Windows

Since Microsoft Windows claims to allow programs to run which are TopView
aware, I thought I would try the version of MS-Kermit V2.28 jrd which
supports TopView.  I used the PIF file entries advised in
PS:<KERMIT-MS>MSVIBM.TOP.  The resultant program runs fine under Windows,
except for the fact that the update to the screen after a CONNECT command is
painfully slow--about equal to the speed of a 300 baud modem connection.
Oddly enough, the program does not exhibit this behavior in local mode,
after a DIR command to Kermit-MS for example.  I have looked at the source
code, but don't know enough about the TopView interface to understand how it
works.  Both the TopView and normal versions of MS-Kermit run equally
quickly when run as standalone programs under normal DOS, so I would have no
objection to the TopView version becoming the standard one.

By the way, I built my Kermit from source using MASM Version 4.00.  Using
EXEPACK reduced the size of the executable file from 43,000 bytes to
32,000 (when the modules were linked in the order given in MSKERM.MAK).

                    Steve Walton
                    Caltech Solar Astronomy
                    [e-mail]
                    [e-mail]
                    ...!ucbvax!cithep!hamlet#walton@deimos

------------------------------

Date: Thu, 09 Jan 86 01:32:47 CST
From:  [e-mail]  (Dr. Michael J. Dyrenfurth)
Subject: Looking for Apple II CP/M Kermit Diskette

Although I have REALLY tried in this region, I have been unable to
secure a working copy of Kermit-80 that runs on my Apple IIe (c/w PCPI CPM
card, Videx Ultra-term 80/160 column card, Hayes 1200 smartmoden, Apple super
serial card).  I desperately need to get 1200 baud CPM communication up.
Is there any way that I can buy a working disk from someone?  I also need
a version that works with a II+ (cw the ALS Smartterm 80 column card, the
Micro-soft CPM card, and Apple Super serial card)

------------------------------

Date: 8 Jan 86 05:15:29 GMT
From: Dennis Bednar <rlgvax![e-mail]>
Subject: XON/XOFF Deadlock between vt100 and Hayes Modem

Kermit XON/XOFF Deadlock Bug Caused by Hayes Command Echo Enabled

    I recently ran into a problem of kermit "locking" up sometimes
when using a Hayes Smartmodem, and I thought I would share it with the
net.

    Well, I looked into this problem and found that it was caused
by me connecting to the Hayes modem directly, and and accidently
typing control-s (XOFF).  The ^S was passed through as data to the
modem.  At this time, I had set the Hayes dip switch to enable echoing
during Hayes command mode, merely for convenience to me. This led to
an XON/XOFF deadlock problem between the vt100 and the Hayes
Smartmodem.

Repeat by:
    # this is a comment
    # enter C-Kermit command mode
    set modem dir    # kermit command to say direct hardwired line
    # I know, I know, C-kermit's dial command will interact
    # with the Hayes, and this problem will not occur if I
    # use the kermit "dial" command, but I was just experimenting.
    set esc 1
    connect
    # kermit connects your terminal to the modem now
    # Now type AT several times, and verify that the OK prompt appears.
    # Now type control-s.
    # Now type AT, but you don't see OK.
    # In fact nothing you type is sent.  This problem assumes that your
    # terminal understands that ^S inhibits the terminal kb's from
    # sending on the tty line.

You MAY NOT BELIEVE THIS, BUT THE THE HAYES ALSO ECHOED the control-s!!!!!!!
Therefore the ^S typed on my keyboard was passed through kermit, echoed by
the modem, and passed back through kermit, and sent to my terminal screen.
This caused my vt100 terminal's KBD LOCKED (Keyboard Locked) LED to turn on.
If you try typing ^Q to break the problem, your terminal does not transmit
it, because output is inhibited until ^Q is received from the host, which
cannot happen, so you are deadlocked.  Fortunately, since I was using a
vt100 terminal, I merely pressed the SET-UP key twice, which turned off the
KBD LOCKED light. For an ignorant user, this could be bad.

Best solution: Disable Hayes echoing during command mode, and this problem
cannot occur.

Dennis Bednar    Computer Consoles Inc.    Reston VA    703-648-3300
{decvax,ihnp4,harpo,allegra}!seismo!rlgvax!dennis [e-mail]

------------------------------

Date: 10-JAN-1986 16:39:18
From: [e-mail]
Subject: Bug fix for Prime Kermit server mode

Here's a fix I had sent in for bug in Prime Kermit causing it to NAK an I
packet instead of sending an Error. Will get through the backlog of bug reports
and such over the next week or so if the link stays going!

         Alan

  Date : 10 January 1986
  From : Rick Burne, Ealing College of Higher Education, London UK
  Subject : Bug in Prime KERMIT in server mode

In server mode PRIME KERMIT responds to an I packet with a NAK rather than
anything sensible such as a qualified ACK or an error packet. This should be
fixed in the next release from The Source, but in the meantime here is a quick
edit to make it respond with an error packet.

File MSG_TYPES.PLP

Around line 24, insert a line
           MSG_INIT by 'I'         /* Init-info packet */
after the line
           MSG_EOF by 'Z'          /* End of file (EOF) */

File SERVER.PLP

Around line 225, insert a new clause in the main do while loop:
          when (MSG-INIT) do;
            snd_msg = 'Unimplemented server command';
            call send_packet('E',length(snd_msg),msg_number);
          end;
before the line
          end;    /* select */

File REC_MESSAGE.PLP

Around line 72, insert a line
         msg_init,
before the line
         msg_rcv_init) return ('1'b);

------------------------------

End of Info-Kermit Digest
*************************
-------
17-Jan-86 20:08:32-EST,16830;000000000001
Mail-From: SY.FDC created at 17-Jan-86 20:08:03
Date: Fri 17 Jan 86 20:08:03-EST
From: Frank da Cruz <[e-mail]>
Subject: Info-Kermit Digest V4 #4
To: [e-mail]
Reply-To: Info-Kermit@CU20B
Queries-To: Info-Kermit-Request@CU20B
Message-ID: <[e-mail]>

Info-Kermit Digest         Fri, 17 Jan 1986       Volume 4 : Number  4

Departments:

  MS-DOS KERMIT -
    New Kermit for Olivetti M24 PC (and IBM PC) with VT100 Emulation
    MS-DOS Kermit Available for RMX-86
    HP-Portable Kermit 2.28 jrd/2
    Don't Drop H-19 Emulation
    Feedback on W-Kermit
    Kermit Versus Cermetek Modem (212PC) and Modem-Mate Software
    TI Pro Kermit at 9600 Baud

  MISCELLANY -
    Contacting Lancaster University for Kermit Distribution in the UK
    Kermit Diskette Wanted for HP-9836
    CMS Kermit 2.01 bugs fixed

----------------------------------------------------------------------

Date: Wed 15 Jan 86 10:45:55-EST
From: Frank da Cruz <[e-mail]>
Subject: New Kermit for Olivetti M24 PC (and IBM PC) with VT100 Emulation

This is to announce MS-DOS Kermit support for the Olivetti M24 PC, which is
IBM compatible except for the keyboard, contributed by Andrew J. Hunt of
CSIRO, Division of Radiophysics, Epping NSW (Australia).  It includes VT100
emulation, and extensive support for the Olivetti keypad.  The new support
is embodied in the files KER:MSXM24.ASM and KER:MSYM24.ASM.  A "boo" file
(encoded .EXE file, decodable using the KER:MSBPCB.BAS or KER:MSBPCT.BAS
programs) based on version 2.27 of MS-DOS Kermit is available in
KER:MSVM24.BOO, and the .EXE file itself (for those who can FTP 8-bit binary
files) in KB:MSVM24.EXE.  I tried it briefly on a PC/AT, and it seemed to
work as a VT100 emulator, at least for EMACS purposes.  Andrew claims it
also simulates the VT100 graphic set sufficiently to produce EDT help
screens.

This code will probably not be used as a basis for any VT100 emulation that
may appear in the forthcoming release, 2.29, but it will certainly be
looked at to see if there is anything there that might be missing from the
Indiana/Purdue VT100 code.  In the meantime, those who are desparate for
VT100 emulation in IBM PC Kermit might be able to get by using this version.

The program is thoroughly documented in KER:MSVM24.HLP.  As usual, all files
mentioned above are available on the Internet using FTP login to host CU20B,
user ANONYMOUS, any password.

------------------------------

Date: Fri 17 Jan 86 16:14:04-EST
From: Frank da Cruz <[e-mail]>
Subject: MS-DOS Kermit Available for RMX-86

This is to announce an implementation of MS-DOS Kermit for iRMX-86 on the
Intel 300 Series from Jack Bryans, California State University, Long Beach
([e-mail]).  This is a rather unusual addition to the MS-DOS
Kermit family, in that the underlying operating system is not MS-DOS at all.
As Jack puts it, "MS-Kermit (essentially unchanged) has been placed in a
cradle which leaves it blissfully unaware that it is not running under DOS".
When he says "essentially unchanged" he means that a few minor syntax
changes were necessary in some of the system-independent modules, which
should be reflected in the forthcoming release 2.29.  The files relating to
this version are in KER:MS%RMX.* ("%" is DEC-20 wildcard notation to match
any single character), available using anonymous FTP from CU20B.

Included is a .BOO file, which will be of use only if the Intel system has a
Basic interpreter that can run one of the .BOO file decoders --
KER:MSBPCB.BAS or KER:MSBPCT.BAS.  The 8-bit binary executable program is in
KB:MSVRMX.EXE; if there is some more standard way of representing it
printably (an Intel HEX file maybe?) then I'd appreciate it if someone
would create one from the .EXE and send it in.  It's probably not possible
to recreate this program from the sources in KER:MS*.* at this point because
of inconsistencies between the current version (2.28) and the version upon
which Jack's work is based (2.26), the name changes, etc, plus the fact that
the current source does not reflect Jack's suggested syntax changes (see
KER:MSVRMX.BWR about this).  If all this sounds too complicated to deal with,
the program may be ordered on diskette from:

     California State University, Long Beach
     University Bookstore
     Attn: Lyle Bartlett
     6049 E. 7th St.
     Long Beach, CA 90840

$6.00 per 5 /14" DSDD RMX format diskette.  Thanks to Jack for this submission.

------------------------------

Date: Wed, 15 Jan 86 19:58:50 mst
From: [e-mail] (Dave Forslund)
Subject: HP-Portable Kermit 2.28 jrd/2

The new jrd/2 version of Kermit works fine on the HP Portable Plus.  I've been
testing it for a few days and have noticed no problems.

Since the last submitted version of MSXHPX.ASM, we have fixed the problem of
leaving the modem/serial port on.  The context diffs follow:

[Ed. - Thanks, Dave!  Code omitted; the updated module is available in
KER:MSXHPX.ASM.]

------------------------------

Date: Mon 13 Jan 86 23:13:46-EST
From: Joe Smith [phone] <[e-mail]>
Subject: Don't Drop H-19 Emulation

Removing H19 emulation won't make the terminal emulator smaller.  Because if
you are doing full VT102 emulation, then you have to respond to <ESC>?2l which
puts a real VT10x terminal in VT52 mode.  Given all the routines to do VT102
functionality, adding H19 features to the VT52 dispatch table is trivial.

In other words, it costs almost nothing to have VT102 and H19 emulation both.

I strongly recommend ripping out the "SET H19" command and replacing it with
a new command, such as "SET TERMINAL xxx" with the default of xxx=ANSI.
People that need H19 response need only "SET TERMINAL H19" or have the host
computer send <ESC>2l to get the VT102 out of ANSI mode and into VT52/H19 mode.

[Ed. - This is the most succinct and sensible statement on the subject to
date, and 2.29 will probably wind up structured along these lines.  Thanks
to all who sent their opinions -- I think this approach will make everyone
happy.]

------------------------------

Date: Fri, 17 Jan 86 08:52:35 PST
From: [e-mail]
Subject: Feedback on W-Kermit

I downloaded WKERMIT.EXE (C-Kermit with windows for MS-DOS) yesterday, the
16th.  Works like a charm on my Zenith Z-151 under MS-DOS version 3.10.  I
connected two machines together directly via the serial ports.  At 9600 baud,
the time to transfer a 33,000 byte executable file was 128 seconds for the
latest version of MS-Kermit, and 90 seconds for WKERMIT.  Since no delays were
involved, this 45% improvement is presumably due to WKERMIT's compression.

Now if we can only convince CompuServe to use windowed Kermit instead of
XMODEM...

                    Steve Walton
                    [e-mail]
                    [e-mail]

[Ed. - Good news!  I would be very interested in any statistics that people
who use the public networks could provide about W-Kermit's performance.  If
anyone is in a position to do some benchmarking, we could really see if the
windowing extension lives up to expectations in the environment it was
designed for.  The idea would be to pick a group of MS-DOS files, say a .COM
file, an .EXE file (preferably unpacked), a plain text file, and a highly
indented text file (like C program source, untabified) -- all of nontrivial
size, say 10K-50K -- and transfer them at 1200 baud over a link having no
built-in delays (say, a direct dialup or hardwired connection) and again
over a public data network (like Telenet or Tymnet), both with windowing and
without.  And maybe even with several different window sizes.  All other
options should remain constant.  Note the elapsed time to transfer each file
in each case.  The test could be conducted between two PCs (XTs, ATs)
running W-Kermit (one of them might be at the TCOMM BBS mentioned by Jan van
der Eijk in his Windows Kermit announcement in Info-Kermit V4 #1), or
between a PC running W-Kermit and the Kermit at The Source (if you have an
account there).  The latest release of Profession YAM is also reported to
support the windowing extension.  Any reports will be reproduced in
Info-Kermit, naturally, and may also make it into the Kermit Book (with full
credit) if I get them in time.  Here's a sample table to fill in:

               (No  windowing)   (Full Duplex Windowing..........)
               Xmodem   Kermit   Kermit   Kermit   Kermit   Kermit
Window Size:      0        0        4        8       16       31

File      File    Elapsed time to transfer at 1200b, in seconds:
Name      Length  Direct connection:

???.COM   ?????   ?        ?        ?        ?        ?        ?
???.EXE   ?????   ?        ?        ?        ?        ?        ?
???.TXT   ?????   ?        ?        ?        ?        ?        ?
???.C     ?????   ?        ?        ?        ?        ?        ?

                  Public network (which one?):

???.COM   (same   ?        ?        ?        ?        ?        ?
???.EXE   files   ?        ?        ?        ?        ?        ?
???.TXT   as      ?        ?        ?        ?        ?        ?
???.C     above)  ?        ?        ?        ?        ?        ?


It's more important to fill in a whole column than a whole row.
Thanks in advance to anyone who undertakes to do any of this!]

------------------------------

Date: 17 Jan 1986 10:21:41 CST
Subject: Kermit Versus Cermetek Modem (212PC) and Modem-Mate Software
From: [e-mail]

What is the latest word on Kermit and internal modems?  Is it possible to
get Kermit to run on PC's with internal modems such as the Cermetek (212PC)?
If the answer is yes I would surely be interested in how, if the answer is
no I would be most appreciative of a laymen's explanation as to why.

Regards,
Sam DelaTorre

[Ed. - This is an oft-asked question.  MS-DOS Kermit includes absolutely no
code to deal explicitly with internal modems.  If it did, the program would
rapidly become unmanageable.  Rather, we depend -- so far, at least -- upon
the modem manufacturer to make the modem behave exactly as the regular
asynchronous adapter does.  Many internal modems do (like the Hayes); others
emphatically do not (like the PCjr's built-in modem).  Those that don't
would require very hardware-specific code to support, and this code would
tend to reduce the transportability of the program (e.g. among IBM
compatibles) as well as its robustness and longevity.  So the party line
remains "avoid internal modems!"]

------------------------------

Date:  Thu Jan 16 11:41:27 EST 1986
From: dolqci!irsdcp!scsnet![e-mail]
Subject: TI Pro Kermit at 9600 Baud

Has anyone had any experience with TI kermit version 2.28 revision 5
transfers at 9600 baud?  I am trying to get my TI to transfer files to my
Unix System III box over a direct line at 9600 baud.  It work MOST of the
time, but intermittently my C-Kermit thinks it got a ^C and aborts, and then
Unix gets a ^D and logs me out.  Any thoughts, suggestions, or messages of
condolance please sene to me via uucp and/or to the digest.  Thanks.

UUCP:    (1) seismo!dolqci!irsdcp!scsnet!sunder        [phone]
    (2) decvax!philabs!ubbs!sund                (voice)
CIS:    74026,3235
Mail:    IRS 1111 Constitution Ave. NW  PM:S:D:NO
    Washington, DC 20224  Atten: Mark E. Sunderlin

------------------------------

Date: 16-JAN-1986 10:18:44
From: [e-mail]
Subject: Contacting Lancaster University for Kermit Distribution in the UK

Lancaster University maintains a collection of almost all Kermit files
online on a VAX, and keeps it as in-step with CU20B as possible.  The files
are in a public access username, which can be logged in to from the JANET or
PSS networks or by dial up at any time.  To access the distribution service,
users should do the following:

From PSS:   1. Call 23425240010104
               to get to our PSS gateway using X29. Depending on what PAD you
               are using the first few digits may need replacing with, eg, "A"
            2. Call 000010404000
               from the gateway to get to our VAX11/780 system (running VMS)
            3. Log in to user KERMIT, password KERMIT.

From JANET: 1. Call 000010404000 using X29
               (The system's NRS name is LANCS.VAX1 which you might have
               already configured and available to match this address)
            2. Log in as (3) above

By Dial-up: 1. Call one of 0524-63423, 0524-67754 or 0524-67671. These are all
               V21/V23 autosense modems: put your modem online as soon as ours
               answers, rather than waiting for carrier. Lines are set for full
               duplex, 8 data bits, no parity, XON/XOFF flow control.
            2. Press RETURN a few times to wake up the pad and get a "PAD>"
               prompt
            3. Type CALL LANCS.VAX1 to connect to the VAX
            4. Log in as above.

News of the day will appear, as well as pointers to the help files and indexes.
The system is rather overloaded and slow, so please be patient when logging in.

I can be contacted in several ways:

By letter:  Alan Phillips
            Communications Group
            Department of Computing
            Computer Building
            Lancaster University
            Lancaster LA1 4YW
            UNITED KINGDOM

By phone :  [phone] x 4881

By e-mail:  To user SYSKERMIT @ LANCS.VAX1
               PSS address   234252400101.000010404000.FTP.MAIL
               JANET address 000010404000.FTP.MAIL
            Please give your own full mail address and site name.  Reply over
            ARPA is unreliable and slow.  I cannot reply over uucp, or anything
            other than JANET and ARPA.

I would prefer contact by e-mail if at all possible. Response may be slow as
this is a one-person operation and it stops when I'm away.

All users can collect files from us by Kermit or by file transfer at no
charge.

I can write tapes in DEC ANSI D or VMS BACKUP formats, and supply some
Kermits on floppy disc (contact me for availability).  Supply is free to all
educational establishments, but there is a handling charge to others.  I
can't, I'm afraid, generally undertake to supply outside outside the UK/Eire
as the work load would become too great.

[Ed. - Many thanks for providing this service within the UK!]

------------------------------

Date: Thu 16 Jan 86 15:19:08-PST
From: David Liu <[e-mail]>
Subject: Kermit Diskette Wanted for HP-9836

Is there anyone who has a copy of HP-9836 Kermit?  I would like to arrange to
get a disk.

[Ed. - This is a frequent request.  Can anyone help David out?  Better
still, does anyone know of the existence of an HP-98xx user group?  If so,
could someone who has this version of Kermit on an HP-98xx-format diskette
please submit it to the user group so that others could order it from there?
If there's no such user group, maybe HP itself would be willing to
distribute it to their customers.

Anyone who manages to set up something like this, please let me know so I
can refer future inquiries of this kind to the user group (or HP).  In fact,
this goes for every microcomputer, PC, workstation, etc, version of Kermit.
If you have a working version, please submit it on native media, with any
appropriate documentation, to a user group that accepts mail orders.
Thanks!]

------------------------------

Date: 16 January 86 17:57 EST
From: NJG@CORNELLA
Subject: CMS KERMIT 2.01 bugs fixed

I have discovered (and corrected!) a couple of bugs in CMS KERMIT version
2.01:

If CMS KERMIT is executed more than once from an EXEC without returning
to CMS command level any attempt to 'take' a file more than once will
fail as the file has been left open.  This can be fixed by closing the file.

Update 2 to version 2.00 of CMSKERM does not pad RECFM F files
with spaces as it claimed, it pads with hex 0's.

When processing a SERVER 'bye' request on a 7171 (or Series/1) line
no XON should be sent before issuing the CP LOGOFF command. If it is
the CONWAIT following the WRTERM will wait forever.
The content of file CMSKERM FIXBYE are:

"8-)" Nick Gimbrone <[e-mail]> [phone]

[Ed. - Thanks, Nick!  The listings are omitted, but have been added to
the KER:CMSMIT.BWR file, and will be included (in one form or another) in
the next release of CMS Kermit.]

------------------------------

End of Info-Kermit Digest
*************************
-------
22-Jan-86 17:15:48-EST,19044;000000000001
Mail-From: SY.FDC created at 22-Jan-86 17:14:00
Date: Wed 22 Jan 86 17:14:00-EST
From: Frank da Cruz <[e-mail]>
Subject: Info-Kermit Digest V4 #5
To: [e-mail]
Reply-To: Info-Kermit@CU20B
Queries-To: Info-Kermit-Request@CU20B
Message-ID: <[e-mail]>

Info-Kermit Digest         Wed, 22 Jan 1986       Volume 4 : Number  5

Departments:

  MS-DOS KERMIT -
        Victor 9000 Support for MS-DOS Kermit 2.28
        APC MS-Kermit
        Info-Kermit
        Olivetti M24 Kermit: VT100 Split-Screen Scrolling Problem

  MISCELLANY -
        MacKermit from Rice?
        SuperKermit File Transfer Times
        Tandem Running Guardian OS Kermit?
        Novation Apple-Cat II?

----------------------------------------------------------------------

Date:     Mon, 20-JAN-1986 20:31 MST
From:     <[e-mail]>
Subject:  Victor 9000 Support for MS-DOS Kermit 2.28

This is to announce Victor 9000/Sirius 1 Support for MS-DOS Kermit 2.28,
contained in two assembly-language files, MSXV90.ASM and MSYV90.ASM.  The
support includes the full option list of baud rates (45.5 to 38400 baud),
the use of either serial port, full HEATH emulation, and restoration of the
screen to its previous condition when reconnecting to the same port after
disconnecting.  The SET KEY option has not been supported since that does
not seem to be necessary with the Victor's soft keyboard.

For those who would like to get more out of the Victor 9000, there is also
a version of MSYV90.ASM which gives full Tektronix 4010 emulation.  This
module provides full text, graphics, and graphics input (GIN) emulation.
The graphics are good quality, thanks to the quality of the Victor's screen,
and the graphics input appears to be adequate for most needs.  However, the
text leaves a little to be desired in terms of readability.  The font is
home grown (my home) and I didn't have a lot of time to put into fine tuning
the different characters for readability, but they can be deciphered with a
little practice.

There are three Victor-specific modules required to generate the Tektronix
version.  These are
      MSZV90.ASM - replaces MSXDMB to get the segments in the right order
      MSXV90.ASM - same one used for the regular KERMIT
      MSYV9T.ASM - provides the Tektronix emulation
The first module is required to get the segment containing the graphics
screen region as low as possible in memory.  The Tektronix emulation mode is
entered by setting the HEATH mode off (i.e., SET HEATH OFF).

                                  Bryan G. Peterson
                                  PETERSONB@BYUVAX

[Ed. - Thanks!  This should allow us to get rid of some of the old Victor
versions that have been cluttering up the Kermit Distribution the last few
years, and allow the Victor to benefit from new MS-DOS Kermit releases.
Since there is no .BOO or .EXE file, the program will have to be built from
the source, following the directions in the documentation.  The files are
in KER:MS%V9*.* on CU20B, available via anonymous FTP on the Internet, and
from KERMSRV at CUVMA on BITNET.  If anyone manages to build a working .EXE
in a place I can FTP it from, I'll add it to the distribution and make a
.BOO file from it.]

------------------------------

Date: Sun 19 Jan 86 17:30:14-PST
From: Ronald Blanford <[e-mail]>
Subject: APC MS-Kermit

The corrected versions of MSXAPC.ASM and MSAPC.EXE are ready for ftp
from my account <CONTEXT>.

This latest version fixes a bug in which MS-Kermit incorrectly handled
the function keys on the APC during Connect mode.  When programmed
using the operating system KEY command rather than from within Kermit,
only the first character would be sent when the function key was pressed,
and the rest would wait until the next keystroke.  This has now been
corrected.  Thanks to Ian Gibbons for the fix.

-- Ron

[Ed. - Thanks, Ron.  The new files are in KER:MS%APC.*, including a new
.BOO file.  The 8-bit binary .EXE file is in KB:MSVAPC.EXE.  These files
are available, as usual, via anonymous FTP from CU20B on the Internet.
All but the .EXE file are also available on BITnet from KERMSRV at CUVMA.]

------------------------------

Date:    Mon, 20 Jan 86 13:58 EST
From:  [e-mail]
Subject: Info-Kermit

I have been archiving the Info-Kermits from the MAIL files on KermSrv.  I
have been putting Volume 1 - 4 into partitioned datasets with an index of
all the subject lists.  This is great and very useful, but unfortunately all
the pre-volume information was not digested into any specific format so I am
at a lost for the best way to break them into smaller chunks.  I was
wondering if you had any ideas on this?  Do you think anyone would be
interested in the digests as partitioned datasets?  I would be more than
happy to send them to you for distribution if you think it a worthwhile
thing.

Thanks again for your time,

mark

[Ed. - If anyone out there is interested in an Info-Kermit PDS, please
respond to Mark directly; if there is sufficient interest, maybe some way
can be devised to distribute it.]

------------------------------

Date: Tue 21 Jan 86 14:30:28-EST
From: PK0P@CMCCTD
Subject: Olivetti M24 Kermit: VT100 split-screen scrolling problem

I downloaded the Olivetti M24 version of Kermit-MS and noticed a problem
with split-screen scrolling in VT100 emulation mode.

I'm using an IBM PC/XT, DOS 2.1, EGA, and Enhanced Color Display.  I'm also
using the ANSI.SYS device driver.

When talking to a VAX/VMS system, I noticed the problem with the VMS PHONE
facility.  From PHONE, one can do DIR to see a list of users on the system,
or on another VAX/VMS system connected through DECNET.  If there are more
than 18 users on the system, PHONE will do a split-screen scroll to list
them (provided the terminal is one of the VT1xx or VT2xx series).  The first
time through, the list will be displayed correctly with split-screen
scrolling.  If you then issue a second DIR command from PHONE, all the lines
with be displayed on top of each other on the status line (on about the 5th
line from the top). Then if you exit from PHONE, you will find your cursor
on line 1, with only a one line scrolling region!  To correct the problem,
you can issue the escape sequence to reset the scrolling region, or escape
back to Kermit-MS and type:

SET HEATH ON
SET HEATH OFF (to get back to VT100 Emulation)

(Note: this is only noticeable if the VAX system has 18 or more users logged
in.  PHONE does not use split-screen scrolling when it can list all the
users on one screen.)

Peter Kanaitis
Research Systems Analyst
Allegheny Singer Research Institute
Allegheny General Hospital
Pittsburgh, PA 15212

Voice: [phone]
Net: [e-mail]

[Ed. - Thanks for the report -- it has been passed along to Joe Doupnik to
make sure the forthcoming version 2.29 will not have the same problem.]

------------------------------

Date: Sat, 18 Jan 86 14:12:11 pst
From: Joel West <[e-mail]>
Subject: MacKermit from Rice?

Frank,

Since I doubt you were at the MacWorld expo this week, I thought I'd pass it
along...

"The Rice University Macintosh Development Project has developed several
public domain products for Macintosh computers.
...
Rice Mac Kermit
        ...It will also allow you to send full applications as
        well as text only documents.  Eighth-bit prefixing
        is supported.  This program is currently in beta test.
...

Rice University
Institute for Computer Services and Applications
POB 1892
Houston, TX 77521

Unfortunately, the guy at the Rice booth didn't know much about it, and said
I had to come back and speak to the woman in charge.  I never made it.

[Ed. - According to the new issue of "Wheels for the Mind" (V2 #1, Winter
1986) the status of Rice Univerity's Macintosh Kermit is "Currently on
hold".  Rice has never been terribly communicative about the various Kermit
programs they've been working on -- they also have a pretty fancy TSO Kermit
written in PL/I, but which requires a proprietary support package which they
sell; hence we don't distribute it.]

If you find out any more about this (either through INFO-KERMIT or whatever
channels you have), I'd like to know.  I'm a heavy Mac and Kermit user, and,
if this is better than the 0.8 C-Kermit, would be glad to add it to our
user-group distribution.

[Ed. - I'll be glad to add it if Rice sends it in.]

At this point, the most interesting issue is whether MacKermit will support
the Hierarchical File System.  The main reason why some programs don't is
that they take the volume ref no, convert that to a disk volume name, and
then make a string of the form "Disk Volume:File Name".  Instead, all file
names MUST be internally stored as volrefno,filename.  (the volrefno now
gives a volume and directory under HFS) If you follow the rules, code can
work under old or new systems.

[Ed. - Reportedly Mac Kermit works just fine under HFS; that is, it works
as well as it does on pre-HFS systems.]

Also, MacKermit does not support out-going wild-cards.  This would be real
useful.

[Ed. - Yup.  So would saving the screen or lines scrolled off the top,
a mouse-positioned cursor, the ability to deal with Mac Binary format, etc.
I hope we'll be able to do some more work in this area some day.]

        Joel West       CACI, Inc. - Federal
        [e-mail]
        {decvax,ucbvax,ihnp4}!sdcsvax!noscvax!westjw

------------------------------

From: Chuck Forsberg WA7KGX <[e-mail]>
Subject: SuperKermit file xfer times
Date: 20 Jan 86 10:46:37 GMT

To answer some questions in INFO-KERMIT, I ran some tests transferring
files with a variety of protocols, including SuperKermit (Kermit with
Sliding Windows).  Here are the results.

        SuperKermit: Some File Transmission Time Comparisons
                        Chuck Forsberg 1-20-86

Two files were used for this series of tests.

A 112070 byte .EXE file produced by the Xenix to DOS cross development
system was used to test the transfer of binary files.  Of the 19886
nulls in the file, many were in buffers, giving a chance to test
Kermit's run length compression.

A 11456 byte document produced by nroff contained no special characters
save CR and LF.  The document used little or no indentation.

Transmissions were from a 9 mHz PC-AT running DOS 3.1 or SCO SYS V Xenix, to
a PC with a NEC V20 at the standard 4.77 mHz.  Ramdisks were used on the DOS
machines.  The 9600 bps transfers used a direct connection between the
adjacent machines.  1200 bps transfers used a Hayes 1200 and MI-2 212a modem
dialup.  Software used was Professional-YAM 15.24, Crosstalk 3.6, and Unix
sb(1).  Pro-YAM to Pro-YAM SuperKermit transfers used 3 byte block check
(CRC-16), eight bit transfers (no quoting), and compression.

Transfers with The Source used the Portland OR Uninet node.  Source Kermit
transfers used 1 byte block check, eight bit transfer, and no compression.
Previous tests have indicated Telenet gives similar results on downloads
from The Source but was very much slower on uploads thanks to poor network
buffering.

.EXE File (112070 bytes)
Time    Speed   Conditions

2:00    9600    Xenix to Pro-YAM YMODEM-g
2:00    9600    Pro-YAM to Pro-YAM YMODEM-g
2:11    9600    Pro-YAM to Pro-YAM XMODEM/CRC
3:54    9600    Pro-YAM to Pro-YAM SuperKermit
4:10    9600    Xenix to Crosstalk XMODEM
5:20    9600    Pro-YAM to Pro-YAM Kermit (NO Windowing)
15:55   1200    Pro-YAM to Pro-YAM YMODEM-k
22:33   1200    Pro-YAM to Pro-YAM SuperKermit
25:22   1200    Pro-YAM to The Source SuperKermit
25:95   1200    The Source to Pro-YAM SuperKermit

Nroff output file (11456 bytes) (all at 1200 bps)
Time    Conditions

1:49    Pro-YAM to Pro-YAM YMODEM-k
1:53    Pro-YAM to Pro-YAM SuperKermit
1:59    Pro-YAM to The Source SuperKermit
5:32    Pro-YAM to The Source Kermit (NO Windowing)

DISCUSSION

Between two directly connected microcomputers, XMODEM protocol gives
good results, 855 bytes per second throughout out of 9600 bps.  The
1024 byte blocks used by Pro-YAM's YMODEM-k and YMODEM-g give a throughput
of 933 bytes per second (97 per cent efficiency).

Pro-YAM's Kermit/SuperKermit routines are based on the code developed at
The Source, which in turn is based on C-Kermit.  Compared to the earlier
Unix Kermit, C-Kermit uses extra layers of processing which limit performance
at high speeds.  The .EXE file should transfer in 2:49 but in fact takes
3:54.  Most of this delay was enforced by the PC stopping the transfer
with XOFF flow control.  A PC-AT or AT&T 6300 should be able to receive
data with SuperKermit at 9600 bps with little or no flow control.

[Ed. - Sigh... Layering is the price we pay for portability.  The old
version didn't run under System III, System V, VMS, or on the Macintosh...]

SuperKermit does allow the receiver (in this case the slower PC) to overlap
serial transfers with its processing.  Without SuperKermit, all the processing
must be done sequentially, resulting in a 5:20 transfer time for the same
file.

The advantage of Sliding Windows or other means of sending multiple blocks
can be seen by comparing the timing for the Xenix to Crosstalk XMODEM
download (4:10) with YMODEM-g download (2:00).

When national or global packet switched networks introduce delays,
the difference becomes significant even at 1200 bps.  The 1:52 transmission
time between two SuperKermits only loses six seconds when uploading to
The Source.  Regular Kermit (no windowing) takes more than twice as long
at 5:32.  Standard XMODEM transfers with Compuserve suffer from similar
delays.

[Ed. - And of course you can't do MODEM transfers with The Source at all,
because an 8-bit path is required.]

The size of the sliding window has little effect on performance as long
as it is large enough to contain the outstanding packets.  The maximum
possible is 31, but it appears that 8 are sufficient for normal conditions.
Of course, if the timesharing system or the network restricts the flow
of data, no amount of windowing is going to help.  I did notice a slight
amount of network flow control when uploading files to The Source.

In the non window transfer with The Source, round trip delay time was
about 1.6 seconds according to my calculations (it seemed longer).
YMODEM-k under these conditions would have uploaded the .EXE file in
19 minutes compared to SuperKermit's 25 minutes.  A Kermit transfer
with 1024 byte packets without windowing would have taken 27 minutes
(losing 3 minutes from the delays, gaining a minute from decreased overhead).

The benefits derived from Kermit's run length encoding form of compression
are greatly dependent on the nature of the files being transmitted.  It
appears most of the difference between the 22:33 minute Pro-YAM to Pro-YAM
SuperKermit transfer and the 25:22 Pro-YAM to The Source transfer is related
to compression available in the Pro-YAM Kermit but not The Source.

However, long files downloaded from bulletin boards are often SQueezed or
compressed before transmission, reducing the value of Kermit's compression.
Most compression programs emit all 8 bit codes, resulting in an average
25 per cent Kermit efficiency loss from control character quoting.

The main Kermit inefficiency in transferring binary files is control
character quoting, which increases transmission time by 25 per cent average.
A useful Kermit extension would be a way to allow most control characters to
be transmitted without quoting.

[Ed. - Right, but this is the same quoting that allows Kermit to work in
environments where MODEM can't.  Extending Kermit to allow a set of control
characters to be transmitted "bare" seems like a good idea, but since it is
just as often the intervening communication hardware or software that is
sensitive to control characters as it is the computers themselves, a great
deal of expertise -- and often "manual intervention" -- would be required
of the user.  Better to pay the price of the overhead.]

A lesser source of overhead comes from the characters that frame Kermit
packets.  It is unfortunate that Kermit does not provide for longer
packets.

[Ed. - But it does -- see the long packet extension, proposed in Info-Kermit
V3 #4.  Some implementations will soon see the light of day.]

                SuperKermit: Unfinished Business

The main item of unfinished business in SuperKermit is to determine the
best criteria with which to force a windowing transfer to abort in a timely
fashion without compromising the robustness of the protocol.  A window
size of 31 means up to 3100 bytes can be sent to the wrong program if one
end of a SuperKermit transfer exits prematurely.  A series of noise bursts
such as dialing crosstalk can generate dozens of spurious packets.  The
normal method of stopping until the line quiets cannot be applied when
the window is open.

[Ed. - Good point!  And thanks for all the work you put into getting
these measurements.]

   Chuck Forsberg WA7KGX  ...!tektronix!reed!omen!caf   CIS:70715,131
   Author of Professional-YAM communications Tools for PCDOS and Unix
 Omen Technology Inc     17505-V NW Sauvie Island Road Portland OR 97231
Voice: 503-621-3406 TeleGodzilla: 621-3746 300/1200 L.sys entry for omen:
omen Any ACU 1200 1-503-621-3746 se:--se: link ord: Giznoid in:--in: uucp

------------------------------

Date: Tue, 21 Jan 86 11:52:43 EST
From: [e-mail]
Subject: Tandem running Guardian OS Kermit?

Do you know of a version of kermit for the Tandem running the Guardian OS?
Or do you know of one under development?

Thanks in advance.

David A. Roth
...decvax!pur-ee!isrnix!pugsly
...ihnp4!inuxc!isrnix!pugsly
Indianapolis,IN

[Ed. - I've received several of these messages lately.  Does anyone know if
Tandem computers have more than one operating system?  We have a version of
Kermit for Tandem, but I think the operating systme is called "Nonstop" --
is that the same thing?  It's written in a language called TAL.  Anybody
know anything about this?]

------------------------------

Date: Tue, 21 Jan 86 21:33:45 EST
From: CHRISTOPHER CHUNG <[e-mail]>
Subject: Novation Apple-Cat II?

Does anyone know of a way to make the Novation Apple-Cat II work with
Kermit?  Is there a version of Kermit that I could get to work with my
Novation modem and my Apple //e or is there a way to modify an existing
version of Kermit to make it work with the Novation?  Any help would be
greatly appreciately!

------------------------------

End of Info-Kermit Digest
*************************
-------
24-Jan-86 14:57:22-EST,12918;000000000001
Mail-From: SY.FDC created at 24-Jan-86 14:56:04
Date: Fri 24 Jan 86 14:56:04-EST
From: Christine M Gianone <[e-mail]>
Subject: Info-Kermit Digest V4 #6
Sender: [e-mail]
To: [e-mail]
Reply-To: Info-Kermit@CU20B
Message-ID: <[e-mail]>

Info-Kermit Digest         Fri, 24 Jan 1986       Volume 4 : Number  6

Today's Topics:
                         Windows over Telenet
                               TIMINGS
                            Frogs in Space
               Problems/suggestions with/for M24-Kermit
     Workaround for VMS V3.7 vs. LAT-11 vs. MSKERMIT V2.28jrd ...
                  More on Tandem's running Guardian
                   Is anyone running HP3000 Kermit?
                    MODEM7/MEX/KERMIT for UTS-30?
                        Ti kermit H19 Question

----------------------------------------------------------------------

Date: Fri 24 Jan 86 13:46:21-EST
From: Christine M Gianone <[e-mail]>
Subject: Windows over Telenet

Below are the results of a test done using WKERMIT.EXE (C-Kermit with windows
for MS-DOS).  Both an .EXE and a .TXT file were transferred.  The speed in all
cases was 1200 baud and mark parity was used, which in turn causes 8th-bit
prefixing in the .EXE file.  The packet size was 90.  This was done at 5:30PM
on a weekday.  The typical network delay was 1-2 seconds (strictly a guess
based on watching modem lights).  Columns A and B show file transfers between
an IBM AT and 'The SOURCE', using a Hayes modem over Telenet; Column A is from
the IBM AT to 'The SOURCE' and Column B is the other direction.  Column C shows
the time it took to send those files from 1 IBM AT to another.  The first time
shown in each column is the result without windowing; the second time shown (in
parenthesis) is the result using a window size of 16.  This test shows a 2-3
fold improvement in speed when windowing is used over Telenet.


File          File     Elapsed time to transfer at 1200b, in mins:secs;
Name          Length
                                      A             B            C

MSKERMIT.HLP  9371                4:15(1:35)    3:04(1:35)   1:45*(1:30)
SHARE.EXE     8896               7:50(2:30)    7:00(2:40)   1:45*(1:30)

* No matter how hard we tried we could not make WKERMIT work between 2
directly conncted PC/ATs.  These numbers are estimates.

------------------------------

DATE: 24-JAN-1986
FROM: BRIAN@UOFT02
SUBJECT: TIMINGS

 Some sample timings for Kermit-11 and long packet support.  The  packet
size  in  the  RSTS/E  to  P/OS  was  500 bytes, the size from RSTS/E to
RSTS/E was 700 bytes. These sizes are somewhat  arbitrary,  they  depend
more on the system's buffering capabilities than anything else.

Host buffering capabilities:

P/OS                    500 (estimated)
RSTS/E 9.0 or later     up to 7000, given sufficient system pool
RSX11M+                 255 (I/D space CPU only)
RSX11M                  34
RT11                    134 (could be larger with simple mod to XC/XL)

 As it can be seen, large packets make sense only for RSTS/E,  P/OS  and
RSX11M+  if  one  wishes  to  avoid XON/XOFF overhead at high speeds. It
should be possible to run  larger  packets  on  M+  and  RT11  at  lower
speeds.


File transfered: K11POS.TSK, size 102,400 bytes (200 disk blocks)
Actual data packet characters AFTER prefixing was 120,857

Time    Speed   Data rate       Comments
seconds baud


1436    1200    84/sec          11/44 to PRO/350, 'Classic' Kermit
                                local phone call
1237    1200    97/sec          11/44 to PRO/350, 500 Char packets
                                local phone call

2915    1200    41/sen          11/44 to PRO/350, 'Classic' Kermit
                                local call, 1 second ACK delay.
1492    1200    81/sec          11/44 to PRO/350, 500 Char packets
                                local call, 1 second ACK delay.

304     9600    397/sec         11/44 to 11/44, 'Classic' Kermit,
                                connected locally via Gandalf switch.
245     9600    493/sec         11/44 to 11/44, 700 char packets,
                                connected locally via Gandalf switch.

 The last two timings are much lower than the  line  speed  due  to  the
fact  the  the  PDP  11/44  is  running 100% busy trying to keep up with
character interupts using a normal terminal driver.  A  special  purpose
driver,  such  as the XK driver found on P/OS, would have lower overhead
and allow somewhat faster data rates.

 Long packets were chosen for Kermit-11 due  to  the  lack  of  suitable
interupt  driven  i/o (at this time) under one of the operating systems,
RSTS/E. The Sliding  windows  would  likely  function  better  in  those
situations  where  the circuit delay is much higher, or when the circuit
can not accomodate large packet sizes.

brian nelson

[Ed. - The long packet specification is in KER:KPROTO.UPD]

------------------------------

Date: 23 January 1986, 16:38:18 SET
From: Richard J Waite           [phone]       C0       at DDAESA10
      VM/CMS S.P.O.D
      European Space Operations Centre
      Robert Bosch Str 5
      6100 DARMSTADT, West Germany.
Subject: Frogs in Space

Good Day,
         For interest only, the little green chap is now helping in
the joint USA - European - USSR "Giotto" project. The data from the
USSR satellite's is being sent from Moscow to us here at Darmstadt
by means of "Kermit". This data is being used by us and also a USA
university. We are using the Turbo pascal Kermit over there on an
IBM clone at 4800. He is doing very well.

Regards.

------------------------------

Date: January 24, 1986, 12:40 CET
FROM:    <#[e-mail]>
Subject: Problems/suggestions with/for M24-Kermit

Hi,
    I've build M24-Kermit from the assembler sources and I've
got some problems:

1.) In module MSYM24.ASM the symbol LNWRAP is defined. This
    symbol is also defined in MSDEFS.H. To compile MSYM24 I've
    commented out the definition line for LNWRAP in MSYM24.ASM.
    (the definitions in the two files are different).
2.) The delete key (<--) does not work in kermits' command mode.
    When I type DEL nothing happens. When I repeat typing DEL the
    whole line disappears. In terminal emulation mode the DEL key
    works perfect.
3.) I can reproduce the scrolling problem in VMS/Phone reported
    earlier this week.
4.) I would prefer to have the ALT/CTRL/F2 active at initalization
    time (see also 5.). Is it possible to do the keyboard mapping
    on a dynamic basis. In this case you can have your standard
    keyboard driver outside of Kermit and a VT100-like driver
    when using Kermit.
5.) This is a suggestion rather than an problem. We have the
    german keybord (type 2) and it would be great to have the
    modified keyboard driver for this type of kb.

    a.) I would be happy to patch the standard KEYBGR.COM
        if someone could tell me what exaxtely is to do.
    b.) I would send a hexified version to KERMSRV.
    c.) Is there anywhere a description (with sources) of
        a keyboard driver (I know it's the wrong list, but...)?


Martin Knoblauch
TH-Darmstadt, D-6100 Darmstadt, West Germany
EARN/BITNET: #D15 at DDATHD21 (the number sign is really
                               part of my UID)

------------------------------

Date: 21-Jan-1986 2320
From: [e-mail]  (SKIN THE BEARS!!!)
Subject: Workaround for VMS V3.7 vs. LAT-11 vs. MSKERMIT V2.28jrd ...

After poking/playing around with all kinds of parameters on both our LAT-11
terminal and our VMS V3.7 system from a Rainbow running MSKERMIT V2.28jrd, and
trying all the suggestions that Frank sent to me (thanx, by the way), the only
solution to all those LAT terminal overruns is to turn down the baud rate on
the Rainbow's comm port, and subsequently the LAT terminal speed as well, to
4800 baud (I had been receiving lots of re-xmit's and buffer overruns on the
LAT line at 9600, more often than not causing the transfer to fail, or else get
roughly one re-transmit for every packet sent- yuucchhhh!!). However, this
behavior does NOT appear when using the same Rainbow, MSKERMIT, LAT port, and a
VMS V4.2 system. THAT works just fine.  I have a feeling that VMS V4.2 has a
lot more intelligence built into its handling of the LAT than VMS V3.7 does.

    Please note, for all those that sent possible fixes, that the LAT
involved here is not a DECSA (or Pluto box as it's sometimes called), nor
is it a DECserver-100; it's "LAT-11", which runs on a Unibus-based -11
with DZ11's, a DEUNA, and 128KW of memory. In this software, you cannot
modify or change flow control; you're stuck with it (maybe to make writing
the application easier?). Turning HOSTSYNC off had helped a bit for a while
on the VMS V3.7 machine, until the machine being used had its LTDRIVER up-
graded to the proper level. Once that happened, turning off HOSTSYNC was
FATAL (i.e., 2 packets get sent, then a timeout occurs), but leaving it on
displayed the same behavior as it did before the LTDRIVER was upgraded.

    Hope this helps anyone getting bitten by this combination.

    Gerry Hafner, DEC LTN (Littleton, MA)

UUCP:    {decvax|ihnp4|allegra|ucbvax|...}
       !decwrl!dec-rhea!dec-wookie!hafner
ARPA:    [e-mail]

------------------------------

Subject: More on Tandem's running Guardian
Date: 23 Jan 86 14:43:43 CST (Thu)
From: ...decvax!pur-ee!isrnix!pugsly
      ...ihnp4!inuxc!isrnix!pugsly

Since I have sent that to you I have talked to the local Tandem sales office
and from what there salesman tells me...  "If it was written in TAL for a
non-stop then it will run on the EXT Tandem under Guardian".  He was in sales
though :-) .

Thanks again!

David A. Roth

------------------------------

Date: Thu, 23 Jan 86 15:55:42 pst
From: amdcad!amdimage![e-mail] (chris moore)
Subject: Is anyone running HP3000 Kermit?

I have been trying to get HP3000 Kermit running, and so far
haven't had any luck.  In the Connect mode, kermit will
accept a line of input, send it out, and then do a read
to get the response back from the other system.  The read
always either timesout with nothing read, or it never returns
at all and kermit hangs.  Is anyone running this version of
Kermit that could give some pointers as to what I may be doing
wrong?  Thanks.
                Chris Moore
                amdimage!cmoore

------------------------------

Date: Thu, 23 Jan 1986  23:54 MST
From: "Frank J. Wancho" <[e-mail]>
Subject: MODEM7/MEX/KERMIT for UTS-30?

I have a number of users in need of a MODEM7/MEX/KERMIT already
configured on a floppy disk for use on a UTS-30 system running CP/M
3.0.  For one user, the need is urgent.  He has been trying in vain to
upload a file for the last month using Sperry's TTY program, and that
file is a report that is growing daily!

Please contact me directly via net mail, or call my office and leave
your name and number and I will return your call.

Thanks,
Frank

AV: 258-6257
FTS:898-6257
505-678-6257

------------------------------

From: dolqci!irsdcp!scsnet![e-mail]
Date:  Wed Jan 22 11:23:45 EST 1986
Subject: Ti kermit H19 Question

I am running my TI PRO to access my UN*X sys III system and am
having trouble with the h19 emulation.  All works well execpt
for the reverse video.  When my screen should go into
reverse video, nothing changes.  Here is the /etc/termcap
entry I use:
# entry for h19 emulation under TI kermit version 2.28 Revision 5
kb|h19|heath|h19-b|heathkit|heath-19|z19|zenith|heathkit h19:\
    :cr=^M:do=^J:nl=^J:bl=^G:\
    :al=1*\EL:am:le=^H:bs:cd=\EJ:ce=\EK:cl=\EE:cm=\EY%+ %+ :co#80:dc=\EN:\
    :dl=1*\EM:do=\EB:ei=\EO:ho=\EH:im=\E@:li#25:mi:nd=\EC:as=\EF:ae=\EG:\
    :ms:ta=^I:pt:sr=\EI:se=\Eq:so=\Ep:up=\EA:vs=\Ex4:ve=\Ey4:\
    :kb=^h:ku=\EA:kd=\EB:kl=\ED:kr=\EC:kh=\EH:kn#8:\
    :k1=\ES:k2=\ET:k3=\EU:k4=\EV:k5=\EW:\
    :l6=blue:l7=red:l8=white:k6=\EP:k7=\EQ:k8=\ER:
Anyone see any faults with this?  I DO have heath 19 on (Just
eliminating the obvious question -:).  Or does kermit h19
not support reverse video?   Thanks to all who helped me with
my last TI problem.   Please mail replies to uucp(1) and+or the
digest.

UUCP:    (1) seismo!dolqci!irsdcp!scsnet!sunder        [phone]
    (2) decvax!philabs!ubbs!sund                (voice)
CIS:    74026,3235
Mail:    IRS 1111 Constitution Ave. NW  PM:S:D:NO
    Washington, DC 20224  Atten: Mark E. Sunderlin

------------------------------

End of Info-Kermit Digest
*************************

-------
28-Jan-86 16:38:26-EST,8106;000000000001
Mail-From: SY.FDC created at 28-Jan-86 16:37:51
Date: Tue 28 Jan 86 16:37:51-EST
From: Christine M Gianone <[e-mail]>
Subject: Info-Kermit Digest V4 #7
Sender: [e-mail]
To: [e-mail]
Reply-To: Info-Kermit@CU20B
Message-ID: <[e-mail]>

Info-Kermit Digest         Tue, 28 Jan 1986       Volume 4 : Number  7

Departments:

  ANNOUNCEMENTS -
    MS-DOS Kermit Support for GRiD Compass
    New Wang PC support module for MS-DOS Kermit
    Victor 9000 Kermit

  MISCELLANY -
    Kermit on the Mac Plus
    Rice TSO and Mac Kermits
    Bug in Wildcard Get in C-Kermit 4C(057)
    HP-3000 Connect Mode (2 messages)
    Tandem Nomenclature Clarification
    FC Tape Format?

----------------------------------------------------------------------

Date: Mon 27 Jan 86 17:21:06-EST
From: Frank da Cruz <[e-mail]>
Subject: MS-DOS Kermit Support for GRiD Compass

This is to announce (belatedly!) support for the Grid Compass II computer
in MS-DOS Kermit, contributed by Jim Noble, Planning Research Corporation,
McLean, VA.  It was found on a tape that he sent us last May, unearthed
during recent excavations.  Only the source file is available for now.  If
anyone out there has a GRiD Compass, please take the file and try it out.
If it works, please point us to an .EXE or .BOO file that we can distribute.
The file is in KER:MSXGRI.ASM, available via anonymous FTP from CU20B.

------------------------------

Date: Mon 27 Jan 86 17:47:26-EST
From: Frank da Cruz <[e-mail]>
Subject: New Wang PC support module for MS-DOS Kermit

Also from Jim Noble -- improved Wang PC support for MS-DOS Kermit, including
key redefinition, ANSI.SYS compatibility, etc.  It's completely untested,
so I'm putting in PS:<KERMIT-MS>MSXWNG.ASM, rather that in the regular
distribution, so as not to overwrite the standard version.  Could somebody
with a Wang PC please grab this new version, try it out (with either
regular 2.28 or else 2.28 jrd), and let me know if & how it works, and
whether the original MSXWNG.ASM can be replaced?  An .EXE or .BOO file would
be appreciated too.

------------------------------

Date: Sat, 25-JAN-1986 11:54 MST
From: <PETERSONB@BYUVAX>
Subject: Victor 9000 Kermit

As is usual with software, immediately after sending in the sources for the
Tektronix version of kermit for the victor, I found a subtle error.  I have
fixed it now and am forwarding a new copy of MSYV9TEK.ASM to you.


                                Bryan G. Peterson
                                PETERSONB@BYUVAX

[Ed. - The new file is in KER:MSYV9T.ASM.]

------------------------------

Date: Mon 27 Jan 86 09:49:41-EST
From: Christine M Gianone <[e-mail]>
Subject: Kermit on the Mac Plus

Had a chance to sample the Mac Plus last week.  It is just as simple as the
Macintosh but much faster in response.  Kermit 0.8(33) works just fine from
both the distribution disk (non-HFS) and the hard disk (HFS).  Files were
easily transmitted from the DEC-20 mainframe to the Macintosh and vise versa
using the Kermit server mode on the DEC-20.

------------------------------

Date: Fri, 24 Jan 86 10:15 EST
From: [e-mail]
Subject: Rice TSO and Mac Kermits

In response to the mention of Rice's Kermits in the last issue of Info-Kermit:

1) TSO Kermit - We are currently running their latest TSO version and
   find it quite capable of binary and text file transfers in both
   interactive and server mode.  Although the installation is a bear, it can
   be done.  It does NOT need the proprietary support package for
   installation and use.  The only reason for these proprietary utilities is
   for recompiling the source.  Although local source modifications to the
   source would be nice, they are not necessary.  The necessary local
   modifications (translate table and local command names) may be made to
   two assembly language routines which have nothing to do with the
   proprietary PL/I software.  Any other needed modifications can be fudged
   in the program call.

2) MacKermit - We had used Rice's MacKermit until the distribution of 0.8
   C-Kermit and found the two leagues apart.  The Rice version was workable,
   but the C version is has so much more in the way being user friendly and
   ease of transfer for either text or application files - it also includes
   better documentation.  Left with the choice, we have chosen C-Kermit
   V0.8(52).

I hope this is of some help to TSO and Mac users with similiar questions.

mark

------------------------------

Date: 23-JAN-1986 16:50:25
From: Kevin Ashley ([e-mail])
Subject: Bug in Wildcard Get in C-Kermit 4C(057)

There is a bug in wildcard get when using C-Kermit under Xenix on a PC/AT (and
possibly in other implementations) causing it to fail after one file. In
CKCPRO, reof() is called to close a file on receipt of an EOF packet. Its
return value is tested to see if this was done successfully. However reof (in
file CKCFNS.C) does not return a value, so what is tested is undefined. When we
compiled C-Kermit with the debug flag on it seemed to work anyway - presumably
the right garbage was being left in the right register - compiling with debug
off, however, caused different garbage to be tested. The cure is relatively
simple, as reof() calls clsof() which does return the value that reof's caller
wants to see. The changes are:

In reof in CKFNS.C:
     After opening {, add
            int  x;

     Change line containing call to clsof to read
            x = clsof(....

     Before the final } add the line

            return(x);

This percolates the return value through corectly.

      Kevin Ashley,
      ULCC Network and Comms Support

      [e-mail], mark f.a.o. Kevin Ashley

[Ed. - Thanks; this change will be in the next release.]

------------------------------

Date: Sat, 25 Jan 86 20:30:41 est
From: Steve Archer  <[e-mail]>
Subject: HP-3000 Connect Mode

I'll take credit for adding the connect mode of the HP3000 Kermit.  Not
knowing hardly anything of SPL, I admit the connect mode is barely usable.
But I do not know any better way to do it.  I would encourage a SPL guru to
step forward and improve the connect mode for the betterment of HP3000
Kermit users. The source does document my assessment of the connect as it is
presently.

steve archer

------------------------------

Date: Mon, 27 Jan 86 11:18:24 pst
From: Sys manager <[e-mail]>
Subject: HP-3000 Kermit

Try disabling xon/xoff on your HP3000. We had problems with HP3000 sending an
xoff right after parsing the password.

Mike

------------------------------

From: tektronix!mako.TEK![e-mail]
Date: Fri, 24 Jan 86 10:02:10 PST
Subject: Tandem Nomencalature Clarification

(I worked for Tandem in '81.)  Guardian is Tandem's only supported OS, which
almost everyone uses.  TAL (Transaction Application Language) is a systems
language, similar to C and ALGOL.  Guardian, and all the other Tandem-supplied
programs, are written in TAL.  NonStop is a trademark of Tandem, used to
describe their computers, i.e. NonStop I, NonStop II, etc.

When you say you have a Kermit for the "NonStop" operating system, you probably
mean for "Tandem NonStop computers, under the Guardian OS".  Hope this helps.

------------------------------

Date: Mon 27 Jan 86 18:17:16-EST
From: Frank da Cruz <[e-mail]>
Subject: FC Tape Format?

Anybody ever heard of FC tape format?  I have a new version of HP-1000
Kermit (the original Fortran version with bug fixes) on an "FC-format" tape
that I can't read -- it's full of ASCII characters mixed with binary data.
Does anyone know of a utility to read it on Unix or a DEC-20?

------------------------------

End of Info-Kermit Digest
*************************
-------
30-Jan-86 12:03:04-EST,9628;000000000001
Mail-From: SY.CHRISTINE created at 30-Jan-86 12:01:49
Date: Thu 30 Jan 86 12:01:48-EST
From: Christine M Gianone <[e-mail]>
Subject: Info-Kermit Digest V4 #8
To: [e-mail]
Reply-To: Info-Kermit@CU20B
Queries-To: Info-Kermit-Request@CU20B
Message-ID: <[e-mail]>

Info-Kermit Digest         Thu, 30 Jan 1986       Volume 4 : Number  8

Today's Topics:
                             7171 warning
                            Strange cursor
                            Hercules Card
      Problem with Issuing Remote Host Commands from VMS Kermit
                    Kermits on the way to you.....
                  Modem7/Kermit for Vector V3-5030?
                 KERMIT for CPM3.0 Osborne Executive
                       Kermit/Osborne Executive
                          Alpha-Micro Kermit
                            Proper credit

----------------------------------------------------------------------

Date: 28 JAN 86 17:19-EST
From: [e-mail]
Subject: 7171 warning

Just a note on using MSKERMIT 2.28 and CMS Kermit thru a 7171 - I thought
I was going nuts!  Everybody's been saying how great it is, etc, etc...
Well, the first thing I HAD to do was setup the ports of the 7171 to what
I thought was 8 data, no parity, 1 stop bit.  Then setup MSKermit in the
same manner (no parity) - all looked fine, till I tried to transfer files,
then NOTHING!!!  All it did was hang - no communication at all.  Then I tried
it on Port 0 (this is always even parity) and everything was fine. To make
a short story long, I set parity SPACE in MSKermit and all was ok from there.
In fact its great! I've defined all the function keys, etc. to my liking - by
the way, did you know that putting comments in a TAKE file effects the define
key area (as in eats ups space!), I found out the hard way (Again).
Hope I can save someone some time with this note....
     [e-mail]

[Ed. - We have also found that 7171's do not like bursts of characters
longer than about 60.  Kermit programs should have their packet lengths
set accordingly.]

------------------------------

Date: 29 Jan 1986 10:58-EST
From: [e-mail]
Subject: Strange cursor

I am running MS-Kermit 2.28 on an IBM-PC with a Hercules card.  A
number times I have noticed that my underline cursor has changed to a
minus sign.  This behavior is very annoying.  Does anyone know what
might be causeing this?  I should point out that exiting and running
most programs will not fix the problem.  The only fix I know is running
MODE or rebooting.  Also, using the commands to change to a block
cursor and back will change to a block cursor, but return to the minus
instead of the underline.  The switchover always occurs when connected,
but I have not discovered what will cause the change.

-Israel ([e-mail])

[Ed. - See next message.]

------------------------------

Date: 29 JAN 86 10:09-MST
From: JRD@USU
Subject: Hercules Card

Hercules graphic adaptor and minus sign cursor. That appears very much like
the bug in DOS itself whereby at startup time the cursor characteristics are
copied from ROM to RAM, but not consistently. The RAM copy can be bad for
a while; if a program picks up the characteristics it may see a minus sign
rather than an underline. There was an article (note really) on exactly this
problem published in PC Tech Journal about one or two months ago. The root
of the problem is the scan line numbers of the cursor are smaller on color
boards (&compats) than on the monochrome adapter. Thus, color board cursor
line numbers end up as a minus sign on the monochrome adapter. How one boots
will determine the presence or absence of the minus sign cursor. A patch is
in the PC Tech note.
        Regards,
        Joe D.

------------------------------

Date: Tue, 28 Jan 86 20:48:37 est
From: biomed![e-mail] (Simon Rosenthal)
Subject: Problem with Issuing Remote Host Commands from VMS Kermit

I am having some trouble with VMS Kermit (3.1.066), running under VMS
3.7. When using it in local mode to talk to C-Kermit running in server
mode on a Masscomp system - (basically SYS V Unix), VMS Kermit insists
on uppercasing the text of any command sent to the server using REMOTE
HOST, according to the debugging log.  Needless to say, the Unix end
doesn't like this at all ...  Is there a Kermit-32 command I'm missing
which will force VMS Kermit to send out exactly what I type, or is this
a misfeature I'll have to live with?

Simon Rosenthal <[e-mail]>

[Ed. - I'm pretty sure this is a feature you have to live with.  I'll
pass your message on to the Stevens folks.]

------------------------------

Date: 28-JAN-1986 10:07:47
From: [e-mail]
Subject: Kermits on the way to you.....

A tape is on its way to you today with a good crop of new Kermits on it.
There's a letter with the tape, but briefly here's what to expect:

   Version 1.30 of Kermit for Acorn BBC micro
   Version 2.1 of Kermit for GEC 4000 series
   New Kermit for Joyce-Loebl Magiscan 2 image processor. This is a UCSD
     p-System machine: the Kermit is based on UCT for Terak, and has had
     8 bit prefixing and some other things added that will be of interest
     to UCSD Kermit users in general
   Kermit for Honeywell MultiSystem Executive and clones under Concurrent
     CP/M-86
   Kermit for a U-Microcomputers U-MAN 1000 micro under CP/M-68k
   Updated version of Chris Kennington's high-portability C Kermit
   A number of new CP/M-80 Kermits, (CP4SYS, TYP and HEX files) for
          Acorn BBC micro with Z80 processor
          North Star Horizon using onboard serial ports rather than SIO board
          North Star Advantage
          Cromemco
          Apple II with Z80 Softcard and CPS card
          Superbrain using auxiliary port, and using main port
          Torch series
          Cifer 1886
          Research Machines RM380Z

Kermit for Amstrad series micros running CP/M-80 is on the way but hasn't
arrived in time to make this tape.

Full details will be in with the tape.

Have passed your message re CP/M to Bertil. Am having mailer trouble (again)
but will try hard to get his reply to you.

           Alan

[Ed. - We will announce these versions when they arrive.]

------------------------------

Date: 20 Jan 86 15:36:52 PST
From: [e-mail]
Subject: Modem7/Kermit for Vector V3-5030?

Does anyone have modem7 and/or kermit for the Vector V3-5030 (CP/M 2.2)
on the ferschlugginer 16-sector (hard) 5.25" floppy?  Please reply to

------------------------------

Date: Mon, 6 Jan 86 10:19:08 est
From: Hal Carter <[e-mail]>
Subject: KERMIT for CPM3.0 Osborne Executive?

 Is there a version of KERMIT that works on an Osborne Executive.
I've tried the generic CPM 3.0 version, but nothing goes out the
AUX port to my modem.  (I have a Prometheus ProModem, and Modem 740
works fine).

Thanks for any leads.

[e-mail]

[Ed. - See next message.]

------------------------------

Date:  Wed, 8 Jan 86 12:28 EST
From:  "Paul E. Woodie" <[e-mail]>
Subject:  Kermit/Osborne Executive

I recently noticed a request on this mailing list for a version of
kermit to run on the Osborne Executive.  I have an Executive and tried
unsuccessfully to get several different cpm3 'generic' versions to run.
I don't know if my failure was due to equipment bugs in my particular
system, operator error on my part, or what.  In any case I finally got a
'generic' version from simtel20 written in turbo pascal.  That also (of
course) did not run completely on my system.  However, I modified it to
directly address the SIO ports instead of using the built-in AUX port of
the 'generic' versions.  Now it runs just fine.

I would be happy to share it with anyone interested.  I haven't so far
because I thought that maybe I had a flaky piece of hardware and my
problems were unique.

--Paul Woodie (Woodie.CPE at dockmaster)

[Ed. - Hope you can submit this to an Osborne User's Group?]

------------------------------

Date:    Wed, 29 Jan 86 07:39 EST
From:  [e-mail]
Subject: Alpha-Micro Kermit

Is anyone running Kermit on an Alpha-Micro with AMOS
V1.3(123)?  Assembly was no problem, but it just refuses
to recognize the AMOS version as valid.  I would appreciate
any patches or comments on this frustrating problem.

mark johnson,
university of notre dame

------------------------------

Date: Wed, 29 Jan 86 07:25 EST
From: [e-mail]
Subject: Proper credit

For the record, I would like to remind Info-Kermit that the bug in
C-Kermit 4C(057) CKFNS.C regarding reof()'s forgetting to return a
value (as reported by Kevin Ashley ([e-mail].w) in the latest
Info-Kermit) was first reported several months ago by a colleague of
mine here at Clemson University, William Faulkner ([e-mail]).
Frank da Cruz had noted that Faulkner's suggested fix would be installed
in 4C(057).  Was this not done?

As an aside, I find it amusing that both Faulkner and Ashley used *exactly*
the same fix, derived independently of each other, I am sure.

                                        -- Larry Afrin

------------------------------

End of Info-Kermit Digest
*************************
-------
 6-Feb-86 12:03:53-EST,12350;000000000001
Mail-From: SY.CHRISTINE created at  6-Feb-86 12:03:00
Date: Thu 6 Feb 86 12:03:00-EST
From: Christine M Gianone <[e-mail]>
Subject: Info-Kermit Digest V4 #9
To: [e-mail]
Reply-To: Info-Kermit@CU20B
Queries-To: Info-Kermit-Request@CU20B
Message-ID: <[e-mail]>

Info-Kermit Digest         Thu,  6 Feb 1986       Volume 4 : Number 9

Today's Topics:
                       TSO and VMS Kermit fixes
                  List of commercial KERMIT products
         VMS C-Kermit fails to provide interactive subprocess
        7171 Entry for Macintosh (VT100 without highlighting)
                       Kermit over LAN gateways
                         MS-Kermit Suggestion
                       Olivetti Keyboard Layout
                       Kermit for Victor/Sirius
                         Re: Strange Cursors
                         Osborne Exec Kermit

----------------------------------------------------------------------

Date: Wed 5 Feb 86 18:56:38-EST
From: Frank da Cruz <[e-mail]>
Subject: TSO and VMS Kermit fixes

Received from Jim Noble, Planning Research Corp, McLean VA -- some fixes
for VMS Kermit and MVS/TSO Kermit.  In KER:VMSMIT.BWR and KER:TSOKERM.BWR,
respectively.  The TSO fix is allow assembly under IFOX00 (whatever that is).
The VMS changes are mostly bug fixes.

------------------------------

From [e-mail]  Sat Feb  1 09:44:01 1986 remote from angel
Date: Saturday, 1 February 1986, 09:42-EST
From: George Carrette <angel![e-mail]>

A new kermit is on the way, derived from LMI KERMIT: MACLISP KERMIT for
PDP-10 Maclisp. (Runs under the ITS and TOPS-20 operating systems).
More info to follow. -gjc (GJC-AT-LMI@MIT-MC)

------------------------------

Date: Sun 2 Feb 86 12:25:30-EST
From: [e-mail]
Subject: List of commercial KERMIT products

I submit the following list of commercially avaiable MS-DOS VT100/TK4010 (&
Macintosh) terminal emulation programs with KERMIT protocol.  Nearly all
support also XModem.  Not all available features of each product are listed,
and some listed options are $EXTRA.  Nearly all are written to run on PC/XT/AT
and compatibles, and some may run additionally specifically on PCjr, Zenith,
Wang, etc.  Some support internal modems.  One product may zoom/pan, another
may save/restore graphics screens, still another may autoswitch text/graphics
modes, etc.

For more info about any of these products, one should call the vendor(s)
directly, but I would welcome comments from people here at Columbia or
elsewhere who have actually used these or similar products.

- Farhad
Nuclear Science & Engineering
Columbia University, NYC
[e-mail]

Caveat-&-Disclaimer: This short list is based on preliminary data and is
submitted for informational purposes only.  It is extracted from recent data
published elsewhere and is by no means claimed to be complete or accurate.

TELEPHONE    LIST VENDOR                 PRODUCT     EMULATION(S)

[MS-DOS:]
608-273-6000 $295 Persoft                SmarTerm240 VT52/100/125/220/240, and
                                                     TK4010/4014
303-690-6279  250 Henson Systems         CRTXE       VT52/100, 20 others, and
                                                     (soon:) TK4010, ReGIS
212-777-6707  249 Coefficient Systems    VTerm/4010  VT100, TK4010
617-367-6846  195 Boston Software Works  LC-Term     VT100
212-777-6707  160 Coefficient Systems    VTerm III   VT100
615-376-4146  150 Scientific Endeavors   VTEK        VT52/100, TK4010,4014
604-732-7411  150 KEA Systems            ZSTEMpc     VT100, TK4010
617-576-2760  124 Mark of the Unicorn    PCIntercom  VT100
617-659-1571   85 Solution Systems       ZAP         VT52/100, TK4010
215-664-4914   70 Cheshire Cat Software  Zap         VT52/100

[Apple Macintosh:]
603--673-8151 $195 White Pine Software   Mac240      VT100/220, ReGIS

[Ed. - Kermit is appearing in more and more commercial communications programs,
and soon we'll have quite a few of them with sliding windows too -- Crosstalk
among them.  Most of these companies have agreed in writing to comply with the
conditions given in our "Policy on Commercial Use and Distribution of Kermit"
flyer (KER:AAXCOM.DOC), which means that purchasers of these products should be
getting the Kermit component "free".]

------------------------------

Date: 4 Feb 86 15:08:00 EST
From: "NUNN, JOHN C." <[e-mail]>
Subject: VMS C-Kermit fails to provide interactive subprocess

The VMS implementation of C-Kermit does not provide an interactive
subshell (subprocess for VMS) for the "!" command.  This problem can
be corrected by making the changes shown below.

[Ed. - Code omitted, added to KER:CKVKER.BWR.]

------------------------------

Date: Wed 5 Feb 86 08:24:29-EST
From: Frank da Cruz <[e-mail]>
Subject: 7171 Entry for Macintosh (VT100 without highlighting)

BY popular demand, here is the 7171 code to support Macintosh
Kermit's VT-102 emulator:

**************************************************************
* MODULE NAME = VT100                         *
**************************************************************
VT-100     TERM  GENI,ORIGIN=X'01',RCHRS=GENSRCHS,FLAGS=X'0C00'
VTCSS1     CSS   ESC,LBRACK,(CHARY),SEMI,(CHARX),H    * POSITION
VTCSS2     CSS   ESC,LBRACK,K        * ERASE EOL
VTCSS3     CSS   ,            *
VTCSS4     CSS   BEL            * TONE
VTCSS5     CSS   BS            * CURSOR LEFT
VTCSS6     CSS   ESC,LBRACK,C        * CURSOR RIGHT
VTCSS7     CSS   ESC,LBRACK,A        * CURSOR UP
VTCSS8     CSS   ESC,LBRACK,B        * CURSOR DOWN
VTCSS9     CSS   ESC,LBRACK,@1,LCQ    * SIGNAL INSERT MODE
VTCSS10     CSS   ESC,LBRACK,@0,LCQ    * SIGNAL END INSERT MODE
VTCSS11     CSS   ,            *
VTCSS12     CSS   ESC,LBRACK,H,ESC,LBRACK,J    * CLEAR
VTCSS13     EQU   *
     CSS '\=\<\[H\[J\[?1h\[?3;6;7l\[20l\[0q\[0m'
VTCSS14     CSS COLON            *
VTCSS15     CSS   ,            *
VTCSS16     CSS   ,            *
VTCSS17     CSS   ,            *
VTCSS18     CSS ESC,LBRACK,(CHARFLD),LCM    *
VTCSS19     CSS   ,            *
*
**************************************************************
* Macintosh PC running Kermit (VT100 w/out highlighting         *
**************************************************************
MAC     TERM  GENI,ORIGIN=X'01',RCHRS=GENSRCHS
     CSS   EQU=VTCSS1
     CSS   EQU=VTCSS2
     CSS   EQU=VTCSS3
     CSS   EQU=VTCSS4
     CSS   EQU=VTCSS5
     CSS   EQU=VTCSS6
     CSS   EQU=VTCSS7
     CSS   EQU=VTCSS8
     CSS   EQU=VTCSS9
     CSS   EQU=VTCSS10
     CSS   EQU=VTCSS11
     CSS   EQU=VTCSS12
     CSS   EQU=VTCSS13
     CSS   EQU=VTCSS14
     CSS   EQU=VTCSS15
     CSS   EQU=VTCSS16
     CSS   EQU=VTCSS17
     CSS   EQU=VTCSS18
     CSS   EQU=VTCSS19
*

------------------------------

Date:         Mon, 3 Feb 1986 15:51 EDT
From:         Bill Seeley <WAS@UMAB>
Subject:      Kermit over LAN gateways

I think the fundamental problem with using Kermit across a LAN gateway
will not be with Kermit per se.  The basic problem seems to be that
most gateway systems require the user to run an application in his/her
workstation in order to communicate across the LAN to the gateway server.
Once a port is allocated on the gateway server, there must be some way
to re-direct Kermit's I/O from COMn: to the communication channel provided
by the server.  I believe Bridge Communications has a product for 3COM
Ethernets in beta test which claims to support "COM1 re-direction."
Ungermann-Bass' Net/One also claims to support a similar function using
a variant of MS-NETWORKS.  I'm curious to know if anyone else out there
has experience using Kermit with these or similar products.  If you would
publish this in your Info-Kermit newsletter I'd be most grateful.

Thanks,
Bill

------------------------------

Date: Sun, 2 Feb 86 23:14:30 PST
From: [e-mail]
Subject: MS-Kermit Suggestion

It would be nice if MS-Kermit would use an DOS environment variable to locate
it's profile (MSKERMIT.INI), so that Kermit can be invoked from various
sub-directories of a hard disk with only *one* copy of the profile stored on
the hard disk.  Alternately, MS-Kermit could employ the search PATH used by DOS
for it's command files.

An example of how the former scheme would work is:

A>SET MSKERMIT=C:\COMM\KERMIT

The above should make MS-Kermit use C:\COMM\KERMIT as its profile if
C:\COMM\KERMIT is a file, but use C:\COMM\KERMIT\MSKERMIT.INI if C:\COMM\KERMIT
is a sub-directory.  This shceme would allow the user to specify not only a
sub-directory, but optionally also the exact name of the profile, all in one
DOS environment variable.

The specification of the scheme may sound complicative at first glance, but it
really is quite intuitive when it is in use.

...Sam Lam

[From jrd -- Path searches really ought to be done I suppose; it just takes
some time to write the code to a) test if DOS found a file on its own and b)
chugging down the PATH= string trying the selections. I sort of put this into
category B, do when time is available, together with things like redefinable
keys at the Kermit prompt level. A directly usable Kermit seems more important
than waiting for the endless series of 'frills' to be added.]

------------------------------

Date: Wed, 5 Feb 86  11:00 EST
From: E. Thaler, Swiss Federal Institute of Technology ( ETH Zuerich )
Subject: Olivetti Keyboard Layout

Hello

We got and installed your Kermit Version 2.27 for Olivetti M24 with
VT 100 emulation. It works fine.

We are using a keyboard of swiss-german type with a different keyboard
layout. To display the appropriate characters, we need to adapt
the keyboard-driver program (KBDVT100).
Is it possible to get the source of the keyboard-driver?

[Ed. - Sorry, this version came via slow boat from Australia.
It would take longer to get this program then it would be to
wait for the next version of MS-DOS Kermit (2.29).]

------------------------------

Date: 29-JAN-1986 13:19:14
From: [e-mail]
Subject: Kermit for Victor/Sirius

It may not be a good idea to remove SIR files just yet. Over here there
have been a lot of changes in Sirius/Victor dealerships, resulting in long
periods when no-one seemed to want to sell anything for them. Result is that
MS-DOS 2 is not, I think, that common - and MS-Kermit won't support MS-DOS 1.
I've put out a question in our UK info digest asking Sirius users for comments,
and I'll get back to you.
                  Alan

[Ed. - Don't worry, we won't delete the old stuff until we're sure it's safe.]

------------------------------

Date:         Fri, 31 Jan 1986 10:33 EST
From:         Nick Gimbrone <NJG@CORNELLA>
Subject:      Re: Strange Cursors

Can someone append the fix for the minus sign cursor seen on MSKermit for those
of us that do no have access to PC Tech J.?

------------------------------

From: dolqci!irsdcp![e-mail]
Date:  Wed Feb 5 17:26:01 EST 1986
Subject: Osborne Exec Kermit

I have managed to get Kermit running on the Exec via generic CP/M 3.0, and I
will try over this weekend to duplicate it, although it was done useing an
older version of Kermit.  I will forward the results to the list.

I am, however, VERY interested in the Turbo Kermit mentioned, and if the
sender of that note would contact me, I would like to get a copy.  I will
submit it to the local OUG (Capitol Osborne User's Group), and I am sure
CapOUG will forward it to FOG (First Osborne Group).

                                                         Jon

~ Addresses:  USnail: IRS, 1111 Constitution Ave. NW   Washington, DC 20224  ~
~             Atten: Jon Albers, Room 6335 D:C:P                             ~
~          Office Number Down Under: [phone]   (FTS)566-5240           ~
~      UUCP:  .....seismo!dolqci!irsdcp!albers (3rd floor Zilog: Down Under) ~
~      ARPA:  [e-mail]                                          ~

[Ed. - If you do manage to track it down and submit it to the User Group,
please let us know so we can add it to the list of diskette sources.]

------------------------------

End of Info-Kermit Digest
*************************
-------
11-Feb-86 14:16:12-EST,13745;000000000001
Mail-From: SY.CHRISTINE created at 11-Feb-86 14:13:35
Date: Tue 11 Feb 86 14:13:35-EST
From: Christine M Gianone <[e-mail]>
Subject: Info-Kermit Digest V4 #10
To: [e-mail]
Reply-To: Info-Kermit@CU20B
Queries-To: Info-Kermit-Request@CU20B
Message-ID: <[e-mail]>

Info-Kermit Digest         Tue, 11 Feb 1986       Volume 4 : Number 10

Today's Topics:
                         MS-Kermit Suggestion
                            MSKERMIT-JRD/2
              Mail Using Kermit; Protocol Clarifacations (2 msgs)
                            TELENET KERMIT
                    Tapes, GEACs, Victors, etc....
                       PROCOMM Freeware Package
                Undocumented Microsoft LINK Option: /E
                   Dashed Cursor Problem on IBM PC
                      THE FROG for 64-bit CDC's?
                           MS-DOS kermits?

----------------------------------------------------------------------

Date: Thu, 6 Feb 86 10:20:28 PST
From: prandt![e-mail] (David E. Tweten)
Subject: Re:  MS-Kermit Suggestion

From: [e-mail]

    It would be nice if MS-Kermit would use an DOS environment variable to
    locate it's profile (MSKERMIT.INI), so that Kermit can be invoked from
    various sub-directories of a hard disk with only *one* copy of the
    profile stored on the hard disk.  Alternately, MS-Kermit could employ
    the search PATH used by DOS for it's command files.

My copy of MS-Kermit version 2.28 (with some local mods which don't affect
this behavior) already does that.  I ordinarily keep both Kermit and its
initialization file in a directory which is on the MS-DOS PATH.  To confirm
that it works more generally than that, I just moved Kermit itself, to yet
another directory on the PATH, and that worked too.  From a third directory,
I invoked Kermit, which MS-DOS found in one directory on the path, and Kermit
read MSKERMIT.INI from yet another directory on the PATH.

    [From jrd -- Path searches really ought to be done I suppose; it just
    takes some time to write the code to a) test if DOS found a file on its
    own and b) chugging down the PATH= string trying the selections. I sort
    of put this into category B, do when time is available, together with
    things like redefinable keys at the Kermit prompt level. A directly
    usable Kermit seems more important than waiting for the endless series
    of 'frills' to be added.]

In my opinion, for those of us who have hard disks (more and more, lately),
searching the PATH for MSKERMIT.INI is not a frill.  It is basic function.
If the (soon to be) 2.29 version of MS-Kermit doesn't do this, I have no
intention of using it until it's modified.

[From JRD: MSKERMIT.INI is sought with paths after all.  The procedures have
not been changed by me from the original Columbia 2.28 release for this item
nor for Take file searchs.  Kermit does find MSKERMIT.INI if it is on the
environment PATH= list.  The RUN command and its Server counterpart REMOTE
HOST command work similarly.]

------------------------------

Date: Thu, 06 Feb 86 17:00:00 EST
From: Edgar B. Butt <[e-mail]>
Subject: MSKERMIT-JRD/2

I FTP'd MSKERMIT-JRD/2 from CU20b on 2/6/86.  Although I haven't had a
chance to test it extensively, it seems to work fine on my Zenith 151.
There are two minor problems which I don't see in the BWR file that are not
hard to solve.

First, when I type SEND with no file specified, MSKERMIT asks for LOCAL
DESTINATION FILE.  I now know that LOCAL is correct and DESTINATION is
wrong.  The REMOTE SOURCE FILE is equally confusing.  Different messages
from those used for GET should be used.

Second, when MSKERMIT is sending a file with a non-ascii character (8-th bit
set) over a 7-bit data path with no 8-bit quoting, it issues a warning and
then proceeds to send the data in a packet with a parity error causing the
transfer to come to an eventual halt.  Below is code to issue the warning,
strip the 8-th bit and continue the transfer.

Regards,
Edgar Butt ([e-mail])

[Ed. - The changes you sent will be in the next version of MS-DOS Kermit
(2.29).  Thanks!]

------------------------------

Date: Wed 5 Feb 86 15:05:40-PST
From: Bob Larson <BLARSON@usc-ecld>
Subject: Mail Using Kermit; Protocol Clarifacations

I have written a mail transport system from our Primes to our Tops-20
systems (and visa-versa) using the kermit protocol for the file transfer.
It uses the existing tops-20 kermit and a special purpose kermit subset I
wrote for this use on the prime.  (I could send this to you, but it does not
pretend to be a general purpouse kermit.)

What is the proper response to a Send-init ("S") packet (acknolaged)
followed by a Break-Trasmission ("B") packet?  Should the break-transmission
packet be acknolaged (as tops-20 kermit does) or should an error packet be
sent?

I think a couple of clarifications could be made to section 6.2 of the
protocol manual (fifth edition, which I think is current):

A sentence to the effect: "The 8th (parity) bit should be taken into account
on the checksum if and only if an 8-bit data channel is known to exist."
would probably be appropriate here, even if though it is stated elsewhere.

An alternate checksum calculation for languages/machines that do not allow
bitwise logical operations but do have integer division (/) and modulus (%)
is:

    check = char ((s + ((s / 64) % 4)) % 64)

(This results in identical checksums as the other calculation.)

Bob Larson
Arpa: [e-mail]
Uucp: ihnp4!sdcrdcf!oberon!blarson

------------------------------

Date: Fri 7 Feb 86 09:07:17-EST
From: Frank da Cruz <[e-mail]>
Subject: Re: Mail using kermit; Protocol clarifacations

An S-B sequence is perfectly valid -- it's the "null transaction".  Depending
on the implementation, it could happen if none of the specified files was
read-accessible.  The B packet should be acknowledged, although the sender
of the B packet should not be overly stringent in waiting for the ACK, because
there's always the situation in which the receiver gets the B packet, ACKs it,
and then exits, but meanwhile the ACK is lost.  (Although the S-B sequence
is valid, it might be a little kinder to the user to send an Error packet
when no files can be sent...)

All the protocol issues you raise are (I hope) clarified in the Kermit book.

- Frank

------------------------------

Date: Fri 7 Feb 86 10:42:20-EST
From: [e-mail]
Subject: Re: TELENET KERMIT

My request for advice on tips for network transfer should have been for
TYMNET, and not TELENET.

I fiddle with parameters, REC timeout and PARity but can only achieve about
a 15% success rate with no pattern for successes or failures.  KERMIT will
usually hang on initial packet, or time out with repeated sends <RET's>.

Any help appreciated.

 joe

[Ed. - Anybody who can help, please reply to Info-Kermit so that others with
similar problems can see the solution.]

------------------------------

Date: 6-FEB-1986 15:23:13
From: [e-mail]
Subject: Tapes, GEACs, Victors, etc....

 I asked around about GEAC - it's a Canadian machine used for specialised
Library work. No-one's heard of a Kermit for it.  For your info, address is
GEAC Computer Corp, 350 Steel Case Road West, Markham, Ontario, Canada. OS
is totally unique but will shortly be UNIX-clones- there is a machine in New
York University library, I'm told. Here endeth the GEAC saga.
 On new Kermit front: both Manchester U. and Imperial College London are doing
new/inproved Kermits for Cybers running NOS (one in Pascal, one in Compass).
Will pass them on when they get finished.
  Your next message will contain a .BOO file for MS-DOS Kermit for the
Victor 9000/Sirius 1.

      Alan

[Ed. - Thanks.  The .BOO file is in KER:MSVV90.BOO.]

------------------------------

From: <decwrl!decvax!mcnc!rti-sel!ethos![e-mail]>
Date: Sat, 8 Feb 86 14:54:49 est
Subject: PROCOMM Freeware Package

    I just picked up a communications package from one of the local BBSs
here in Research Triangle Park, NC.  It's called PROCOMM, a freeware package by
PIL software systems.  This program is probably the best one I've seen at *any*
price for MS-DOS.  It's fully as good as MEX on CP/M.  It supports both xmodem,
and kermit protocals, terminal emulation, keyboard macros, and scripts.  Its
rather large, so I won't post it on the net unless there is enough interest.  I
will however put it on my BBS.  The reason I mentioned it is that it supports a
env variable called PROCOMM which contains the path for the parameter files,
it searches this if it doesn't find them on the current directory.  Highly
recommended.

Jay Denebeim                "One world, one egg, one basket."
  {seismo,decvax,ihnp4}!mcnc!rti-sel!ethos!jay
  Deep Thought, ZNode #42 300/1200/2400 919-471-6436

------------------------------

From: Ya'[e-mail]
Subject: Undocumented Microsoft LINK Option: /E
Date: Mon 10 Feb 1986 13:44-MST

There exists an undocumented(?) switch to Microsoft LINK.EXE ver 3.XX,
which will cause an automatic compaction during binding.  This process
will eliminate storage for uninitialized arrays from the .EXE file
produced by the linker, reducing the .EXE file size by up to 300
percent!  To use this feature, specify the /E option to the command
line, eg

        LINK myprog/E;

should work.  For example, PCKERMIT.EXE ver 2.27 was 80K when linked
normally but shrunk down to 33K when linked with the /E option...

[Ed. - The question is will any arbitrary DOS machine be able to execute
an .EXE file that was produced this way?]

------------------------------

Date: 7 FEB 86 10:51-MST
From: JRD@USU
Subject: Dashed Cursor Problem on IBM PC

In response to the minus sign as a cursor problem reported in recent Digests
the PC Tech Journal article discussing the problem is "The Dashed Cursor",
by Paul Pierce, PC Tech J., Dec. 1985, page 47. His code goes like this:
...................................
;
; Program FIXCURS.ASM by Paul Pierce, PC Tech Journal, Dec 1985, page 47.
;
code    segment public 'code'
        assume cs:code, ds:code, es:nothing
;
;       This program is set up to be made into a COM file
;
        org     100H
;
; First check for the monochrome adapter.
;
start:  int     11H             ; set ax = equipment flag
        and     al,30H          ; mask off all but video bits
        cmp     al,30H          ; test for monochrome adapter
        jne     exit            ; jump if not monochrome
;
; Now check for incorrect cursor mode returned from the Bios
;
        mov     ah,3            ; call bios to get cursor type
        int     10H             ;
        cmp     cx,0607H        ; check for invalid (color) type
        jne     exit            ; jump if not a bad value
;
; At this point we know that the monochrome adapter is in use and that
; the bios cursor mode is incorrect.
; Call the bios to set the cursor type correctly.
;
        mov     cx,080cH        ; use correct cursor type
        mov     ah,1            ; call bios to set cursor type
        int     10H

exit:   mov     ah,0            ; exit back to DOS
        int     21H

code    ends
        end     start
............................................
[Reproduced without anyone's permission.]
        Regards,
        Joe D.

------------------------------

Date: Mon, 10 Feb 86 14:18:00 pst
From: Joel West <[e-mail]>
Subject: THE FROG for 64-bit CDC's?

Is anyone aware of a version of kermit for one of the following
two machines (I'm told the software would be similar):
    * Cyber 205 running VSOS
    * Cyber 170 running NOS/VE
The existing CDC kermit for NOS, NOS/BE likely won't work for several
reasons:
    * different, yet another semi-compatible CDC OS
    * 60- (old) vs. 64-bit (new) machine word size
    * 6- (old) vs. 8-bit (new) characters
    * CDC character set vs. ASCII

One last hope is that every 205 has a 170 as a front end, so if the
one I'm going to use has NOS, then I can use the existing kermit.
Otherwise, it sounds like I'll have to do a port of C-Kermit or the
mini-kermit in the protocol manual...

    Joel West    CACI, Inc. - Federal
    [e-mail]
    {decvax,ucbvax,ihnp4}!sdcsvax!noscvax!westjw

[Ed. - See message above from Alan Phillips.]

------------------------------

From: hplabs!seismo!mcvax!wcwvax![e-mail]
Date: Sun 9 Feb 1986 12:51:05 GMT
Subject: MS-DOS kermits?

There seems to be a vast number (spawn?)  of Kermits available for different
operating systems and machines; in particular, several different versions
for MS-DOS have been mentioned in this digest.  Can someone publish a list
of all the variants that are available currently in the public domain?

A friend of mine is looking for an MS-DOS kermit: is the source code of such
available from anyone in the U.K. (on tape, perhaps)?

[Ed. - Alan Phillips (see message from him above) at Lancaster University
distributes Kermit on magnetic tape & other media in the U.K. as time permits
him:  his postal address and phone number are:

    Alan Phillips
    Communications Group
    Department of Computing
    Computer Building
    Lancaster University
    Lancaster LA1 4YW, ENGLAND
    Phone [phone] x 4881
]

------------------------------

End of Info-Kermit Digest
*************************
-------
13-Feb-86 17:04:33-EST,11120;000000000001
Mail-From: SY.CHRISTINE created at 13-Feb-86 17:03:50
Date: Thu 13 Feb 86 17:03:50-EST
From: Christine M Gianone <[e-mail]>
Subject: Info-Kermit Digest V4 #11
To: [e-mail]
Reply-To: Info-Kermit@CU20B
Queries-To: Info-Kermit-Request@CU20B
Message-ID: <[e-mail]>

Info-Kermit Digest         Thu, 13 Feb 1986       Volume 4 : Number 11

Today's Topics:
                MS-DOS Kermit 2.29 Not Forgotten
                  Re: MS-Kermit path suggestion
                     Problems with MSKERMIT?
                        Okstate Downtime
                            C-Kermit
                   THE FROG for 64-bit CDC's?

----------------------------------------------------------------------

Date: Wed 12 Feb 86 09:51:36-EST
From: Frank da Cruz <[e-mail]>
Subject: MS-DOS Kermit 2.29 Not Forgotten

In case you've been wondering what ever happened to MS-DOS Kermit 2.29,
or missed the earlier announcements of 2.28 jrd, 2.28 jrd/2, etc, here's
a brief status report.

Joe Doupnik at Utah State University (connected to us by BITNET), has been
putting an incredible amount of work into the forthcoming release (considering
that he, like all of us, has a "real job" to do as well).  He now has a
remarkably complete VT102 emulator built in to the program, without having
sacrificed the Heath-19 emulator.  In fact, since VT52, H19, VT100, and VT102
are all so closedly related, he's got them all in there.  Several test versions
of this have gone back & forth (well, mostly forth), and the last remaining
nits are being picked, with the terminal emulation as well as fine points
relating to operation under TopView, MS Windows, PC Network, with EGA board,
etc.  It seems that the fine points are what take the time (the old 80/20
rule) and raise the most hackles.

Once the nits are quelled (parents of young children will understand this
allusion), the final job will be to get the program working again on the
non-IBM MS-DOS systems -- Rainbow, etc.  I think the best idea is for us to
provide .EXE and .BOO files for those systems we can test (IBM family,
Rainbow, HP-150), and leave the others alone (at 2.27 or 2.28 level) until
somebody sends us new, tested ones.  So if you have any of the other MS-DOS
systems Kermit claims to support -- NEC APC & APC3, Victor/Sirius, HP110,
Wang, Apricot, Grid, Heath/Zenith, Sanyo, TI Professional, etc. -- please
be prepared to grab the source or object files when they become available,
build and test the new release, and send us a .BOO and/or .EXE file by
electronic mail (or postal mail on IBM PC format diskette), or put them
somewhere where we can get them with FTP.

And I might as well make my usual pitch about diskettes -- when you have a
new version of Kermit working on your system, PLEASE send it on diskette
to an appropriate user group, "public domain" diskette service, or other
entity capable of reproducing and selling it by mail order at low cost
(what's low?  I'd say under $10 or $20 for a diskette) for the benefit of
all the PC/micro users in the world who don't have tape drives, network
access, or other "traditional" ways to get Kermit on their machines.

------------------------------

Date: Tue 11 Feb 86 10:59:22-PST
From: Ted Shapin <[e-mail]>
Subject: Re: MS-Kermit path suggestion

I don't think KERMIT is the proper place to make up for missing DOS functions.
I use the public domain DPATH30.COM which lets me search the path for files
to open so I only need one copy of MSKERMIT.INI.  There are other programs
that do the same thing, e.g. IBM`s File Facility in their personally developed
software line.

------------------------------

Date: 0  0 00:00:00 EST
From: "Steven Kaberline [phone]" <kaberline@ford-vax>
Subject: Problems with MSKERMIT?

I just recently built MS-KERMIT for my Victor.  It works
great, with the exception that the status line at the bottom
of the screen is trashed during a "SEND" or "RECEIVE"
command??  The status line is correct during the "CONNECT"
mode.  I've tried both the 2.28 and 2.28(jrd) versions,
they both seem to have the same problem.  The IBM-PC version
I'm also using does not do this, so it appears to be Victor
specific?

I also downloaded (from CU20B) the MSVV90.BOO file described
in the latest Kermit Digest.  When converted to the .EXE file
and run, it demonstrates the same symptoms.

This is not a serious problem, but it is annoying.  Does
anyone have any suggestions??

Thanks.

            Steven Kaberline
            Kaberline@FORD-VAX

------------------------------

Date: 11 Feb 86 20:24:58 CST (Tue)
From: [e-mail]
Subject: Okstate Downtime

The Oklahoma State University Kermit Distribution service will not be available
from Saturday, February 15 until Monday, February 17 (if all goes well).  We
are in the process of changing from UNIX Version 7 to UNIX System V (actually
Perkin-Elmer's port of S5 called XELOS).  We anticipate some problems with
the Kermit Server portion of the Kermit service since the server code that we
use is based on C-Kermit 4.2 and the code that we added for path restriction
has never been tested on System V.  The real problem may be in the UUCP portion
of the service.  As I understand it System V is really picky about only talking
to systems that are in your L.sys (or Systems) file and I have not yet received
my System V source license (paperwork!) so I don't yet have the source to "fix"
this "problem" (actually it requires breaking a few features.... sigh..).

I will report back to this list when various parts of the service start working
again (hopefully within a week or so).

Mark Vasoll
Department of Computing and Information Sciences
Oklahoma State University

UUCP:  {cbosgd, ea, ihnp4, isucs1, mcvax, pesnta, uokvax}!okstate!vasoll
ARPA:  [e-mail]

------------------------------

Date: 11 Feb 86 18:38:26-MET (Tue)
From: Karl Kleine -- F Z I Karlsruhe <[e-mail]>
Subject: C-Kermit

  We invested some work in C-Kermit.  base is 4C (050).  though this is
not the very latest, we hope it still is relatively current.

first:  bugs found in porting it to pcs / cadmus.  these are 68010 based
Unix machines running MUNIX, an adoption of System III by PCS.  PCS is a
Munich based German manufacturer of micros, so you know what the M stands for.
its american branch is CADMUS (Boston).  there were no real problems !!!
congratulations to the quality of your code !!! except for some places where
the authors obviously lived on a vax: the old pointer/int problem in C.
arguments to libary routines / system calls were 0 terminated instead of
(char *)(0). this made a difference on our system.  these places were
corrected to use the proper NULL constant.

second: brevity.  we shortend some of the strings printed, particularly in
the connect message.  we also suppress printing script lines unless logging
is active for the following reason:  we regularly connect from a local machine
(pcs) thru a local net (ungemann/bass net/1) to a couple of other different
machines.  mechanism: take files with scripts making the connection and
initiation of logins.  as this often occurs with visitors present we do not
like to have it all echoed on the screen -- there are some malvolent hackers
around, i'm afraid.

third: for the same setup as explained above we added the feature to supply
an alternate startup file instead of .kermrc as last [and usually only]
command argument.  i just type  kermit U750  which connects me from my pcs
to a unix vax.  very handy when you have lots of different hosts you connect
to -- i even use it to go thru various (local and public) networks to an
arpa machine in la right from my desk.

forth: another feature we missed in 4c(050) was file inclusion as typed
from the local terminal.  not all of the remote hosts have a kermit (yet)
and there are some utilities which do not like files, but only terminal
input.  furthermore, you need something for a 'pushing bootstrap'when
you want to bring kermit source over to the other system!  so we added
`ESCAPE I' in connect mode. It asks for a filename {we didn't do anything
fancy here -- maybe we could reuse code from other parts we didn't look at
-- this part certainly has to be redone, particularly to make the thing
the same for all target systems of C-kermit} and passes the chars in the
file tothe other side.  newlines are converted to carriage returns
(as you TYPE it) and a little delay was added.  the latter feature
was a pragmatic implementation hack to give the remote side a little
pause for digestion of the line sent.

these changes were made by a student of mine ond some by me myself.
all the code is made available to the public as is your policy, and
for all legal purposes we herewith transfer rights to columbia university.

if you wonder: the FZI of the mail header is "Forschungszentrum Informatik",
a non-profit research institute for applied research in computer science.
we are associated with (but independent of) the Technical University of
Karlsruhe.  I'm a scientist / project leader in the software engineering dept.

the rest of the message is a summary of all the changes, and we would like
that you incorporate them in newer kermit versions. the list was prepared
by the student; maybe the english isn't perfect.  if you wish, we can also
send the files, but hope this mail is in essence sufficient.

Karl Kleine
    csnet:        kleine@Germany
    usenet/eunet:    mcvax!unido!uka!kleine


[From Frank -- Some of these changes are already in 4C(057).  Most of the
others should wind up, in some form, in a forthcoming release.]

------------------------------

Date: Wed, 12 Feb 86 12:08:33 cst
From: [e-mail] (Jim Knutson)
Subject: THE FROG for 64-bit CDC's?

I am no longer working with Cybers anymore so my support of Cyber Kermit
has become rather limited.  I would like to see support for it continue
on a "real" Cyber site (not this homegrown OS stuff).  Basically, the
support needed is finish server support and be willing to write tapes
for other CDC sites.  Perhaps a general cleanup of all the nasty
conditional code is in order also.  Anyone willing to take this on should
contact me to obtain all the materials I have.

It is interesting to see that other sites are writing Kermits to run
on CDC equipment.  I can understand writing in Pascal but writing one
in Compass makes me shudder.  I have had to support several Compass
programs in the past and it is a nightmare when trying to make mods.
I wish them all the luck in the world in that endeavor.

Jim Knutson
ARPA: [e-mail]
UUCP: {ihnp4,seismo,kpno,ctvax}!ut-sally!ut-ngp!knutson
Phone: [phone]

------------------------------

End of Info-Kermit Digest
*************************




-------
14-Feb-86 17:35:32-EST,7199;000000000001
Mail-From: SY.CHRISTINE created at 14-Feb-86 17:34:50
Date: Fri 14 Feb 86 17:34:50-EST
From: Christine M Gianone <[e-mail]>
Subject: Info-Kermit Digest V4 #12
To: [e-mail]
Reply-To: Info-Kermit@CU20B
Queries-To: Info-Kermit-Request@CU20B
Message-ID: <[e-mail]>

Info-Kermit Digest         Fri, 14 Feb 1986       Volume 4 : Number 12

Today's Topics:
                       Kermit Valentine Message
                   QK-KERMIT, a Turbo Pascal Kermit
                       Kermit for Flex 9 System
                       Two More New Kermit-80's
                More CP/M-80 Implementations of Kermit

                        HAPPY VALENTINE'S DAY

                             (  \   /  )
                            (    \ /    )
                             ( Kermit & )
                              (  You   )
                                (    )
                                  \/

----------------------------------------------------------------------

Date: Tue, 11 Feb 86 09:57 EST
From: Victor Lee <[e-mail]>
Subject: QK-KERMIT, a Turbo Pascal Kermit

I would like to submit our version of Turbo Pascal Kermit which runs on both
the MS-DOS and CP/M systems.  It is named QK-Kermit after our SHARE
installation name, QK (Queen's Kingston).

I made some attempt to get together with Jeff Duncan, but it was not very
successful.  The files we sent back and forth to one another kept getting
lost.  And I got somewhat confused as to which files went together. At
Queen's the developement of the MsDos Kermit features had to take priority
over any CP/M features.  Consequently this Turbo Pascal KERMIT is primarily
our own Kermit.

[Ed. - Jeff Duncan at Prime Computer has also been working on a Turbo Pascal
Kermit, but concentrating on CP/M.  His previous Turbo Pascal CP/M-80
Kermit remains available as KER:TURBO.*.]

The Turbo Pascal Kermit which we call QK-KERMIT has been widely used on
campus to tie in with Kermits on the VM/CMS, VAX systems, RT11 system and
micro to micro systems.  In addition to the features found in the Kermit-MS,
QK-KERMIT has added the following:

    1. VT100 emulation, with definable function keys.
    2. VT100/TEK4010 graphics terminal emulation.
       We are also currently developing  a TEK4105 version.
    3. APL character set for those that have an APL character ROM.
    4. Automatic Server mode for send and receive files.

Because this Kermit is easy to use and modify, it has been used by others
who have added there own particular modifications such as file encription,
data compression, and Greek terminal emulation.

There are about 3000 lines of code contained in several source Pascal files.

[Ed. - Thanks, Victor!  This program runs on the IBM PC,XT,AT; the Apple II,
and the Kaypro II.  A simple hex file (2-for-1 encoding of the binary .COM
file) is provided for the IBM PC family (with and without graphics).
Additional hex files for other combinations of PCs/terminals/graphics may
appear from time to time.  The files are in KER:QK*.* on CU20B.  The binary
.COM files are in KB:QK*.COM on CU20B.  Hexify/dehexify programs are in
KER:QKCOMH.PAS and KER:QKHEXC.PAS.  The source files are concatenated
together into KER:QKKER.PAS; KER:QKKER.DOC is the manual; there are various
auxilliary files for key definition, etc.  To run the program, you need to
have a key definition file on your current disk.]

------------------------------

Date: Thu, 13 Feb 86 08:17:02 n
From: <[e-mail]>
Organisation:   European Molecular Biology Laboratory
Postal-Address: Meyerhofstrasse 1, 6900 Heidelberg, W. Germany
Phone: [phone] [switchboard]
Subject: Kermit for Flex 9 System

I have just mailed the Flex Kermit source code to the address which
succeeded last! I hope that it arrives OK...

The program was written by D. J. Rowland, Brighton Polytechnic Computer
Centre, Watts Building, Lewes Road, Brighton, Sussex, UK.  Here are the
comments from the author, which seem to comprise the sum total of the
documentation:

"This program is a very basic kermit, the basic code is based on the Apple
version of Kermit and modified to run on the 6809 cpu.  I don't guarantee
its operation!  It's a bit crude but it does work!  It has be run with the
DEC VAX Kermit server and the DEC Pro Kermit server.

[Ed. - I assume this means it will only work with a Kermit server on the
remote end, but it shouldn't matter which server.]

"It will get a file, send a file, and close down the server.  It operates
with text files only and does not have 8 bit quoting.  There are no set and
show commands; to change the values modify the source!  There is a receive
data timer (for packet receive); this can be modified or deleted!  It's a
simple timing loop round the recieve-data subroutine."

regards
peter bendall

------------------------------

Date: 13-FEB-1986 16:49:18
From: [e-mail]
Subject: Two More New Kermit-80's

  Here's a couple more towards the Great 200 Mark. First off is the hex for
Kermit-80 for the Epson PX8 portable, sent in by Tony Addyman of Salford
University ([e-mail].E). Then comes the hex for a Research Machines
RM380Z with 5-1/4 inch single density discs, from Brian Robertson of Aberdeen
University ([e-mail]). There was a Kermit-80 hex file for this system
on the tape I sent you- belatedly it was found that this ran on systems with 8
inch single density discs only (the addresses of the UART changes between the
models). Can you install the one on the tape as CP4380.HEX, and have this new
one as CP438M.HEX, please (the "M" is apparently meaningful to Those Who Know
These Things). The SYS and TYP files for these are being done by Bertil now,
and will be on a PC disc to you before long.
                 Alan

[Ed. - Thanks, Alan!  The Epson hex file is in KER:CP4PX8.HEX, and the RM380Z
version in KER:CP438M.HEX, available, as usual, via anonymous FTP from CU20B
and on BITNET via KERMSRV at CUVMA.  The others will be installed when they
arrive.]

------------------------------

Date: 13 Jan 1986 1423-EST
From: Robert LaFara, Indianapolis 317-353-7750
Via: LCG.KERMIT@DEC-MARLBORO
Subject: More CP/M-80 Implementations of Kermit

The following files contain the machine dependent code for the
Access-Matrix, Action Computer Enterprise Discovery, and the Personal Micro
Computer MicroMate.  Although I have included source code for two others, I
no longer have the HEX files.

          CP4ACC.HEX
          CP4DISC.HEX
          CP4MM.HEX

I also uploaded the file: CP4SYS.DIF which contains (I hope) all the
differences between the CP4SYS.ASM on the distribution tape and my versions
of the file.  Included are comments about two errors that we have found in the
distributed code and I have included comments about EQU's to be used in
CP4TYP.ASM.

Sincerely, Bob LaFara

------------------------------

End of Info-Kermit Digest
*************************
-------
20-Feb-86 15:01:00-EST,9693;000000000001
Mail-From: SY.FDC created at 20-Feb-86 15:00:06
Date: Thu 20 Feb 86 15:00:06-EST
From: Frank da Cruz <[e-mail]>
Subject: Info-Kermit Digest V4 #13
To: [e-mail]
Reply-To: Info-Kermit@CU20B
Queries-To: Info-Kermit-Request@CU20B
Message-ID: <[e-mail]>

Info-Kermit Digest         Thu, 20 Mar 1986       Volume 4 : Number 13

Today's Topics:
                       MS-DOS Kermit 2.28/jrd5b
              CP/M Kermit Announcements from Last Digest
       MS-Kermit for Sirius/Victor on Available Disc in the UK
                        QK-Kermit Reports (and Answers)
       IBM PC - Tek 4010/4014 Emulation Beta Offer (w/ Kermit)
                     Mac Kermit vs Printer Port?
                     C-Kermit Bug on Pyramid 90x

----------------------------------------------------------------------

Date: 20 Feb 1986 1400-EST
From: Frank da Cruz <SY.FDC@CU20B>
Subject: MS-DOS Kermit 2.28/jrd5b

If anybody wants to try out the current iteration of Joe Doupnik's MS-DOS
Kermit, for the IBM PC family (& clones) only, with VT52, H19, VT100, VT102
emulation built in, plus the ability to set foreground & background color
on color monitors.  No real documentation is available yet, but you can use
question mark at command level to find out what the new commands are.  A
couple commands have changed, so your MSKERMIT.INI file might need some
changes:

SET AUTOWRAP has become SET TERMINAL WRAP (but see below)
SET HEATH has become SET TERMINAL HEATH (or VT100, or VT102, etc)

The following bugs have been observed, so you don't need to report them:

1. SET TERMINAL WRAP command doesn't work (doesn't parse).
   The actual wrap mechanism seems to work OK, but can only be turned on
   and off by escape sequences.

2. There's no help for SET TERMINAL COLOR command (it takes two numbers
   in the range 0-7 as arguments, e.g. SET TERM COLOR 4,2).

3. Insert char in H19 or VT102 mode displays garbage instead of the inserted
   characters.

4. When you change colors, the background color is not set until after the
   screen is cleared the first time, but the foreground color is set.

This version is in PS:<KERMIT-MS>MSJRD5B.BOO (and .EXE for those who can
transfer 8-bit binary files), available, as usual via anonymous FTP from CU20B.
Please report any additional bugs to me, and I'll relay them to Joe.
Meanwhile, the program seems to be highly usable on the IBM PC family for most
applications, emulating any of the above terminals, so those of you who have
been hankering for VT10x emulation might be able to get by with this version
until the final release.  I'll also put the MSJRD5B.BOO file in KERMSRV on
CUVMA for BITNET access.

------------------------------

Date: 20 Feb 1986 0900-EST
From: Frank da Cruz <SY.FDC@CU20B>
Subject: CP/M Kermit Announcements from Last Digest

Apologies to everyone who tried to get any of the five new CP/M Kermit .HEX
files announced in the last digest.  The first group, from Bob LaFara, was
there, but not as advertised; the filenames were changed somewhat from those
listed in Bob's message:

Machine          Bob's Name      Stored As:

Access-Matrix    CP4ACC.HEX      CP4ACC.HEX   (no change)
ACT Discovery    CP4DISC.HEX     CP4DIS.HEX   (shortened to 6.3)
PMM Micromate    CP4MM.HEX       CP4PMM.HEX   (to avoid confusion)

The source for these files has been added to the "beware" file, KER:CP4KER.BWR.

The other two,

Epson PX8 Portable               CP4PX8.HEX
Research Machines 380Z           CP438M.HEX

were lost somehow.  They have been restored (thanks to Alan Phillips for
sending them again).  Since we're without a real CP/M-80 Kermit maintainer,
all new CP/M systems will have to be supported this way, i.e. installation
of the .HEX files, without corresponding change to the source.  I hope to
inveigle someone into taking over CP/M-80 Kermit maintenance to the extent of
making one last pass through the source, so that the program can be organized
in such a way as to take advantage of the MODEM overlays.  Any volunteers?

------------------------------

Date: 14-FEB-1986 16:03:28
From: [e-mail]
Subject: MS-Kermit for Sirius/Victor on Available Disc in the UK

I can now supply MS-Kermit 2.28 on disc for the Sirius/Victor to anyone
wanting it in the UK. As before, e-mail address is [e-mail]1, phone
is 0524-65201 x 4881.
              Alan Phillips

[Ed. - Thanks!  Are there any other public spirited volunteers willing to
supply Kermit on native media for their machines, or to submit them to user
groups who can?]

------------------------------

Date: 18 FEB 86 09:58-PST
From: [e-mail]
Subject: QK-Kermit Report

Problems and bug report on the new QKERMIT in turbo pascal:

   VT100 terminal emulation has some problems
     Does not respond to DEC VMS set term/inquire.
     Has problems with the "TAB" character expansion.

   Something is wrong with the kermit handshaking (program waits until
   host times out then sends next packet) (each packet took about
   5 seconds to send).

            Don Jenkins  DON@UCRVMS (bitnet)
            University of California, Riverside
            Academic Computing Center

[Ed. - See below.]

------------------------------

Date: Wed 19 Feb 86 20:22:01-CST
From: Pete Galvin <[e-mail]>
Subject: QK-Kermit Report

I transfered the sources for QKKERMIT and compiled a version under MSDOS 3.1,
trying to build a VT100 version.  The compile went fine, and on startup
QKKERMIT claims I have VT100 emulation.  Unfortunately, when I dial in to the
DEC-20 on campus, almost no VT100-hood can be seen in the program: blanking the
screen and deleting characters works fine, but invoking any editor produces
"random" results.  Mostly, the screen blanks a lot during the display of text
or prompts, and the cursor stays near the top of the screen.

I'm hoping someone will point out the silly mistake I made an tell me how to
get a working VT100 emulator up.

                                        Thanks,
                                        Pete Galvin, U of Texas

------------------------------

Date: Wed, 19 Feb 86 14:06 EST
From: VIC@QUCDN
Subject: Reply to QK-Kermit Bugs

     I think my choice of names for the various protocols was bad. You
should not be using the Xon-Xoff with a Dec20. The Xon-Xoff refers only to
the funny IBM way of using Xon-Xoff. What I called "SERIES/1" protocol
should be used by most computers.  I am considering to change the name
of the protocol to something less confusing; but I am afraid that the
name may also have to be quite meaningless.

     It appears that my VT100 emulation is not complete enough for most
DEC users, although it is sufficient our needs. I will try add some of
the missing features as soon as possible.  Your feed back of the problems
will help me decide what features are most needed.

[Ed. - Victor has also sent in a hex file for the Kaypro II since the
last digest.  It's in KER:QKCPK2.HEX.  Remember, this is a straight
hexadecimal encoding of the .COM file, not an Intel format .HEX file to
be used with the CP/M LOAD command.]

------------------------------

Date: Tue 18 Feb 86 10:39:09-EST
From: Michael Fuchs <[e-mail]>
Subject: IBM PC - Tek 4010/4014 emulation beta offer (w/ Kermit)

Would anyone be interested in beta testing our latest version of a product
that does Tektronix 4010/4014 emulation (with EGA support) as well as VT102,
VT52, file transfer (Kermit, Xmodem, propietary protocols), 132 columns in
software (or optional hardware), old screen recall, programmable softkeys,
etc.?

If so, please contact (by voice only, please):

John Bailin
Coefficient Systems Corporation
212/777-6707

Please do not mail replies to this account (it's his project!)

Michael Fuchs
Coefficient Systems Corp.

------------------------------

Date: 16 Feb 1986 0825-EST
From: [e-mail]
Subject: Mac Kermit vs Printer Port?

There is a bug in MacKermit 0.8(33).  If the modem port is in use by a hard
disk (Tecmar for example), there is no way to use MacKermit as it generates
an error message indicating that the port is in use and then exits.  It does
not permit the user to use the printer port instead.  Do you have a patch to
get around this problem???

[Ed. - From one of the authors of Mac Kermit: "The ability to use the printer
port is not supported -- it was something we were going to put in but never got
around to.  Since I ordered a Tecmar I'll probably get around to fixing this.]

------------------------------

Date: Mon, 17 Feb 86 16:29:36 EST
From: munnari!moncskermit.oz![e-mail] (John Carey)
Subject: C-Kermit bug on Pyramid 90x

I have discovered a bug sending more than one file using C-Kermit 4c(056)
on a Pyramid 90X, e.g.

        kermit -s file1 file2 ...

The first file is sent ok - but the others are not.

Here is the fix to "ckcpro.w" - sfile() has a parameter which was not used:

<sseof>Y  { if (gnfile() > 0) {         /* Got ACK to EOF, get next file */
                if (sfile(xeof)) BEGIN ssdata;  /* <---- parameter added */

This may cause problems on other machines that a have different
stack aritecture from the VAX.

                                John Carey.
                                [e-mail]

------------------------------

End of Info-Kermit Digest
*************************
-------
28-Feb-86 10:32:51-EST,8094;000000000001
Mail-From: SY.CHRISTINE created at 28-Feb-86 10:31:21
Date: Fri 28 Feb 86 10:31:20-EST
From: Christine M Gianone <[e-mail]>
Subject: Info-Kermit Digest V4 #14
To: [e-mail]
Reply-To: Info-Kermit@CU20B
Queries-To: Info-Kermit-Request@CU20B
Message-ID: <[e-mail]>

Info-Kermit Digest         Thu, 28 Feb 1986       Volume 4 : Number 14

Departments:

  ANNOUNCEMENTS -
        Kermit for the HP2647
        New Kermit-11
        Victor 9000 Kermit Updates

  MISCELLANY -
        ProComm
        C-Kermit Bug for Pyramid 90x
        Uucpker and Kermsrv Are Back
        Bug in C-Kermit

----------------------------------------------------------------------

Date: 1986 Feb 27   19:31 EST
From: John F. Chandler <[e-mail]>
Subject: Kermit for the HP2647

There is now a Kermit available for the HP2647 "Rover" programmable graphics
terminal, with or without tape units, written in 8080 assembler.  It
supports data compression and interaction with servers.  The executable
module is in the form of a long ESCAPE sequence that drives the resident
loader.  After being loaded it can be invoked as needed by typing 'kermit'
in command mode.  This Kermit can probably be adapted to run on other HP264x
models.  Source and documentation are available through KERMSRV.

John F. Chandler
Harvard/Smithsonian Center for Astrophysics

[Ed. - The program, hex file, and documentation are in KER:HP264X.* on CU20B
(anonymous FTP) and HP2647X * on KERMSRV at CUVMA (BITNET).]

------------------------------

DATE: 21-FEB-1986
FROM: BRIAN@UOFT02
SUBJECT: NEW KERMIT-11

New Kermit-11 on dialup and bitnet from U of Toledo

 A new version (2.45) of Kermit-11 is available.  The  literal  list  of
changes  is  too long, but major things are: long packets, dial command,
set dial  commands  (for  adding  modems),  set  phone  number  command,
further  TSX+  mods,  new  install  and  user  doc.  Edit  history is in
K11CMD.MAC

 This  version  should  not  be  sent  to  Columbia  yet as it is highly
desirable  to  test  long  packet  support  against  a  different  Kermit
implementation.  Additionally,  there  are  a  couple of very soon to be
resolved issues regarding P/OS v3. I am also awaiting a task  image  for
IAS 3.2 update C.

Bitnet access:
from VM/CMS:    CP SMSG RSCS MSG UOFT02 KERMSRV DIR
                CP SMSG RSCS MSG UOFT02 KERMSRV SEND K11*.*
from VMS Jnet:  $ SEN/REM UOFT02 KERMSRV SEND K11*.*

dialup: [phone]
        Service class  VX785A
        User: KERMIT
        Password: KERMIT

[Ed. - Thanks!  We will announce Brian's new release when we
receive it at Columbia.]

------------------------------

Date:     Sat, 22-FEB-1986 15:32 MST
From:     <PETERSONB@BYUVAX>
Subject:  VICTOR 9000 KERMIT updates

I apologize to anyone who may be using the VICTOR 9000 Kermit for the bug
in the mode line during file transfers.  It was a severe oversight on my
part.  I am forwarding corrected versions of MSXV90.ASM, MSYV90.ASM, and
MSYV9T.ASM to Columbia U. to replace the ones with the bug.

[Ed. - The new files in KER:MS*V9*.* on CU20B and on BITNET
(without the KER:)]
In addition, since I was working on it anyway, I have cleaned up the
character set on the Tektronix emulation a little bit to make the lower-case
letters more readable.  By popular demand I have also added code in the
Heath emulation mode of both versions to swallow up any ANSI escape
sequences that may come along.  No action is taken when an ANSI sequence is
received, but there are apparently many devices (such as the IBM 7171
protocol converter) that send these sequences and they are very annoying.
Also, the receipt of the sequence ESC [ is supposed to activate the hold
screen mode on the VICTOR - not an entirely desirable characteristic if the
host is merely trying to tell the VICTOR to switch text characteristics.

I appreciate all who have called bugs in the VICTOR version to my attention.

                                        Bryan G. Peterson
                                        (BITNET PETERSONB@BYUVAX)
                                        Telephone:  [phone]

P.S. - I will be sending the corrected codes on VICTOR format disks to the
VICTOR PULSE public domain library in the next few days.  If anyone wishes
to contact them the address is:

                        Victor PULSE
                        c/o Brad Chase
                        P.O. Box 705
                        Exeter, NH  03833-0705

[Ed. - Thanks for fixing these bugs, for sending us the source,
and a SPECIAL thanks for submitting this version to a Users
Group. If you could also send us a .BOO file, it would be greatly
appreciated.]

------------------------------

Date: Tue, 25 Feb 86 09:06:12 CST
From: C346595@UMCVMB (Bruce Barkelew)
Subject: ProComm

PIL Software Systems
PO Box 1471
Columbia, MO 65201
[phone]

I am the co-author of the communications program ProComm.  I noticed
our program mentioned here, so I thought I would let you know some
more information.  ProComm is a user supported product.  We have just
released version 2.2 (02/21/86).  Version 2.2 has many improvements
and additions.  We now emulate 10 popular async terminals.  The VT-100
emulation has been greatly improved.  We support XMODEM, YMODEM, TELINK,
MODEM7 and KERMIT file transfer protocols.  Our KERMIT implementation
has been completely re-coded from the ground up, and now supports all
the latest features such as data compression, file attributes, and the
new Sliding Window (full duplex) extension.  Our script command language
has been expanded also.  ProComm runs under MS-DOS 2.0 or greater, and
requires 128k of RAM.  We have a 24 hour support BBS running at (314) 449-
9401.  The latest version is always available there.

I don't mean this to sound like a commercial, but I saw messages here
inquiring about us, so I thought I would supply the information.  I can
be reached at the above address or at C346595 at UMCVMB.

-Bruce Barkelew

[Ed. - We do not usually put commercial announcements in our
digest, but this may be a way for people to try windows kermit.]

------------------------------

Date: Thu, 27 Feb 86 09:02:10 EST
From: munnari!moncskermit.oz![e-mail] (John Carey)
Subject: C-Kermit bug for Pyramid 90x

Sorry my last article had a typo.
                if (sfile(xeof)) BEGIN ssdata;  /* <---- parameter added */

Should have been :-
                if (sfile(xflg)) BEGIN ssdata;  /* <---- parameter added */
                          ^^^^
Thanks to John F. Rovert (jrover@nswc-g) for pointing out my mistake

                                                John Carey.
                                                [e-mail]

[Ed. - Thanks for the correction.]

------------------------------

Date: Thu, 27 Feb 86 0:02:20 CST
From: Mark Vasoll <[e-mail]>
Subject: uucpker and kermsrv are back

Both the uucpker and kermsrv logins are back in working order on
okstate.

------------------------------

Date: 28 Feb 86
From: Frank da Cruz <[e-mail]>
Subject: Bug in C-Kermit

I just discovered a bug in C-Kermit that might explain some problems that
have been reported recently.  If you ever send it an ACK, but the ACK is
lost somehow, and then you time out and send it a NAK (as I believe the PC
will do if its timer is on) before C-Kermit times out, the two Kermits get
into a deadlock, in which Unix Kermit sends packet n and the PC sends a NAK
for packet n+1, up to the retry limit.  The cure, in the case of Unix
Kermit, is to add a test in the input() function.  If it receives a NAK for
packet (n+1)%64, then it should return('Y'), i.e. behave as though it got an
ACK for packet n.  - Frank

------------------------------

End of Info-Kermit Digest
*************************
-------
 5-Mar-86 16:28:02-EST,10108;000000000001
Mail-From: SY.CHRISTINE created at  5-Mar-86 16:26:29
Date: Wed 5 Mar 86 16:26:29-EST
From: Christine M Gianone <[e-mail]>
Subject: Info-Kermit Digest V4 #15
To: [e-mail]
Reply-To: Info-Kermit@CU20B
Queries-To: Info-Kermit-Request@CU20B
Message-ID: <[e-mail]>

Info-Kermit Digest         Wed,  5 Mar 1986       Volume 4 : Number 15

Departments:

  ANNOUNCEMENTS -
    Kermit for Gould/SEL 32/8750 with MPX 3.2A
    New os9 Kermit (68000 and 6809)

  C-KERMIT -
    Kermit for Ultrix-11?
    Pixel Support for C-Kermit
    C-Kermit and TACs

  MS-DOS KERMIT -
    Tektronix Emulator in QK-Kermit
    Re: Tektronix Emulator in QK-Kermit
    PCjr w/Tecmar memory vs 2.28/jrd Kermit-MS

  MISCELLANY -
    Minor Problem with VMS Kermit (BLISS/MACRO) V3.1.066:

----------------------------------------------------------------------

Date: Wed 5 Mar 86 09:50:14-EST
From: Frank da Cruz <[e-mail]>
Subject: Kermit for Gould/SEL 32/8750 with MPX 3.2A

Announcing SEL-Kermit Version 1.0 for the Gould/SEL Concept 32/8750 with MPX
3.2A, written in Fortran-77+ by Marlon Gordon and Dave Durand, Singer/Link
Houston.  According to the documentation, it works in both remote and local
mode, and can run as a Kermit server.  The file arrived on some crazy kind
of tape, which we read the best way we could.  It all seems to be intact.
The files are in KER:GM1*.* on CU20B, available as usual via anonymous FTP
on the Internet, and also via KERMSRV at CUVMA on BITNET.

------------------------------

Date: Fri 28 Feb 86 18:04:22-PST
From: Bob Larson <[e-mail]>
Subject: New os9 Kermit (68000 and 6809)

Since someone finally confirmed that I didn't break the 6809 support
when I added 68000 support to kermit, the new version should be made
standard.  (Thanks Mark Sunderlin, scsnet!sunder.)

The new version is on usc-eclb.arpa as ps:<blarson.os9>os9*.* .  The
files that have changed are second generation, so os9*.*.2 will get
you only the new files.

The only real changes for 6809 users are in the .hlp and .bwr files
and some code to make connect mode on a bit-banger port easier to
implement.  (A special device driver is needed, any volunteers?)

Bob Larson <[e-mail]>
Uucp: ihnp4!sdcrdcf!oberon!blarson

[Ed. - Thanks!  The new files are in KER:OS9*.* on CU20B, and in
OS* * on KERMSRV at CUVMA.]

------------------------------

Date:     Fri, 28 Feb 86  10:44 EST
From:     Mark Katsouros <[e-mail]>
Subject:  Kermit for Ultrix-11?

 I've had no luck in getting Kermit working on our Ultrix-11 system.  Tried
making several different versions, and fooled around with mixing up the flags,
but was unsuccessful in coming up with anything even close.  If you happen to
hear of a way to get what I have (ck*.*) made for Ultrix-11, please let me
know.  Also, I'd really appreciate it if you would let me know if you hear of
anyone else on the net using Ultrix-11.  (Perhaps they have some sort of Kermit
protocol.)  Thank you for your time,

Mark Katsouros
University of Maryland, College Park

[Ed. - Does anybody have any hints about making C-Kermit work in
Ultrix-11?  What is Ultrix-11, anyway?  A 2.9 derivative?  A version
7 derivative?  Venix in disguise?]

------------------------------

Date: Fri 28 Feb 86 11:15:39-EST
From: Chris Lent <[e-mail]>
Subject: Pixel Support for C-Kermit

    Just put C-kermit on a Pixel 1000 which is a 68000 based Berkley
Unix box.  Make bsd almost works but it seems the getppid() function
which is used to determine the parent process id of the shell running
C-kermit is missing from the run-time library.  So I made a
change to ckufio.c adding an #ifdef PIXEL and substituted a
kill(0,9) for kill(getppid(),1).
The unix diffs of the current version of ckufio.c and ckuker.mak follow:
$ diff ckufio.c ckufiopix.c
198a199,201
> #ifdef PIXEL
>     return(kill(0,9));
> #else
199a203
> #endif
$ diff ckuker.mak ckukerpix.mak
174a175,179
> #Pixel 1000 (Almost) Berkeley Unix 4.1 or 4.2 (and presumably also 4.3)
> #Pixel 1000 V2.1 (Has no getppid() function)
> pixel:
>     make wermit "CFLAGS= -DBSD4 -DDEBUG -DTLOG -DPIXEL"
>

------------------------------

Date:  2 Mar 1986 12:26:45 EST
Subject: C-Kermit and TACs
From: Glen Foster <[e-mail]>

Has anybody set up C-Kermit on a VAX running Unix (4.2bsd in this case)
to get it to perform the proper Telnet protocol negotiations with a
TAC so the TAC doesn't interfere with a file transfer?

I know what Telnet sequence to send, I'm just not familiar enough with
C-Kermit and Unix to know how to do it.  I'm sure it could be done
relatively easy with a Kermit script file, perhaps someone has done
something a little fancier with a shell script the "knows" whether the
remote is coming through a TAC or not and sets binary mode if it is.

The Tops-20 Kermit at ISI does this, surely C-Kermit and Unix must have
this capability!

Thanks in advance.

Glen Foster - [e-mail]

[Ed. - There is no code in C-Kermit to put TACs in binary mode, though there
is no reason why it couldn't be added.  For now, just use TAC commands like
@b i s and @b o s.]

------------------------------

Date: 26 Feb 86 06:50:00 PST
From: ALEX WOO <wu@ames-aero>
Subject: Tektronix Emulator in QK-Kermit

Has anyone got the tek4014 emulator in qk-kermit to work?  I don't have
a Zenith but a Hercules card so I tried to recompile the relevant
modules.  Here is a summary of my failed efforts.

1.  It was necessary to overlay the source.  I chose to overlay the local
and definewords procedures since they are not critical for terminal
emulation.

2.  There was a definite error in the DefineWorld(1,0,779,1023,0) call.
I changed it to either
            DefineWorld(1,0,0,779,1023)
or            DefineWorld(1,0,0,3120,4095)
depending on which tektronix driver I'm using on the mainframe.

After fixing these errors, I find that when the terminal goes into tektronix
mode the screen blanks out.  It recovers correctly but nothing is ever painted
to the screen.  It almosts looks as if the vectors are drawn on a RAM screen
(but I set that boolean to be false).  Any suggestions?

Alex.

P.S.  I was surprised that turbo-pascal could drive the serial ports at
19,200 baud.

------------------------------

Date:    Tue, 4 Mar 86 11:03 EST
From:    VIC@QUCDN
Subject: Re: Tektronix Emulator in QK-Kermit

    Since we don't have the Hercules board, I can only guess at what
your problems might be.  Here are some possibilities to consider:
  1. QK-KERMIT emulates a TEK4010 which is slightly different from a
     TEK4014 terminals.  You maybe sending TEK4014 sequences that are
     not interpetted the same on a TEK4010.
  2. Make sure that you are using the Hercules routines from the Turbo
     tool box.
  3. Do not change the  DefineWorld definition. Although it appears to
     be backwards it is fixed up with some other code. ( Two wrongs
     make it right?)
  4. Try leaving the RamScreen definition unchanged.  We changed it to
     false to reduce the amount of memory used.  I am not sure how this
     affects the Hercules routines so you may leave it alone.
  5. Are you running at 19.2 baud? I have never tested it out at that
     rate. May I suggest you run your test at a lower baud rate  to
     insure that your problem is not a baud rate problem.

------------------------------

FROM: EGRJN@TUCC
Date:     Tue, 04 Mar 86 08:52 EST
Subject: PCjr w/Tecmar memory vs 2.28/jrd Kermit-MS

I got version 2.28 of the IBM PC Kermit from KERMSRV and I discovered a
problem that few others may have found, and which I hope you can report to
the right folks.  I have a PCjr with TECMAR memory which brings my system
memory to 640K.  When I run KERMIT 2.28, the program bombs with a message
indicating "insufficient memory".  If I disable the TECMAR memory, the
program runs fine.  Version 2.27 runs fine in either case.  Something was
done to 2.28 which creates this incompat- ibility with my system.  Disabling
the extra memory is inconvenient because it prevents me from using RAM disks
or programs like Sidekick. Perhaps if they knew of it, the KERMIT wizards
could avoid this improvement in future versions.

[Ed. - Has anyone else experienced this problem?  If so, did it go away when
you tried jrd/2 or later?  Joe Doupnik found some problems with the dynamic
memory allocation and fixed them.]

------------------------------

Date: Fri 28 Feb 86 11:15:39-EST
From: Chris Lent <[e-mail]>
Subject: Minor Problem with VMS Kermit (BLISS/MACRO) V3.1.066:

   If you didn't recompile KERMIT under VAX/VMS 4.X from the MACRO (or BLISS
I assume) a version compiled under VAX/VMS 3.2 to 3.7 may stall in what
looks like a CTRL/S-CTRL/S (XOFF-XOFF) standoff when using DEC's VT220
terminals.  I assume the terminal sends a CTRL/S between the time you type
the escape character and the time you type the C to close a CONNECT session.
It might also be that PASSALL mode (rather than VMS 4.X PASTHRU) mode is
used and the terminal's incessant CTRL-S/CTRL-Q sequences eventually lock up
KERMIT.

   Recompiling under VAX/VMS 4.X seems to solve thsi problem.  Note that
this hangup problem did NOT occur on VT100's or IBM-PC's using KERMIT
to be terminals.

   To determine what version your kermit was linked under do a

$ ANALYZE/IMAGE SYS$SYSTEM:KERMIT.EXE

and look at the linker identification under the heading Image Identification
Information.  If the string starts with a 3 you probably should rebuild your
KERMIT.EXE.

                Chris Lent
                The Cooper Union for the Advancement of Science and Art.
                ihnp4!allegra!phri!cooper!chris
or care of:
                [e-mail]

------------------------------

End of Info-Kermit Digest
*************************
-------
10-Mar-86 16:52:37-EST,15189;000000000001
Mail-From: SY.CHRISTINE created at 10-Mar-86 16:50:36
Date: Mon 10 Mar 86 16:50:36-EST
From: Christine M Gianone <[e-mail]>
Subject: Info-Kermit Digest V4 #16
To: [e-mail]
Reply-To: Info-Kermit@CU20B
Queries-To: Info-Kermit-Request@CU20B
Message-ID: <[e-mail]>

Info-Kermit Digest         Mon, 10 Mar 1986       Volume 4 : Number 16

Departments:
                      New Kermit-32.Hex Enclosed
           Kermit for Heath/Zenith 100 with UCI EZPC Board
                           Zenith-100 Bugs
                         C-Kermit on HP9000s
                       Suggestions, C-64 Kermit
                              Ultrix-11
                         Kermit on Ultrix-11
                        Setting TAC Parameters
                     Kermit/TACS and Other Hosts
                       Bug in Kermit for VM/CMS
                            Unix C-Kermit
      Problem with Kermit-11 and Intel MDS Kermit (Kermit-Isis)
                         Altos Oasis Kermit?

----------------------------------------------------------------------

Date: Sun, 9 Mar 86 20:49:36 CDT
From: Stan Barber <drillsys![e-mail]>
Subject: New Kermit-32.Hex Enclosed

So that others won't have to suffer as I did, here is a freshly hexed
verion of kermit-32. Enjoy.

[Ed. - Thanks!  For those who don't know why we needed a new hex file for
VMS Kermit, it's a long story.  But now it agrees with the VMSHEX and VMSDEH
programs we distribute with it, and the warning messages can be (and have
been) removed.  VMS Kermit itself has not been changed; it's still version
3.1(066).  The new hex file is in KER:VMSMIT.HEX on CU20B and in VMSMIT HEX
on CUVMA for BITNET.]

------------------------------

Date: Thu 6 Mar 86 16:48:29-EST
From: Frank da Cruz <SY.FDC@CU20B>
Subject: Kermit for Heath/Zenith 100 with UCI EZPC Board

From Marvin Hamdan, UCI Corporation, 948 Cherry Street, Kent, OH  44240,
a version of IBM PC MS-DOS Kermit 2.27 modified to run on the H/Z-100 with
UCI's EZPC board, which is supposed to make H/Z-100 IBM compatible (oh
well).  Before trying to run this, you have to pry off a couple chips
and bend some pins (it's explained in the directions).  The files are
in KER:MS*EZP.* on CU20B and MS*EZP * from KERMSRV via BITNET at CUVMA.

------------------------------


Date: Fri 7 Mar 86 00:03:44-EST
From: "Gordon C. Holterman" <[e-mail]>
Subject: ZENITH BUGS

HELP!!!

I recently grabbed a copy of the kb:msvz10.exe file to run kermit on my
Zenith 100.  However, I am experiencing two major bugs.  First, receiving or
getting files doesn't work.  It starts to work and says it gets the first
packet, but then hangs (the cursor sits at thge end of the file name) and
the only way out is to reboot.  The connection is fine and the remote system
is definately sending data--just no receiving.  Second, the status command
causes a similar lock.  No information gets printed--the cursor runs to the
edge of the screen prints an E and then locks.  Rebooting is the only out.

I would love to get these bugs fixed as soon as possible or get an old
version that works.

        Thanks,
            Gordy Holterman@MIT

[Ed. - The old version is in PB:<KERMIT-OLD>MSZ100.BOO (or .EXE) on CU20B.
Has anyone else had similar problems with the current version, or can give
some hints about making it work right?  This could be an instance of 2.28
being built from source, with the segments coming out in the wrong order,
as described in the .BWR file.]

------------------------------

Date: Thu, 6 Mar 86 11:57:31 PST
From: Arvind Kumar <hpcea![e-mail]>
Subject: C-Kermit on HP9000s

Has anyone else had difficulties trying to make C-Kermit work in terminal
emulation mode on HP9000 computers?

I am trying to use it to go out to a hardwired port (actually an Infotron
port selector) but have had no luck, either on the Series 500 or the Series
220.  In each case, the command 'set line /dev/sw0' takes forever to come
back with 'unable to lock device' or some similar message.  Setting
modem-dialer to racal-vadic allows me to proceed until the Connect step,
which terminates terminal emulation immediately, saying 'host closed
connection' or something similar.

Any clues?

Arvind Kumar
  kumar@hplabs@csnet-relay
  ucbvax!hplabs!kumar

[Ed. - The stupid UNIX "lock files" are the bane of UNIX Kermit.  Read the
section in the Kermit User Guide (the C-Kermit chapter of which is on
line as ckuker.doc) about this.  If all else fails, comment out the code
that looks for the lock file and rebuild the program.  - Frank]

------------------------------

Date: Wed, 5 Mar 86 20:25:53 pst
From: Joel West <[e-mail]>
Subject: Suggestions, C-64 kermit

I have the C-64 kermit 1.7(52).  I'm happy with using it with another
local micro, but thus far have failed with a remote host (probably
due to modem status controls, etc. in the cable).

In c64ker.doc, the authors make comments about suggestions and improvements.
Responding to their ideas, I'd like to offer my 2 cents:
     1.    SET BAUD needs 2400 baud, if said throughput is feasible
    on the C-64
     2.    Slower cursor blink is needed.
     3.    The authors suggest RENAME and SCRATCH command.  I think
    the existing DISK works fine:
        DISK S0:scratched
        DISK R0:new=old
    Perhaps they could modify DISK ? to prompt these options.
     4.    Screen colors would be nice, but B/W is quite readable.
     5.    "Implement wildcard send -- need info on 1541 DOS!", to quote
    from the manual.  According to my 1541 manual,

DIRECTORY
Track 18, Sector 1
    0-1    track, sector next directory block
    2-31    1st entry
    34-63    2nd entry
    66-95    3rd entry
    98-127    etc.
    226-255    last entry

DIRECTORY ENTRY:
    0    128+type 0=Deleted, 1=SEQ, 2=PROG, 3=USER, 4=REL
        128 indicates file properly closed
    1-2    T/S of 1st data block
    3-18    file name padded with shift-space (0xA0 ?)
    19-20    T/S first side sector for relative file
    21    record size, relative file
    22-25    filler
    26-27    T/S replacement file when OPEN@ in use
    28-29    # of blocks in file: low byte, high byte
It would seem that only 0-18 are really needed for kermit applications.

One last comment.  I have two commercial word processors, but neither
seems to use plain CBM ASCII text. If the SpeedScript editor
is really public domain, maybe it could be distributed with kermit
--or a comparable replacement.

    Joel West    CACI, Inc. - Federal
    [e-mail]
    {decvax,ucbvax,ihnp4}!sdcsvax!noscvax!westjw

------------------------------

Date: 7 Mar 1986 0422-EST
From: [e-mail]
Subject: Ultrix-11

Ultrix-11 V2 is a Digital product based on V7 and 2.9.  Ultrix-11 V3 will
have some Sys 5 compatibilities (was announced at Fall Decus) and should be
out soon.  The respondent didn't indicate what version of Ultrix-11 he was
using and what machine he was running it on.

I plan to bring up C-Kermit under Ultrix-11 V2 (and V3 when available) on an
11/73 and will post any diffs necessary to get it to work.

Venix and Pro/Venix are products of Venturcom and are independent of Ultrix-11.

When will a windows version of C-Kermit be available?  Is anyone working on
such a beast?

[Ed. - A version of C-Kermit with windows was announced in Info-Kermit V4 #1.
It's based on an earlier version of C-Kermit (4.0 rather than the current 4C).
It's not in our regular Kermit distribution because of the name conflicts
with the regular release, but it can be FTP'd from PS:<KERMIT-W>*.* on CU20B.
Sorry, it's not available on BITNET.  Eventually, the windowing code will be
added to the distributed version of C-Kermit.]

------------------------------

Date:  86/03/06. 09.28.49.
From:  [e-mail]
SUBJECT: Kermit on Ultrix-11

  In regards to Mark Katsouros question on Kermit for Ultrix-11, we run an
Ultrix-11 system and have installed a working host version of Kermit.  The
Kermit version that we installed was the Unix Kermit from a tape written at
Columbia on 11-12-84.  Identified in the sccsid as version 3.0(1) mod date
11/5/84.

[Ed. - This was our old, pre-C-Kermit version of UNIX Kermit.  It didn't
do much, but it was quite transportable among V7 and Berkeley-based UNIX
systems.]

Ultrix-11 is Digital's version of Unix for the VAX line of computers.
Ultrix-11 is basicly Berkley 4.2 Unix.

[Ed. - Ultrix-11 runs on PDP-11s.  Ultrix-32 runs on VAXes.  Are we talking
about the same thing?]

Ryan Popken
University of Nebraska, Lincoln

BITNET: RYAN@UNLCDC
CSNET:  kermit@unl

------------------------------

Date: Thu, 6 Mar 86 22:25:44 EST
From: Dave Swindell <[e-mail]>
Subject: Setting TAC parameters

In the last digest (V4#15), there was a message from a user wanting to use
C-Kermit over a TAC.  The digest editor gave the correct TAC commands to use
(@ b o s and @ b i s), but gave them IN THE WRONG ORDER!  You must use the @
b o s command (binary output suppress, or something like that) BEFORE you
issue the @ b o s command (binary input suppress).  If you issue the @ b i s
command first, the TAC will not accept the @ b o s command.  Also, if you
are sending data to a host system connected via a TAC, you may need to set
the send packet-length parameter to a value of 64 or less to keep from
over-running the TAC input buffer.

Hope this helps,

Dave Swindell
BBN Laboratories

------------------------------

Date:  6 Mar 1986 15:30:39 EST
Subject: Kermit/TACS and other hosts
From: Glen Foster <[e-mail]>

"Thanks" to all the people who sent me information on TAC commands.  Perhaps
my request was not specific enough.  What I am looking for is a way to have
a Unix host running C-Kermit send the telnet sequence:

IAC WILL BIN    (wait for: IAC DO BIN) then send:
IAC DO BIN      (wait for: IAC WILL BIN)

Then (without the remote user ever having been aware of anything) Kermit
will take over and the user will see the C-Kermit> prompt or whatever.
Another negotiation should be performed upon leaving Kermit to return
control of the TAC to the user although this is not crucial.

IAC is the character 377 octal (Interpret As Command), this is the telnet
"escape" character and is never sent by Kermit (I am told) because octal 177
(ASCII DEL) is not "printable."  It (octal 377) has to be doubled to get
through a TAC even in binary mode.

Telnet negotiation between hosts uses special characters 376 (DONT), 375
(DO), 374 (WONT) and 373 (WILL).  The character that follows one of these
four indicates which option is being negotiated, which for binary is 0
(BIN).

This should only occur if the user is coming over a TAC and not telnetted
host to host, local hard-wired or dialup.  Of course, error detection and
recovery should be taken care of in the best of all possible worlds.

The important thing is that it remain transparent to the users, they should
only have to type "kermit server" ("kermit -x" under UNIX), escape to
command level and transfer files with the greatest of ease.  What do they
know about TAC commands?  I have a key programmed to tell the TAC to jump
and whinny but this causes all sorts of "funny" output that confuses my
users.

Again, TOPS-20 can do it, why can't UNIX.  (Maybe that should rile enough
UNIX gurus so I'll get an answer!)

Glen

[Ed. - It's just a matter of someone writing the code.  It's one of many
items on the list of things to do.]

------------------------------

From: mcvax!eurifb![e-mail]
Date: Fri, 7 Mar 86 12:12:27 +0100
Subject: Bug in Kermit for VM/CMS

A problem erupted when we tried to send lots of packets from a UNIX machine
via a 7171 over a 70-foot line. The 7171 guarantees only 50 foot, and lots
of acknowledgement-packets were garbled, and UNIX-kermit did a retry.  This
was all OK, exept when the old packet-number was 63 ('_').  VM/CMS kermit
wrapped around to 0 (' ') and didn't recognise the resent packet as a retry.
It appeared that masking was forgotten on several occasions. I have tried to
locate all the spots where it should be needed, and inserted them (see the
lines with BN-860227).  It works fine now (upto now for approx. 100 MB).

Ben Noordzij,
Erasmus University, Rotterdam, The netherlands
......!mcvax!eurifb!benno

[Ed. - Thanks for the report.  We've omitted the code from the digest, but
it has been added to the CMS Kermit beware file.  The problem will be fixed
in the forthcoming release (version 3.0).]

------------------------------

Date: 12 February 1986, 10:35:10 SET
From: Wolfgang Hake             0521-106-4941        UHRZS007 at DBIUNI11
Subject: Unix C-Kermit

wir haben probleme, den c-kermit unter der amdahl unix-version UTS V
zu installieren. in der versionsliste ist die UTS V zwar mitaufgefuehrt,
aber im make-file ist dafuer kein spezieller eintrag vorgesehen. die
eintraege fuer fruehere UTS-Versionen (UTS 2.4) sind unter UTS V nicht
lauffaehig. Unter UTS V fehlt der CBREAK-Modus.
Gibt es eine neuere version fuer den C-Kermit, der dem UTS V tribut
zollt? falls sie eine solche haben, schicken sie sie bitte an mich
via EARN.

[Ed. - Der "sys5" Eintrag im make-file gilt auch fuer UTS V.  Kermit
versionen koennen von KERMSRV@CUVMA nachgefragt werden durch BITNET
(EARN) -- z.B. "SMSG RSCS MSG CUVMA KERMSRV SEND CK* *" (CMS).
Excuse my fractured German.  - Frank]

------------------------------

DATE: 7-MAR-1986
FROM: BRIAN@UOFT02
SUBJECT: Problem with Kermit-11 and Intel MDS Kermit (Kermit-Isis)

 Problem: ISIS Kermit can get files from Kermit-11 server but can't send
them. Reported Mar 1986 by [e-mail]

 I know exactly what's wrong, if you would get the current save image from
my Vax it would go away.  The problem in older k11's is when kermit-11 gets
a short (6 char) S packet (ie, the absolute minimum) it stuffs a literal
null into the QBIN field of it's reply, which is a field that does not get
encoded. Please get a new version as described.  The same thing happened to
FidoNet Kermit with Kermit-11. This problem was fixed on 01-Nov-1985 version
2.37.

[e-mail]

[Ed. - Brian will be sending his new release to Columbia shortly.  Until
then, it's available on his VAX at the U of Toledo via BITNET or dialup,
as announced in Info-Kermit V4 #14.]

------------------------------

Date: Thu, 6 Mar 1986 13:06 EST
From: [e-mail]  (Eloise Kleban)
Subject: Altos Oasis Kermit?

Is there a version of Kermit for the Altos running Oasis?  We would
appreciate information and/or a diskette if anyone out there can supply us!
My BITNET address is ELOISE@MAINE.  My US mail address is:

                     Eloise Kleban
                     Computing Center
                     University of Maine
                     Orono, ME 04469

------------------------------

End of Info-Kermit Digest
*************************
-------
13-Mar-86 17:50:54-EST,14063;000000000000
Mail-From: SY.FDC created at 13-Mar-86 17:49:50
Date: Thu 13 Mar 86 17:49:50-EST
From: Frank da Cruz <[e-mail]>
Subject: Info-Kermit Digest V4 #17
To: [e-mail]
Reply-To: Info-Kermit@CU20B
Queries-To: Info-Kermit-Request@CU20B
Message-ID: <[e-mail]>

Info-Kermit Digest         Thu, 13 Mar 1986       Volume 4 : Number 17

Today's Topics:
                    BOO File Encoding and Decoding
            Kermit for the Apple ][ Pascal System (Q & A)
                        TI PC Kermit Ommisions
                          MSZ100.BOO Kermit
                 Kermit on HP Integral Problem (csh)
                     DEC-20 LAT Service vs Kermit
                 Kermit vs Telebit TrailBlazer Modem
                        Kermit on Epson QX-16?
                          Kermit & Wang PC's
            Kermit Diskettes for Atari 800XL or Macintosh?

----------------------------------------------------------------------

Date: Tue 11 Mar 86 14:46:09-EST
From: Howie Kaye <[e-mail]>
Subject: BOO File Encoding and Decoding

I have added UNIX support to the C-language .BOO file maker, MSBMKB.C,
so now it can be compiled for UNIX, MS-DOS, or TOPS-20.  On UNIX and MS-DOS,
it now does efficient blocked i/o, rather than character-at-a-time.  The
DOS version compiles under either Lattice or Microsoft C.

I've also written a .BOO file decoder in C, equivalent to MSBPCT.BAS.  It runs
in about 10 seconds on a PC, rather than 20 minutes.  There is a bug in this
program, which adds extra bytes to the end of the file every time it gets run.
This should not affect anything, as the data is all past what the program
thinks is it's end...If you encode/decode twice though, you do not get
identical files.

/Howie

[Ed. - Thanks, Howie!  The files are in KER:MSBMKB.C (and .BOO), KB:MSBMKB.EXE
(the .BOO and .EXE file are for MS-DOS), and KER:MSBPCT.C (and .BOO), and
KB:MSBPCT.EXE.  All these are available on the Internet from CU20B via
anonymous FTP.  The C and BOO files are also available on BITNET from KERMSRV
at host CUVMA.]

------------------------------

Date: 10 Mar 86 21:11:12 +0100
From: [e-mail] ([e-mail])
Subject: KERMIT for the APPLE ][ PASCAL system

I'm looking for a KERMIT that runs on an APPLE ][ under the (UCSD-)PASCAL
system. Any pointers are very welcome.  Please respond to me directly, as I'm
not on all the lists I'm sending this to.

Thank you very much

Ralf Bayer
Computing Center @ the Technical University of Darmstadt, West Germany

Arpanet address:   [e-mail]
BITNET  address:   xbr1yd22 @ ddathd21

[Ed. - See next message (yes, I responded to him directly too).]

------------------------------

Date: Thu 13 Mar 86 13:24:01-EST
From: Frank da Cruz <[e-mail]>
Subject: Kermit for Apple II UCSD p-System

I have a letter from Ph. P. Visser, Rekencentrum der Rijksuniversiteit,
Groningen, Netherlands:

"Enclosed you will find two diskettes concerning a Kermit version for
Apple II (e) and (+).

"The version is made by P. Terpstra of the Laboratory of Biochemics of the
State University of Groningen.  The version is written in UCSD Pascal.
It concerns Apple DOS 3.3 with several interface cards such as:
- Apple Communication Card (ACC)
- California CCS 7710 ASI Card (CCS)
- Hayes Micromodem Card (HMC)
- Apple Super Serial Card (SSC)
- IBM AP2 Serial Card (AP2)

"It is a corrected version of the Stevens version."

Unfortunately, I can't read the diskettes, which are in Apple II Pascal
format, 5.25 inch, double sided.  Could someone who has an Apple p-System
volunteer to read these diskettes and send the contents to Columbia?
Preferably someone on one of the networks, but failing that, someone who'd
be willing to send the files back to us on IBM PC or AT DOS diskettes,
Rainbow DOS diskettes, or 9-track magnetic tape.  Thanks!

------------------------------

Date: Wed, 5 Mar 86 20:33:34 cst
From: Rusty Haddock <seismo!ut-sally!im4u!ti-csl!tilde!haddock>
Subject: TI PC Kermit Ommisions

I've checked the sources for version 2.28 revision 5 and found that the things
that have been asked about are UNIMPLEMENTED!  Things like local echo, inverse
video, auto wrap, and the like are just not there (in file MSYTIP.ASM).  Local
echo should check the 'ecoflg' flag in some data structure and display the
outgoing character accordingly.  Inverse video is a "stub" that just returns.
These should be trivial to actually code *OR* you can take the old MSXTIP and
MSYTIP from a previous version of Kermit, assemble, and link them in as the old
version at least had local echo.

Unfortunately, hacking with MS Kermit is very low on my list of things to do
but... who knows, I might get to it.

            -Rusty-

------------------------------

Date: 11 Mar 86 17:00:00 EST
From: "M. COOK" <[e-mail]>
Subject: MSZ100.BOO KERMIT

Gordan C. Holterman indicated in his message of 7 March that he was unable
to successfully use the STATUS command inthe KB:MSVZ10.EXE version of
Kermit.  The same problem exists in the MSZ100.BOO version.  On the contrary
I have had no problems Receiving or Getting files.  I have however
experienced hangups while reading Mail on the MILNET; but this seems to
occur only when a capture file is open. Usually, all that needs to be done
is to depress the RETURN Key. But, even at that some information is dropped.
                                    Regards,  MHE COOK  (NORDET)

------------------------------

Date: Tue 11 Mar 86 05:26:16-EST
From: [e-mail]
Subject: Kermit on HP Integral Problem (csh)

    I recently installed the new operating system ROMs in my HP Integral
PC.  Since then I have had a minor problem with C-Kermit (050) while running
under csh.  It is likely a problem with either the OS and/or csh, but since
C-Kermit is the only effected program (so far), I thought that I would inquire
here for suggestions.

Situation:    Connecting to a Hayes compatible modem to dial a number.  Line
        set to /dev/tty00 and baud set to 1200.
Behavior:    Running under sh and either the old HP-UX ROMs (System III?)
        or the new HP-UX ROMS (S5R2) kermit works normally.  Running
        under csh and the old HP-UX ROMs kermit also works normally.
        Running under csh and the new ROMs, the echo from the modem
        does not appear on the screen.  Typing the pulse dial command
        (ATDPxxxxxxx) and hitting a carriage return results in having
        the modem dial the number xxxxxxx.  Even after a connection has
        been made, no echo appears on the screen.  Escaping (or
        attempting to) to local control (^\-C) results in csh being
        logged off (SIGINT or SIGKILL is being sent?).  Attempting to
        log session, packets, debugging and transactions is sort of
        futile, only the debugging log shows anything.  The following
        is the tail end of the debugging log complete with initial
        header:

    Does anyone out there have any idea as to why C-Kermit works with sh
under both versions of the ROMs and only with the old version of the ROMs if
csh is used?  I plan to look into this this summer, but getting a note back as
to the cause and fix may be difficult as I will no longer have access to any
networks.  Also I don't have ADB so debugging is going to be fun.  This summer
I will try to get C-Kermit to work with the shell PAM, right now the system
locks up badly if kermit is started up from PAM as opposed to sh or csh.

                        Gordon Haverland
                        GH0N @ TC.CC.CMU.EDU
                        Box 596
                        Dawson Creek, B.C.
                        Canada
                        V1G 4H5

[Ed. - I asked Gordon to try the current version of C-Kermit, 4C(057), to
see if the problem persists.  Anybody else have any hints or experience with
this?]

------------------------------

Date: Thu 13 Mar 86 14:40:53-EST
From: Frank da Cruz <[e-mail]>
Subject: DEC-20 LAT Service vs Kermit

When you are connected to a DEC-20 through a DEC Ethernet terminal concentrator
(like DECserver-100) using the LAT protocol, you will find that you can't
transfer files of any kind into the DEC-20 using Kermit or MODEM or any similar
protocol.  You can, however, transfer files from the DEC-20 to the PC with no
problem.  Logging packets during uploading reveals that a typical Kermit data
packet (80-90 characters) is truncated by the LAT box to 30-40 characters.  If
you reduce the Kermit packet size to, say, 37, then everything works.

The problem occurs because TOPS-20 LAT service defines the LAT input buffer
length to be 40 instead of the recommended 127 (133 would be better for MODEM).
The problem does not occur with Ultrix-32 LAT service.  For now, those who want
to use Kermit to send files to a DEC-20 through a LAT box must set their packet
size to 37 or less.  Those who want to use MODEM will have to use Kermit
instead, since MODEM packet sizes cannot be changed.

------------------------------

Date: Thu 13 Mar 86 15:16:03-EST
From: Frank da Cruz <[e-mail]>
Subject: Kermit vs Telebit TrailBlazer Modem
Keywords: Telebit

We had the chance to try out a pair of Telebit TrailBlazer modems recently.
These modems use a proprietary packet protocol to provide error-free
transmission up to 10,000 baud over ordinary dialup lines.  They include the
regular Hayes command set, augmented by a lot of special settings.  We used the
"old ROM" version -- apparently there is a "new ROM" that makes things better.

The short story is that Kermit works over these modems, but the performance is
awful.  The modem's algorithm for sending a packet seems to be to wait until
its buffer is full, or else until its timer goes off.  Unfortunately, its
buffer is bigger than a Kermit packet, so it will never send a Kermit packet
until it times out.  The timeout interval seems to be something like 5 seconds,
and there's no way to change it.  Furthermore, there's no concept of "data
forwarding characters" like you have in an X.25 PAD, so you can't tell it to
transmit whatever it has in its buffer whenever it sees a carriage return.
As you might imagine, interactive terminal use is pretty bursty.

For "classic" Kermit between two PC/AT's at 9600 baud over a local phone call,
the effective data rate was something like 40 baud.  Windows-kermit on the same
connection did a lot better: about 3700 baud.  But even with windowing, there
were many pauses and delays; the throughput should have been more like
7000-8000 baud.

The manual doesn't say anything about its packet buffering and forwarding
technique, except to imply that its buffer is about 10,000 characters long.
There is a sentence, however, to the effect that "many communication software
packages (especially those using half duplex protocols such as XMODEM) may not
be optimized for use the TrailBlazer."  Later on they say "The TrailBlazer's
packetizing and retransmission behavior must be accommodated by any protocol
that contains timers for inter-character delays or response limits."

Some commercial software packages, like Crosstalk, have added explicit
TrailBlazer support.  It would have been better if Telebit had used the power
of the 68000 to make the operation of the modem a little more flexible by
letting the user specify the timeout interval and break mask.

------------------------------

Date: Mon, 10 Mar 86 15:33:14 PST
From: arch%renoir@berkeley (Arch Turner)
Subject: Kermit on Epson QX-16?
Keywords: Epson

Has anyone made Kermit work on an Epson QX-16?  Can it be set up as if the
QX-16 were an IBM PC?

                Thanks,
                    Arch Turner, CSSG Staff
                    467 Evans, 2-1319
                    arch@renoir

------------------------------

Date: 11 Mar 86 23:33:00 EST
From: <dana@bbnccr>
Subject: Kermit & Wang PC's
Keywords: Wang PC Kermit

I tried to load KB:MSVWNG.EXE using FTP and then KERMIT and got a 'not
enough memory' error (on a 640k machine).  So I downloaded MSVWNG.BOO and
MSBPCT.BAS and built the executable.  The STATUS command printed a few
thousand spaces, a few random bytes of memory, and then the system died.
Not too long ago (a few months at least) a new version of the operating
system was received from wang. The version numbers are:

    Wang professional computer: V2.40
    Bios:                V1.21
    MS-DOS:                V2.01

Also, I tried the generic KERMIT and it worked fine (it's not the ASM or
LINKER, as thats how I built the generic version. Bothe the ASM and LINKER
are version 1.10). HELP!!!

                Thanks,
                    Eric Dana
                    dana@bbnccr
                    BBNCC/MIS

[Ed. - Can anybody out there help?  If you have a working version of Wang
PC Kermit, could you send in, or point us at, an .EXE or .BOO file for it?
I know Wang PC Kermit worked at one time, because it was written here at
Columbia.  Unfortunately, the person who wrote it and the PC itself are both
long gone.]

------------------------------

Date: 12 Mar 1986 1453-EST
From: LCG.KERMIT@DEC-MARLBORO
Subject: Kermit Diskettes for Atari 800XL or Macintosh?
Keywords: Mac Kermit, Atari Kermit

I would like to obtain a copy of Kermit both for the Atari 800XL and for the
Apple Macintosh.  However, I have no communication software whatever on either
machine, and on the Atari I have only Basic (so KERBOO does not help).
Can anyone out there in Kermit-Land help me?  If so, please contact me
as follows:
    Paul Liebow
    W.R.Grace & Co.
    1114 Avenue of the Americas
    New York, NY 10036
    212/819-6963
... And thanks!

[Ed. - We sent him a note about how to order Mac Kermit on diskette from
us.  Can anybody help with Atari Kermit?  If so, would that person care to
volunteer as a general Atari Kermit diskette distributor?  Or to submit the
Kermit diskette to some kind of Atari user group that could distribute it,
and then tell us about it so we could refer future inquirers there?]

------------------------------

End of Info-Kermit Digest
*************************
-------
18-Mar-86 15:30:28-EST,10216;000000000000
Mail-From: SY.CHRISTINE created at 18-Mar-86 15:28:00
Date: Tue 18 Mar 86 15:28:00-EST
From: Christine M Gianone <[e-mail]>
Subject: Info-Kermit Digest V4 #18
To: [e-mail]
Reply-To: Info-Kermit@CU20B
Queries-To: Info-Kermit-Request@CU20B
Message-ID: <[e-mail]>

Info-Kermit Digest         Tue, 18 Mar 1986       Volume 4 : Number 18

Today's Topics:

           MS-DOS Kermit 2.29 Almost Ready, Testing Needed
                          KERMIT on the Z100
                    I have a working AMIGA KERMIT
                  MACKERMIT Terminal Emulation Fixes
                 Kermit on LAT with VMS (2 messages)
                  Re:Kermit(057) on the HP Integral

----------------------------------------------------------------------

Date: Tue 18 Mar 86 13:51:43-EST
From: Frank da Cruz <[e-mail]>
Subject: MS-DOS Kermit 2.29 Almost Ready, Testing Needed
Keywords: MS-DOS Kermit

Joe Doupnik has begun the task of adapting the system-dependent support
modules for the various non-IBM system to the current prerelease of MS-DOS
Kermit, 2.28 jrd/5e.  This is very close to the final 2.29 release.  The
Rainbow version has already been built and seems to work just fine (a neat
trick for Joe, considering he didn't have a Rainbow to test it on, and the
memory management code had to be redone).

The files are on CU20B, in PS:<KERMIT-MS>.  Included are a complete set
of system-independent sources (MSS*.ASM and .H), objects (MSS*.OBJ), and
system-dependent sources (MSX*.ASM, MSY*.ASM, and MSZ*.ASM).  The objects
were produced using MASM 1.10 on a DEC Rainbow.  The .EXE and .BOO files
are already built for the IBM PC family and the Rainbow.

I would appreciate it if anyone on the Internet who has access to any of the
following systems would FTP the necessary source &/or object files and try
to build 2.28 jrd/5e for their systems, and give it a good workout.  If there
are problems, please report them.  If it works, please send a .BOO file, or
point us to where we can FTP an .EXE file from.  Here are the systems to be
tested:

PS:<KERMIT-MS>

 MSXAP3.ASM  NEC APC 3
 MSXAPC.ASM  NEC APC
 MSXAPR.ASM  Apricot
 MSXDM2.ASM  DECmate III with MS-DOS option
 MSXEZP.ASM  Z100 with UCI EZ PC card
 MSXGEN.ASM  Generic DOS
 MSXGRI.ASM  Grid Compass
 MSXHP1.ASM  HP150
 MSXHPX.ASM  HP 110, and (or?) Portable
 MSXIBM.ASM  IBM PC, XT, AT, etc, and compatibles (.BOO and .EXE available)
 MSXM24.ASM  Olivetti M24
 MSXMBC.ASM  Sanyo
 MSXRB.ASM   DEC Rainbow (.BOO and .EXE available)
 MSXTIP.ASM  TI Pro (not quite ready yet)
 MSXV90.ASM  Victor 9000
 MSXWNG.ASM  Wang PC
 MSXZ10.ASM  Heath/Zenith 100

These files are not available on BITNET, since the only way to make them
available via KERMSRV would be to overwrite the current release, which should
not a be done until the new release is checked out for all these systems.

Anyone using FTP to get the binary (.OBJ and .EXE) files from CU20B might have
to take special measures.  If you're coming in from a system that's not a
DEC-20, you'll have to give special FTP commands to get the binary files,
like TYPE L 8.

------------------------------

Date:  Sun, 16 Mar 86 23:20 EST
From:  [e-mail]
Subject:  KERMIT on the Z100
Keywords: Z-100 Kermit
Cross-Ref: Z100, Zenith Kermit, Heath/Zenith (see also z-100 Kermit)

In reponse to the request for Z-100 kermit problems, I'd like to add my
observations:

1)  The new version 2.28 does indeed do nasty things when certain
    commands are executed.  Status, for one, hangs the machine.

2)  The problem added after PC-KERMIT, that of hanging up the modem
    with a change from connect to send or receive, has not been fixed
    with version 2.28

3)  The misbehavior of KERMIT with VI has been fixed with 2.28;  it
    seems that the terminal emulator can finally keep up with the
    modem without long delays after screen refreshes, etc.

4)  The DELSTR for the Z100 KERMIT is different than for 2.27;  it must
    be changed from the source 'bs,' ',bs to require another bs.
    The reason for the change is not entirely clear, but if not fixed, it
    makes KERMIT appear not to erase its input.

I would like to have a totally working version of KERMIT past 1.27j, but
until problem 2) is fixed, my transfers must be done with that old version.

A question is, WHO is current with KERMIT for the Z-100?  I have sent
mail to both INFO-HZ100 and INFO-KERMIT and not received any responses.
Can it be that the Z100 KERMIT is up for grabs?

My best to the lucky ones, and a thanks to Catchings, da Cruz, Tzoar, et. al.
for giving us a fun protocol to hack at......

[Ed. - Try the new version of MS-DOS Kermit 2.28/jrd5e from the previous
message and see if the same problems occur.]

------------------------------

Date: 14 MAR 86 17:02-EST
From: DPVC@UORDBV
Subject: I have a working AMIGA KERMIT
Keywords: Amiga Kermit

I am a long-standing fan of KERMIT, so when by brother bought an AMIGA
micro-computer recently, bringing up KERMIT for it was one of my first
projects.  I have a working AMIGA KERMIT, based on the UNIX C-KERMIT
version.  It is line-oriented, not menu-oriented, as is the MACKERMIT, but I
felt that getting a solid, tried-and-true KERMIT working was more important
than a slick look, at least to start with.

There have been a number of requests for AMIGA KERMIT on INFO-AMIGA and
net.micros.amiga, so I feel that it would be a good product to add to your
list of available KERMITs.  I am still developing some of the less important
features, but all the file transfer parts work very well.  I have NOT
implemented local shell commands (directory, cd, etc.), nor thier
server-mode equivolents, though, SEND, GET, HELP, FINISH and BYE are
supported in server-mode.  I do not support wildcard file look-ups (yet),
and have no special terminal emulation (VT100 is planned); at the moment,
when you CONNECT you just get a dumb terminal.

I have had a number of requests to distribute my version.  I would like your
advice on how best to do this, and on whether I should distibute myself, or
if you would rather route it through KERMSERV on BITNET.  I would be happy
to send you the sources to you, but I hesitate to send them to too many others,
as they amount to quite a bit (CKUCMD, CKCFNS, etc.).

I plan to continue to develop AMIGA KERMIT, though I feel that it is well
enough along for many people to benefit from it.  I was able to bring it up in
less than three weeks (working evenings only), which I attribute to the
excellent design of the common C-KERMIT modules.  It is a pleasure to work with
your code.

Please let me know whether you are interested in this as soon as possible, as
there are people waiting for AMIGA KERMIT to be released.

[Ed. - Kermit for the Amiga is on the way and will be announced as soon
as it arrives. ]

                                Davide P. Cervone
                                University of Rochester
                                Computing Center
                                Taylor Hall
                                Rochester, NY  14627

                                [e-mail]
                                seismo!rochester!ur-tut!dpvc.UUCP
                                [phone]

------------------------------

Date: 14 MAR 86 17:02-EST
From: DPVC@UORDBV
Subject: MACKERMIT Terminal Emulation Fixes
Keywords: Mac Kermit

Sometime in November, I sent you a message about enhancements to the
MACKERMIT VT100 emulator that we have made here ate the U of R.  Did you
ever receive it?  We have been using these corrections here since then
throughout the University, and find them very helpfull.  The VT100 emulation
is much better than the current release version.  If you are interested in
these, please let me know, and I will send them, too.

[Ed. - Nope, I must have missed this message somehow!  Davide has since sent
along the Mac Kermit changes, and they fix most of the problems with VT100
terminal emulation (like the notorious boldface problem), and add some highly
desirable new features too, like using the mouse to send arrow-key cursor
positioning commands.  In a couple hours of testing, the only problems I
found with it were that it incorrectly reported itself to be a VT100 with AVO
rather than a VT102, and that the control keys no longer autorepeat.  Since
this version has not yet been thoroughly tested, it won't become the standard
one just yet, but it has been placed KER:MC2*.* for now, alongside the regular
version.  Please try it out.]

------------------------------

Date: Thu 13 Mar 86 20:49:41-EST
From: Richard Garland <[e-mail]>
Subject: Kermit on LAT with VMS
Keywords: VMS Kermit

FYI - Kermit works fine using LAT under VMS.  I use it every day.
                        Rg

[Ed. - This message and the following one are in response to the note in the
last Kermit Digest V4 #17.]

------------------------------

Date: 14 Mar 86 12:53:00 PST
From: [e-mail]
Subject: Kermit on LAT with VMS
Keywords: VMS Kermit

    I have had the same problem with VAX VMS LAT ver 1.0.  Supposedly the
new version 1.1 or 2.1 will fix the problem.  I found your discussion very
useful.  Thanks.

Alex.

------------------------------

Date: Sat 15 Mar 86 17:13:07-EST
From: GH0N@CMCCTC
Subject: Re:Kermit(057) on the HP Integral
Keywords: HP Intregal, C-Kermit

    This note is in reply to my previous post about an incomptibility
between C-Kermit and csh on the HP Integral that has the new (SVR2) ROMs.
Installing the latest version of C-Kermit(057) did not have any effect on
the supposed incompatibilty.  Running with csh alone or sh on top of csh
resulted in the loss of communication from the modem to kermit.  When escape
to local control (^-\C) was attempted the csh process stopped.  It is not
known whether csh is recieving EOF or some signal such as SIGINT or SIGKILL.
Sometime in the near future (hopefully) I will get the oportunity to run
C-Kermit from debug to find out what is happening.

                        Gordon Haverland

------------------------------

End of Info-Kermit Digest
*************************























-------
21-Mar-86 19:51:11-EST,14994;000000000000
Mail-From: SY.FDC created at 21-Mar-86 19:50:33
Date: Fri 21 Mar 86 19:50:33-EST
From: Frank da Cruz <[e-mail]>
Subject: Info-Kermit Digest V4 #19
To: [e-mail]
Reply-To: Info-Kermit@CU20B
Queries-To: Info-Kermit-Request@CU20B
Message-ID: <[e-mail]>

Info-Kermit Digest         Fri, 21 Mar 1986       Volume 4 : Number 19

Today's Topics:
           New C-Kermit Release Available for UNIX and VMS
                 Printable Encodings for Binary Files
               Re: Printable Encodings for Binary Files
                          Kermit & Telebits
                          Sperry 1100 Kermit
                   Spooling Prints from an IBM/PC?
                  Re: Spooling Prints from an IBM/PC
                 Problems with Kermit on SCO Xenix V
               MS-DOS Kermit on ATT 6300 vs VMS Kermit?

----------------------------------------------------------------------

Date: Fri 21 Mar 86 11:11:21-EST
From: Frank da Cruz <[e-mail]>
To: Info-Kermit@CU20B, info-unix@brl-sem
Subject: New C-Kermit Release Available for UNIX and VMS
Keywords: C-Kermit
Cross-Ref: VAX Kermit, UNIX Kermit (see also C-Kermit)

This is to announce a new release of C-Kermit.  It is only a minor release,
and incorporates no new functionality.  The only intention is to fix the
more serious bugs.  Future releases will involve more serious reworking of
the code to improve organization and performance, and to add missing features,
like extended packets, sliding windows, and attribute packets.

The new release is called 4C(058), for UNIX and VMS.  The fixes that
apply to all (or most) systems supported by C-Kermit include:
. Bug with set send/receive padding fixed.
. Bugs that interfered with wildcard sends fixed.
. Bug that mixed up send and receive packet terminators fixed.
. Bug with single-file cancellation (^F or ^X) fixed.
. NAK for next packet now handled correctly as equivalent to ACK for current.
. NAK is no longer immediately sent after RECEIVE or SERVER command given.
. Long bursts of incoming data no longer crash the program.
. Longer sleep done at end of file transfer to prevent other side from hanging.
. ^S removed from among CONNECT escape character arguments.
. Dial pause of 0 no longer causes problems.

The fixes specific to UNIX include:
. Fixed support for 2.9 BSD (tested on DEC Pro 380).
. New makefile entry for Masscomp (untested).
. Some 0's in system calls changed to NULLs.
. SET SEND/RECEIVE TIMEOUT 0 no longer prevents file transfer from working.

VMS changes (untested):
. '!' should now spawn an interactive DCL.
. REMOTE commands to VMS C-Kermit server should now work.

The new version of Macintosh Kermit that is based on C-Kermit is not ready
yet because it's too big for our SUMACC cc68 cross-compiler to handle.
We're trying to dig up a version of cc68 with an expanded symbol table
(anybody have one we can FTP?).

The new C-Kermit files are in KER:CKC*.*, KER:CKU*.*, KER:CKV*.* on CU20B,
available via anonymous FTP, and in CKC* *, CKU* *, and CKV* * on CUVMA
via KERMSRV over BITNET.  They should also find their way to uucp host okstate
at Oklahoma State University within a day or two.

------------------------------

Date: Tue, 18 Mar 1986  09:12 MST
From: "Frank J. Wancho" <[e-mail]>
Subject: Printable Encodings for Binary Files
Keywords: Binary Files

Apparently the Intel HEX format, which HEXIFY generates, is not usable
on the PCs.  What do you use?  Is it those .BOO files?  If so, how do
you generate them?  Can they be generated on the 20?  And, what is
used on the PC side to recreate the original?

------------------------------

Date: Thu 20 Mar 86 08:53:10-EST
From: Frank da Cruz <[e-mail]>
Subject: Re: Printable Encodings for Binary Files
Keywords: Binary Files

We have a couple programs on the DEC-20 for doing this kind of stuff.

KT:HEXIFY.* and KT:HEXCOM.* convert CP/M .COM files to Intel hex format
& vice versa.  These were written by Bruce Tanner of Cerritos College, and
run on the DEC-10 or DEC-20.  But I believe Intel hex format is of little
use on MS-DOS systems.

KT:HEXE.* and KT:UNHEXE.* convert between 8-bit binary files and straight
2-for-1 hex encoding (with CRLFs inserted for readability).  I wrote these in
about 10 minutes one day.  They only work on the DEC-20.

The .BOO file format is something we invented for distributing MS-DOS Kermit,
but it should work for any 8-bit binary file.  It's sort of like Macintosh
BinHex (but .BOO came first): 4-for-3 printable ASCII encoding, with
compression of repeated zero bytes.  A typical .BOO file is shorter than the
corresponding .EXE because of the zero-compression.  Here are the relevant
programs:

KER:MSBMKB.C turns an 8-bit binary file into a .BOO file.  KB:MSBMKB20.EXE is
a version that runs on the DEC-20; KB:MSBMKB.EXE is for MS-DOS.  It can also
run on Unix.

KER:MSBOOT.FOR is a Fortran program that runs on a mainframe that downloads
a .BOO file to a PC.  It runs on DEC-10, DEC-20, VMS, even IBM mainframes.
KER:MSBPCB.BAS is the corresponding Microsoft Basic program that receives the
.BOO file from MSBOOT, decodes it on the fly, and stores the resulting binary
file on the disk.

KER:MSBPCT.* are the programs that translate a file from .BOO format back to
.EXE (or whatever).  They assume you have already downloaded the .BOO file.
The C version can run on Unix or MS-DOS (it takes a few seconds to process a
40K file).  The .BAS version is in Microsoft Basic for MS-DOS -- it takes about
20 minutes to do the same 40K file.

------------------------------

Date: Thu, 20 Mar 86 07:54:29 EST
From: [e-mail] (Scott Brim)
Subject: kermit & Telebits
Keywords: Telebit

Frank, some mail you sent to Don Porter has wended its way to me.  I'm
surprised you got even that much throughput running Kermit with the
Telebits.  The answer is to use the new "interactive mode" PROMs - much
smaller delay times and a few other changes for tuning for real
terminal use.  I think you'll see much better performance.

[Ed. - We might be getting some of these next week.  If so, will give
them a spin.]

------------------------------

Date: Wed, 19 Mar 86 17:00:47 cet
From: [e-mail]
Subject: Sperry 1100 Kermit
Keywords: Sperry

We are running the Sperry Kermit by Paul Stevens, dated june/july 1985.
If anyone is interested, here is a report of some of our problems with
this Kermit, and our fixes for them.   Apart from these minor annoyances,
Kermit has been a pleasure to use!

       (1) There is no need for Kermit to assign the Sperry work file
           exclusively, apart from the risk that someone else writes to
           the file during transmission.   To me, this was more annoying
           than useful, so I changed the file assignment as shown.

       (2) As distributed, Kermit will not treat program file elements
           with multiple cycles (indicated by fieldata S in S3 of the
           label control word), unless the data part of the label conforms
           to the SDF standard (*SDFF* in first word).   As a result,
           elements written by the system line editor ED, will not be
           transmitted correctly.   That is, if our fix is not applied...

       (3) When ACK'ing a previous data packet, Kermit as distributed put
           the first 6 characters of the ACK'ed packet into the data part
           of the ACK.   I haven't seen any Kermit do that before, but it
           looks straight enough.   However, after receiving a couple of
           those 'long ACKs', IBM PC-Kermit (2.28) fills the next one or
           two packets with garbage (typically, a lot of zeros - nicely
           encoded, though, so the receptor does not notice).   The result
           is an apparently successful transmission, with a few 'black holes'
           in the element on the Sperry host.   Changing the data size to
           zero in these ACKs seemed to eliminate the problem.

These are the fixes in Sperry correction card format

  (1) -3177,3177
                sTrng     '@ASG,A  K$E$R$M$I$T$ . ' . Not exclusive
  (2) -4287,4288
  (3) -4713,4715
                sz,h2     prline           . Do a normal ack of length 0
                l,u       a2,prline        . Seems to confuse PC-Kermit

-fi
Frithjov Iversen
Trondheim University Computing Center, Norway

[Ed. - Taksgardeha!  (Did I spell that right?  Not a chance...)  I've added
your note to the .BWR file.  I trust that pAul sTevens will see it himself
one day.]

------------------------------

Date: Thu, 20 Mar 86 12:22:20 est
From: Ken Mandelberg <[e-mail]>
Subject: Spooling Prints from an IBM/PC?
Keywords: PC Kermit

Is there any combination of kermits, that would allow spooling of files for
printing from an IBM/PC to a Unix host, without any operator interaction?
The normal steps of terminal emulation for login, escape to command mode,
initiating a file transfer, back to terminal emulation to issue some unix
print command, escape and terminate, seems to frustrate our secretaries. In
fact anything short of typing a one line command, or better yet a function
key, seems to be a problem.

I am a little out of date on what is available in each kermit version. The
server mode for Unix kermit would seem to speak to the question, but I think
PC kermit does not exploit it. Even if available, the server approach might
not be a great solution. The logistics of starting, stopping, the server,
and dealing with any malfunction would be very frustrating to these users.

Any suggestions and information would be appreciated. If there is a better
approach then kermit for this problem, that too would be appreciated.

Ken Mandelberg
Emory University
Dept of Math and CS
Atlanta, Ga 30322

{akgua,sb1,gatech,decvax}!emory!km   USENET
km@emory                      CSNET
km.emory@csnet-relay          ARPANET

------------------------------

Date: Fri 21 Mar 86 09:01:37-EST
From: Frank da Cruz <[e-mail]>
Subject: Re: Spooling Prints from an IBM/PC
Keywords: PC Kermit

What you really need is a script facility in MS-DOS Kermit.  But there
isn't one.  The release after next will probably have it.  With a script
facility, you could put all the commands for logging in to Unix and
starting up the server into a command file, and the user could "take unix"
or whatever (you could even define a command macro for this to make it
easier, or use a utility like ProKey to bind it to a function key).

Without a built-in script facility in MS-DOS Kermit, you might still be
able to accomplish the same effect by writing a little program to log them
in and start the Kermit server.  It could be run from their autoexec.bat
file, or whatever.

Then, when they wanted to print a file, they could say "xprint foo.bar",
where xprint was a .bat file which simply translated the command into
"kermit send foo.bar".

On the Unix end, you could have server cd'd to a special spooling directory
(publicly writable), and then you could have a separate daemon process that
would wake up every so often, and print and delete any files that showed up
in this directory.

Finally, to let the user finish up for the day, you could have them type
simply "kermit bye".  If that's too complicated, you could bind this string
to another function key, or write a little .bat file with a more suggestive
name that does the same thing.

The users could not be entirely oblivious of what was happening.  The amount
of time to transfer a file from the PC to Unix could be significant if the
file is long.  In 2.29 of MS-DOS Kermit, you could include "set display off"
on the command line, which would disable the screen display during file
transfer.  Then, if they were using one of the "multitasking" systems like
DesqView, TopView, MS Windows, etc, they could continue with other work without
being bothered.  In the future, there may be a version of Kermit for MS-DOS
that can be installed as a device driver.  Once connected to a Kermit server
on the other end, it would work just like the PRINT command -- you could say
"send foo.bar", and it happen by itself, leaving even an ordinary DOS system
free to do other work during the transfer.  But don't hold your breath for
this one.

------------------------------

Date: Fri, 14 Mar 86 09:55:15 EST
From: [e-mail] (John Yatteau)
Subject: Problems with Kermit on SCO Xenix V
Keywords: Xenix Kermit

I obtained source for C-Kermit 4C(057) 31 Jul 85 from the harvard vax and
compiled it under SCO Xenix Sys V Rel 2.0 on both an IBM PC/AT and an
IBM PC.  The result was a dialect of Kermit in which the PC's can
communicate normally with each other, but not with the vax or any other
normal Kermit.  The Xenix Kermits appear identical to C-Kermit on the vax
in every other way.  The debug log shows the transfer hanging up on the
packet check ("rpack: chk_      should be [").  I had to modify the
makefile slightly to use the "middle model" option of cc, and tried all
likely makefile options (sys 3's and 5's).  I even recompiled C-Kermit
on the vax to insure that the sources were identical.

Any ideas?

    Jack Yatteau
    [e-mail]
    617-495-9663
    Pierce Hall/CEPP
    29 Oxford St.
    Cambridge, MA 02138

[Ed. - Beats me!  This program is known to work on at least some versions
of Xenix on the IBM PC family.  Has anyone out there seen anything like
this?]

------------------------------

Date:     Fri, 21-MAR-1986 11:22 MST
From:     KEVIN GRAY <GRAYK@BYUVAX>
Subject:  MS-DOS Kermit on ATT 6300 vs VMS Kermit?
Keywords: MS-DOS Kermit, VMS Kermit

I am running MSDOS-KERMIT version 2.28 on an AT+T PC6300 and have experienced a
few problems that I hope you can help me remedy.  While transferring files to a
Vax-8600 KERMIT-32 I have an inordinate number of retries-approximately 1 retry
for every 10 packets sent.  I have also had difficulty transferring files of
20Kbytes or more to KERMIT-32.  With the KERMIT-32 in server mode I have been
able to download files of up to 200Kbytes with 0 retries but when uploading
large files I very rarely have a successful transfer.  Sooner or later I get
a KERMIT-32 device timeout error or a KERMIT-32 receive error.  Smaller packet
sizes have made no difference.  I have spoken to other users on the same system
who use different micros and none have reported the same problem so I am not
sure if the error is in my machine or not.  I would greatly appreciate any help
you could give me regarding this problem.

                                        Thank You,
                                        Kevin Gray "grayk@byuvax"

[Ed. - Another "beats me".  Does anyone else have any experience
transferring very large files between these two systems?]

------------------------------

End of Info-Kermit Digest
*************************
-------
25-Mar-86 16:25:44-EST,6651;000000000000
Mail-From: SY.CHRISTINE created at 25-Mar-86 16:24:05
Date: Tue 25 Mar 86 16:24:05-EST
From: Christine M Gianone <[e-mail]>
Subject: Info-Kermit Digest V4 #20
To: [e-mail]
Reply-To: Info-Kermit@CU20B
Queries-To: Info-Kermit-Request@CU20B
Message-ID: <[e-mail]>

Info-Kermit Digest         Tue, 25 Mar 1986       Volume 4 : Number 20

Today's Topics:
                       Amiga Kermit Executable
                            New Kermit-10
                          MS-DOS Kermit 2.29
                       Kermit-11 Known Problems
                           OK State Access
                       Request for Epson QX10?

----------------------------------------------------------------------

Date: 24 MAR 86 15:41-EST
From: [e-mail]
Subject: Amiga Kermit Executable
Keywords: Amiga Kermit

I am sending you a file called CKAKER.BOO, which is the Amiga Kermit executable
in BOO format.  I also include my version of MSBPCT.C, which should translate
it back into the executable.

This version is a PRE-RELEASE version.  I am sending it so that you can test
it, and send me any comments you may have.  I am getting the sources in shape
to send, but it is taking longer than I thought it would (doesn't it always?).

Right now, the known problems/deficiencies are:

        1)  Wildcards are not allowed in filenames
        2)  No LOCAL commands are supported (DIRECTORY, CWD, etc.)
        3)  No DIAL or login scripts
        4)  The SERVER mode only does GET, SEND, BYE, FINISH and REMOTE HELP
        5)  No XON/XOFF flow control
        6)  REMOTE HELP messages go to the DOS window, not the KERMIT window
            (in fact, they don't show up until you exit from Kermit)
        7)  The program thinks the window is 80 columns wide, when, in fact,
            it is only about 76 columns wide (it can be resized to be even
            smaller)
        8)  No terminal emulation (just a dumb terminal in CONNECT mode)
        9)  File transactions all report elapsed time of 0 seconds (although
            timeouts work properly)

That's all I can think of right now.  Please let me know if you come up with
any other problems or improvements.

You should receive 2 files:  CKAKER.BOO and MSBPCT.C

                                        Davide

[Ed. - Thanks!  These files are in KER:CKAKER.* and KER:MSBPCT.C.]

------------------------------

Date:     Tue, 25 Mar 86 14:03:48 EST
From:     dstevens (David L Stevens) @ sitvxb
Subject:  New Kermit-10
Keywords: Kermit-10

The latest version of KERMIT-10 is now available.  The changes made are
documented in K10133.MEM.  The K10V3.RNO documentation is still valid.

Please note that you must rename K10MIT.HLP to KERMIT.HLP if you wish to
have KERMIT give you online help.  If there are any problems with this
release please let me know.

 - David L. Stevens
 - Stevens Institute of Technology
 - DSTEVENS@SITVXB

[Ed. - Thanks!  The new files are in KER:K10*.*.  The .EXE file, for those
who can FTP binary files, is in KB:K10MIT.EXE.]

-------------------------------------

Date: 25 MAR 86
From: SY.CHRISTINE@CU20B
Subject: MS-DOS Kermit 2.29
Keywords: MS-DOS Kermit

2.29 is almost ready for release.  It has been tested on the IBM PC family
and the DEC-Rainbow but not on anything else.  It's all there, just waiting
for people to try it out for the NEC, Sanyo, Victor, Apricot and all the
other non-IBM compatible systems.  Please test this and send reports back to
us.  If it does work, please send us a .BOO file.  If it doesn't, please
report the bugs.  We will just continue to distribute the old .BOO files
with the new source for those systems we do not get reports about.  The
files are in PS:<KERMIT-MS>*.* .  Thanks!!

                                      -Chris

------------------------------

Date: 25 MAR 86 09:04-EST
From: BRIAN@UOFT02
Subject: Kermit-11 Known problems
Keywords: Kermit-11

 Attribute processing is incorrect for some attribute types. This  dates
back  to  April 1984 when support was first added, but no other versions
were available to test against.  The  correction,  made  to  K11ATR.MAC,
will  cause  V3.49  or later of Kermit-11 to have compatability problems
with previous versions  of  Kermit-11.  The  main  problem  will  be  in
informing  each  other of binary file arrival; the only workaround is to
explicitly force two communicating Kermit-11's  into  binary  mode  with
the SET FILE command. See K11INS.DOC for further information.

 The  specific  problem is that the protocol requires the attribute TYPE
field to be  followed  by  a  LENGTH  byte  to  specify  the  number  of
characters  following.  Kermit-11  was  not  always inserting the LENGTH
field. The new  version,  3.49,  will  be  able  to  tell  if  an  older
Kermit-11  is sending in the incorrect format by virtue of the fact that
the first attribute packet that is  sent  is  the  system  id  code  and
operating  system. Since this attribute will always be a short one (2 or
3 characters at most) it is a simple matter to detect the presence of  a
'D'  (for  DEC)  in  the  position  of  the  LENGTH field and set a flag
accordingly. However, in the case of the corrected Kermit-11 sending  to
a  pre  3.49 version, this will not be the case and all attempts to rely
on the transfer of attribute packets will fail.

The dialup service on the VAX 11/785 will be updated on 26-Mar-1985.
Columbia will be sent a tape on 27-Mar-1986.

[e-mail]

------------------------------

Date:     Mon, 24 Mar 86 15:18:00 CST
From:     Mark Vasoll <[e-mail]>
Subject:  OK State Access
Keywords: Okstate

Some of the files recently announced on Info-Kermit (like the new C-Kermit
files) may have been delayed in getting to okstate for UUCP access because
the system that okstate gets them from was down for a couple days.
Everything should be back to normal by the time you read this.

------------------------------

Date: Mon, 24 Mar 86 16:59:02 cet
From:  [e-mail]
Subject: Request for Epson QX10?
Keywords: Apple III, Epson

I am supporting Kermit at the university of Liege, Belgium.  I have a
request from a guy who owns an Epson QX10 (both CP/M 2.2 and 3).  Do you
have a ready version or information for that machine?

Thank you for getting me on the mailing list, I also long await the promised
Apple III version.

A. Pirard
SEGI
Universite de Liege
15, avenue des Tilleuls
4000 Liege  BELGIUM

------------------------------

End of Info-Kermit Digest
*************************
-------
 3-Apr-86 18:45:43-EST,6779;000000000000
Mail-From: SY.CHRISTINE created at  3-Apr-86 18:44:49
Date: Thu 3 Apr 86 18:44:49-EST
From: Christine M Gianone <[e-mail]>
Subject: Info-Kermit Digest V4 #21
To: [e-mail]
Reply-To: Info-Kermit@CU20B
Queries-To: Info-Kermit-Request@CU20B
Message-ID: <[e-mail]>

Info-Kermit Digest         Thu, 03 Apr 1986       Volume 4 : Number 21

Today's Topics:

                     Macintosh Kermit 0.8(34) Available
                           New KERMIT-10 Release
                       Supported Protocol Converters?
                       Datastream Protocol Converters?
                     Using Kermit With FASTLINK Modems?

----------------------------------------------------------------------

Date: Thu 27 Mar 86 17:40:23-EST
From: Frank da Cruz <[e-mail]>
Subject: Macintosh Kermit 0.8(34) Available
Keywords: Mac Kermit

This is to announce Macintosh Kermit 0.8(34).  It includes the fixes that
were made to the system-independent parts of C-Kermit, announced recently,
plus the fixes to the VT102 emulation made by Davide Cervone of the
University of Rochester ([e-mail]), including:

. Blinking block cursor
. A new consistent VT100 font, including boldface & VT100 graphics characters
. Mouse-directed cursor movement with "arrow keys", a`la MacTerminal.

The new version has been tested with IBM 3270 full screen emulators, like
the 7171 running the Yale ASCII package, and with the Mac Plus.  Mac Kermit
seems to work satisfactorily as a full-fledged VT100, boldface included.

The protocol bugs with single-file interruption and packet padding have been
fixed.  The new files are in:

KER:CKMKER.HQX - Macintosh Kermit resource file, in BinHex V4 format.
KER:CKMKER.DOC - New manual chapter (Scribe source in KER:CKMKER.MSS).
KER:CKMKER.BWR - Known bugs & limitations
KER:CKMKER.UPD - List of changes since last release
KER:CKMFNT.HQX - VT100 font in BinHex V4 format
KER:CKMVT1.DOC - List of VT102 features supported and not supported

These files are available via anonymous FTP from CU20B on the Internet,
and via KERMSRV at CUVMA on BITNET, and should be available within a few
days via UUCP from host okstate.  Macintosh Kermit diskettes can also be
ordered for $10.00 each (prepaid) from

Kermit Distribution
Columbia University
Center for Computing Activities
612 West 115th Street
New York, NY  10025

The diskette includes the documentation in plain text format.  The old
version is still available in KO:CKM*.*.

------------------------------

Date: Tue, 25 Mar 86 14:03:48 EST
From: dstevens (David L Stevens) @ sitvxb
Subject: New KERMIT-10 Release
Keywords: Kermit-10

This is to announce the latest version of KERMIT-10.  The changes made are
documented in KER:K10133.MEM.  The KER:K10V3.RNO documentation is still valid.
Please note that you must rename K10MIT.HLP to KERMIT.HLP if you wish to
have KERMIT give you online help.  If there are any problems with this
release please let me know.

 David L. Stevens
 Stevens Institute of Technology
 DSTEVENS@SITVXB

[Ed. - All the Kermit-10 files are in KER:K11*.* and can be obtained via FTP
and KERMSRV (see previous message).]

------------------------------

Date: 21 Mar 1986 11:53:18 PST
From: Billy <[e-mail]>
Subject: Re: Supported Protocol Converters?
Keywords: Protocol Converters

This reader of INFO-IBMPC wants to send files from his PC to a 370 through a
protocol converter. I know there must be Kermits that do this, but don't
know enough to steer him to the right versions.  Is there an "out of the
box" solution to his problem?

[Ed. - The protocol converter must be the Series/1, 7171 or equivalent
running the Yale ASCII Communication Program.  If this user is not using a
supported protocol converter, he will need to use a line-mode TTY
connection.]

------------------------------

Date:     Mon, 31 Mar 86  20:15:38 EST
From:     RAF@NIHCU
Subject:  Datastream Protocol Converters?
Keywords: Protocol Converters

We are going to be getting some Datastream ASCII/3270 protocol converters.
I would like to find out if anyone has any experience using Kermit with such
devices and either MVS or CMS on the IBM 370.

Roger Fajman  <[e-mail]>
National Institutes of Health

[Ed. - Has anyone ever used the Datastream protocol converter?]

------------------------------

Date: Tue, 25 Mar 86 00:28:26 CST
From: Chet Murthy <[e-mail]>
Subject: Using Kermits With FASTLINK Modems?
Keywords: Modems

I have a pair of FASTLINK modems from DCA which support 9600 baud usage..
However, they use an adaptive duplex encoding method to basically avoid
errors completely.  This basically involves packetizing within the modem so
that errors are handled via retries, etc, in the modem.  This is really
nice, but it makes interactive use, and use for file transfer protocols a
real pain in the <expletive deleted>.  The big problem is that it takes a
while to turn the line around when you want to transmit an ACK.  I would
like to run KERMIT thru this modem, and take advantage of the higher
throughput possible with this modem.  There seem to be two possibilities:

    1) use windowing (sliding window protocol)
        This does not seem to be available at the present time.
    2) modify C-KERMIT to support the longer packet size.  This seemed
to be the way to go, and so I did this.  It worked, but there seem to be
more places in the code than I can find where the program uses the fact that
the maxpacksiz is 94.  I modified the #defines in ckcker.h, and recompiled
the whole thing.  I also modified the protocol to where it uses 2 characters
to encode the length.  All of this worked, and I got efficiencies of 87% on
a 1200 baud line thru a pair of Hayes modems.  However, the program seems to
be writing over some of the user interface keyword tables in the process of
running.  I can't seem to find any other places in the code where it could
be using an array, but I'm not sure.  If anyone knows of places in the code
where the packet size is assumed to be small, I would appreciate it if they
could notify me by mail ([e-mail] or [e-mail]).

In addition, if ANYONE has ANY information about using FASTLINK modems for
file transfer on UNIX, I would appreciate hearing from you.  I LOVE mail.

Thanks in advance,

Chet Murthy ([e-mail])

[Ed. - The next version of C-Kermit is expected to include both sliding
windows and long packets.  Release time is not known at this time however.
In the meantime, you can use FTP to GET the file KER:KPROTO.UPD describes
the conversion to long packets in great detail.]

------------------------------

End of Info-Kermit Digest
*************************
-------
 9-Apr-86 16:55:38-EST,24002;000000000000
Mail-From: SY.CHRISTINE created at  9-Apr-86 16:51:46
Date: Wed 9 Apr 86 16:51:46-EST
From: Christine M Gianone <[e-mail]>
Subject: Info-Kermit Digest V4 #22
To: [e-mail]
Reply-To: Info-Kermit@CU20B
Queries-To: Info-Kermit-Request@CU20B
Message-ID: <[e-mail]>

Info-Kermit Digest         Wed,  9 Apr 1986       Volume 4 : Number 22

Departments:

  ANNOUNCEMENTS -
    New Kermit-10, BITNET, etc
        Kermit-32 version 3.2.075
        New Release of Tandem Kermit
        Kermit for Apple II UCSD p-System
        Re: Apple Kermit (Pascal and CP/M)

  UNIX KERMIT -
        C-Kermit on HP Integral Problem Solved
        Installing 4C(58) on 2.9BSD
        Kermit and 4.xBSD rlogin
        C-Kermit 4C(58) on the Sequent BALANCE 8000
        Curious Observation re C-Kermit 4C(058)

  MACINTOSH KERMIT -
        MacKermint 0.8 (34) & Mac Plus
        New MacKermit Problems
        Mouse-Activated Cursor in Mackermit 0.8(34): HOW TO..

  MS-DOS KERMIT -
        MS-DOS Kermit and Zenith Z-158
        Problems with Kermit v2.28 jrd/5e

  MISCELLANY -
        Re: Kermit with FASTLINK modems
        C64 Kermit installation experience

----------------------------------------------------------------------

Date:     Wed 9 Apr 86 0:0:0
From:     Anonymous
Subject:  New Kermit-10, BITNET, etc
Keywords: Kermit-10, BITnet

The new DECSYSTEM-10 Kermit release announced in the last digest is in the
files KER:K10*.*, not KER:K11*.*, as stated.  Hope nobody took it seriously
(April Fool, ha ha).

Also, contrary to what it might say below, some of the new files announced
in this digest might not have made it to BITNET KERMSRV by the time you read
this, since we have been having some trouble with our CU20B-CUVMA link.

------------------------------

Date:     Tue, 8 Apr 86 14:17:05 EST
From:     rmcqueen (Robert C McQueen) @ sitvxb
Subject:  VAX/VMS Kermit-32 version 3.2.075
Keywords: VMS Kermit
Cross-Ref: VAX/VMS Kermit, VAX Kermit, Kermit-32 (see also VMS Kermit)

A maintenance/minor developmental release of Kermit-32 is now available.
Kermit-32 version 3.2 provides bug fixes for some of the known problems.

BEWARE:  Version 3.2 only runs on VAX/VMS version 4.0 or later.

The edits in this version include:

      o  Fixed processing of CRCs without 8-bit quoting.

      o  Fix various problems in the help file.

      o  Fixed problems with restoring of the terminal's <CR> and  <LF> fill
         counts.

      o  Fixed a problem  reading  files  with  FORTRAN  carriage  control.

      o  Changed the functionality of the  FINISH  command.   It  will  now
         return to the prompt level, and not exit to DCL.

Robert McQueen
Stevens Institute of Technology

[Ed. - The new files are in KER:VMS*.*, available via anonymous FTP from
CU20B, or via BITNET from KERMSRV at CUVMA.  KER:VMSMIT.HEX is the hexified
task file for the new version.  KER:VMSV31.HEX is the previous version,
which can be used with VMS version 3.]

------------------------------

Date: 27 Mar 1986 0319-EST
From: Tony Camas
Via: LCG.KERMIT@DEC-MARLBORO
Subject: New Release of Tandem Kermit
Keywords: Tandem Kermit

I've uploaded an updated version of the Tandem (yes Tandem) kermit server
as TANDEM.TAL.  It is intended as a replacement for current version.  This
version does three things the old version didn't:

(1) It adds an option, "NOBREAK", which can be of use on noisy lines.
(2) It supports kermit "I" packets, which evidentally did not exist when it
    was created.  This makes it talk to MS-Kermit v2.27 (previously it would
    only talk to v2.26 and before).
(3) It has a prettier banner with a version number, etc.

I've tested this pretty extensively (been working on a tandem project for
several months now) and it works fine.  It's quite possible that the
original author and I are the only people who've ever used this
implementation, but nevertheless, the one being distributed by Columbia
ought to work with current versions of PC kermits.

   Tony Camas
   [phone]

------------------------------

Date: Thu 13 Mar 86 13:24:01-EST
From: Ph. P. Visser, Rekencentrum der Rijksuniversiteit, Groningen, Netherlands
Subject: Kermit for Apple II UCSD p-System
Keywords: Apple II Kermit

Enclosed you will find two diskettes concerning a Kermit version for
Apple II (e) and (+).

The version is made by P. Terpstra of the Laboratory of Biochemics of the
State University of Groningen.  The version is written in UCSD Pascal.
It concerns Apple DOS 3.3 with several interface cards such as:
- Apple Communication Card (ACC)
- California CCS 7710 ASI Card (CCS)
- Hayes Micromodem Card (HMC)
- Apple Super Serial Card (SSC)
- IBM AP2 Serial Card (AP2)

It is a corrected version of the Stevens version.

[Ed. - Thank you, and thanks to Francis Wilson of Columbia Teachers College
for deciphering the disk for us, and to the many other people all over the
world who volunteered to do the same in response to our plea several issues
ago.  The files are in KER:UCA*.* on CU20B (Internet), and UCA* * on CUVMA
(BITNET).  But before you rush off to get this new version, read the
following message.]

------------------------------

Date: Tue 8 Apr 86 17:00:48-EST
From: Francis Wilson <CCIMS.WILSON@CUTC20>
Subject: Re: Apple Kermit (Pascal and CP/M)
Keywords: Apple II Kermit

After having no trouble in the morning using the Pascal Kermit as a terminal
emulator, I did not expect any (bad) surprises, but there were two.

1) The Apple 2e in the Micro Center at TC has a Videx ASIO card; this card
has the same 6551 ACIA as the Apple Super Serial Card, and uses the same
addresses; we have written (Apple CP/M) routines interchangeably for these
cards.  When I tried to use the program, the Kermit would not even change
the baud rate from 19,200, so I couldn't very well use a modem.

[Ed. - Maybe there's a way to set the baud rate outside Kermit, and then
have Kermit use the serial card as it finds it?]

2) On another Apple (with a real Super Serial Card), I tried file transfer
to a PC (unsuccessful) and via modem to a DEC mainframe (also unsuccessful);
in both cases, I successfully used terminal emulation immediately prior to
the attempted file transfer, so it was not a matter of bad connections.

[Ed. - Maybe it's something with parity, and SET PARITY ODD (or whatever)
will make it work.]

In other words, I have followed the instructions as best I can, but I am
not able to make the Kermit program work.  It emulates a (glass) terminal
ok, but does not transfer files.

To make matters worse, for others who want to try do a better job, from
looking at the documentation, specifically, the third documentation file,
it seems that there are files needed to assemble a working version that are
not included in source form (see the .DOC file).


[Ed. - If anyone out there has better luck, let us know!  The address of
the contributors (in Holland) is in the documentation, and they have offered
to provide diskettes.]

------------------------------

Date: Sun 6 Apr 86 11:40:15-EST
From: [e-mail]
Subject: C-Kermit on HP Integral Problem Solved
Keywords: C-Kermit, HP Integral Kermit

        This is part 3 in the ongoing saga of an incompatibility between
C-Kermit (now (057)) and csh when a HP Integral is running the SVR2 ROMs.

        The reason for the C-Kermit crashing when an attempt is made to
escape back to local control has been found.  When C-Kermit connects to tty
it needs to generate a child process (why I don't know).  On the HP Integral
with the new operating system ROMs, the fork to generate the child process
always fails if csh is running, either in the active window or any other
window.  The pid returned by this failed fork is -1.  When escape to local
control is attempted, C-Kermit sends out a kill(-9) to the child process.
Since the pid is -1, the effect of this kill is to kill ALL processes except
0 (the kernel) and 1 (init).

        I think that this is a possible bug in C-Kermit, the not checking
for a failed fork after a child process is created.  Granted it is not
very likely that this situation will occur, but if it did happen on a
system where there are a large number of users it could be quite harmful.
For now the only fix that I have is that people running C-Kermit on
HP Integral's with the new ROMs, is that they do not have csh running
anywhere on that machine when C-Kermit is going to be used.

                                                Gordon Haverland
                                                Box 596
                                                Dawson Creek, B.C.
                                                V1G 4H5
[e-mail]                              Canada

[Ed. - Thanks for finding the problem.  It will be fixed in the next
release.  Meanwhile, those who find their systems unable to create forks
can change the file ckucon.c to check if the pid returned by the fork()
invocation is -1, and if so, to report failure and return.]

------------------------------

From: Vic Abell <[e-mail]>
Date:  8 Apr 1986 1519-EST (Tuesday)
Subject: Installing 4C(58) on 2.9BSD
Keywords: C-Kermit

The standard 2.9BSD distribution and some of the redistributions of 2.9BSD
accomplish 4.2BSD directory compatibility with simulation that is based on
the header file "ndir.h" and the library "libndir".  The current C kermit
distribution, 4C(58), does not follow those conventions.  Of course, one must
also add -lndir to some make rule.  Since we don't use the distributed
Makefile, I am omitting diffs for it and leaving that exercise to the
interested reader's imagination.

As always, I am grateful to Columbia for their efforts with Kermit.

Vic Abell
Purdue University Computing Center
[e-mail]
...!pur-ee!pucc-j!abe

[Ed. - In some cases, it's true that ndir.h should be used.  In others, it's
dir.h.  In either case, the library reference should be made in the makefile
(and it is).  If your 2.9BSD system uses ndir.h rather than dir.h, then in
ckufio.c, the section

> #ifdef        BSD29
> #include <ndir.h>

should be changed to refer to <ndir.h>, or possibly <sys/ndir.h>.  Let's
hear it for consistency.  A warning has been put in the makefile about this.]

------------------------------

Date:  9 Apr 1986 1105-EST (Wednesday)
From: Vic Abell <[e-mail]>
Subject: Kermit and 4.xBSD rlogin
Keywords: C-Kermit

There is an undocumented option on the 4.xBSD rlogin call that must
be used when C Kermit is at the end of a TCP/IP rlogin connection.
The option is "-8" and should be used in the following fashion:

        % rlogin hostname -8
        % kermit

Vic Abell, Purdue University Computing Center
[e-mail], ...!pur-ee!pucc-j!abe

------------------------------

Date:  8 Apr 1986 1935-EST (Tuesday)
From: Vic Abell <[e-mail]>
Subject: C Kermit 4C(58) on the Sequent BALANCE 8000
Keywords: C-Kermit, Balance 8000

I just finished installing C Kermit 4C(58) on the Sequent BALANCE 8000.
It transported without modification, compiled under the -DBSD4 option,
and functions correctly.  I am really impressed with the quality of the
4C(58) release and the ease with which 4.2BSD software can be transported
to the BALANCE 8000.

My compliments to Columbia and Sequent for jobs well done.

Vic Abell, Purdue University Computing Center
[e-mail], ...!pur-ee!pucc-j!abe

------------------------------

Date:     Mon, 7 Apr 86 21:06 EST
From:     [e-mail]
Subject:  Curious observation re C-Kermit 4C(058)
Keywords: C-Kermit

Well, the new Kermit survived its testing period, and as I was installing it
today as our new production version, I noticed that 4C(057)'s executable
image was 168K bytes, while 4C(058)'s image was only 128K bytes.  Both
versions were compiled on the same compiler and the same system, an NCR
Tower running Tower OS version 2.01.  (Both versions were put together
with a "make sys3" command.)

Any idea where the 40K went?

                                        -- Larry Afrin
                                           Dept. of Computer Science
                                           Clemson University

[From Frank - Beats me!  I think I might have made some buffers a little
smaller in some versions, but not 40K worth.  On VAX 4.2BSD, the old and new
versions come out exactly the same size.  On PDP-11 versions, particulary
2.9BSD, some buffer sizes (like for filename expansion) had to be reduced.]

------------------------------

Date: Tue, 1 Apr 1986 16:01 EST
From: Dave Elbon  <[e-mail]>
Subject: MacKermint 0.8 (34) & Mac Plus
Keywords: Mac Kermit

MacKermit (and the keyboard configuration program) don't recognize the
cursor keys and the Enter and Clear keys on the Mac Plus.  I also can't
get the mouse to move the cursor.  Any ideas?  Wait for the next release?

[Ed. - Anybody out there with a Mac Plus to check this on?  Maybe it's
just that the configurator program doesn't know the layout of the new
keyboard, so it works in this case like it does with the keypad -- you can't
see it, but you can still set it.  Anyone want to try this approach and
report back?]

------------------------------

Date: Thu 3 Apr 86 00:42:15-EST
From: Subba Shankar <[e-mail]>
Subject: New MacKermit Problems
Keywords: Mac Kermit

        I recently downloaded the new MacKermit from CU20B with my old
MacKermit, ran Binhex v4 on it, and happily telecommunicated away.
While I find the new font and the terminal emulation features to be a
great improvement, I have found some problems.  MacKermit causes the
system error message with the restart button enabled to be shown
whenever I try to call up the Control Panel Desk Accessory, and the
Transfer to Application menu option causes the Mac to hang.  This is
highly reproducible.

[Ed. -- Hmmm... not by us!  Maybe you have some other programs loaded
(in Switcher, maybe?) that figure into this somehow?  Anybody else out
there seen a problem like this?]

------------------------------

Date:  8 Apr 1986 1949-EST (Tuesday)
From: Vic Abell <[e-mail]>
Subject: Mouse-Activated Cursor in Mackermit 0.8(34): HOW TO..
Keywords: Mac Kermit

The mouse-activated cursor code in Mackermit 0.8(34) is a welcome addition.
I had a little trouble getting it to work, so I am sending this hint to help
others with it.  Here are the steps needed to activate it:

1. Create a settings file.
2. Edit the settings file with CKMKEY.
3. Define the following functions:
        100: \033[A
        101: \033[B
        102: \033[D             (yes, 'D' is correct!)
        103: \033[C             (yes, 'C' is correct!)

To use the mouse-activated cursor from within Mackermit, move the arrow to
the place to which you want to move the cursor; hold down the option and
cloverleaf keys together (the cursor should change to an open box around
the target character); and press the mouse button.  You can press the
option and cloverleaf keys before you move the open box cursor, if you want.

Vic Abell, Purdue University Computing Center
[e-mail], ...!pur-ee!pucc-j!abe

[Ed. - Thanks!  Also, the program comes with a VT100-keypad startup file,
which starts up Mac Kermit for you with the keys configured for you this way
when you double-click on it.  It's in KER:CKMVT1.HQX.  Unfortunately, we
forgot to include it with the other files when the new version was first
announced.  It's there now.  Sorry!]

------------------------------

Date: Wed, 2 Apr 86 00:49:54 EST
From: [e-mail]
Subject: MS-DOS Kermit and Zenith Z-158
Keywords: MS-DOS Kermit, Zenith

I've been having problems with kermit/jrd v.2 and 5e on a Zenith Z-158 with
Hayes 1200B (board) modem. Whenever I escape to local kermit, the connection
is dropped from my end. I have tried connecting to different hosts a Z-150
with a 1200B, and neither has worked. Jrd/2 works fine on a freestanding
modem though, I've heard. It also works fine on a hardwired port at 9600
bps.

The connection problem also happens when I transfer files to the host, at
around the moment when the status screen appears at the local station.

[From JRD: I tried and tried to get this to happen with a real Hayes 1200B
in a Columbia portable and the darned thing just kept working fine. Guessing
time on Hayes switches.  Kermit works 100% on my Hayes 2400 external modem
and I pump maybe 0.5 Mb per day through that combination with never a
problem. My computer is a Zenith 151 too. The 2400 has no switches,
everything is in software, and I tried many combinations to make Kermit drop
DTR. Finally, I wrote a new Kermit command, HANGUP, to save testing time.
Try those switches.  Further thought on the matter, but not much further.
When Kermit is not using the serial port it returns the previous interrupt
address to the UART to leave things tidy. DTR and RTS are left high (on).
Could it be that code at that previous address was reacting to the modem and
dropping DTR? Put another way, could the Hayes 1200B implementation of a
UART and modem adversely react to a change of interrupt address; hardware
troops make those kinds of boo boo's.]

------------------------------

Date:     Fri, 4 Apr 86 11:43:53 EST
From:     Dave Swindell <[e-mail]>
Subject:  Problems with Kermit v2.28 jrd/5e
Keywords: MS-DOS Kermit

I have been using MS-Kermit version 2.28 jrd/5e on and off for the
past few weeks and have observed a few possible bugs.  The first one
is that the local buffering of one's session doesn't seem to work
correctly.  When I try to scroll back through my session (by using the
pg up key), I get a very strange display composed of IBM graphics
characters.  The second problem I noted occured while I was
transmitting a text file from a "functioning" Kermit-10 to my pc.  The
transfer proceded normally, but when I edited the transmitted file, I
noticed several imbedded control-m characters interspurced in the file
which did not appear in the original file.

On the plus side, the VT100 emulation looks real good!  I've tried
running several full screen editors that support the VT100 using
Kermit with great success.  The support for video attributes and the
AVO character set all work nicely.  I also like being able to use the
IBM (or in my case Leading Edge) cursor keys as VT100 cursor keys.  I
have used the new version of kermit both at 1200 and 9600 baud with
sucess, outher than the problems noted above.

[From JRD: Several people with Leading Edge machines report video
difficulties when scrolling back the Connect mode screen.  The model M at
least has a dip switch selecting L.E. Enhanced video or regular.  A friend
had similar video garbage until he switched the machine from unleaded to
regular.]

As a final question, when do you anticipate that sliding window
support will be incorporated into the "production" version of IBM
Kermit?  I've tried to use WKermit over Telenet, but have not had
success.  WKermit seems to get confused when displaying the Telenet
prompts; graphics characters are interspurced into the display.  My
guess is that Telenet is setting the eighth bit of some or all of its
prompt characters to high, and that this is confusing WKermit.

[Ed. - It'll be a while before sliding windows gets into C-Kermit,
maybe a few months.  Meanwhile, you should be able to use WKermit over
Telenet by doing SET PARITY MARK.  Works fine for us.]

Thanks for all your work,

Dave Swindell
BBN Laboratories Incorporated

------------------------------

Date: Tue, 8 Apr 86 21:51:59 pst
From: Gary Mills <[e-mail]>
Subject: Re: Kermit with FASTLINK modems
Keywords: Modems

I have no experience with FASTLINK or any other error-correcting modems,
but there does seem to be a trend to shifting parts of the communication
protocol to hardware.  I use Kermit with 212A modems over switched lines
with variable amounts of noise, and it does perform very nicely, and gets
my files from one machine to another.  However, it seems to me that if a
pair of sophisticated modems are providing error-free transmission, that
Kermit does not need to be used at all.  You should be able to just
"copy" the file from one machine to the other.  Of course, it's unlikely
that normal system commands would do this.  Also, the Kermit user
interface is quite attractive.  Maybe some variation of Kermit with
relaxed error-checking could be used in this instance.  It would also
likely be useful for hard-wired connections.

[Ed. - Maybe this will happen some day.  YMODEM already has such an option.
You still have to be a bit cautious about errors that slip in between the
modem and the computer (wiggly cables, buffer overruns, etc).  But it may
turn out that removing Kermit's errror checking wouldn't speed things up
much anyway, since the bottleneck in many of these modems relates to line
turnaround, in which case only long packets or sliding windows will help.]

------------------------------

Date: Wed, 26 Mar 86 15:07:24 cet
From:  [e-mail]
Subject: C64 Kermit installation experience
Keywords: Commodore 64 Kermit
Cross-Ref: C-64, Commodore 64, (see also Commodore 64 Kermit)

Can you please take note and forward to the authors of C64 Kermit?  I've
just generated version 1.6(49) of C64 Kermit and have some remarks:

1) The kludge factor you use for 1200 bauds is valid only for U. S.  machines
(NTSC). So called International machines (PAL) have other requirements.
Assuming the correction is subtracting 10 decimal from CBM values, this
yields the following values:

1200: 301=$012D
1800: 164=$00A4
2400:  95=$005F
1200 and 1800 bauds have successfully been tested with these values,
but 2400 bauds resisted file transfer.

Also you might include the kluge factor in each speed definition to make all
high speed available through the SET BAUD command.

2) You plan using the serial bus for disk access (TALK ...). I would
strongly advise you against that. Some drives interface cartridges work by
re-vectoring the high level access interface (CHROUT ...) and using their
own low level bus for disk parallel access. You would miss those busses.
Also better not restore the vectors! If your complaint is speed, I'd
recommend to transfer disk data by chunks of say 16 bytes to minimize the
talk-untalk overhead.

3) The DISK command refused service. Patching the module to store a
carriage-return (not a null) at the end of the buffer in routine DOSPRS,
puts things right.

4) The last SET values byte is not correctly SAVEd/RESTOREd.  CPY
#QUOTE+1-ESCP should be +2 or better some equated SETSLEN.

5) If you consider wildcard sends valuable, may I suggest the following
solution. A) open a drive input file whose name is
$:user-specifiled-file-pattern (a la CBM DOS), and secondary address 0.

B) Read this file (BASIC format like) using the following algorithm,
   extracted from COMforth, a wonderful Forth development system
   available here in Belgium.
   Skip 2 bytes.

   BEGIN
     Read 2 bytes, OR <> WHILE ( not double null )
     Skip 2 bytes ( containing file blocks count )
     BEGIN Skip 1 byte ASCII " = UNTIL
     BEGIN Read 1 byte, ASCII " <> WHILE
       copy it to filename buffer
     REPEAT
     BEGIN Skip 1 byte null = UNTIL
     not first block IF ( not drive name )
       Use filename to drive file transfer
     ENDIF
   REPEAT

C) Close file.
Never buy what you can steal. (They say).

I hope to have contributed to a work of patience to which we are heartfully
grateful.
                                        A. Pirard
                                        SEGI
                                        Universite de Liege
                                        15, avenue des Tilleuls
                                        4000 Liege

------------------------------

End of Info-Kermit Digest
*************************
-------
11-Apr-86 12:07:01-EST,13807;000000000000
Mail-From: SY.CHRISTINE created at 11-Apr-86 12:05:30
Date: Fri 11 Apr 86 12:05:30-EST
From: Christine M Gianone <[e-mail]>
Subject: Info-Kermit Digest V4 #23
To: [e-mail]
Reply-To: Info-Kermit@CU20B
Queries-To: Info-Kermit-Request@CU20B
Message-ID: <[e-mail]>

Info-Kermit Digest         Fri, 11 Apr 1986       Volume 4 : Number 23

Departments:

  ANNOUNCEMENTS -
        Many New Kermit Versions from the UK
        Kermit for Sperry 90/60 with VS9 from WPI

  MISCELLANY -
        Setting Kermit-32 Up As A Server
        Kermit-11 Known Problems Update
        Kermit v2.28 jrd/5e on the Leading Edge Model D
        Modems and Error Correction, etc.
        New Source for OS9 and Tandy CoCo Kermit Diskettes
        File Renaming Problem in C-Kermit?

----------------------------------------------------------------------

Date: Thu 10 Apr 86 18:23:01-EST
From: Christine M Gianone <[e-mail]>
Subject: Many New Kermit Versions from the UK
Keywords: England Kermits

This is to announce new Kermit versions submitted by Alan Phillips of
Lancaster University, UK.  The files are described by him as follows.
Each group is indicated by the wildcard file specification that will fetch
the files via FTP or NFT from CU20B, except they should be preceded by KER:.
On BITNET, they may be fetched from KERMSRV at CUVMA with the names
indicated (without the KER:, but also without the dot).

BBC*.*
        These files are version 1.30 of Kermit for the Acorn BBC Micro.  Old
files have been replaced.  BBC130.ANN contains the announcement details.
There are 2 HEX files for this version, covering disc based and EPROM based
variants.  The .ADE file contains a concatenation of the individual source
files.

C86XFU.*
        These files are the Kermit-86 for the Future FX20/FX30 machines sent
in by Toby Chabot of Birmingham University.  The code will run under either
CP/M-86 or Concurrent CP/M-86.

C86XR2.*
        These files are a variant of the existing Kermit-86 for the DEC
Rainbow, sent in by Mark Woollard of the Animal and Grassland Research
Institute.  A SET BAUD command has been added.

CKMKB*.*
        These files are two separate UK keyboard settings files for the
Macintosh.  CKMKBD.* is from Sak Wathanasin of Sussex University; CKMKB2.*
is from Phil Jimmieson of Liverpool University.  The latter set of files
includes an introductory guide to Mac Kermit 0.8(33) in MacWrite format.

CN8*.*
        These files form a Concurrent CP/M-86 implementation for the
Honeywell Multi System Executive and clones (Argos Pro PC, Daisy PCi, Fallon
2000, FTS PCi, and Orion PCi) sent in by Mark Hewitt of Birmingham
University.  This set is based on the existing Kermit-86, with a new device
dependent file and a lot of changes to the UTL file.  The version uses
the PRO, FIL, TRM, and CMD files from Kermit-86 unchanged.

CP4*.*
        Kermit-80 implementations:

CP4380.HEX      Research Machines RM 380Z
CP4ADV.HEX      North Star Advantage
CP4APC.HEX      Apple II with Z80 Softcard/CPS serial card
CP4BBC.HEX      Acorn BBC Micro with Z80 second processor
CP4BRA.HEX      Superbrain, using auxialiary port
CP4BRM.HEX      Superbrain, using main port
CP4COM.HEX      Comart Communicator
CP4CIF.HEX      Cifer 1886
CP4CRO.HEX      Cromemco
CP4HOR.HEX      North Star Horizen without SIO board
CP4TOR.HEX      Torch series

        The CP4SYS.ASM and CP4TYP.ASM files contain all the system dependent
code for the above versions.  Authorship of the versions is as follows:

380, APC, BBC, ADV      Brian Robertson, Aberdeen University
CRO, HOR, COM           Andrew Cole, Leeds University
BRA, BRM, TOR, CIF      Bertil Schou of Loughborough University

        Bertil Schou of Loughborough performed the Herculean task of
co-ordinating the developments and putting the results together into the SYS
and TYP files.  Some further implementations are on the way.

GECKER.*
        These files are version 2.1 of Kermit for the GEC 4000 series from
Martin Loach of Rutherford Appleton Laboratories.  These replace the old
GEC*.* files.

MDS*.*
        These files are some updates and fixes to the MDS set for Intel MDS,
sent in by Paul O'Hare of the Open University.  Bugs have been fixed and the
documentation has been expanded.  The other files for this version are
unchanged.

CUC*.*
        These files are the latest versions of a C-Kermit from Chris
Kennington, University College London.  Based on the original Kermit of the
protocol manual, the code has been adapted to be extremely portable with
little work needed.  The diagnostic facilities have been expanded
considerably too.  File CUCLKV5.C is a system dependent module for UNIX
system V, added by Icarus Sparry of Bath University.

UCJ*.*
        These files from Henry Balen of Lancaster University, are an
adaptation of the Terak UCSD p-System Kermit for the Joyce Loebl Magiscan 2
image processor.  8th bit prefixing has been added and a number of other
features.  The result should be easily ported onto other UCSD systems.  The
.TXT file contains a concatenation of the sources.

UMKERMIT.*
        These files are a version of the original Kermit in the Protocol
Manual for a U-Microcomputers U-MAN 1000 under CP/M-68k.  The files are
contributed by Icarus Sparry of Bath University.  Work on this version is
still in progress, so currently the implementation is not perfect and is
supplied very much on an "as is" basis.  Icarus would welcome contact from
anyone interested in this implementation and will co-ordinate any
developments:  his UK network address is [e-mail]63.

[Ed. - Many thanks to Alan for these versions, and for his dedicated work
in coordinating the Kermit goings-on of the UK, and for distributing Kermit
on UK networks, and on diskettes and tapes in the UK.]

------------------------------

Date: Wed 9 Apr 86 17:24:45-EST
From: Frank da Cruz <[e-mail]>
Subject: Kermit for Sperry 90/60 with VS9 from WPI
Keywords: Sperry

SP9KER is Kermit for the Sperry 90/60, written by Ben Thompson of
Worcester Polytechnic Institute, Worcester, MA.

The program only runs as a server since the SPERRY 90/60 can not initiate use
of an RTIO line other than the terminal line itself.  It accepts no interactive
commands, just escape to to your computer's command mode and initiate a
command.  Implemented commands are: GET, SEND, and BYE.

KER:SP9KER.SRC is the IBM-like assembler source file, KER:SP9KER.DOC is the
documentation.

Thanks to Al Johannesen for submitting the program.

------------------------------

Date: Thu, 10 Apr 86 20:38:59 EST
From: rmcqueen (Robert C McQueen) @ sitvxa
Subject: Setting Kermit-32 Up As A Server
Keywords: Kermit-32

Kermit-32 can be set up as a server in the following manner:

$ KERMSRV := $SYS$SYSTEM:KERMIT SERVER

Then just issue the KERMSERV command.  Kermit-32 will accept any legal
Kermit command in this manner.  You could just define a KERMIT command
in your LOGIN.COM file and then give a DCL command of the format:

$ KERMIT command

Which will cause Kermit-32 to be invoked and the command processed.

Kermit-32 has had initialization file processing and a TAKE command since
version 3.1.  When Kermit-32 starts it will automatically process
VMSKERMIT.INI;0 or if that does not exist it will process the file that the
logical name VMSKERMIT points to.  If you have a command procedure that you
would like Kermit-32 execute you can give either the TAKE command followed
by the file specification or "@" followed by the specification.

Robert McQueen
Stevens Institute of Technology

[Ed. - Thanks, Bob!  We'll add this hint to the beware file, too.]

------------------------------

Date: Mon, 7 Apr 86 12:57 EST
From: <[e-mail]> (brian nelson)
Subject: Kermit-11 Known Problems Update
Keywords: Kermit-11
Cross-Ref: K-11, PDP-11 Kermit (see also Kermit-11)

On RT11 FB systems with a large number of devices, Kermit can displace the
USR (force it to swap) and crash when accessing the USR from the higher
addressed overlays in Kermit. The fix for something like this may not be
practical; it can be worked around by UNLOADING and REMOVING unneeded device
drivers from lowest address to higher addresses (to prevent fragmentation of
background memory). If you run K11RT4.SAV on a FB system and find either (1)
The program crashes on file transfers or (2) KMON says the save image is too
large, then remove the unneeded drivers and set the USR to swap.

------------------------------

Date:     Thu, 10 Apr 86 21:31:36 EST
From:     Dave Swindell <[e-mail]>
Subject:  Kermit v2.28 jrd/5e on the Leading Edge Model D
Keywords: MS-DOS Kermit, Leading Edge

In the last digest, I reported a problem scrolling back through displayed
text using Kermit V2.28 jrd/5e on my Leading Edge Model D.  As it turns out,
Kermit appears to work just fine; the problem appears to be due to some kind
of interaction between the new Kermit and a resident program named INT10
used in conjunction with the Hercules graphics card (and clones!).  When I
install INT10 on my LE, I can't use the scrolling features in the new
Kermit.  When this program is removed, things work fine.  In that INT10, as
its name implies, affects interrupt processing, I assume that it some how
gets in the way of the mechanism jrd/5e uses to scroll through displayed
text.

Other than this problem, I have had no other display-oriented problems using
the new release on my LE model D.  The model D comes complete with two
graphics adaptors on the motherboard; a monochrome/Hercules port and a
standard IBM CGA port.  I have tried jrd/5e using both ports (at different
times!) and have had no problems (once INT10 was removed).

Sorry I didn't think to remove the memory resident programs I was using
before I reported the problem!  By the way, I am using NANSI.SYS as my
console driver on the LE.  It does not appear to interfere with Kermit.

Dave Swindell
BBN Laboratories Incorporated

------------------------------

Date: Thu, 10-Apr-86 10:54:14 PST
From: vortex![e-mail] (Lauren Weinstein)
Subject: Modems and Error Correction, etc.
Keywords: Modems

It is a fallacy to assume that when error correcting modems are in place you
don't need error detection/correction in the software.  In practice, not
only do noise errors creep in between the modems and the computers, but the
problems of buffer overflow and flow control related errors, on both sides,
can be quite serious, particularly at "higher" speeds.

In my own experiments with various software, I've found that removing or
even relaxing the per-packet error checking characteristics of software when
using error-correcting modems generally does little or nothing to increase
throughput, and in fact you frequently end up with decreased throughput
since flow control problems (and the resulting need to resend large
quantities of data) can be intense on even slightly noisy phone lines or
when dealing with even moderately loaded systems.

--Lauren--

------------------------------

Date:  Thu Apr 10 09:57:06 EST 1986
From: dolqci!irs3!scsnet![e-mail]
Subject: New Source for OS9 and Tandy CoCo Kermit Diskettes
Keywords: Os9 Kermit, Tandy Kermit

This is to announce that disks containing the Tandy/Radio Shack RS-DOS
kermit and os9 kermit can be obtained by sending $5.00 for
each version to:

  Mark E. Sunderlin
  1430 Greystone Terrace
  Winchster, Va. 22601

The RS-DOS version is provided on standard RS-DOS format. The os9 version
is provided on either 35 or 40 track CoCo os9 format.  Please state which
versions you want and for os9, what format.

Each disk contains complete source as up to date as possible, currently
RS-DOS kermit version 1.1 and os9 version 1.6.  Also on each disk is the
full documentation.  Binaries will be placed on the disks on request.

The RS-DOS verson in in EDTASM+ assembler, but EDTASM+ is not needed to
create a binary as BASIC program is provided to generate the binary.  The
os9 version in written in Microware 'C'.  An 'S' record file for os9 level I
will be placed on the disk on request for those who do not have the 'C'
compiler.

Please note that this is a PRIVATE project and is in no way related to the
IRS or any other government agency.

------------------------------

Date: 6 Apr 1986 0306-EST
From: [e-mail]
Subject: File Renaming Problem in C-Kermit?
Keywords: C-Kermit

I have discovered a problem when sending files from a BSD 4.2 system
to a V7 system with both machines running C-Kermit version 4C(057).

The file names on the BSD system were greater than 14 characters and the
first 14 characters of several of the file names were the same.

The BSD Kermit was running in server mode and was set for literal file names.
The V7 Kermit was set for literal file names and file warning on.

The first file came over ok, but when the second file came over, Kermit
discovered that the file existed and renamed it by replacing the end of
the file name with ~1.  The new file name was still longer than 14 characters
and the new file clobbered the previous file!

Was this fixed in version 4C(058)?  Should Kermit check for the existence of
the altered file name before doing the create?

[Ed. - If the behavior you report is true, the cause isn't obvious.  The
"make-new-name" function, znewn(), chops the last 3 characters off the name
before adding the "~1" suffix.  In any case, the behavior wasn't changed in
edit 058.  We'll look into in more detail later.  For now, your message has
been added to the beware file.]

------------------------------

End of Info-Kermit Digest
*************************
-------
15-Apr-86 18:07:03-EST,8308;000000000000
Mail-From: SY.CHRISTINE created at 15-Apr-86 18:06:18
Date: Tue 15 Apr 86 18:06:18-EST
From: Christine M Gianone <[e-mail]>
Subject: Info-Kermit Digest V4 #24
To: [e-mail]
Reply-To: Info-Kermit@CU20B
Queries-To: Info-Kermit-Request@CU20B
Message-ID: <[e-mail]>

Info-Kermit Digest         Tue, 15 Apr 1986       Volume 4 : Number 24

Departments:

  ANNOUNCEMENTS -
    MS-DOS Kermit 2.29 Is Even Closer To Being Ready
    New Release of TRS-80 Model 4 Kermit

  MISCELLANY -
    Sending Break on Mac+ from Kermit (several messages)
    DEC-10 Kermit Files

----------------------------------------------------------------------

Date: Tue 15 Apr 86 14:25:17-EST
From: Frank da Cruz <[e-mail]>
Subject: MS-DOS Kermit 2.29 Is Even Closer To Being Ready
Keywords: MS-DOS Kermit

Joe Doupnik's latest prerelease of MS-DOS Kermit 2.29 is available for
evaluation.  It is called "2.28 jrd/5g 13 April 85".  It has been tested by
us on the IBM PC family and compatibles (not including the new PC
Convertible, which is probably NOT compatible), the DEC Rainbow, and the
HP-150, and by Ron Blanford at the University of Washington on the NEC APC,
and also on the Intel RMX system by Jack Bryans at Cal State.

Aside from fixes for the bugs that have been reported in earlier
prereleases, 5g includes dynamic memory sizing in the IBM PC version -- it
uses whatever memory is available for scrolling memory, rather than
requiring that a certain amount be available, so that it can fit in smaller
memories, like on the PCjr (does anyone have a real PCjr to test this on?).
It also has a new screen-dump feature (again, on the IBM version only),
activated by <esc-char>F.  In case you have missed earlier postings about
this new release, it also incorporates nearly complete VT102 terminal
emulation for the IBM PC family, and full DOS 2.0 compatibility (a full
DOS path can be used in any file specification).

The .BOO file for the IBM version is available on CU20B via anonymous FTP as
KER:MSJRD5G.BOO, and it is also available on BITnet from KERMSRV as CUVMA as
MSJRD5G BOO.  The other versions are available on CU20B only, via FTP, in
the directory <KERMIT-MS>.  BOO files have been built for the Rainbow
(MSVRB1.BOO) and the HP-150 (MSVHP1.BOO).  The <KERMIT-MS> directory also
contains 8-bit binary .EXE files for these versions.  The new documentation
is not ready yet, but use of "?" in commands will produce menus whenever
needed.

The operation of the new version on the other IBM-PC-Incompatibles supported
by previous releases of MS-DOS Kermit has not been tested; these include:

 MSVAP3  NEC APC 3
 MSVAPR  ACT Apricot
 MSVDM2  DECmate-II or III with MS-DOS option
 MSVEZP  Z100 with EZPC board
 MSVHPX  HP 110, Portable
 MSVM24  Olivetti M24
 MSVMBC  Sanyo MBC
 MSVTIP  Texas Instruments Professional
 MSVV90  Victor 9000/Sirius 1
 MSVWNG  Wang PC
 MSVZ10  Z100

If you have one of these PCs, and can make an FTP or DECnet connection to
CU20B, or you are directly on BITnet, and you're willing to try out the new
release on your system, please send a note to Info-Kermit-Request (or simply
Kermit) at CU20B, and we'll get the necessary files to you.  You should be
able to mail directly to CU20B from both the Internet and BITnet.  Those
versions that have not been tested within the next week or two will be
distributed with the old .BOO files until positive reports are received.

P.S. The network and disk problems that have prevented us from updating the
Kermit collection on BITnet have been fixed, and KERMSRV at CUVMA is again
up to date.

------------------------------

Date: Mon 14 Apr 86 17:28:04-EST
From: Frank da Cruz <[e-mail]>
Subject: New Release of TRS-80 Model 4 Kermit
Keywords: TRS Kermit

Announcing TRS-80 Model 4(p) KERMIT version 5.0 for TRSDOS 6.x, from Gregg
Wonderly at the Oklahoma State University Department of Computing and
Information Sciences.

This is an advanced Kermit derived from TRS-80 Kermit, which was in turn
derived from CP/M-80 Kermit.  Several new features were added since version
4.0 (March 85), including Remote Server Commands, and lots of cleaning up
and rewriting.

The files are in KER:M4*.*, including source in KER:M4*.ASM, and:

M4MIT.HEX -- Hexified object module
M4MIT.NR  -- Nroff source for M4MIT.DOC
M4MIT.DOC -- Documentation
M4MIT.HLP -- This file
M4BOO.BAS -- Basic program for converting the hex file to a runnable program

------------------------------

Date:  Sun, 13 Apr 86 01:36 MST
From: Barry Margolin <[e-mail]>
Subject:  Sending Break on Mac+ from Kermit
Keywords: Mac Kermit

What do I have to do to Macintosh Kermit 0.8(33) (I'll be upgrading to
0.8(34) soon, if that helps) so that I can send a break.  The Mac+ does not
have an Enter key next to the Space bar, and the keypad's Enter key sends a
Line Feed.

On a related topic, it would be nice if someone would update KermKey so that
it detects whether it is being used on a Mac+, and display correct keyboard
layout.
                                        barmar

[Ed. - See following messages.]

------------------------------

Date:     Mon, 14 Apr 86 16:49 EST
From:     (Davide P. Cervone, User Services Consultan ...) <[e-mail]>
Subject:  Break key for MacKermit
Keywords: Mac Kermit

I don't have a Mac+ to try this on, but on a Mac, if you bind F126 or F127
to any key, that key will send a "break".  F127 is a longer break than F126
(in version .8(34) the cursor should stop flashing for a few seconds).

About the Kermit keyboard reconfigure program, I agree that it would be nice to
be able to detect the different keyboards.  It would also be nice to have a
keypad diagram.  I'm not sure whether it is possible to detect which kind of
keyboard/keypad configuration is being used however.

                                        Davide P. Cervone

------------------------------

Date: Mon 14 Apr 86 15:39:27-EST
From: Robert Cartolano <[e-mail]>
Subject: Re: Sending Break on Mac+ from Kermit
Keywords: Mac Kemrit

For now, you may still use the CKMKEY 0.8 (6) to configure the Mac Plus
keyboard.  I have done it myself.  The function F126 has been defined as the
break, and you can define it as the enter on the older Macs with no problem.
For the Mac Plus, do the following:

    - Run CKMKEY 0.8 (6), and open a file.
    - Select KEYS... from the SET menu.
    - Press the Enter key on the Mac Plus keyboard.
    - Insert the cursor into the keyboard map number, and
      type 126.
    - Click on the SET FUNCTION KEY button.
    - Quit and Save.

I have been able to configure every key on the MacPlus keyboard, including
the cursor keys, in this manner.  You just have to make sure you are hitting
the right key, since you can't see the key on the screen.

Rob Cartolano
CUCCA User Services.

------------------------------

Date: Mon, 14 Apr 86 10:25:58 est
From: Mike Ciaraldi  <[e-mail]>
Subject: DEC-10 Kermit Files
Keywords: DEC-10 Kermit
Cross-Ref: DECsystem-10 (see also DEC-10 Kermit)

I tried to access DEC-10 Kermit over the Arpanet today.  There was no "DOC"
file.  All the "MAC" and "BLI" files, which I assume are the source code in
Macro and Bliss, are messed up.  I tried to get them in ASCII mode, and was
told they are not 7-bit files.  I then tried to transfer them in Tenex mode,
and got something that wasn't human-readable.  The only ASCII file I could
find was the "MEM" file, which was a list of patches.

Is this a mistake, or is DEC-10 Kermit being retired or updated?

I need to bring Kermit up on a DEC-10.  Can I use the DEC-20 version
instead?  I checked the 20 documentation, and it doesn't say it will run on
the 10.

Thanks for any help you can give me.

Mike Ciaraldi
University of Rochester
ciaraldi@rochester

[From Frank - Whoops, you're right.  In fact, the files were stored in a
strange way, that was perfectly OK for our system, but that confused our FTP
server.  I've changed the bytesize from 36 to 7 for all these files, and you
should now be able to FTP them without further problem.  And no, you cannot
run DEC-20 Kermit on a DEC-10 machine.]

------------------------------

End of Info-Kermit Digest
*************************
-------
21-Apr-86 17:49:49-EST,9608;000000000000
Mail-From: SY.CHRISTINE created at 21-Apr-86 17:48:51
Date: Mon 21 Apr 86 17:48:50-EST
From: Christine M Gianone <[e-mail]>
Subject: Info-Kermit Digest V4 #25
To: [e-mail]
Reply-To: Info-Kermit@CU20B
Queries-To: Info-Kermit-Request@CU20B
Message-ID: <[e-mail]>

Info-Kermit Digest         Mon, 21 Apr 1986       Volume 4 : Number 25

Departments:

  ANNOUNCEMENTS -
        New Kermit Versions from Lancaster University

  MISCELLANY -
        Kermit-MS 2.28 jrd/5g on PCJr
        BOO Files
        Bug in MacKermit VT102 Emulation
        Multiple Parameters in MacKermit VT100 Emulation
        Macintosh Kermit Recieve Dialog Box

----------------------------------------------------------------------

Date: Wed 16 Apr 86 16:56:06-EST
From: Christine M Gianone <[e-mail]>
Subject: New Kermit Versions from Lancaster University
Keywords: England Computers

This is to announce more new Kermits from Alan Phillips of Lancaster
University, England.

VME*.*
        These files are the Kermit version 1.00 for ICL 2900 systems running
the VME Operating System (also known as VME2900 and VME/B - all identical).
The version comes from the South West Universities Regional Computer Centre
(SWURCC) at Bath University, UK.  The source is written in "S3".

CYB*.*
        These files are a new Kermit version 1.00 for the CDC Cyber systems
running NOS 2.2, sent in by A.V. Le Blanc of the University of Manchester
Regional Computer Centre (UMRCC).  The version is written in Compass, and is
supposedly more useful to other sites than the Texas University version,
which is highly site specific.

        Cyber Kermit is a version of Kermit which runs on a CDC mainframe
under the NOS-2 operating system.  It runs only as a remote Kermit and has
moderately advanced server capabilities.  File transfer uses a 7-bit line;
binary files can be transferred only by using a bit-prefix.  The program is
in assembler (COMPASS 3.6) and requires a field length of 2,922 (decimal)
words, including all system library routines and I/O buffers.

FLX*.*
        These files are a Kermit for the Flex 9 systems, written at Brighton
Polytechnic and sent in by Peter Morgan.  The source is written in assembler.

[Ed. - These files are available in KER: via ARPANET on CU20B, and via
BITNET at CUVMA through KERMSRV.  Thanks once again to Alan Phillips of
Lancaster University, UK and to those who have contributed these Kermit
versions.]

------------------------------

Date: Wed 16 Apr 86 08:20:45-CST
From: Rob Pettengill <[e-mail]>
Subject: Kermit-MS 2.28 jrd/5g on PCJr
Keywords: MS-DOS Kermit
Cross-Ref: IBM PC Kermit, PC Kermit, MS-DOS (see also MS-DOS Kermit)

I have tried out the new Kermit on:
* 640k IBMPC with NEC V20
* 128k IBMPCJr
And found normal operation at 1200 baud in Tops20 emacs, and both
ascii and binary file transfers.  The only anomaly that I have observed
so far is that when the new kermit starts up on the PC jr, a warning
message, "unrecognized baud rate" is displayed.  My mskermit.ini file
sets the baud rate to 1200 and that works fine.  I haven't checked but
I assume that msjrd5g.exe was compiled with a default baud rate (9600?)
higher than the Jr's serial port can handle.

Thanks for the good work - I had been about to send off a message asking
if anyone knew how to get the new ms-kermit running on the jr!

-rob

[Ed. - Kermit leaves the serial port alone.  It may be that setting the baud
rate to something specific initializes the serial port the first time after
you turn the machine on.]

------------------------------

Date: Mon, 21 Apr 86 13:27:30 est
From: Doug Snow <[e-mail]>
Subject: BOO Files
Keywords: BOO files

I hope this ends up being a question of general interest.  I recently
obtained the beta version of mskermit 2.29 from kermsrv at cuvma on bitnet.
However, this comes in boo file format and this is something that I'm not
familiar with. A bit of exploration on kermsrv found me a file called
m4boo.bas.  I tried to run this program on a number of copies of msjrd5g
only to consistently get 'unexpected eof encountered' (+/- ) Well, I'm
really just guessing as to whether or not this is the program I want... can
you help? How do I get the boo file to exe format, what does boo represent
(bootable?).  Any help would be greatly appreciated.

[Ed. - BOO-format is an encoding we use for making an 8-bit binary file,
such as an MS-DOS .EXE file, printable so that it can be sent through
electronic mail, put on ANSI or OS labeled tapes, etc.  The encoding is more
efficient than straightforward 2-for-1 hex encoding.  A BOO file (BOO is
short for bootstrap) has a 4-for-3 encoding, and in addition repeated zero
bytes are compressed.  The result for a typical executable program image is
about the same as -- and often smaller than -- the orginal binary file.  BOO
files are made using the program MSBMKB.C, and are decoded in one of two
ways: (1) On the fly, during download, using the pair of programs MSBOOT.FOR
on the mainframe and MSBPCB.BAS on the micro, or (2) after download by some
other method, using MSBPCT.C (fast) or MSBPCT.BAS (slow).  Downloading of
BOO files is described in detail in the MS-DOS chapter of the Kermit User
Guide.]

------------------------------

Date: Tue, 8 Apr 86 16:29:29 -0200
From: Bj|rn Larsen <[e-mail]>
Subject: Bug in MacKermit VT102 Emulation
Keywords: Mac Kermit, Terminal Emulation

There is a bug in the way that the MacKermit VT102 emulator handles the SGR
escape sequence.

If MacKermit receives the escape sequence "<ESC>[7m", it sets the graphic
rendition to reverse. If it receives "<ESC>[;7m", it does not.

I don't have the ANSI standard available, but in the VT100 Users Guide,
p. 3-14 it says:

        Character Attributes

        ESC [ Ps;Ps;Ps;...;Ps m

        Ps refers to a selective parameter. Multiple parameteres are
        separated by the semicolon character (073 octal). The parameters
        are executed in order, and have the following meanings:

        0 or None       All attributes off
        1               Bold on
        4               Underscore on
        5               Blink on
        7               Reverse video on

        Any other parameters are ignored.

This implies that "<ESC>[m" should be interpreted as "All Attributes off".
This is also the way MacKermit works.

But then, "<ESC>[;7m" should first turn off all attributes, then turn on
reverse.  MacKermit doesn't.

This misfeature makes it difficult to use a Mac as a terminal against a VAX
if you wish to use the EVE editor (or other VAXTPU programs).  Since EVE
uses reverse video to display your select region, you are in for some big
troubles.

Since we use both EVE and VAXTPU heavily, a new version of MacKermit would
be most welcome.

[e-mail]         Bj|rn Larsen
                                                System Manager,
                                                Unversity of Oslo,
  Computers never make misteaks  ;-)            Norway.


[Ed. - See message below...]

------------------------------

Date:     Tue, 15 Apr 86 15:23 EST
From:     (Davide P. Cervone, User Services Consultan ...) <[e-mail]>
Subject:  Multiple Parameters in MacKermit VT100 Emulation
Keywords: Mac Kermit, Terminal Emulation

This is a known bug.  The documentaion I sent to columbia states:

     o  In escape sequences where multiple parameters are allowed, only the
        first is used; that is, ESC[p1;p2;...pn c  will process only p1 (e.g.,
        ESC[0;7m is processed as ESC[0m; this is not consistent with VT100
        specifications). [apparently, this never made it into the BWR file]

In the escape sequence ESC[;7m, the first parameter is 0 (by default),
hence MacKermit only does ESC[0m and ingnores the second number.  This is
a problem, and I know it affects TPU.

The problem was inharent in the original design of the VT100 emulator for the
MAC, which made no provisions for more than two parameters for any of its
commands, and only used one for those that usually only supply one.  At the
time I re-worked the VT100 emulator, I noted the problem, and debated whether
to fix it, but it would have required re-writing of a major sort.  We did not
have VMS4.2 running at that time, and MacKermit worked with EDT, so I figured
it would be "safe" for a while.  Alas, I should have know.  I like to use TPU,
too, so I expect I'll fix it sometime, but not in the immediate future.  There
may be an easy fix to accept TWO parameters for ESC[p1;p2m, which would fix
your current problem, but not the general one. I will look into it...

                                        Davide P. Cervone

P.S. this is not a new bug, it existed in the old version of MacKermit as well.

------------------------------

Date: 14 Apr 86 18:55 EDT
From: (David HM Spector) <[e-mail]>
Subject: Macintosh Kermit Recieve Dialog Box.
Keywords: Mac Kermit
Cross-Ref: MacKermit, Macintosh Kermit (see also Mac Kermit)

The Recieve-file dialog box in the current (and previous) versions of Macintosh
Kermit needs to be increased to the size of the send-file dialog box (or
larger).  Currently, the dialog box is mal-formed and won't work with HFS too
well.  That is not to say that Macintosh Kermit doesn't work with HFS,
as far as I can tell it works very well, just the dialog box is too small.

                        David

[Ed. - Noted.]

------------------------------

End of Info-Kermit Digest
*************************
-------
24-Apr-86 17:28:07-EST,15658;000000000000
Mail-From: SY.CHRISTINE created at 24-Apr-86 17:26:24
Date: Thu 24 Apr 86 17:26:24-EST
From: Christine M Gianone <[e-mail]>
Subject: Info-Kermit Digest V4 #26
To: [e-mail]
Reply-To: Info-Kermit@CU20B
Queries-To: Info-Kermit-Request@CU20B
Message-ID: <[e-mail]>

Info-Kermit Digest         Thu, 24 Apr 1986       Volume 4 : Number 26

Departments:

  ANNOUNCEMENTS -
     New PDP-11 Kermit
     Prerelease Test Versions of MS-DOS Kermit 2.29 More Widely Available

  MS-DOS KERMIT -
     MSJRD5G on Olivetti-M24 with Keyboard 2
     Bugs in MS-DOS Kermit jrd5g
     Kermit's Mode Line: A Treatise.

  MISCELLANY -
     SmartTeam Modem Problem.
     New PC Compatible (Laptop) Modem
     SCO XENIX V AND C-KERMIT 4C(58)?
     Apple II CP/M Kermit Diskette?
     Kermit-10 Problem and Fix
     Re: Info-Kermit Digest V4 #25, PCJr Baud Rate Detection

----------------------------------------------------------------------

Date: Tue 22 Apr 86 11:45:27-EST
From: Frank da Cruz <[e-mail]>
Subject: New PDP-11 Kermit
Keywords: PDP-11 Kermit

Announcing version 3.50 of PDP-11 Kermit for RSX-11/M, RSX-11/M-Plus, IAS,
RT-11, RSTS/E, TSX+, P/OS, and Pro/RT from Brian Nelson of the University of
Toledo, Toledo Ohio ([e-mail]).  The major changes include
addition of support for long packets and a mechanism for controlling dialout
modems.  In addition, many commands have been added, many bugs fixed, etc
etc, since the last release, 2.29, July 1985.

The new files are in KER:K11*.*, available via anonymous FTP from host CU20B
on CCnet and the Internet, and via KERMSRV at CUVMA on BITNET.  There are
107 files, occupying a total of about 3.7 megabytes.  The hexified task
images (or otherwise runnable program images) are in KER:K11*.HEX, one for
each system.  The manual is in KER:K11USR.DOC (and .RNO for the Runoff
source).  The file KER:K11FIL.DOC lists all the files and explains what they
are.  You might want to read this file before transferring any of the
others, to avoid swamping the networks with files you don't really need.

Brian will be running a session on Kermit at Dallas DECUS, Tuesday, April
29, at 10:00am concentrating on the PDP-11 and other DEC versions.  He has
also written an article which will be in the June issue of The DEC
Professional.

------------------------------

Date: Tue 22 Apr 86 11:45:27-EST
From: Frank da Cruz <[e-mail]>
Subject: Prerelease Test Versions of MS-DOS Kermit 2.29 More Widely Available
Keywords: MS-DOS Kermit

By popular demand, prerelease test versions of Joe Doupnik's new release of
MS-DOS Kermit are being placed in the regular Kermit distribution.  For now,
only the .BOO files will be available, and only for those versions we have
.BOO files for, which have been tested to some degree.  They will be placed
in KER:MST*.BOO ("T" for Test), and from there they will make their way to
BITNET and other distribution areas.  For starters, we have MSTIBM.BOO for the
IBM PC family and compatibles, MSTRB1.BOO for the DEC Rainbow, and MSTHP1.BOO
for the HP-150.  The sources are not available in this way.  Those who wish to
try out the new versions are encouraged to do so, and report any problems back.
Our goal is to have a final release as soon as possible, and we hope that these
programs are very close to final form.  Any additional commands or enhancements
will have to wait till a subsequent release.

------------------------------

Date: Thu, 22 apr 1986, 08:45 B
FROM: <[e-mail]>
Subject: MSJRD5G on Olivetti-M24 with Keyboard 2
Keywords: MS-DOS Kermit, Olivetti-M24

Hi, we are using MSJRD5G on an Olivetti M24 with keyboard 2. It works very
fine on all speeds up to 9600 Baud. Terminal Emulation (VT102) is ok and
works without problems with the VAX/PDP-EDT editor and a 3270 protokol
emulator. Long live the FROG and his supporters !!!!

I've got only two questions. The first is more important than the second:

 1.) On the Olivetti "keyboard 2" the cursor-keys and the keys
     2 4 6 8 on the separate numeric keypad seem to be "hard/soft-
     wired" to send the same SCAN-codes. Also the keys "SCTPRT" and
     "HELP" doesn't seem to send any SCAN-Code at all.
     This is the only point that prevent the VT102 Emulation to be
     complete (from my point of view). My request (very urgent) is:
     Has anybody out there got the source code for the MS-DOS 2.11
     terminal drivers (esp. KEYBGR) and is willing to send it to
     me?

 2.) I thought that MS-Kermit V2.29 would have long packet and or
     sliding windows. Since I haven't seen them on MSJRD5G I may
     have been wrong all the time. Anybody to confirm?

    Thanks a lot in advance

     Martin Knoblauch
TH-Darmstadt, D-6100 Darmstadt, West Germany
EARN/BITNET: <[e-mail]>

[Ed. -  Long packets and sliding windows will not be included in MS-DOS
2.29.  These features will probably be implemented in C-Kermit first, which
in turn may eventually absorb MS-DOS Kermit.]

------------------------------

Date: 21-APR-1986 14:37:00
From: [e-mail]1
Subject: Bugs in MS-DOS Kermit jrd5g
Keywords: MS-DOS Kermit

Two points about the latest mskermit:

   a) (this is rather obscure) if you SET MODE OFF, then SET MODE ON,
       then SET MODE OFF again, the mode line does not disappear, it just
       becomes normal, rather than inverse video, text.

   b) in reply to the person saying that the vt100 emulation doesnt work
      properly on a unix system, may I suggest he examines his termcap
      again, as I have had no trouble with vi on any of the 4 unix systems
      here. I have redefined the arrow keys to send hjkl instead of esacpe
      sequences (then there is no trouble with the machine failing to keep
      up when i lean on arrow key), redefined backspace to send ctrl-H and
      redefined Del to send a unix kill.

What is the difference between vt102 and vt100? I notice that vt100 isnt
an option. But whoever Joe Doupnik is, hes doing a good job....


sebastian rahtz
southampton

[Ed. - See next message.]

------------------------------

Date: 22 APR 86 17:07-MST
From: [e-mail]
Subject: Kermit's Mode Line: A Treatise.
Keywords: MS-DOS Kermit

        In response to the comment from Peter Kanaitis regarding the 25th
line usage in IBM Kermit. Peter is correct in stating the 25th line is part
of the active display with a terminal type of None. The reason is that there
is no emulator present to understand cursor movements and hence to protect
the 25th line. In this situation Kermit sets the mode line to Off, as is
shown on the status display. Later, changing to a full emulator the 25th
line is reserved for status information (Kermit's or the user's) and it is
protected. However, the mode line is still commanded to be off from the
previous terminal type none operations. Off in this situation means that
Kermit cannot place its own status line at the bottom of the screen. When
Kermit exits command mode it saves all 25 lines so that a user controlled
25th line will not be permanently erased, and it restores all 25 lines when
connect mode is resumed. In this case the 25th line was generated by
terminal type none operations. To redisplay Kermit's normal status line the
mode line must be enabled again by Set Mode On rather than just the ^]M
toggle; the toggle has effect only when Kermit's mode line is enabled.

        This is working as planned, even if the explanation is awkward. Again,
the 25th line can be used either by Kermit (normal) or by a remote application.
Exiting and then reentering Connect mode is not known to a remote application
and thus Kermit must and does preserve the 25th line around such interruptions.
Unfortunately, Kermit does not preserve a long history log of just how
the 25th line was generated. If an application writes there that will forcibly
disable the mode line (off state) to prevent Kermit from generating its own.
When the mode line is off and connect mode is reentered then the 25th line
shows whatever information was present there when connect mode was exited.
If the mode line is disabled by an application or by the command Set Mode Off
then the only way to turn it (Kermit's mode line) on again is to give the
command Set Mode On.

        The positioning of the cursor is a knotty problem. The position
is remembered across interruptions to connect mode; if it weren't then
we would be very unhappy indeed. For example, while in connect mode typing
the escape character ^] in fact temporarily or permanently exits connect
mode; losing the cursor position to do a simple toggle or menu operation would
be unacceptable. Undoubtedly, there are some side effects of this cursor
preservation strategy; the bad ones we will find and fix.

        I hope this clarifies how Kermit treats the Connect mode screen.
Maybe someone needs to put a little AI into Kermit since the pure logic can be
baffling.

        Regards,
        Joe D.

[Ed. - Thanks!]

------------------------------

Date: 21 APR 86 21:57-MST
From: JRD@USU
Subject: SmartTeam Modem Problem.
Keywords: SmartTeam Modem, Modem

        Someone had been telling me for some time that Kermit gets stalled
and does not recover. He was talking from an IBM compatible to a VAX. After
translating things back and forth I decided his modem might be at fault.
Side by side testing of his modem and mine today yielded: both receive files
from the VAX with no problem. Mine sends files ok, his sends flakey packets
and the VAX gives up with Device Errors after a dozen packets or so. His
modem is a SmartTeam 1200 external unit widely advertized under various
names. The problem seems to be the modem's small internal power regualtors
run very hot and allow the power to droop during sending. This might result
in a power-induced carrier phase shift and hence badly framed chars.  The
problem is evident only at 1200 baud when the modem sends long packets (ACKs
get through ok to the VAX). Work around suggested was to send shorter
packets until the power supply heat problem is fixed. Running his unit with-
out the case yielded excellent file transfers and a couple of toasty
fingers.  If all this is correct then there might well be a design problem
in these units remeniscent of older modems dying from overheated power
regulators (pre-VLSI era). My modem is a Hayes 2400 external unit (at the
price it had better work!)

        Regards,
        Joe D.

------------------------------

Date: Mon Apr 21 23:00:25 1986
From: Herm Fischer <hermix![e-mail]>
Subject: New PC Convertible (Laptop) Modem
Keywords: IBM Convertible PC, Modem, Internal Modem

Just got a document today which indicates that the laptop's internal modem
behaves mostly like the PC Jr's internal modem (as far as modem commands
go)...  Rest (screen, etc) behaves like a PC...  Some notes on modem having
to be set into a "transparent state" to ignore whatever puts it into command
state...

And, oh yes, its execution is faster than the plain PC because static CMOS
ram does not use clock cycles for refreshing.  But it should go thru bios
for input (keyboard) so that if waiting for keyboard it powers down...

  Herm

------------------------------

Date: 22 Apr 1986 1523-EST
From: William M Esser, [phone] (via LCG.KERMIT)
Subject: SCO XENIX V AND C-KERMIT 4C(58)?
Keywords: C-Kermit

        Have received a copy of C_KERMIT 4C last week and have attempted to
compile on a Sperry IT (AT type) under SCO XENIX V. C_kermit compiles under
sys3nid or xenix if -Mm is added to the make file for each of these. However
the system produces a unique type of Kermit, which will only talk to a second
C_kermit running under SCO XENIX V. Has any one else found this true and if
so, is there a fix ?????

------------------------------

Date: Wed, 23 Apr 1986 09:10 EST
From: Jack Shaw <JDS2F@UOTTAWA>
Subject: Apple II CP/M Kermit Diskette?
Keywords: Apple II CP/M

I am looking for someone with a copy of Apple CP/M Kermit for use with
an Apple Super Serial Card (6551 ACIA I believe). I would appreciate
it if you would post this in Info-Kermit. I'll be glad to send down a
diskette to the volunteer! Thanks.

                          Jack Shaw
                          [e-mail]
                          Univ. of Ottawa

[Ed. - Since we do not have an Apple II micro here, we cannot supply
diskettes to users.  Peter Trei has been kind enough to offer his services
to distribute Apple II DOS diskettes but we do not yet have a volunteer for
the Apple II CP/M version in the U.S.  If anyone has this version of Kermit
please submit it to a Users Group and let us know.]

------------------------------

Date: 22 Apr 86 20:48 +0200
From: [e-mail]
Subject: Kermit-10 Problem and Fix
Keywords: Kermit-10

Problem:
  .run k10mit

  TOPS-10 KERMIT version 3(134)
  Kermit-10>set file (parameter) byte-size (to) 7
  ? Unrecognized switch or keyword: "7"
  Kermit-10>set file (parameter) byte-size (to) ? one of the following:
  7-bit         36-bit          8-bit           auto-byte       eight-bit
  seven-bit     thirty-six-bit

Diagnosis: The command table is not sorted properly. The new "36-bit"
           parameter comes after "7-bit". It should be vice versa.

Cure:      exchange two lines in the table FBS020 in K10MIT.MAC

[Ed. - Thanks for the fix.  The change has been made to our copy of
KER:K10MIT.MAC.]

------------------------------

Date: Thu, 24 Apr 86 09:35:03 est
From: Tom Putnam <[e-mail]>
Subject: Re: Info-Kermit Digest V4 #25, PCJr Baud Rate Detection
Keywords: PCJr

A little known and less appreciated fact is that the IBM PCJr uses a
slightly different clock frequency to run the 8250A UART.  While I haven't
taken the time to look at the code in Kermit-MS 2.28 jrd/5g, it is apparent
that it reads the baud rate divisor register on startup and, if it is set to
some value, it uses the value to look up the baud rate in its table.  The
table values that are supposed to be used for PCJr are slightly different
than for the rest of the PC line.  I suspect Kermit-MS doesn't know about
this difference.  The differences are small enough that you can get by with
the "normal" PC settings and things will generally work.  Here are the
values from the IBM Tech Reference manuals:

        Baud rate       PC,XT,AT        PCJr
        300             384             373
        1200            96              93
        2400            48              47
        4800            24              23
        9600            12              12

"Smart" software that knows about the PCJr can check ROM location F000:FFFE
where the PC Type is flagged: FC=AT, FD=Jr, FE=XT, FF=PC.  (There re
probably others by now).  Is it worth it?  I doubt it...

Tom Putnam                              Manager of User Services
ARPANET: [e-mail]             Purdue University Computing Center
     or  [e-mail]            Mathematical Sciences Bldg.
BITNET:  PUTNAMT@PURCCVM                West Lafayette, IN 47907
USENET:  [e-mail]                317/494-1787

[Ed. - Thanks!]

------------------------------

End of Info-Kermit Digest
*************************
-------
30-Apr-86 18:35:57-EDT,10608;000000000000
Mail-From: SY.CHRISTINE created at 30-Apr-86 18:35:13
Date: Wed 30 Apr 86 18:35:13-EDT
From: Christine M Gianone <[e-mail]>
Subject: Info-Kermit Digest V4 #27
To: [e-mail]
Reply-To: Info-Kermit@CU20B
Queries-To: Info-Kermit-Request@CU20B
Message-ID: <[e-mail]>

Info-Kermit Digest         Wed, 30 Apr 1986       Volume 4 : Number 27

Today's Topics:

              Announcing Kermit for the Commodore Amiga
               Commodore Amiga Kermit Bootstrap Progam
                    Announcing UNIX Kermit 4D(060)
            MSKermit 2.28 jrd/5e Works on IBM Convertible
                         Gould MPX-32 Kermits
                                Ideas

----------------------------------------------------------------------

Date: Tue, 29 Apr 86 16:12 EDT
From: Frank da Cruz <SY.FDC@CU20B>
Subject: Announcing Kermit for the Commodore Amiga
Keywords: Commodore Amiga Kermit, C-Kermit, UNIX Kermit

A version of C-Kermit for the Commodore Amiga is now available.  It's an
adaption of C-Kermit (which also runs on UNIX, VAX/VMS, and the Apple
Macintosh) for the Amiga by Davide P. Cervone of the University of Rochester,
User Services, [e-mail].  It was developed in Lattice C V3.03; it is
not known whether it is compatible with other compilers, or cross-compilers.

This version runs as a regular local Kermit, and also provides a server mode
supporting GET, SEND, REMOTE HELP, and BYE.  The user interface is
line-oriented (it runs from the CLI), with command completion and help in the
style of the UNIX Kermit.

The limitations of this version are discussed in KER:CKIKER.BWR, and the
differences between Amiga Kermit and UNIX Kermit are described in
KER:CKIKER.DOC.  The procedure for creating an executable from the sources
is outlined in KER:CKIKER.BLD (an automated EXECUTE file, KER:CKIKER.MAK, is
provided).  A BOO-format encoded executable is available (KER:CKIKER.BOO),
together with the program to decode it (KER:MSBPCT.C).  There's also a BASIC
version in CKIBOO.BAS (see next message).

Amiga Kermit is still under development, with planned enhancements to include:
a menu and mouse driven interface, wildcard file expansions, VT100 terminal
emulation, and local and remote command execution.  Now that Davide has
received his copy of the ROM kernel manuals, he should be able to add these
more advanced features.  Another version of Kermit for the Amiga, also based on
C-Kermit, has been in development at SAS Institue.  Davide has made contact
with these people, in hopes that the two versions can be merged into one.

The complete set of new files is in KER:CKU*.*, KER:CKC*.*, and KER:CKI*.*
on Internet host CU20B, available via anonymous FTP, and on KERMSRV at CUVMA
on BITNET.  The "I" system designator was selected for the Amiga because "A"
was already in use for general C-Kermit information; "I" stands for
Intuition (the Amiga operating system?).  Also, the bare minimum Amiga files
can be found in KER:CA*.*, for the benefit of those who order Tape A
(micros) and expect the Amiga to be among them.

------------------------------

Date: Mon, 28 Apr 86 15:24 EST
From:  [e-mail]
Subject: Commodore Amiga Kermit Bootstrap Progam
Keywords: Commodore Amiga Kermit

I am sending a modified version of MSPCTRAN.BAS which will unpack the .BOO
file for the Amiga Kermit for those of us lacking the benefit of a C
compiler.  The work was done by Andy Hollander here at Notre Dame and the
file is called CKAKER.BAS.  It takes about an hour to unpack the current
pre-release version of CKAKER.BOO, but it is worth the wait.  Our
compliments to Davide Cervone.

mark johnson
univ of notre dame

[Ed. - Thanks!  The file is in KER:CKIBOO.BAS.]

------------------------------

Date: Tue, 29 Apr 86 16:13 EDT
From: Frank da Cruz <SY.FDC@CU20B>
Subject: Announcing UNIX Kermit 4D(060)
Keywords: UNIX Kermit, C-Kermit

This is a minor new release of UNIX Kermit.  The big change is the addition of
Commodore Amiga support by Davide Cervone (see above), hence the escalation of
the minor version from C to D.  Also, a couple minor problems have been
corrected:

. Multiline GET in TAKE command files now works (thanks to G|ran Uddeborg
  for reporting this one) - KER:CKUUSR.C.

. File collision renaming bugs fixed and algorithm improved - KER:CKUFIO.C.

. CONNECT command handles fork creation failure more gracefully - KER:CKUCON.C.
  Thanks to Gordon Haverland, Dawson Creek, BC, for reporting this one.

The new files are in KER:CKU*.* and KER:CKC*.*.  Fixed bugs removed from list
in KER:CKUKER.BWR.  This new release was tested on a VAX with Ultrix 1.1
(4.2BSD), built using all the new modules, including the ones to which Amiga
support was added.

------------------------------

Date: Thu 24 Apr 86 18:18:02-PST
From: David John Buerger  <[e-mail]>
Subject: MSKermit 2.28 jrd/5e Works on IBM Convertible
Keywords: MS-DOS Kermit, IBM PC Convertible

I have received an evaluation unit of the new IBM PC Convertible and have
managed to get MS Kermit 2.28 jrd/5e (3/20/86) working on it.  Using a 3.5"
external disk drive attached to a PC/AT, I copied the necessary Kermit files
onto the new diskette.  This version of Kermit seems to work fine with no
modifications.

[Ed. - Good News!]

Unfortunately, the IBM internal modem for the Convertible does not recognize
Hayes AT commands (or most others familiar to us all).  Consequently, to
dial a number with Kermit on the Convertible, you must get into the Kermit
Connect mode, issue a ^N, then type D xxxxxxx where the x's are the number
you are dialing.  After logging off of a host, you type ^N, then H<return>
to disconnect the line.  When will IBM ever learn (sigh)?

[Ed. - We're IBM.  We don't care.]

Oh well, I'm happy that Kermit works on it.

[Ed. - Us too.]

David J. Buerger
Director, PC Center
Santa Clara University
[e-mail]

------------------------------

Date: Thu 24 Apr 86 21:52:23-MST
From: Mike Niswonger <[e-mail]>
Subject: Gould MPX-32 Kermits
Keywords: Gould MPX-32 Kermits

    I have rounded up the missing include file from the Singer-Link
version of Gould MPX-32 Kermit (GM1).  Please add this to the existing GM1
files. I will be reorganizing this group of files, but I have had several
requests for this file so I wanted to get it out ASAP.

[Ed. - Thanks!  It's installed in KER:GM1KER.INC.]

    I also have a more advanced version of Kermit for the Gould system,
from Simulation Associates.  A complete preliminary set of files with the
GM2 prefix can be found in my work directory.  I say preliminary because I
haven't had time to polish the doc, and server mode still doesn't work all
of the time.  The files have been checked out on my system, independently
from the author's system, and the Kermit is known good.

[Ed. - Thanks again.  We haven't managed to get this one yet, but will
keep trying.  It should show up on CU20B within a couple days.]

    Please add these files to CU20B's Kermit repository -- permission
has been granted by both authors.  I will let you know when updates to doc
or code are available.
                    -- Mike Niswonger

------------------------------

From: "Roger Fajman" <RAF@NIHCU>
Date: Wed, 30 Apr 86  15:42:54 EDT
Subject: Ideas
Keywords: Compression

A couple of ideas for improvements to Kermit:

(1) It would be nice to be able to give a list of files in a SEND command.
I often want to send several files at once, but can't express it with a
wildcard.  Now I must either rename the files, make up a command file (works
only if the receiving Kermit is a server), or sit at the PC and issue
another SEND command after each file is transfered.  I am going to try to
get this into the NIH TSO Kermit, if we can, so I would like to have a
standard syntax for it.

[Ed. - There's nothing in the Kermit protocol that prevents a program from
allowing this kind of syntax.  In fact, you can use it with UNIX Kermit when
you invoke it from the command line ("kermit -s foo bar baz").  The problem
is that many Kermit programs that have interactive command parsers use the
first filespec as the file(s) to send, and the second as the name to send it
under, or the initial filespec of a group, so it's just a question of
finding some alternate syntax.]

(2) Some of the file compression programs available for the IBM PC, such as
ARC, can achieve a considerable reduction in the size of a file (often 50%).
As the resulting file is binary, this results in a corresponding reduction
in transmission time when an 8-bit channel is used (assuming no 8th bit
quoting and neglecting the effect of control character quoting).  The
advantage of extending Kermit's compression capability to a more
sophisticated algorithm is that the user would get the benefit automatically
when both Kermits have the capability.  No separate compression and
decompression steps would be required.  Also, the method of encoding the
file could be designed to reduce the need for quoting characters, especially
when a 7-bit link is used.  The April 1986 issue of the Communications of
the ACM contains an article called "A Locally Adaptive Data Compression
Scheme" by Bentley, et. al. They claim that their algorithm does just about
as well as Huffman coding, without requiring two passes over the file.

[Ed. - There are a lot of whizzy compressions algorithms around, some
requiring one pass, some two, and each has its advocates.  In fact, there's
nothing that precludes Kermit programs from using any of them, but obviously
the two programs have to agree on the method used, and the key (if any).
The Attributes packet actually has some fields defined for this purpose.  In
practice, however, the simple run-length encoding that Kermit programs
currently use is often quite effective, and it's very easy to program.
Other methods are often better employed outside of Kermit -- like piping
UNIX Kermit through the (Lempel-Ziv) 'compress' program on either end, or
for that matter through tar.  Building this stuff into Kermit itself is a
big chore, and therefore probably wouldn't be done to more than a couple of
Kermit programs, thereby limiting its usefulness.]

Any comments?

[Ed. - etaoinshrdlu]

------------------------------

End of Info-Kermit Digest
*************************
-------
 7-May-86 15:26:24-EDT,7166;000000000000
Mail-From: SY.CHRISTINE created at  7-May-86 15:23:00
Date: Wed 7 May 86 15:23:00-EDT
From: Christine M Gianone <[e-mail]>
Subject: Info-Kermit Digest V4 #28
To: [e-mail]
Reply-To: Info-Kermit@CU20B
Queries-To: Info-Kermit-Request@CU20B
Message-ID: <[e-mail]>

Info-Kermit Digest         Wed, 07 May 1986       Volume 4 : Number 28

Departments:

  ANNOUNCEMENTS -
         New TSO Kermit in Pascal
         New HP-86 Kermit Available
         New CP/M Source Files

  MISCELLANY -
         Compression, cont'd
         Quad board reported harmful to Kermit on Compaq

----------------------------------------------------------------------


Date: 05/07 05:43:19
From: M70B@CBEBDA3T
Subject: New TSO Kermit in Pascal
Keywords: TSO Kermit
Cross-Ref: MVS/TSO, see TSO Kermit

Finally my version of TSO-KERMIT is finished.  I read in a file on the
KERMIT-server that you're expecting my version since a year.  I have had my
program for beta-test since Nov 85, but the guys were not so sensitive to
inform me about their experiences.  But on our installation we run it with
great success.

There is a total of 7 files, containing the following:

     * TS2DS.ASM     Some ASM routines for TSODS command
     * TS2DS.INS     Installation procedure for TSODS command
     * TS2DS.PLI     Some PL/I rotines for TSODS command

     # TS2KER.INS    Installation of TSO/KERMIT
     # TS2KER.DOC    User's Guide of TSO/KERMIT
     # TS2KER.ASM    Some ASM routines for KERMIT
     # TS2KER.PAS    KERMIT main program

*) The TSODS command is used within the KERMIT program, to redirect
   TSO command output into a temporary file, accessible from the PASCAL
   main program.

   Fritz Buetikofer
   Amt fuer Informatik des Kt. Bern
   Laengassstrasse 51
   CH-3012 BERN (Switzerland)
   BITNET: M70B@CBEBDA3T

[Ed. - The files are installed in KER:TS2*.* on CU20B, and TS2* * on CUVMA.
This version is based in part on the Pascal/VS Kermit for VM/CMS by Victor
Lee of Queen's University, with some modules in Pascal, others in assembler,
still others in PL/I.  This version of Kermit is more advanced than the
old assembler version from the University of Chicago (KER:TSO*.*); it allows
transfer of binary files, includes 8th-bit prefixing, wildcard send, repeat
count compression (receive only), alternate block checks, server mode, etc.
It runs only on line-mode ASCII connections through a 3705-style front end;
there is currently no support for Series/1-style protocol converters.]

------------------------------

Date: Mon 05 May 86 21:53:08-EDT
From: Martin Rootes, Sheffield City Polytechnic, UK
Subject: New HP-86 Kermit Available
Keywords: HP86 Kermit
Cross-Ref: Hewlett-Packard, see HP

This is to announce Version 1.00 of HP86 Kermit.  HP86 Kermit provides
terminal emulation and Kermit protocol file transfer for the following
systems:

  Hewlett-Packard HP86.
  Hewlett-Packard HP87 - NOT TESTED.

The program has been tested at Sheffield City Polytechnic on the HP86,
with a  HP 82939A  serial interface.  Since the  program is written in
HP86/87 BASIC it is  expected that it will  work on the HP87,  however
this has yet to be confirmed.

The  program  was  written  in  HP86/87  BASIC and requires the binary
program UTIL/1  to supply  utilities for  enhanced screen  control, it
also relies on the I/O ROM for control of the serial interface. As the
program is written  in BASIC various  problems arise, the  major three
are:-

  1. It is noticeably slower than many other Kermit implementations.

  2. The baud rate is limited to 300, this was the fastest rate that
     could be handled by the terminal emulation section.

  3. The program is limited to sending files of type DATA, and numeric
     variables cannot be sent without conversion.

It  is  hoped  that  in  the  future some enterprising individual will
convert this program into assembler, this would undoubtedly  alleviate
problems 1 & 2 and hopefully 3.

The files are :-

HP8AAA.HLP -- List of all the HP8*.* files, with brief explanations.
HP8KER.DOC -- Kermit User Guide for v1.00.
HP8INS.DOC -- Kermit installation guide.
HP8BOO.FOR -- Downloading program.
HP8KER.BOO -- Kermit program in BASIC for downloading (see documentation).
HP8KRC.BAS -- Commented Kermit program (Reference only).

Author:- Martin Rootes,
         Computer Services Department,
         Sheffield City Polytechnic,
         Pond Street,
         Sheffield,
         S1 1WB
         United Kingdom.

         Tel:- (U.K.) 0742 20911 ext 2342

[Ed. - Thanks!  The new files are in KER:HP8*.* available via ANNONYMOUS FTP
from CU20B and BITnet KERMSRV from CUVMA.]

------------------------------

Date: Mon 05 May 86 21:53:08-EDT
From: Alan Phillips of Lancaster University, UK
Subject: New CP/M Source Files
Keywords: CP/M-80 Kermit

This is to announce new system dependent Kermit-80 files, edited with loving
care (and a lot of work) by Bertil Schou of Loughborough University.  They
now contain the system dependencies for all the currently available .HEX
files on CU20B.  As the SYS file is getting rather large, Bertil has
included a commented-out CHN directive about half way down which may be
useful to some people.

[Ed. - Thanks!  The new files are in KER:CP4TYP.ASM and KER:CP4SYS.ASM.
The .HEX files have been available for many months now without the source.
This brings the source up to date.  Just in case there turns out to be some
inconsistency in the new source, the old ones are preserved in KO:.]

------------------------------

From: "Roger Fajman" <RAF@NIHCU>
Date: Thu, 01 May 86  12:54:35 EDT
Subject: Compression, continued
Keywords: Compression

The advantage of having the compression algorithm built into Kermit is that
different systems have different compression programs.  Everything's OK if I
run something through ARC, for example, on an IBM PC, and then send it to
another IBM PC.  However, if I want to send the fine to a different kind of
machine, it is not likely to have a suitable decompress program.  Also,
using a separate compression utility makes transmitting a file into a 3 step
process, and thus more difficult for an unsophisticated user and more time
consuming for everyone.  Of course, many Kermits would have to implement the
same algorithm for it to be effective.  That means a quite a bit of work,
but the same can be said of sliding windows.

------------------------------

Date: Wed 7 May 86 12:58:41-EDT
From: Christine M Gianone <[e-mail]>
Subject: Quad board reported harmful to Kermit on Compaq
Keywords: Compaq

A Kermit user called and reported that the Quad board (I assume he meant
Quadram?) with the built-in clock, when installed on the Compaq along with
QUADCLOCK.SYS (?), prevents Kermit from transferring files.  Booting without
QUADCLOCK.SYS fixes the problem.

------------------------------

End of Info-Kermit Digest
*************************
-------
15-May-86 15:53:18-EDT,8105;000000000000
Mail-From: SY.CHRISTINE created at 15-May-86 15:51:52
Date: Thu 15 May 86 15:51:52-EDT
From: Christine M Gianone <[e-mail]>
Subject: Info-Kermit Digest V4 #29
To: [e-mail]
Reply-To: Info-Kermit@CU20B
Queries-To: Info-Kermit-Request@CU20B
Message-ID: <[e-mail]>

Info-Kermit Digest         Tue, 15 May 1986       Volume 4 : Number 29

Departments:

  ANNOUNCEMENTS -
        New Gould/SEL Kermit Available
        New Kermit-32 With Bug Fixes

  MISCELLANY -
        Quad board reported harmful to Kermit on Compaq, cont'd
        Discussion group for technology for the handicapped
        Turbo Lightning and Kermit?
        Kermit for Digital Minc?
        WKermit on the AT?

----------------------------------------------------------------------

Date: Wed 7 May 86 20:02:43-MDT
From: Mike Niswonger <[e-mail]>
Subject: New Gould/SEL Kermit Available
Keywords: MPX-32 Kermit, Gould/SEL, SEL

I'm sending an alternative version of Kermit for Gould/SEL MPX-32 system
that was submitted by Simulation Assoc.  This version has some added
features that the old didn't.

[Ed. - The files are in KER:GM2*.* available via ARPANET using FTP, user
ANONYMOUS, any password and via BITnet at CUVMA using KERMSRV.  The older
version will be kept in KER:GM1*.* until some Gould/SEL users tell us that
there is no reason to keep it.]

------------------------------

Date: Fri, 9 May 86 12:41:29 EDT
From: rmcqueen (Robert C McQueen) @ sitvxb
Subject: New Kermit-32 With Bug Fixes
Keywords: Kermit-32, VAX/VMS

I think (and hope) that I have taken care of the items that you have referred
to me.  There is a completely new set of source files which include the one
and only .MSS file, all of the MACRO-32 files and the Bliss modules.  There
is a new .HEX file which includes the fix for sending files with FORTRAN
carriage control.

[Ed. - The two fixes relate to allowing control characters to pass through
transparently during CONNECT, and transfer of FORTRAN-format files.  The new
release is in KER:VMS*.* on CU20B, and also available as VMS* * from
KERMSRV at CUVMA.]

------------------------------

Date: Thu, 8 May 86 09:55 AST
From: <[e-mail]> (Eberhard W. Lisse)
Subject: Quad board reported harmful to Kermit on Compaq, cont'd
Keywords: Quad Board, Compaq

>> A Kermit user called and reported that the Quad board (I assume he meant
>> Quadram?) with the built-in clock, when installed on the Compaq along with
>> QUADCLOCK.SYS (?), prevents Kermit from transferring files.  Booting without
>> QUADCLOCK.SYS fixes the problem.

This is not restricted to the Compaq, but to the IBM XT as well. I have had
the same problem when transferring files to the VMS/VAX here in the
hospital. I managed to transfer by setting the TIMER off.

I have reported this problem to jrd directly, but he didn't know yet what could
have caused this.

This has also been reported by Jim Moore in a recent IBM info (5 47) as
follows:

>> Date: 24 Apr 86 09:11 EST
>> From: Jim Moore <moore@ncsc>
>> Subject: Quadram Quadboard
>>
>> I recently sent a message to INFO-KERMIT concerning the inability of the
>> latest kermit release (v2.28 jrd/5g 13 apr 86) to perform file transfer from
>> our 11/750 under UNIX 4.1.  Well, it turns out that the problem is once
>> again my Quadram Quadboard.
>>
>> I've had problems before with the print spooler and ram disk that come with
>> the quadboard interfering with the Symphony communications package, so I
>> just used a different spooler.  Now it turns out that the CLOCK on the
>> quadboard interferes with kermit somehow!
>>
>> That's (at least) two popular software packages that Quadram's Quadboard
>> really mungs up.  So, until I get my JRAM-3 board I'm using this
>> wonderful "multi-function board" of mine for just the memory....
>>
>> Jim Moore
>> Naval Coastal Systems Center

------------------------------

Date: 8 May 86 06:45 EDT
From: Jim Moore <moore@ncsc>
Subject: Quad board and Kermit on Compaq
Keywords: Quad Board, Compaq

As I mentioned a few months ago, the device driver QUADCLOK.SYS interferes with
an IBM PC-XT also.  A way around this is to put QUADCLOK.COM into the AUTOEXEC
batch file; the clock is still read and kermit transfers work fine.

jim moore
naval coastal systems center

------------------------------

Date: Thu 8 May 86 10:33:53-EDT
From: Frank da Cruz <[e-mail]>
Subject: Discussion group for technology for the handicapped
Keywords: Handicapped

A mailing list has been set up at North Dakota State University for
discussing computer and other technology for people with any kind of
handicap, plus meetings, conferences, funding agencies, and so forth.  It is
run by Bob Puyear, [e-mail] (via Arpanet,
[e-mail]), who will add you to the mailing
list if you send him a request to do so.  To send mail directly to the list
itself, replace NU025213 by L$HCAP in the addresses above.

------------------------------

Date: Thu, 8 May 86 08:48:28 pdt
From: Bob Borchers <[e-mail]>
Subject: Turbo Lightning and Kermit?
Keywords: Turbo Lightning

Has anyone run into a bug that makes file tranfers with Kermit incompatible
with having Turbo Lightning resident. The file transfer appears to go fine
but the file either received or sent is trashed. Terminal traffic is just fine
and I have found nothing else that is having trouble with lightning. For
reference I am using an AT at 8Mhz, either version 2.26 or 2.28 of Kermit
and a fairly early version of Lightning talking to a Vax running BSD4.3 at
1200 baud.

Bob<[e-mail]>

[Ed. - Try the latest pre-release of MS-DOS Kermit, in which the dynamic
memory management has been fixed up considerably.  If Turbo Lightning is
well-behaved, then it should be able to peacefully coexist with the new
version of Kermit.  The latest test version for the AT is in KER:MSTIBM.BOO
on CU20B, or, if you can transfer binary files directly, KER:MSTIBM.EXE.]

------------------------------

Date: 8-MAY-1986 15:41:58
From: [e-mail]
Subject: Kermit for Digital Minc?
Keywords: Minc-11

Has anyone transferred files from a Digital Minc computer using Kermit.
We have a user who is interested in doing this and would like to know of
anyone who has a version of Kermit for the Minc computer.

[From Brian Nelson, author of PDP-11 Kermit (the Minc is a laboratory model
of the PDP-11) -- If the Minc runs a reasonably current version of RT11
(v5.x is best), and they have an extra DLV11 on it, it should work.]

------------------------------

Date: 10 May 86 23:55:50 PDT (Sat)
From: [e-mail]
Subject: WKermit on the AT?
Keywords: Sliding Windows, WKERMIT

Did anyone ever figure out why WKermit (Kermit with Sliding Windows) doesn't
work when trying to communicate between two AT-class machines?  Someone
wrote in with a message about two or three months ago (I don't remember the
exact message) saying they couldn't get it to work between two AT's, and I
had no luck just recently with two Compaq Portable 286's.  I've got an
application ideally suited for sliding windows.  I can recompile the code
locally, but my hardware specific knowledge about the AT is limited.  If
anyone (like the author) has any ideas about where to start looking, it
would be greatly appreciated.

      - Dennis Persinger
        Aerospace Corp.
        djp@aerospace

[Ed. - The person who put together WKERMIT (Jan Van der Eijk) assumed that
it would be used only with modems, so the program requires the presence of
carrier detect.  You should be able to get around this restriction by
cross connecting DTR and CD in one of the connectors, or shorting DTR and
CD in both connectors.]

------------------------------

End of Info-Kermit Digest
*************************
-------
22-May-86 17:53:48-EDT,10271;000000000000
Mail-From: SY.CHRISTINE created at 22-May-86 17:53:03
Date: Thu 22 May 86 17:53:03-EDT
From: Christine M Gianone <[e-mail]>
Subject: Info-Kermit Digest V4 #30
To: [e-mail]
Reply-To: Info-Kermit@CU20B
Message-ID: <[e-mail]>

Info-Kermit Digest         Thu, 22 May 1986       Volume 4 : Number 30

Departments:

  ANNOUNCEMENTS -
        New Release of Prime Kermit
        Sliding Windows Kermit Available for PC-DOS
        VMS Kermit 3.2.077 Hex File

  MISCELLANY -
        Stevens P/OS Kermit Doesn't Work Under P/OS 3.0
        Sending BREAK from C-Kermit on the Fortune 32:16?
        Speed Difference Between Upload and Download Using Kermit?
        Humble Apology for Amiga Kermit Beware File Mistakes

----------------------------------------------------------------------

Date: Thu 22 May 86 16:55:47-EDT
From: Frank da Cruz <[e-mail]>
Subject: New Release of Prime Kermit
Keywords: Prime, Windows

This is to announce version 7.57 of Prime Kermit for the PRIMOS operating
system, R19 or later, contributed by John Mulligan and Hugh Matlock of The
Source Telecomputing in McLean, VA.  This version corrects the bugs that
were reported for the last version and also supports the sliding window
protocol extension.  It is in use at The Source, and has been used
successfully over Telenet (with its characteristic delays) with very high
efficiency, as reported in previous issues of the Info-Kermit Digest.

The new version is in KER:PRIME.* on CU20B, available via anonymous FTP
(Internet) or NFT (CCnet), and in PRIME * on CUVMA, available via KERMSRV on
BITNET.  Thanks to Leslie Spira of The Source for sending it in.

The old version, which contains some special functions for dealing with SPSS
Portable Files, remains available as KER:PRIMEK.* (PRIMEK * on BITNET).

------------------------------

Date: Thu 22 May 86 16:59:56-EDT
From: Frank da Cruz <[e-mail]>
Subject: Sliding Windows Kermit Available for PC-DOS
Keywords: MS-DOS Kermit, Windows, C-Kermit

This is to announce a version of Kermit that runs on the IBM PC and
compatibles under PC-DOS, and which supports the sliding window protocol
extension.  It may be used in conjunction with Prime Kermit to accomplish
very efficient data transfers.  It was written by Jan van der Eijk of NUS,
commissioned by The Source Telecomputing, based on an old version of
Columbia C-Kermit.  It has not been integrated with "real" C-Kermit yet for
a variety of reasons, but this will come eventually.  The files are in
KER:WKERMIT.* on CU20B, available via anonymous FTP (Internet) or NFT
(CCnet), and in WKERMIT * on CUVMA, available via KERMSRV on BITNET.  Thanks
to Leslie Spira of The Source for submitting it.

------------------------------

Date: Thu, 22 May 86 09:15:10 EDT
From: SY.FDC@CU20B
Subject:  VMS Kermit 3.2.077 Hex File
Keywords:  VMS Kermit

When VAX/VMS Kermit 3.2.077 was announced in Info-Kermit Digest V4 #29, the
hex file for the program's task image was inadvertantly not updated.
Apologies to those who took the trouble to get the file and dehexify it,
only to find that it was still 3.2.075, and thanks to those who reported the
problem.  A hex file for 3.2.077 is now available in KER:VMSMIT.HEX on CU20B
(and VMSMIT HEX on CUVMA).

------------------------------

Date: Thu, 22 May 86 09:15:10 EDT
From: rmcqueen (Robert C McQueen) @ sitvxb.ccnet
Subject: Stevens P/OS Kermit Doesn't Work Under P/OS 3.0
Keywords: Professional-300, P/OS

The DEC Professional-3xx version of Kermit from Stevens doesn't work in
version 3.0 of P/OS.  It worked in all of the field test versions of the new
P/OS 3.0, but doesn't work in the released version.  We are currently
working on the problem, but I can not give you any time frame as to when it
will be fixed in that version.

Bob

------------------------------

Date: Mon, 12 May 86 11:18:09 BST
From: Philip Dunne EuroKom <mcvax!euroies![e-mail]>
Subject: Sending BREAK from C-Kermit on the Fortune 32:16?
Keywords: C-Kermit, Fortune

I have just installed the C-KERMIT programs on a FORTUNE 32:16 (OS 1.2.3).
The executable file was created using the make ft17 option.  I am using
C-KERMIT to transfer files between the Fortune and a GEC 63/40 running
SYSTEM V.  Inorder to contact the GEC I have to go through a Gandalf switch.
When I try to send a BREAK to get the attention of the switch I get this
message:

Can't send BREAK : Not a typewriter.

Can anyone tell me what alterations are needed so that I can send a BREAK
from the Fortune and so use KERMIT normally.

                Thanks in advance
                                  mcvax!euroies!philip

[Ed. - The Fortune support in C-Kermit uses the 4.2 BSD method for sending a
BREAK, namely ioctl(ttyfd,TIOCSBRK,(char *)0).  You are apparently getting a
negative return code from this function, which means either that that's not
really the right way to send a BREAK on the Fortune (anybody know for sure?),
or the function isn't implemented correctly, or somehow you're passing it a
file descriptor that's not for a tty.  The code in question is in the file
ckutio.c, function ttsndb().]

------------------------------

Date: 9 May 86 16:40:49 GMT
From: P Wei <[e-mail]>
Subject: Speed Difference Between Upload and Download Using Kermit?
Keywords: Performance

I am using Kermit (v.2.26) transfering files between IBM PC and VAX (running
UNIX 4.2bsd and C-Kermit).  Everything works fine except that it only takes
a few minutes to download 50K bytes file from VAX to PC, whereas it takes
*hours* to upload the file.  (I am using a network line with 9600 baud rate.
The only setting after I invoke ms-kermit is "set parity even" and "set baud
9600".  AND the transfering is at midnight. The vax has less people to serve
at this hour than in daytime).  Can anyone shine some light on me ? What is
going wrong ?  Is this an intrinsic problem with the kermit program?  Thank
you in advance for your help!

[Ed. - The speed difference you observe is not the normal behavior of
Kermit.  It's probably caused by the network.  Many network terminal
concentrators, statistical multiplers, and similar devices allocate much
higher bandwidth in the host-to-terminal direction than in the terminal-to-
host direction on the assumption that the data coming from the "terminal"
consists only of human keystrokes, whereas the host is capable of spewing
forth vast amounts of data in response to a short command.  Of course, when
the terminal is really a PC running a file transfer program like Kermit,
this assumption is very wrong.]

------------------------------

Date: Tue, 20 May 86 17:03 EST
From: <[e-mail]>
Subject: Humble Apology for Amiga Kermit Beware File Mistakes
Keywords: Amiga Kermit

It has come to my attention that a preliminary evaluation that I wrote
concerning Phil Julian and Jack Ralphs' version of Amiga Kermit was distributed
along with the CKIKER.BWR file for Amiga Kermit.  This report was not intended
to be included in the beware file, and has been removed.  It contained a
number of inaccuracies, which I hope to remmedy below.  More important, is was
viewed as a condemnation of Phil and Jack's version, which it was not meant to
be.  Phil and Jack have been very generaous to me in sending their code for
evaluation.  I learned a lot from it, and I find it to be an excellent
product, far superior to mine in many respects.  My main intent in that letter
was to indicate that the files, as they were given to me, were not in a form
appropriate for distribution, and that some work would be required to put them
into a distributable form.  It did not mean that the program should not be
distributed, nor that major changes were required to make it distributable.
This was not clear from what I said in my letter, for which I appologize.

Phil and Jack's version WILL be distributed, and I recommend that people use
it.  I suggested (recently) that their version replace mine as the "official"
version, but I do not know whether this will happen.  I will continue to work
on an Amiga-style interface for Kemit (something along the lines of MacKermit)
that is menu-driven and uses requestors, etc.  This will be some time in
coming, however, I'm afraid.

Since my complaints about Phil and Jack's version were aired publicly, I
think that the corrections to my complaints should be as well.  Many of the
"problems" I listed were really personal preferences, not mistakes with the
product.  These should not have been included in a list of bugs.  Inaccuracies
in the list that was published include the following:

   1)  It no longer uses the C-Kermit 057 version files.

   2)  The function keys do not, in fact, produce garbage, they produce no
       output, and the arrow keys produce arrow movements as they should.
       In addition, a number of the most important ANSI escape sequences are
       correctly interpreted by the console driver, so that Amiga Kermit
       can be used with many full-screen programs that expect a VT100
       terminal.  The HELP key is the only one I could find that produced
       strange results.

   3)  The changes I claimed were made to the Unix modules actually were made
       in the Amiga-dependent code, which is OK to do.  The copy I received
       was missing a section of Unix code in one place, but I understand that
       this has been replaced in the final version.

   4)  The reference to "inferior code" in the summary section referred to
       MY version, not Phil and Jack's; this was not clear from the context.

One final disclaimer:  my letter did not affect the decision about which
version to distribute, as my version was announced in the INFO-KERMIT Digest
BEFORE I sent that evaluation.  I deeply regret any misunderstandings that
may have been caused by the publishing of that report.

                                Davide P. Cervone

------------------------------

End of Info-Kermit Digest
*************************
-------
28-May-86 14:25:31-EDT,9601;000000000000
Mail-From: SY.CHRISTINE created at 28-May-86 14:23:39
Date: Wed 28 May 86 14:23:39-EDT
From: Christine M Gianone <[e-mail]>
Subject: Info-Kermit Digest V4 #31, Special Edition
To: [e-mail], [e-mail]
Reply-To: Info-Kermit@CU20B
Message-ID: <[e-mail]>

Info-Kermit Digest         Tue, 28 May 1986       Volume 4 : Number 31

             Special Edition: MS-DOS Kermit 2.29 Released

----------------------------------------------------------------------

Date: Wed 28 May 86 11:08:51-EDT
From: Frank da Cruz <[e-mail]>
Subject: Announcing Version 2.29 of MS-DOS Kermit
Keywords: MS-DOS Kermit, IBM PC, Rainbow, HP110, HP150, Heath/Zenith-100
Keywords: NEC APC, Sanyo MBC, TI PC, Victor 9000

This is to announce version 2.29 of MS-DOS Kermit for the IBM PC family and
compatibles, the DEC Rainbow, Heath/Zenith-100, HP-1xx, NEC APC, Sanyo MBC, TI
PC, Victor 9000, several other systems, and generic MS-DOS.  This version
replaces version 2.28, which was released June 10, 1985.

The new release was prepared by Joe R. Doupnik of Utah State University
([e-mail]) over many long months of detailed work.  Joe began by adding
full DOS 2.0 file support to 2.28 along with a range of server functions, and
fixing the bugs that were listed in the .BWR file.  Then he took the VT100
emulation code from James Harvey of Indiana/Purdue University (which was
written for version 2.27) and merged it in, adding features to bring it up to
nearly complete VT102 emulation, while leaving the VT52 and Heath-19 emulation
intact.  Joe has also added many new features and commands, and has tirelessly
coordinated testing of the new program on different systems through many
generations of prerelease, and cheerfully checked and merged in improved
support for various systems (like the Z100).

The result is finally ready for distribution.  In addition to the new programs,
there is a completely new MS-DOS Kermit chapter for the Kermit user guide, new
help and beware files, and other new material.  On most systems, the new
version requires less memory than the previous one, and only slightly more disk
space.  On the IBM PC family, the program needs about 60K to run, but will
allocate more if it can.

New Features of This Release:

. Full DOS 2.0 file system support in all commands. DOS 1.x support removed.

. On the IBM PC family, emulation of VT102, VT52, H19, and dumb terminal.
. Support for host control of 25th line during terminal emulation on IBM PC.
. Screen rollback memory now dynamically sized rather than fixed.
. IBM PC VT102 emulation includes all major VT102 features except
  132 columns, smooth scrolling, printer control, and diagnostic functions.

. On IBM PC family, peaceful coexistence with TopView, DesqView, MS Windows.
. Some support for IBM Extended and Professional Graphics Adapters.
. New SET TERMINAL command for setting terminal type and parameters,
  including foreground and background color and intensity on systems that
  support it (currently only for IBM family).
. New screen dump feature (on the DEC Rainbow and IBM family only).
. Increased screen rollback memory on Rainbow & IBM.
. HANGUP command for dropping DTR & RTS, to signal modem to hang up phone
  (IBM family only).
. Heath/Zenith-100 port i/o now interrupt driven, therefore much faster.

. The MS-DOS Kermit server now responds to advanced server commands (REMOTE
  DIR, REMOTE HOST, REMOTE DEL, REMOTE TYPE, REMOTE CWD, etc).
. SET RETRY n command for changing the packet retry threshold.

. Improved file name handling, to prevent destruction of directory, system,
  hidden, read-only, and volume label files.  File renaming algorithm much
  improved for conversion of incoming file names to DOS conventions, and for
  filename collision avoidance.

. LOG command now also logs debugging information (packets, terminal session)
  if SET DEBUG ON command has been given.
. New file transfer display options: SET DISPLAY QUIET, REGULAR, SERIAL.
. Serial display used by default in generic MS-DOS Kermit.

. Program segments are now ordered independently of MASM/LINK version, without
  any special switches required for building.
. Assembles with MS MASM 1.25, IBM MASM 2.0 aka MS MASM 3.0, and MS MASM 4.0,
  as well as Intel RMX assembler.  As released, the programs were assembled
  with Microsoft MASM 4.00 and Link 3.05.  Runs under all existing versions of
  MS/PC-DOS, 2.0 and higher.

. All known bugs in version 2.28 fixed including:
   Severe problems if program assembled and linked improperly
   GET command filename confusion
   Many problems with file renaming, name truncation, etc.
   Exported filenames with no filetype no longer end with period
   SET DEST PRINTER didn't work correctly
   Problems with dynamic memory allocation
   Display problems on early PC, Compaq
   Heath-19 emulation bug regarding receipt of CR or LF at col 80 vs autowrap
   The "C?" bug in the command parser
   ^C of a file transfer now honors SET INCOMPLETE KEEP
   Lost clusters on disk if BYE command given with log file open
   RUN command did not default file types .EXE, .COM, .BAT
   Long debug lines would overflow screen
   Overruns of half duplex systems at high baud rates
   Control-prefix operands in packets not range checked
   Interrupt and performance problems on IBM PC family
   Numbers sometimes disappearing from file transfer display
   Problems parsing SET PORT options in generic MS-DOS Kermit
   Program crashed with "divide overflow" when transferring very long file
   Tendency to hangup Hayes 1200B internal modem upon startup
   Problems when padding with more than 2 or 3 characters

Incompatibilities with previous release:

. SET HEATH gone, replaced by SET TERMINAL { HEATH, VT102, VT52 }
. SET AUTOWRAP gone, replaced by SET TERMINAL WRAP
. Filename completion (recognition) no longer works, because of support for
  fully qualified DOS 2.0 pathnames.

Tested on the following systems:

. IBM PC, XT, AT, PCjr, Portable PC, Convertible PC, and RT with AT DOS option
. Compaq, Z150, Z160, and other IBM compatibles
. DEC Rainbow
. Heath/Zenith-100
. HP-150, HP-110, and Portable Plus
. NEC APC and APC-3
. Victor 9000 / Sirius 1
. ACT Apricot
. Sanyo MBC 550
. Texas Instruments Professional PC
. Intel 300 series with iRMX-86
. Generic MS-DOS

Needs testing on:

. Wang PC
. Olivetti M24 PC
. Grid Compass II
. DECmate-II,III with XPU (MS-DOS) option

IBM PC family H19 and VT102 emulators tested successfully with:

. EMACS (DEC-20, CCA, GNU, and others, using line/char insert/delete)
. EDT, PHONE (VAX/VMS)
. 1-800-DEC-DEMO
. UNIX vi, sysline, etc
. Various torture tests

The new files are in KER:MS*.* on CU20B, available on the Internet via
anonymous FTP, and in MS* * on CUVMA, available on BITNET through KERMSRV at
CUVMA.  Within a few days they should also be available for UUCP transfers from
okstate (Oklahoma State University).  The executable programs are encoded in
"BOO" format (a printable 4-for-3 encoding of the .EXE file, with compression
of repeated zeros).  The BOO files are in KER:MSV*.BOO (for instance, the
version for the IBM PC family is in KER:MSVIBM.BOO), which may be decoded with
the program MSBPCT.BAS (slow) or MSBPCT.EXE (fast, but you need the Basic
program to get the fast version in the first place, because it too is
BOO-encoded).  BOO files for the old release (2.28) are still available as
KER:MSO*.BOO.

The new manual chapter is in KER:MSKERM.DOC (long, about 122K).  A summary of
the Kermit-MS invocation and commands is in KER:MSKERM.HLP (shorter, about 9K).
KER:MSKERM.BWR lists the known bugs and deficiencies, along with some
implementation notes.  KER:MSR229.UPD contains the release notes for this
version (somewhat similar to this message).

Before you get all of the KER:MS*.* files over the network, first get the
following files, which will help you zero in on the particular files you need:

. KER:MSAAAA.HLP - describes the organization MS-Kermit files in detail.
. KER:MSBAAA.HLP - describes the bootstrapping procedure for BOO files.
. KER:MSSAAA.HLP - describes how to build the program from source files.

Most people will not need the source files, which add up to quite a chunk.

If you are new to Kermit network distribution, then even before you get these
files, you should get and read KER:AAAREAD.ME (AAAREAD ME on BITNET KERMSRV).
If you can't access CU20B or CUVMA by network, you can order diskettes by mail
from:

    Kermit Distribution
    Columbia University Center for Computing Activities
    612 West 115th Street
    New York, NY  10025

Include a check for $10 US ($15 if you also want a Kermit User Guide) payable
to Columbia University Center for Computing Activities, to cover our
reproduction and handling costs.  To order from outside North America, write
to the above address for further information.

Please send inquiries, bug reports, comments, complaints, and suggestions to
Info-Kermit-Request@CU20B, or by postal mail to the above address.  In
particular, reports that the program works (or doesn't) on the as-yet-untested
machines will be most welcome.

P.S. It might take a while for the files to show up on BITNET, due to
temporary troubles with our network connection to CUVMA.

------------------------------

End of Info-Kermit Digest
*************************
-------
 5-Jun-86 12:03:00-EDT,6712;000000000000
Mail-From: SY.CHRISTINE created at  5-Jun-86 11:57:46
Date: Thu 5 Jun 86 11:57:46-EDT
From: Christine M Gianone <[e-mail]>
Subject: Info-Kermit Digest V4 #32
To: [e-mail]
Reply-To: Info-Kermit@CU20B
Queries-To: Info-Kermit-Request@CU20B
Message-ID: <[e-mail]>

Info-Kermit Digest         Thu,  5 Jun 1986       Volume 4 : Number 32

Today's Topics:

         Modified MVS/TSO Kermit Via 7171 Protocol Converter
                           New OKSTATE.TXT
              New GEC 4000 Kermit Version from Lancaster
                Many modifications for RT11 Kermit-11
                   C-Kermit vs. MS-Kermit Server II
                    Minor problem with MSYIBM.ASM
                      C-kermit & SCO Xenix Sys V

----------------------------------------------------------------------

Date:    Fri, 23 May 86 09:08 EST
From:  [e-mail]
Subject: Modified MVS/TSO Kermit Via 7171 Protocol Converter
Keywords: MVS/TSO Kermit, 7171 Protocol Converter

Please find enclosed a slightly modified version of TSODYNAL.ASM for the
TSOS1 Kermit.  We had to make a relatively minor change so RECEIVEd datasets
were correctly allocated to the user's proper disk pack. The two affected
lines are commented out with the changes following them.

Mark

[Ed. - The new modified version of TSOS1 Kermit is in KER:TSODYNAL.ASM
available via FTP at CU20B, user ANONYMOUS (any password) and from BITnet at
CUVMA using KERMSRV.]

------------------------------


Date: Mon, 26 May 86 18:40:54 CDT
From: Gregg Wonderly <[e-mail]>
Subject: New OKSTATE.TXT
Keywords: Okstate, UUCP

        There is the new update of OKSTATE.TXT for anyone who is
interested in downloading files via UUCP.

Gregg

[Ed. - The new file is in KER:OKSTATE.TXT.  The file is too long to include
here in the digest.]

------------------------------

Date: Thu 29 May 86 16:54:36-EDT
From: Christine M Gianone <[e-mail]>
Subject: New GEC 4000 Kermit Version from Lancaster
Keywords: GEC 4000

        This is to announce a new version (3.5) of the Kermit for the GEC
4000 series minis running OS 4000, from Martin Loach of Rutherford Appleton
Laboratories.  The files should replace the current GEC set.  The language
is Babbage rather than SERC/MUMS.

[Ed. - These files are in KER:GEC*.*.  Thanks again to Alan Phillips of
Lancaster University for maintaining Kermit in the U.K. and for sending us
updated Kermit versions.]

------------------------------

Date: Fri, 30 May 86 08:05 EST
From: <[e-mail]> (brian nelson)
Subject: Many modifications for RT11 Kermit-11
Keywords: Kermit-11, RT11/TSX+

 A minor release of Kermit-11 is available. This version, 3.51,  differs
only in a number of RT11/TSX+ specific modifications from the previously
announced Kermit-11.

 Specifically:

 1. Reduction in the size of the  root  for  XM  to  facilitate  running
Kermit as a foreground task.

 2. Complete rewrite of terminal emulation, specifically to enhance  the
support of the XL/XC/CL handlers. It  is  now  completely  event  driven
thus  performance  should be improved as well as presenting a much lower
load on the CPU. It should also function better under SJ.

 3. Restructuring buffer allocation to (1) Reduce the root size for  XM,
and  (2) To enable the USR to swap over buffers for SJ and FB. This will
eliminate Kermit crashing on USR requests in 95% of  the  cases  for  SJ
and  FB  systems  with  minimal  background  memory  available (ie, many
devices in the system and/or large RMON).

 4. Control C delivery has been improved by adding a watchdog  timer  to
check for control C's as RT11 does not generate an AST on control C.

 The  files  are  currently  available  via  [e-mail] or by
dialup from  the  University  of  Toledo's  VAX  11/785.  Columbia  will
receive a new distribution shortly.

Brian Nelson
[e-mail]

[Ed. - This is will be announced when we receive the new tape.]

------------------------------

Date: Tue, 3 Jun 86 09:13:31 pdt
From: Steve Walton <ametek![e-mail]>
Subject: C-Kermit vs. MS-Kermit Server II
Keywords: C-Kermit, MS-DOS Kermit

The problem with this combination is solved, and warrants a warning.  We
were starting our MS-Kermit server from our host, by doing a CTTY COM1: when
the PC was booted.  Apparently the CTTY sufficiently degrades the
performance of the serial port that Kermit will not work reliably even at
1200 baud.  When the CTTY was not done, and MS-Kermit was put into server
mode from the PC's keyboard, no problems were encountered at 9600 baud.

I hope this information is useful to others.

Stephen Walton, Ametek Computer Research Division

[Ed. - Has anyone else experienced these performance problems when CTTY
is in effect?  I assume Steve is using an IBM PC or compatible.  Is there a
difference between the new release (2.29) and previous ones in this respect?
We have tested use of Kermit through CTTY on the Rainbow up to 9600 baud
with no problems.]

------------------------------

Date: Wed 4 Jun 86 10:01:11-EDT
From: Frank da Cruz <[e-mail]>
Subject: Minor problem with MSYIBM.ASM
Keywords: MS-DOS Kermit, MSYIBM.ASM

The MS-DOS Kermit terminal emulation module for the IBM PC, MSYIBM.ASM,
contains a definition for the symbol SETBLK, which duplicates the definition
from the header file, MSSDEF.ASM.  Late-model assemblers are not perturbed
by this, but earlier assemblers complain about it, and some may refuse to
generate an object module.  Cure: remove the EQU for SETBLK from MSYIBM.ASM.
This has already been done on the master copies in Kermit distribution.
Thanks to the several people who pointed out the problem.

------------------------------

Date:  Tue, 3 Jun 86 22:18 EDT
From:  Roger Hartmuller <[e-mail]>
Subject:  C-kermit & SCO Xenix Sys V
Keywords: C-Kermit, SCO Xenix, System V

   I finally got the fix to allow kermit transfers with C-kermit running
under SCO Xenix System V on an IBM AT.  I haven't seen it published in
the forum, so I'm sending it in, even though I didn't discover the fix
myself.  In ckcfn2.c, in the routine chk1(), declare chk as an unsigned
int rather than an int.

    The problem was supposedly caused by an error in the C compiler.
Anyway, the fix works.

[Ed. - KER:CKCFN2.C has that change in it now.]

------------------------------

End of Info-Kermit Digest
*************************
-------
16-Jun-86 16:58:19-EDT,8623;000000000000
Mail-From: SY.FDC created at 16-Jun-86 16:56:30
Date: Mon 16 Jun 86 16:56:30-EDT
From: Frank da Cruz <[e-mail]>
Subject: Info-Kermit Digest V4 #33
To: [e-mail]
Reply-To: Info-Kermit@CU20B
Queries-To: Info-Kermit-Request@CU20B
Message-ID: <[e-mail]>

Info-Kermit Digest         Mon, 16 Jun 1986       Volume 4 : Number 33

Today's Topics:
                     Kermit for PDP-8 with OS-278
                New Kermit User Guide, Protocol Manual
                        BITNET KERMSRV Backlog
         Series/1 and Clone Initialization File for MSKERMIT
               Kermit 2.29 Packet Count Display Problem
   Problem with 2.29 Server and Block Checks, and Cursor Shape Hint

----------------------------------------------------------------------

Date: Wed 11 Jun 86 16:30:43-EDT
From: Frank da Cruz <[e-mail]>
Subject: Kermit for PDP-8 with OS-278
Keywords: PDP-8 Kermit

This is to announce Kermit for the DEC PDP-8 or DECmate running an operating
system called OS-278.  OS-278 is similar to OS-8, but has support for more
modern devices -- like RX50 diskette drives -- added.  OS-278 is not the same
as WPS.  It is not a DEC product, but is available from DECUS, and is used
within DEC for DECmate development.  This Kermit program is based on the OS-8
version of Kermit done by Jerry Sands & Randy Hippe of Bureau of Engraving Inc,
Minneapolis MN, and was adapted to OS-278 by Martyn Hemmings at DEC in
Germany.  The files are in KER:K278*.* on CU20B, available via anonymous FTP,
or on CUVMA as K278* *, available (traffic permitting) via BITNET KERMSRV.

It is hoped that this program will eventually serve as a basis for a "native"
DECmate WPS Kermit.  Anyone interested in doing this work should contact us
(Kermit Distribution at Columbia) first.

------------------------------

Date: Tue 10 Jun 86 16:13:40-EDT
From: Frank da Cruz <[e-mail]>
Subject: New Kermit User Guide, Protocol Manual
Keywords: Kermit User Guide, Kermit Protocol Manual

Revision 2 of the 6th Edition of the Kermit User Guide is now available.  It
contains new chapters for MS-DOS Kermit 2.29, Macintosh Kermit 0.8(34), VMS
Kermit 3.2, and a new bootstrapping section for CP/M-80 Kermit (thanks to
Bernie Eiben for the latter -- it turns out that the old bootstrapping
procedure, which has been in the manual for years, simply did not work).  The
User Guide is formed from KER:KUSER.MSS, plus individual chapters for each
implementation covered, whose MSS files reside with the other files for that
implementation.  Only minimal changes have been made to KUSER.MSS.
KER:KUSER.DOC is the complete manual, suitable for reading on a CRT screen;
it's about 280 pages long (700K).

A new edition of the Kermit Protocol Manual -- the 6th edition -- is also
available.  The new material consists mostly of corrections to the old, plus
new sections on long packets and sliding windows.  The new protocol manual
is in KER:KPROTO.MSS (Scribe source) and KER:KPROTO.DOC (CRT-readable file).
The files KER:KPROTO.UPD and KER:KPROTO.UP2 (which described long packets and
sliding windows, respectively) have been removed.

The new manuals are available via anonymous FTP from CU20B (Internet) and
from KERMSRV at CUVMA (BITNET), and in printed form from Kermit Distribution
at Columbia (see KER:AAXFLY.DOC for ordering instructions).

------------------------------

Date: Wed 11 Jun 86 14:01:03-EDT
From: Frank da Cruz <[e-mail]>
Subject: BITNET KERMSRV Backlog
Keywords: BITNET, KERMSRV

Due to the overwhelming number of requests for Kermit files from KERMSRV
at CUVMA, and to the unavailability of key BITNET routing hosts for
extended periods of time over the past few days, CUVMA's queues for outbound
BITNET files filled up to the point that the system could no longer
function, so the queues had to be flushed.  Over 1000 files were affected.
Therefore:

. People who requested files from KERMSRV over the past week may have
  to request them again, but...

. It would be better if files were only requested by one person -- preferably
  the Kermit maintainer -- at each site, to prevent duplication.

. We will try to work out some arrangement with BITNET management (EDUCOM)
  to let the Kermit files flow more smoothly over BITNET.  The most likely
  interim solution will be the establishment of additional BITNET Kermit
  file servers at other geographical locations.  These will be announced as
  they become available.

Apologies for the inconvenience.

------------------------------

Date: Wed, 4 Jun 86 12:35 EDT
From: "John C. Klensin" <[e-mail]>
Subject:  Series/1 and Clone Initialization File for MSKERMIT
Keywords: Series/1, 7171, Protocol Converter, MS-DOS Kermit

I enclose two logical files, one that describes what the other does, called
MSI7171.HLP and MSI7171.INI, for setting up the IBM PC with MS-Kermit 2.29 for
communicating with an IBM VM/CMS mainframe through a Series/1-style front end
(7171, 4994, Yale ASCII package).  This has been tested against the
Series/1-VM/CMS combination at MIT; I have no way to know if it will work in
other combinations.

Motivation: keyboard-switching drives me crazy and, for example, my left-hand
little finger instinctively reaches toward the second vertical row of function
keys and likes finding "clear" there.  If it does not find "clear" there, it
better not find anything destructive, like whatever the S/1 does when it sees
whatever VT100 PF2 maps to.

In other words, 2.29 is set up as much like a VT100 as one can reasonably make
a completely different keyboard layout, and I think that Joe made a relatively
good set of compromises where there was no "right" thing to do.  But the
problem is whether one wants to try to map keys functionally (Joe's approach)
or geographically.  The S/1 is really using a VT100 to imitate a 3278; using
MSKERMIT's VT102 mode involves using the PC to imitate a VT100 imitating a
3278.  The keyboard file does a little better imitation of a 3278 keyboard on
the PC so that it becomes a bit more like a PC imitating a 3278 using VT100
codes and the S/1 as intermediaries.

[Ed. - Thanks!  The files are installed in KER:MSI7171.* on CU20B and
MSI7171 * on CUVMA.]

------------------------------

Date: 3-Jun-86 12:29:47-EDT
Subject: Kermit 2.29 Packet Count Display Problem
From: [e-mail]
Keywords: MS-DOS Kermit

When using Version 2.29 to download a file from a Kermit-20 server, the Packet
counter will not reset.  This happened when I either cancel a file or when I
get a second file.  (I am not doing wild card gets).  The counter just picks up
where it left of from the last transfer.  The screen displays 0 packets
received, clears the screen and shows the number of packets from the last
transfer and starts counting.

The files transfer correctly and the number of KBytes transferred is updated
properly only the number of packets seems to be affected.  Other then this it
seems to work just fine.

Marc Frederick

[Ed. - This is indeed a bug, and has been noted in the "beware file".  It also
happens when SENDing to a server.]

------------------------------

Date: Sun 15 Jun 86 17:23-EDT
From: Ed Barton <[e-mail]>
Subject: Problem with 2.29 Server and Block Checks, and Cursor Shape Hint
Keywords: MS-DOS Kermit, Cursor

I believe I have discovered a bug in IBM-PC kermit version 2.29.  When
MS-Kermit is operating in server mode, it does not appear to respect the
block-check setting.  If I use version 2.28 and set block-check 3, I can
transfer files from my CP/M system that uses set block-check 3.  If I use
version 2.29 in server mode, I cannot ship files over from my CP/M system
unless I put the CP/M system in set block-check 1 mode.

[Ed. - Thanks for the report, we'll check it out.]

By the way, on at least some systems that have the cursor-shape bug, if you run
a program that explicitly sets the cursor-shape in the AUTOEXEC.BAT file, then
the cursor-shape will be correctly remembered from there on.  This worked for
my system and perhaps could be mentioned in the documentation.

[Ed. - Thanks for the hint.  Such a program was listed in Info-Kermit V4 #10,
and can also be found in the latest incarnation of the MS-DOS Kermit "beware"
file, MSKERM.BWR.]

------------------------------

End of Info-Kermit Digest
*************************
-------
27-Jun-86 15:22:03-EDT,10162;000000000000
Mail-From: SY.CHRISTINE created at 27-Jun-86 15:19:27
Date: Fri 27 Jun 86 15:19:26-EDT
From: Christine M Gianone <[e-mail]>
Subject: Info-Kermit V4 #34
To: [e-mail]
Reply-To: Info-Kermit@CU20B
Queries-To: Info-Kermit-Request@CU20B
Message-ID: <[e-mail]>

Info-Kermit Digest         Fri, 27 Jun 1986       Volume 4 : Number 34

Today's Topics:

                    New Release of Kermit for Magiscan 2
             Announcing MS-DOS Kermit 2.29 for IBM Semi-Clones
          Announcing MS-DOS Kermit V2.29 for the Seequa Chameleon
                          MS-DOS Kermit 2.29 Fixes
                        CP/M-80 Kermit Developments

----------------------------------------------------------------------

Date: 16 Jun 1986 1556-GMT
From: CENT01::SYSKERMIT "Alan Phillips, KERMIT distribution" 16-JUN-1986 11:54
Subject: New Release of Kermit for Magiscan 2
Keywords: Magiscan 2 Kermit, Joyce-Loebl, UCSD p-System

This is to announce an updated release of Kermit for the Joyce-Loebl Magiscan 2
image processor, running UCSD p-System. Changes from the previous release are:

    I micro-coded the receive packet routine so data shouldn't get clobered
    when it is being received. This means that transfers can take place at
    greater baud rates. (Though for terminal emulation you are still limited to
    1200 baud because the magiscan cannot scroll faster).

    The receive packet routine is now just a simple loop that puts all the
    characters is a buffer for decoding later.

    The option to use the Winchester on #9 on the Magiscan 2a version has been
    included, also the directory on the 2a disks are larger so this has been
    taken care of in the SYSUNIT.

    For the 2a I have used JL's own image load and save routines as these are a
    lot faster, 2-30secs(depending on wether a floppy or winchester) cf 2.5mins
    for the Magiscan 2.

    A new command has been added, SET MUX number- this command is analogous to
    the one of similar name on the BBC kermit. It enable the user to set a
    delay porportional to the number between each byte of data sent(the default
    is zero).

I hope that will cover all. If there is anything new/or bugs could
you let me know.

     Henry Balen
     c/o Image Processing Group,
     Dept. Physics and Astronomy,
     University College London,
     Gower Street,
     London.

[Ed. - Thanks for thee update, Henry and Alan.  The files are in KER:UCJ*.*
available with FTP at CU20B over the Internet and via BITnet using KERMSRV
at CUVMA.  These files have replaced the old Kermit version.]

------------------------------

Date: 16 Jun 1986 1556-EDT
From: Glenn Everhart, via <LCG.KERMIT@DEC-MARLBORO>
Subject: Announcing MS-DOS Kermit 2.29 for IBM Semi-Clones
Keywords: MS-DOS Kermit, MS-DOS 2.29, IBM Semi-Clone Kermit

I have created MSXCLO.ASM now which is edited from MSXIBM.ASM for MS Kermit
V2.29.  MSXCLO is a "half generic" MS-DOS Kermit that uses the IBM BIOS INT 14H
call for i/o to its comm port. The screen I/O is however exactly the IBM PC
version's, so you get good VT102 emulation but are able to work on a machine
that uses a different serial chip from IBM's but which emulates the IBM BIOS.
The Seeque Chameleon and DG/1 are examples of this sort of box.  The beastie
works OK at 1200 baud, may work a bit faster for file transfers - I haven't
looked.

To use, you need to jumper pins 20 and 6 to get the BIOS to think DSR is high,
else it emits nothing.

I've also made an MSVCLO.LNK which is linker instructions for the clone
version, and MSICLO.INI, which sets the keyboard layout so that the AT keypad's
lower 4 rows are exactly as the VT100's, F1 to F4 become PF1 to PF4, and F7,F8,
f9 and F10 become up, down, left, and right arrows. This is easier to follow at
our site than the "standard" layout.

I intend to come up with an MSXSEEQ.ASM one of these days that will run faster
on a Seequa, but this is of greater general interest.

The speed setting code may only work on setup; the thing defaults to 1200 baud
but can be forced by MODE, then dialing, if desired. I suspect the BIOS is
refusing to change once it sees DSR there... so some care is needed in the
jumpering. Anyhow, much less flaky looking than the old SEEQUA.ASM.

Glenn Everhart

[Ed. - We've built and tested this program on an IBM PC/AT.  Glenn is right,
you certainly do need to cross-connect DTR and DSR, and as he says, the speed
setting code is not entirely reliable.  In fact, on our PC/AT, it seems that
the speed would change from 1200 to 1800 occasionally during CONNECT, and
the only way to get it back to 1200 would be to exit from the program and
use some other utility (like MODE, or the real PC/AT Kermit) to set it back
to 1200.  On the AT, we couldn't transfer files at all, because upon escaping
back from CONNECT, the speed would always change from 1200 to 1800.  But then,
the program wasn't intended to be run on a real IBM system, only on semi-clones
with IBM-compatible BIOS, but with different serial i/o chips.  Everyone with
DG/1's, Seequa Chameleons, and other systems that fall into this category are
encouraged to pick up this version and report back their results.  The files
are in KER:MSXCLO.ASM, KER:MSVCLO.LNK, KER:MSVCLO.BOO, KER:MSVCLO.EXE (if you
can transfer binary file directly) all on CU20B, and on KERMSRV at CUVMA
with the same names, but without the KER: in front or the dot in the middle.]

------------------------------

Date: 20 Jun 1986 0902-EDT
From: Glenn Everhart, via <LCG.KERMIT@DEC-MARLBORO>
Subject: Announcing MS-DOS Kermit V2.29 for the Seequa Chameleon
Keywords: MS-DOS Kermit, MS-DOS 2.29, Seequa Chameleon Kermit

I've now (finally) got a Kermit (the MSXSEE.ASM part anyhow; the rest uses
IBM PC modules) for Seequa Chameleon that works, even at high baud rates (at
least to 19.2, maybe higher; tries up to 38.4). It's interrupt driven and
works nicely, and finally gives the Chameleon and its 8274 port a decently
fast public Kermit.  MSVSEE.LNK is the MS-DOS Link command file to put it
together, and MSVSEE.BOO is the encoded .EXE file.

I expect that these pieces will replace the old SEEQUA.ASM.

Glenn Everhart, RCA Labs, 609-338-6022

[Ed. - Thanks, Glenn!  The files have been placed into KER:MS%SEE.* on CU20B
(available on the Internet via anonymous FTP), and are also available on
BITNET via KERMSRV at CUVMA, and they have indeed replaced the old (circa
November 1983) SEEQUA.ASM in the Kermit distribution.]

------------------------------

Date: Mon 23 Jun 86 16:57:13-EDT
From: Frank da Cruz <[e-mail]>
Subject: MS-DOS Kermit 2.29 Fixes
Keywords: MS-DOS Kermit, MS-DOS 2.29

The MS-DOS Kermit "beware file" now contains patches for the following
problems, which were reported over the past few weeks with version 2.29 of
MS-DOS Kermit.  Thanks to Joe Doupnik for collecting and verifying them (and to
those who submitted them in the first), and for devising some of them himself.

. Current packet number in the file transfer display is not set back to 0 when
  a SEND or GET command is issued to a remote Kermit server.
. Server mode does not always use the negotiated block-check type.
. Receive command fails if it follows a Get which ended with an error message.
. Hayes 1200B internal modem hangs up at inconvenient times.
. Occasional transmission of a null (ASCII 0) flow control character.

The "beware file" is in KER:MSKERM.BWR, available via anonymous FTP from
host CU20B, or MSKERM BWR on CUVMA via BITNET KERMSRV.

It is expected that after a few more weeks, after the bug reports have
settled down, there will be a new release of MS-DOS Kermit that incorporates
these and other fixes, and possibly a few new features.

------------------------------

Date: 23-JUN-1986 11:19:42
From: Alan Phillips <[e-mail]>
Subject: CP/M-80 Kermit Developments
Keywords: CP/M-80 Kermit

Here's the latest news on CP/M-80 Kermit from the UK:

1. CP4TTK.HEX is for a Teletek CP/M-80 micro with an ADM 22 terminal.  It's
   from David Moore, Software Development, APV Automation, Fleming Way,
   Crawley RH10 2YX, UK. Telphone (UK) 0293-51890.  Source will probably be
   built into Bertil Schou's 4.07 release.

2. Bertil has produced what he's calling version 4.07 (wonder what happened
   to 4.06???), and it's about ready for test release. We'll put it out over
   here to get out the major bugs, than think about whether we should get the
   pre-release stuff to you for more general use. Bertil has split the SYS file
   into one per implementation, fixed the outstanding bugs in the system-
   independent stuff, and added a few features that we found were needed to
   talk to a common, but UK-specific mainframe version.

   One thing that occured to me is that we ought to change the naming structure
   of the files to match the MS-Kermit method, now we've split the SYS file.
   Having CP4 as the prefix dosn't give enough characters, so how do you
   feel about renaming it to CP? Then we can use

         CPSxxx.ASM   for system independent source
         CPXxxx.ASM   for system dependent
         CPVxxx.HEX   for the hex files

   Let us know what you feel on that.

[Ed. - The new naming is just fine.  The CP4 prefix was only to distinguish
the then-new version from the previous one (whose prefix was CPM), because
they had to coexist for a while.  Thanks to Bertil for doing all this work,
and to you for coordinating it with us.  Now that the system-dependent files
are all separated, I hope someone (maybe Bertil?) can take on the task of
making them compatible with the MODEM overlay files, so that Kermit and MODEM
(XMODEM, YMODEM, MEX, etc) can share the same set of overlays.  The new
version will be announced on Info-Kermit when it arrives.]

------------------------------

End of Info-Kermit Digest
*************************
-------