Columbia Kermit/kermit.zip/e/mail.90b

Internet Message Format | 2020-01-01 | 181KB

From cmg  Wed Jul 18 16:20:31 1990
Return-Path: <cmg>
Received: by watsun.cc.columbia.edu (5.59/FCB)
    id AA10474; Wed, 18 Jul 90 16:20:31 EDT
Date: Wed, 18 Jul 90 16:20:31 EDT
From: Christine M Gianone <[e-mail]>
To: Info-Kermit
Subject: Info-Kermit Digest V12 #1
Reply-To: [e-mail]
Queries-To: [e-mail]
Message-Id: <[e-mail]>

Info-Kermit Digest         Wed, 18 Jul 1990        Volume 12 : Number 1

Departments:

  ANNOUNCEMENTS -
        Updated MS-DOS 3.02 Test Version Available
        New Release of Kermit for HP-3000
        Announcing NCR 9800 Kermit
        New Release of Kermit for UNISYS (Burroughs) A-Series
        New Kermit Programs for Luxor ABC Series and FACIT DTC/DTC2

  IBM MAINFRAME KERMIT -
        New MS Kermit REMOTE PRINT interface with Kermit-370
        Kermit-370 support for IBM 3174 AEA

  VAX/VMS KERMIT -
        VMS Kermit-32 Hints
        How to Create a Kermit Connection over X.25 from VAX/VMS?

  MISCELLANY -
        Kermit for Microsoft Windows
        External Kermit Driver
        Kermit for Atari Portfolio?

Digest submissions may be sent to [e-mail],
requests for addition to or deletion from the Info-Kermit subscriber list to
[e-mail] or to [e-mail].

Kermit files may be obtained over networks and by mail order.  On the
Internetwork, use FTP to log in to host WATSUN.CC.COLUMBIA.EDU, a SUN-4/280
running UNIX (SUNOS 4.1), IP host number 128.59.39.2.  Login as user anonymous
(note, lower case), any password, and GET or MGET (MULTIPLE GET) the desired
files.  The Kermit files are in directories kermit/a, kermit/b, kermit/c,
kermit/d, and kermit/e.  Test versions are in kermit/test.  Binaries are in
kermit/bin (use ftp in binary mode).  You can also get Kermit files over the
BITNET/EARN network; to get started send a message with text HELP to KERMSRV,
the Kermit file server, at host CUVMA.  For detailed instructions, read the
file kermit/a/aanetw.hlp (AANETW.HLP on KERMSRV).  To order by mail, request a
complete list of Kermit versions and an order form from Kermit Distribution,
Columbia University Center for Computing Activities, 612 West 115th Street,
New York, NY 10025 USA.

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

Date: Fri Jul 13 18:16:23 1990
>From: Christine M Gianone <[e-mail]>
Subject: Updated MS-DOS 3.02 Test Version Available
Keywords: MS-DOS Kermit 3.02

Additions to Joe Doupnik's MSR302.UPD file since the previous announcement
in Info-Kermit V11 #8:

22. Add more character set corrections from Matthias Reichling.

23. Correct problem of placement of CR/LF in text screen dump (broken in
    recent v3.02 changes), from Brian Holley.

24. Make small change to Self Test code, DECTST, CSI 2 ; Ps y  (VT100) and
    CSI 4 ; Ps...; Ps y  (VT320). Do a terminal reset only if a Ps is 0 or 1.
    This is in the VT terminal emulator. Ps values greater than 1 are for
    testing the terminal serial port, printer, and repeating the tests; they
    are ignored here. All cases move the cursor back to the main display.

25. Minor change to ensure modem status is correct even if the port has not
    yet been used. File msxibm.asm.

26. Modify the way characters are placed on Tektronix graphics screens from
    starting them at intervals of 8 PC screen dots across the screen to
    placing the lower left at the current drawing position (1 dot resolution).
    Characters are 8x8 dots. The effect is better positioning accuracy along
    the x-axis; the y-axis already behaved the better way. File msgibm.asm.

27. Tiny tweak to Tek graphics code to overcome a deficiency in some Bios'
    on storing video mode values if the high bit is set (means do not clear
    the display buffer). Brian Holley found such a case and GRAPHICS.COM in
    DOS 4 became confused.  The Bios on most machines clears that bit.  msgibm.

28. Follow the lead of C-Kermit 5A and attempt simple correction of Parity
    on the communications line during packet transfers.  Parity will be
    shifted to EVEN, ODD, or MARK by the detector, in addition to the older
    warning about removing the high bit on characters.  The first two packet
    characters determine the parity, though the first four are examined for
    unexpected setting of the high bit.  msscom, mssset, mssrcv, msssen.

29. Adjust Tektronix emulator slightly so that SET TERM CLEAR-SCREEN does
    a screen clear using the existing character coloring to write all spaces,
    rather than doing a full reinitialization of the emulator. The text
    emulator is not affected. Since ESC [ 30's; 40's m screen coloring command
    sets the fore- and background color palette registers (7 and 0, resp) a
    screen clear manually or by receipt of ESC [ 2 J will use this palette.
    A terminal reset restores the built-in default palette.

    More changes are expected.

The files are in the Kermit test area, kermit/test/mstibm.boo and
kermit/bin/mstibm.exe on watsun, and T:MSTIBM.BOO on CUVMA.

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

Date: 15 June 1990
>From: Tony Appelget, General Mills Inc, Minneapolis, MN, USA
Subject: New Release of Kermit for HP-3000
Keywords: HP-3000 Kermit

The HP3000 SPL Kermit seems to be badly neglected.  The listing in "Kermit
News number 4" shows your most recent version to be v1.1 dated 85/06/24.  I am
enclosing what I am assuming to be a much more modern version.  It is the
product of a lot of hours put into the v1.0 version over the past five or six
years and works very well here.

All my changes  are listed in comments at the beginning of the program.  A few
of the big changes are:

- Added a HELP function.
- Implementated a very versatile command name abbreviation scheme.
- Implemented 3-byte checksums in addition to the old standard one-byte
  checksums.
- Implemented long packets with a maximum of 2000 bytes.  Decreasing packet
  size in response to packet errors is not implemented.
- This Kermit sets a JCW (program completion code).
- Cleaned up a plethora of small bugs.
- At the insistance of our security types, a file validation scheme was
  built into the program.  No one uses it.  Leaving it in place will cause
  no harm.  It should be removable without too much trouble.

The version number, 2.7, that I have stuck on the program is totally arbitrary
as far as I am concerned.  If my enclosed Kermit meets your standards for
distibution, it would be a feather in my cap for you to do so.

(signed)
Tony Appelget
K0DCF/AFA3AO/AFF3MN

[Ed. - Thanks, Tony, it does, apply feather to cap!  It looks like Kermit News
#4 is shaking a lot of Kermit updates out of the woodwork.  This one replaces
the old 1.1 version from 1985 in the Kermit "D" area as hp3000.*.]

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

Date: Fri Jul 13 13:53:17 1990
>From: Christine M. Gianone <[e-mail]>
Subject: Announcing NCR 9800 Kermit
Keywords: NCR 9800 Kermit

This is to announce a Kermit program for the NCR 9800-4 computer, contributed
by Paul E. Gladden of NCR Corporation, San Diego, CA, USA, for the NCR VE4.0
operating system.  There are separate variations for the IVS and MCS
environments.

Both products are written in the C language, based on C-Kermit 4E with
features added or deleted depending on VRX system capabilities, and NCR
selected product content.  Module names reflect the same usage as in C-Kermit
4E.  New modules have a short explanation.

IVS-Kermit and MCS-Kermit share common source code. MCS-Kermit has two
additional files to interface to the MCS telecommunications facility.  MCS
modules are labeled MCS ONLY.

A large number of files are included.  These have been installed in the "D"
area of Kermit Distribution as ncrker.*.  The file ncrker.doc contains user
documentation and installation instructions.  The file ncrker.jar is a "join"
text archive of the numerous source files, which contains instructions at the
top on how to break it apart.

Many thanks to Paul for submitting this new Kermit implementation.

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

Date: 22 June 1990
>From: Dave Squire, University of California at Davis
Subject: New Release of Kermit for UNISYS (Burroughs) A-Series
Keywords: UNISYS A-Series, Burroughs A-Series

Enclosed is the 1.040 release of our version of Kermit for Unisys A-Series
systems.  This is an upgrade of "B78" Kermit 1.019 from 1986.  The important
new features of this release are: long packets, alternate block-checks, and
a "take" command.  The program has also been modified to use the A-Series
hardware more efficiently.

This release contains the Kermit symbol (written in Algol) and a documentation
file.  We will continue to distribute Kermit directly to A-Series sites who
contact us.  We will also consult with new Kermit users to help them get
started.  There is no fee for either service.  You may refer any Unisys
A-Series users to us.  Also, please feel free to contact me if I can help with
any A-Series questions.

Dave Squire
Computing Services
University of California
Davis, CA  95616-8563  USA
Phone [phone]

[Ed. - Thanks to Dave and to Larry Johnson and Katie Stevens at UC Davis for
their work on this program and for sending in this new version!  It's in the
Kermit Distribution "D" area as uasker.*.  The previous release has been kept
as b78ker.*, in case the new release does not run on the B7800 or on older
Burroughs A-Series machines or operating system releases.  If it is not
necessary to keep the old version, please let us know: does this new version
run on the B7800?  Also, does anybody know the name of the operating system
for these machines?]

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

Date: Sun, 8 Jul 90 0:30:08 MET
Subject: New Kermit Programs for Luxor ABC Series and FACIT DTC/DTC2
>From: Bo Kullmar <[e-mail]>
Keywords: Luxor, ABC-80/800

I am sending you updates for the ABC80 and the ABC800 Kermit. Two members of
the ABC-Klubben have done the work.

Joergen Westman has fixed the repeat prefix handling in the ABC80 Kermit.  It
did not work against Kermit programs that could not do run-length encoding.
(Jorgen with dots over the o.)

Mikael Johansson has updated the ABC800/ABC802/ABC806 Kermit to version 4.11
and included support for FACIT DTC and FACIT DTC2. FACIT DTC/DTC2 is a ABC800
clone.

--Bo Kullmar

[Ed. - Thanks, Bo!  The lux*.* files in the Kermit "C" area have been updated
to the new versions.]

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

Date: Tue, 1990 Jun 26   16:58 EDT
>From: "John F. Chandler"   <[e-mail]>
Subject: New MS Kermit REMOTE PRINT interface with Kermit-370
Keywords: MS-DOS Kermit, REMOTE PRINT Command, IBM 370 Kermit

I noticed from reading Info-Kermit V11 #8 that MS-DOS Kermit 3.02 has a REMOTE
PRINT command.  For those not familiar with the guts of Kermit protocol, I'd
like to remark that this command is essentially a slight modification of the
MAIL command (you can see traces of that history on the screen when you issue
the command), and support exists for the mainframe ends of both in release
4.2.0 of Kermit-370.  A slight modification of the KERMAIL command, renamed
KERMPRT, will do the job (see IKxKER.DOC or IKxKER.PS for descriptions), as I
have already demonstrated on my CMS system.  If there is sufficient interest,
I could add samples of these mainframe commands to the Kermit-370 area, but
the implementations will likely vary widely from site to site.

One of these days, I'll see about implementing a REMOTE PRINT subcommand in
Kermit-370 so a mainframe user connected with a PC as a terminal can make hard
copies on an attached desktop laser printer.  Right now, though, I'm
concentrating on implementing Kermit support for the transparency mode in the
new B2 microcode for the IBM 3174 (about which, more later).
                                    John

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

Date: Tue, 1990 Jun 26   17:34 EDT
>From: "John F. Chandler"   <[e-mail]>
Subject: Kermit-370 support for IBM 3174 AEA
Keywords: IBM 370 Kermit, IBM 3174 AEA

I now have word from IBM that the new release of 3174 microcode is out.  It
is called B2 (that is, Level 2 of Configuration B) and is supposedly
available to all customers with the "B" configuration of the 3174.  As I
understand it, "B" costs extra and requires a bit more hardware (minimum
requirement is model 11L or equivalent), while "A" comes with the box.
Apparently, there are no plans for upgrading "A".  If you have "B"
configuration installed, though, this upgrade should finally make it possible
to run Kermit through the 3174.  I have some documentation about the new
"ASCII Graphics Mode", and I think the necessary Kermit code is pretty
simple.  Indeed, I have already made a stab at it (pending the answers to a
few questions).  I'm looking for volunteers to try out the new feature and
troubleshoot the code.  If you think you want to try it, the first thing to
do is make sure that you (1) have the "B" configuration and (2) have received
and installed the "B2" update from IBM.  I have no idea what the shipping
schedule is like for things like that.  I can send you the Kermit update as
soon as I check on a few details or even sooner if you're really eager.
Meanwhile, let me know if you're interested.
                                  John

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

Date: Fri Jul 13 19:13:27 1990
>From: Christine M. Gianone <[e-mail]>
Subject: VMS Kermit-32 Hints
Keywords: VAX/VMS Kermit

Several people have complained that Kermit-32 has been sending files
incorrectly when the file type is set to binary.  This can happen when the VMS
file has a carriage control attribute; for example, VMS Lotus files are
created this way.  The recent release of Kermit-32 has a new command SET FILE
TYPE BLOCK which seems to get around this difficulty.

Also, judging from many messages received in the past month, many people who
have complained that Kermit-32 did not pick up their terminal name correctly
("No default terminal line for transfers") have not obtained version 3.3.126,
announced in Info-Kermit V11 #8, which fixes that problem, as well as
problems related to spawning and batch operation.

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

Date: 22 Jun 90 13:33:16 GMT
>From: [e-mail] (R.E. Sonneveld, [phone], PTT Research)
Subject: How to Create a Kermit Connection over X.25 from VAX/VMS?
Keywords: VAX/VMS Kermit, X.25 Network

Wanted: Kermit communication over X.25 (with for example EuroKom) with my
'own' VMS system as my home base.  In other words: is it possible to start
Kermit on the VAX, then SET HOST/X29 to e.g. EuroKom, then start Kermit at the
remote side and establish the connection?

We have tried the following:

 1) loopback one DECserver port-X to port-Y
 2) define the DECserver ports to be 'transparent'
 3) define DECserver port-Y to autoconnect
 4) with LCP, create LTA port pointing to the DECserver port-X
 5) define default port for Kermit (KER$COMM), pointing to the LTA device

Starting Kermit and using the default port will result in a connect via the
DECserver loopback to the original VMS-system, thus creating the possibility
of establishing a X.25 connection.  This works great! The major problem and
the reason why we won't release this 'facility' is SECURITY: whenever a
connection is established by one person and this connection aborts
unexpectedly, than the next user who tries to make a connection using this
default port gets the session of the first user!

Any help greatly appreciated!

Rolf Sonneveld        E-mail: [e-mail]

PTT Research          *      Tele phone : [phone]
Neher Laboratories,   *      Tele  fax  : [phone]
The Netherlands       *      Tele   x   : 31236 prnl nl

[Ed. - This is a common question from Europe.  As yet, neither C-Kermit/VMS
nor VMS Kermit-32 contain any explicit support for VAX/PSI or X.25 in any of
its forms.  We are hoping that someone with an X.25-connected VAX/VMS system
will add this support.  Volunteers?]

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

Date: Fri, 29 Jun 90 05:27:31 EDT
>From: Erez Zadok <[e-mail]>
Subject: Kermit for Microsoft Windows
Keywords: Microsoft Windows Kermit

I'm running now WIN100 V2.0 and it's a definite advantage over older
versions.  I have a few comments and questions.

COMMENTS:

(1) Good job!  I like it in the GUI environment.  I actually downloaded
files while playing Solitaire.  Multitasking on my desk.  I liked the fact
that there was a running number of packets on the minimized kermit icon so I
can always keep a watch over the file transfer.  I liked the beep at the end
of the transfer and the Alert that popped up for me at the end.

(2) This is definitely the wave of the future.  I think windows kermit
*will* be a major communication package to use on ms-dos platforms and will
bite a large chunk of the regular ms-kermit.  But there's a lot to be done.
With Windows 3.0 out now, you have all the reasons in the world to make this
package at the same level of MS-Kermit 3.02.

(3) The first things that struck me as in need of improvement were (and bear
in mind that I know MS-Kermit 3.02 *very* well):

- Not enough variety of fonts to choose.  My VGA does not fit 80
  columns with this font (courier) and the other font (preview) is
  way too small.  Maybe the fonts are windows dependent and not
  depend on kermit?
- No apparent way to map the keyboard,  Esp. swapping ` and ESC, and
  mapping CAPSLOCK to CTRL.
- No dialup scripts to use.
- Not enough colors to choose from (esp. the high intensity ones.)
- Win100 does not use the new builtin help feature in Windows 3.0.

(4) Then, upon closer look, I found that the next few items should be
improved (lower priority in my opinion):

- Support for long packets.
- When changing a font or its size, I would like not to have to
  restart kermit.
- I would like to see a way to set the number of lines as an input
  from the keyboard and not only by resizing the window.
- I would like to cut from the kermit screen by using the mouse only
  and marking and cutting.  The current way is not as clean.
- Screen refreshes are not as fast (maybe that's due to my
  hardware configuration and lack of memory.)

(5) The vt100 emulator works well with all kind of applications including
EMACS and curses-based applications.

(6) Possible serious bug:  At one point I got an alert "out of token memory"
error or something, and kermit aborted.  My line was not disconnected.  I am
running Windows 3.0 in real mode (no extended or expanded memory yet on my
286) and it seems that kermit ran out of memory of some sort.  In either
case it should not have aborted but only gave an alert.  Maybe this error is
unrecoverable...

[Ed. - This is one of several messages about Bill Hall's new VT100-emulating
Kermit for Microsoft Windows.  All of them contained similar questions and
favorable comments.  Bill replies as follows:

Most of the suggestions are on my worklist to do - someday!.  Life if pretty
busy since I work a regular job and also write the Windows column for PC
Magazine.  But, I do want to improve the version I have put up as a beta.

Please be patient.  There is no help because it is a 2.0 application.  The
font is terrible, but don't blame me for this.  I would have to design a
complete series of fonts for a range of displays if I could not use the ones
supplied by Windows.  Maybe some kind soul will eventually help me with this
really non-trivial effort.

The screen update is slow.  As you know, everything in Windows is done in
software so this is a problem.  However, I'm sure I can do something to
improve it a bit, and I'll give it a try.

The implementation of the Kermit part is confined at the present to the
standard stuff.  It may be archaic, but it takes a lot of time to get all the
new features working.  Also, making Kermit work smoothly in Windows is quite a
chore.  It is so hard that I'm doing an article on it using the level I have
developed up to now as the example.  When the article is done, I will then
take up the task of upgrading the program.]

[Ed. again - By the way, Bill has sent in a slightly updated version of the
program, and some preliminary documentation: win100.msp (to be viewed in
Microsoft Paint) and win100.wri (for Microsoft Write).  They document just the
emulator part of the program, not the file transfer part.]

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

Date: Tue, 26 Jun 90 23:43:20 CST
>From: BOB SHERMAN <[e-mail]>
Subject: External Kermit Driver
Keywords: MS-DOS Kermit 3.0

Greetings:
  I am running a BBS on an IBM PC.  Do you have any suggestions
  for a external kermit driver?  Thanks for any help.

                                         Bob Sherman

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

Date: Mon, 25 Jun 90 11:33:39 CDT
>From: [e-mail] (J. Philip Miller)
Subject: Kermit for Atari Portfolio?
Keywords: Atari Portfolio Kermit

In a review of the Atari Portfolio - a pocket size, almost DOS PC - there was
mention of a modified version of Kermit that would work on the Portfolio.
Could some point me to where it is available?

This machine runs the DIP Operating System, which is very close to DOS 2.11.
I understand it is a small patch to the regular PC version.

-phil

J. Philip Miller, Professor, Division of Biostatistics, Box 8067
Washington University Medical School, St. Louis MO 63110
[e-mail] - Internet  [phone]
uunet!wuarchive!wubios!phil - UUCP [phone](FAX)  C90562JM@WUVMD - bitnet

[Ed. - Yes, and please point us at it too!]

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

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

From cmg  Fri Aug  3 14:50:25 1990
Return-Path: <cmg>
Received: by watsun.cc.columbia.edu (5.59/FCB)
    id AA29240; Fri, 3 Aug 90 14:50:25 EDT
Date: Fri, 3 Aug 90 14:50:24 EDT
From: Christine M Gianone <[e-mail]>
To: Info-Kermit
Subject: Info-Kermit Digest V12 #2
Reply-To: [e-mail]
Queries-To: [e-mail]
Message-Id: <[e-mail]>

Info-Kermit Digest         Fri, 3 Aug 1990        Volume 12 : Number 2

Departments:

  ANNOUNCEMENTS -
        Another Update of the MS-DOS Kermit 3.02 Test Release
        Version 8.12 of PRIME Kermit Now Available
        New Documentation Available for VAX/VMS Kermit-32 3.3.126
        New Test Release of DEC Rainbow Kermit

  MS-DOS KERMIT -
        MS-DOS Kermit 3.0x and Microsoft Windows 3.0
        MS-DOS Kermit 3.0 Hints
        MS-Kermit Server and Hayes 2400bps Modems?

  KERMIT-370 -
       IBM Mainframe Kermit and Trailing Blanks
       IBM Kermit 4.2 and tn3270

Digest submissions may be sent to [e-mail],
requests for addition to or deletion from the Info-Kermit subscriber list to
[e-mail] or to [e-mail].

Kermit files may be obtained over networks and by mail order.  On the
Internetwork, use FTP to log in to host WATSUN.CC.COLUMBIA.EDU, a SUN-4/280
running UNIX (SUNOS 4.1), IP host number 128.59.39.2.  Login as user anonymous
(note, lower case), any password, and GET or MGET (MULTIPLE GET) the desired
files.  The Kermit files are in directories kermit/a, kermit/b, kermit/c,
kermit/d, and kermit/e.  Test versions are in kermit/test.  Binaries are in
kermit/bin (use ftp in binary mode).  You can also get Kermit files over the
BITNET/EARN network; to get started send a message with text HELP to KERMSRV,
the Kermit file server, at host CUVMA.  For detailed instructions, read the
file kermit/a/aanetw.hlp (AANETW.HLP on KERMSRV).  To order by mail, request a
complete list of Kermit versions and an order form from Kermit Distribution,
Columbia University Center for Computing Activities, 612 West 115th Street,
New York, NY 10025 USA.

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

Date: Wed Aug  1 19:56:09 1990
>From: Christine M. Gianone <[e-mail]>
Subject: Another Update of the MS-DOS Kermit 3.02 Test Release
Keywords: MS-DOS Kermit 3.02

>From Joe Doupnik.  Changes since the version announced in Info-Kermit V12 #1
are listed below.  Items 38 and 39 will be of interest to Honeywell users for
supporting connections to the Honeywell DPS-6 (see article by Frank Dreano in
Kermit News #4) -- they remove the need for a custom version of MS-DOS Kermit
to communicate with the the Honeywell systems.  Please report any problems to
Joe at [e-mail] or [e-mail].

30. Add correction to ensure NUL and DEL are passed through when printing
    transparently. msxibm

31. Revise REPLAY filespec a little. Previously at the end of the file any
    key would exit Connect mode. Now all keys remain active so that screen
    dumping and screen rollback function; ALT-X and Control-C (emergency
    bailout) exit Connect mode. msxibm

32. Internal revisions to details of handling 75/1200 baud split speeds.
    Previously, filling the receiver buffer would cause an XOFF to be sent
    at 1200 baud rather than at the correct 75 baud. Now the XOFF character
    is sent at 75. A pseudo-queue is present to prevent conflicts of using
    the timer chip for beep or regular 75 baud output when the receiver
    interrupt occurs (and resulted in the XOFF being sent at interrupt level
    rather than at task level). The queue makes the XOFF be sent at task level
    and at the proper 75 baud rate. Dan Norstedt had the idea, this queueing
    stuff is my solution. 75 baud output is done as a software UART. msxibm

33. Details here and there to save code segment space, from Dan Norstedt.

34. Add terminal type of VT100. This performs identically to a VT102 except
    the response to the type inquiry from a host is ESC [ ? 1 c (a VT100).

35. Found and fixed a protocol problem present in MSK 3.0 to date. If an I
    packet is sent to a server Kermit which does not understand I packets
    the resulting Error packet from the server is to be taken as a forgivable
    error, rather than otherwise being a fatal one. The version 3.0 and 3.01
    code forgot to forgive. I packets are sent by GET and REMOTE commands.
    Fixed on 19 July. mssser.

36. Remove VTxxx response to CSI [ .. R. That should not have been present.
    Thanks to Ted Medin for discovering its presence.

37. Add 80/132 column support for Paradise Autoswitch EGA Mono board, thanks
    to David Zielke of Duke Univ. msyibm

38. Add two new commands

    SET SEND DOUBLE-CHAR <number between 0 and 255>
        which sends this character twice in a row in outgoing packets.
        The doubling occurs as packet bytes are being sent to the
        communications channel and hence does not occur during packet
        construction. This accomodates communications devices which
        need doubling to let through a single copy. The doubling
        will not appear in the packet log. Padding characters are
        not affected by this command since padding is to be discarded
        at the other end anyway.

    SET RECEIVE IGNORE-CHAR <number between 0 and 255>
        which ignores this character in received packets. This
        accomodates communications devices which may insert a
        character into a stream, such as a Line Feed inserted before a
        Carriage Return. The ignored character will not appear in the
        packet log. Note that NUL (0) and DEL (127) are normally
        ignored even without this command.

39. Add terminal type of HONEYWELL to the emulator. This is a VT100 with
    two special responses. A received ENQ character, decimal 5, causes the
    emulator to send the 14 characters

        '7813  P GC  A' 03h

    and receipt of  ESC y  causes the emulator to send the 27 characters

       ESC '[8p  OT' 03h ESC '[y7813  P GC  A ' 03h

    where the quote marks (') above are not sent but are present so we can
    see the spaces which are sent; other spaces are for reading convenience.
    03h is Control-C, a binary value 3. The terminal ident response is VT100.
    These Honeywell VIP7809 emulation features are from Frank Dreano,
    [e-mail].

40. Modify the internals for SET KEY LK250 to result in checking for an
    active external LK250 driver and if found activate the LK250 usage in
    Kermit. If the driver is not found the message "?LK250 keyboard external
    driver is not active." is displayed. Note that to obtain the default
    LK250 key mappings the user must say SET KEY CLEAR after the above
    command, and then add any local definitions. Tnx to Terry Kennedy. msuibm

41. In command WAIT <timeout> \CD \CTS \DSR   let the backslash character
    be optional, to merge syntax with C Kermit 5A. mssscp

42. Add further Honeywell terminal type modifications from Frank Dreano:
    - change invocation ESC y to be ESC [ y     (see item 39 above)
      This will cause loops if the host echoes the response.
    - add  ESC `  (accent grave) clears screen and homes the cursor.

43. Revise slightly the query for the active Code Page, and the table of
    character sets for use by SET FILE CHARACTER-SET, to be system dependent
    so that MS-DOS in Japan can be used more effectively. That MS-DOS lacks
    the concept of Code Pages. Thanks to Hirofumi Fujii for the suggestions.

44. Add another host invocation control sequence to the text terminal emulator.
    Reception of  CSI Pn;...Pn ~  invokes a macro named PRODUCT, if it
    exits, and sets variables \%1, \%2, and so forth up to \%9 to be the ascii
    version of the numeric parameters Pn above. Omitted parameters are taken
    to be zeros. Only as many variables are set as numeric parameters, and
    script item ARGC is one larger than this quantity. If macro PRODUCT does
    not exist only the \%x items are changed. Connect mode is not reentered
    automatically if the macro exists. This is very similar to TERMINALR and
    TERMINALS, except for the variable setting part.
    The invocation sequence may change so don't write it into applications
    until Kermit is released again. It is not invocable from the keyboard,
    because of the needed parameters. mssset.asm, msyibm.asm, mszibm.asm.

45. Correct a keyboard translation problem. Control codes could be translated
    to printable characters for a few National Replacment Character sets,
    because that was where the special graphical symbols are located on the
    IBM PC display adapter. This has been corrected to never translate control
    codes.

46. Slightly revise script INPUT and REINPUT command sensing of timeouts to
    do the time reading after each serial port character reading operation.
    This might cure complaints of REINPUT 0 reporting premature FAIL status.

47. If disk reading fails while sending a file tell the receiver to dispose
    of the file with a Delete status, rather than the previous status of
    just end-of-file. There is no other simple way of informing the receiver
    of such a local problem. Other files in a group will be processed normally.

  More changes are expected.

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

Date: Fri Aug  3 10:46:17 1990
>From: Christine M. Gianone <[e-mail]>
Subject: Version 8.12 of PRIME Kermit Now Available
Keywords: PRIME Kermit

>From Matthew Sutter of Lincoln National Corporation in Fort Wayne, Indiana,
USA, comes version 8.12 of PRIME Kermit, an upgrade of version 8.00 that was
prepared by John Horne of Polytechnic South West in Plymouth, England.

The major feature of version 8.12 is support for local-mode (dialout)
operation using the AMLC lines.  CONNECT, GET, FINISH, and BYE commands have
been added, as well as the script commands INPUT, OUTPUT, CLEAR, and PAUSE.

This version also contains fixes to repeat character processing and sliding
windows, but the sliding window feature still needs more work in order to
interoperate with MS-DOS Kermit 3.0 or C-Kermit 5A.  This work is underway,
watch Info-Kermit for further announcements.

The new files are in kermit/d/prime8.* on watsun, and PRIME8.* on CUVMA.
There is, as yet, no new documentation.  Thanks to Matt for his work and for
contributing it to the Kermit collection!

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

Date: Wed Aug 1 18:29:49 1990-EDT
>From: Christine M. Gianone <[e-mail]>
Subject: New Documentation Available for VAX/VMS Kermit-32 3.3.126
Keywords: VAX/VMS Kermit

The VAX/VMS Kermit-32 chapter of the Kermit User Guide has been updated to
include all the information about the new release, and the help text has also
been updated.  Thanks to Jonathan Welch of the University of Massachusetts for
his help in clarifying the actions and interaction of the SET FILE BLOCKSIZE
and SET FILE TYPE commands, and for proofreading the manual.

The files for the new manual are VMSHDR.MSS and VMSMIT.MSS (Scribe source),
VMSMIT.DOC (plain ASCII text) and VMSMIT.PS (Postscript).  The help text is in
VMSMIT.RNH (Runoff source).  Tape B (kermit/b, etc etc).

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

Date: Thu Aug 2 13:01:34 1990-EDT
>From: Christine M. Gianone <[e-mail]>
Subject: New Test Release of DEC Rainbow Kermit
Keywords: MS-DOS Kermit, Rainbow Kermit, DEC Rainbow

>From Robert Weiner, a new version of Kermit for the DEC Rainbow, based on
the system-independent parts of the July 22nd MS-DOS Kermit 3.02 test release.
The Rainbow version lacks many of the IBM-specific enhancements that appeared
in MS-DOS Kermit 3.0, like international character sets, instantaneous screen
rollback, etc, but these MAY be added before the final release of this
program.  The system-independent features -- script programming enhancements,
sliding windows, long packets, VT200/300 emulation (it's still at the VT102
level), etc.

Thanks to Rob for keeping the Rainbow up to date!  The files are in
kermit/a/mstrb1.boo ("BOO" file to be un-boo'd into an .EXE file using any of
the MSBPCT files) on the Internet or MSTRB1 BOO on BITNET KERMSRV at CUVMA.
For internet binary-mode FTP access only, also kermit/bin/mstrb1.exe.

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

Date: Thu, 2 Aug 90 11:18:30 PDT
>From: [e-mail] (William Hall)
Subject: MS-DOS Kermit 3.0x and Microsoft Windows 3.0

Just tried MS-DOS Kermit 3.0 in enhanced mode Windows.  I began by running a
DOS shell then running Kermit.  Did not bother with a PIF file.  I changed the
settings to run from exclusive to background.  You can get to these setting
with ALT-SPACE, then moved it to a Window.  For fun, I ran vttest on UNIX and
checked the character set, especially the one for DEC special graphics.  They
looked as expected.

Then I tried a long file transfer.  I made the window iconic, and the file
transfer ran in the background to completion with no errors.  At the end, the
bell beeped to let me know it was done.

So it works and quite well to the extent that I tested it.

--Bill

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

Date: 1-AUG-1990 20:33:04.67
>From: Joe Doupnik <[e-mail]>
Subject: MS-DOS Kermit 3.0 Hints
Keywords: MS-DOS Kermit 3.0 Troubleshooting

[Ed. - This is extracted from a reply by Joe to a user who reported a
nonfunctioning Kermit on a Compaq computer.]

One common item is an internal modem which fails to follow the normal rules of
how to behave like a regular serial port.  Another is two devices are having a
small battle for an IRQ line or a memory (port) address.

MS-DOS Kermit 3.02 (not 3.2) is strictly development software, as indicated in
the note file MSR302.UPD and on the startup banner.  The REMOTE command
problems you report fall into the category of fixed, broken, and then fixed
again (sigh).  In all of the broken cases Kermit would retry many times and
that takes up to a minute or so to finish.  While that is happening one side
can send an XOFF to the other and forget to send a matching XON later; Kermit
waits 10 seconds to figure out this situation when it needs to send and breaks
through regardless.  So, this "flow control deadlock" can add to the waiting
interval, but it's better than being told to never speak ever again.

Another situation, which happened to me a couple of years ago, was the poor
hard disk controller had a conflict with another board and every once in a
while the machine would hang waiting on the hard disk for 10 minutes or more.
Usually I had to push the big Red switch. When Kermit has to go to the hard
disk then these kinds of things can happen.

Generally, I try to sort out the problem by trying Connect mode between
machines right away. If that works then I know the communications line part is
basically ok.  If packets fail then I say SET DEBUG ON and SET DISPLAY SERIAL
to watch what's happening during a file transfer or REMOTE command (REMOTE WHO
is my favorite "protocol" quicky, no disk access).

Let's suppose the Compaq is in sad shape.  My suggestion is to backup the hard
disk contents and ensure they are correct (say to DOS VERIFY ON to help).
Then do a low level format of the drive (yow!) and a DOS FORMAT with the
correct version of DOS.  Put things back on the hard disk and keep your
fingers crossed.  Double check the settings of the boards too.  Unload the
likely mountain of favorite TSR's and see if things work.  If they do then
start adding them back one at a time and retesting.  Make sure that CONFIG.SYS
has BUFFERS=20 or so and FILES=20 or so.  Watch out for Desqview because it
has troubles remembering that a communications program needs to service
interrupts from the serial port.  Don't mix DOS files from different
releases/manufacturers.

Ensure that parity is the same on both machines, NONE being better than any
other flavor (Kermit does it's own checking in a much more secure way).  Don't
use MODE COM1:....,P with that ",P" (for Printer waiting) on the same port as
the communications channel because DOS will grab the port and won't release
it.  Watch for mice drivers nibbling on the same serial port.  In short, take
the machine down to bare metal and rebuild it slowly from a consistent set of
original DOS floppies (put write-protect tabs on them).

Did I forget to mention virii?

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

Date: Tue, 02 May 89 16:54:34 CDT
>From: Barry Pederson  <[e-mail]>
Subject: MS-Kermit Server and Hayes 2400bps Modems?
Keywords: MS-DOS Kermit Server Mode

Hi, we've been using MS-Kermit for a while now, and it's been incredibly
useful, but we're having a slight problem.  We have some IBM model 30-286
machines connected to Hayes 2400bps external modems.  They work fine except
when we try to have the modems answer the phone while Kermit is in server
mode.

We have a script set up to set the speed to 2400, parity to none, then we
output ATS0=1\13 to the modem, and go into server mode.  Sometimes it works,
but a lot of the time, when the phone rings the modem will drop down to
1200bps.

In a previous Kermit Digest, I thought I saw something about C-Kermit having
problems with Hayes modems, does MS-Kermit have a known incompatibility
between it's server mode and a Hayes modem?

I suspect that Kermit is working fine, but the Hayes is doing something screwy
(we've tried MS-Kermit 2.31 and 2.32/a).  I'd really appreciate any
suggestions on how to keep the Hayes from slowing down.

Thanks.

Barry Pederson    University of North Dakota School of Medicine
     [e-mail]     or    [e-mail]

[Ed. - When MS-Kermit is in server mode, it times out every 30 seconds or so
and transmits a negative acknowledgement packet (the familiar "^A# N3").  It
is likely that the NAK packet is confusing the modem.  The workaround is to
give MS-DOS Kermit the SET TIMER OFF command before putting it in server mode,
which is safe as long as the other Kermit will do timeouts (some, like IBM
mainframe CMS Kermit, cannot).  In MS-DOS Kermit 2.32/A or later, you can
disable server command wait timeouts without turning the timer off, by using
the command SET SERVER TIMEOUT 0.]

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

Date: 6-Jul-90 22:03:17-GMT
>From: Randy [e-mail]
Subject: IBM Mainframe Kermit and Trailing Blanks
Keywords: IBM 370 Kermit, VM/CMS Kermit, Blanks

We're running Kermit CMS and MS Kermit to transfer files with a record length
of 1500 bytes. What's happening is that the records have trailing blanks.
Kermit strips these blanks off. We need them to remain intact for input into a
commercial package we are running under DOS. Is there any way to keep the
blanks from being stripped? I know that you can specify LRECL and RECFM at the
CMS level but that is for files being received in CMS.  We need the same
capability for MS-DOS Kermit.

Randy Schirmer
West Chester University, West Chester, PA
215-436-1094, RSCHIRME@WCU

[From John Chandler - When the file type is TEXT and the recfm is F,
Kermit-370 strips off trailing blanks from each record before sending a file.
In order to keep trailing blanks in a downloaded file, you can convert it to
RECFM V in CMS before sending it, e.g., by using COPYFILE with the RECFM V
option.  This is true of versions from 4.1 onward.]

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

Date: Wed, 20 Jun 90 08:33:25 -0500
>From: C Lance Moxley <[e-mail]>
Subject: IBM Kermit 4.2 and tn3270
Keywords: IBM 370 Kermit, tn3270

I just assembled Kermit/370 on an IBM 3081 running VM/SP 5.  The program
assembled just fine.  But, I have no idea how to set things to work through
tn3270. I've used MS-DOS Kermit for quite a while now and also am very
comfortable with C-Kermit, but this seems to be alot different. I would
appreciate any help you can give on this.  I also have the ability to use 3708
protocol converters, but I don't think there is any way I can put them in
line-by-line mode. I would really prefer to use tn3270. If you are the wrong
person to ask this to, please direct me to the right person. Also if there are
any examples anywhere, let me know. I couldn't find anything on watsun.

Thanks for a very fine product. The other versions that I use are the best of
their kind. Especially the new C version.

                                Thanks,
                                Lance

[From John Chandler - Actually, no, I haven't used tn3270 myself, but Bob
Babcock has -- and from a Unix system only.  It should have been essentially
the same as your attempt, but it worked.  The special considerations are only
two: you must SET CONTROLLER SERIES1 by hand, and you cannot (apparently)
upload using long packets.  The system in question was a CONVEX, as opposed to
a SUN, but I think the tn3270 would have been the same.]

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

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

From cmg  Tue Aug 28 16:03:24 1990
Return-Path: <cmg>
Received: by watsun.cc.columbia.edu (5.59/FCB)
    id AA28887; Tue, 28 Aug 90 16:03:24 EDT
Date: Tue, 28 Aug 90 16:03:23 EDT
From: Christine M Gianone <[e-mail]>
To: Info-Kermit
Subject: Info-Kermit Digest V12 #3
Reply-To: [e-mail]
Queries-To: [e-mail]
Message-Id: <[e-mail]>

Info-Kermit Digest         Tue, 28 Aug 1990        Volume 12 : Number 3

Today's Topics:

         Duplicate Copies of Info-Kermit Digest V12 #1 and #2
         Proposed Kermit Extension for SET FILE TYPE
          And ANOTHER New Test Release of MS-DOS Kermit 3.02
        A New Version of Kermit for OS/2 Presentation Manager
               New Release UCPECAN Kermit V1.1
             MS-Kermit 3.0x and German telephones
                 Looking for Stories


Digest submissions may be sent to [e-mail],
requests for addition to or deletion from the Info-Kermit subscriber list to
[e-mail] or to [e-mail].

Kermit files may be obtained over networks and by mail order.  On the
Internetwork, use FTP to log in to host WATSUN.CC.COLUMBIA.EDU, a SUN-4/280
running UNIX (SUNOS 4.1), IP host number 128.59.39.2.  Login as user anonymous
(note, lower case), any password, and GET or MGET (MULTIPLE GET) the desired
files.  The Kermit files are in directories kermit/a, kermit/b, kermit/c,
kermit/d, and kermit/e.  Test versions are in kermit/test.  Binaries are in
kermit/bin (use ftp in binary mode).  You can also get Kermit files over the
BITNET/EARN network; to get started send a message with text HELP to KERMSRV,
the Kermit file server, at host CUVMA.  For detailed instructions, read the
file kermit/a/aanetw.hlp (AANETW.HLP on KERMSRV).  To order by mail, request a
complete list of Kermit versions and an order form from Kermit Distribution,
Columbia University Center for Computing Activities, 612 West 115th Street,
New York, NY 10025 USA.

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

Date: Tue Aug 28 17:44:54 1990-EDT
>From: Christine M Gianone <[e-mail]>
Subject: Duplicate Copies of Info-Kermit Digest V12 #1 and #2

Please disregard any duplicate copies of recent Info-Kermit
Digests.

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

Date: Thu Aug 16 17:44:54 1990-EDT
>From: Christine M Gianone <[e-mail]>
Subject: Proposed Kermit Extension for SET FILE TYPE
Keywords: Kermit Protocol, Labeled File Type

Kermit programs presently differentiate between text and binary files via
the SET FILE TYPE command.  When the file type is TEXT, the Kermit program
that is sending the file converts the file's record format and character set
from its local form to a standard form, and the receiving Kermit program
converts from the standard form into its own local record format and character
set.  When the file type is BINARY, the file is sent as-is, byte for byte.

These two ways of handling files are sufficient in many cases, but fall short
when one or both computers has a complex file system, such as the Macintosh or
DEC operating systems like VAX/VMS.  The Kermit protocol includes a mechanism
for transmitting a file's attributes in a generic way, but these attributes
are of little use when the file is being received by a computer with a simple
file system, such as UNIX or MS-DOS, that can't do anything with them.  And
they are not sufficient to convey every conceivable bit of information about
about every kind of file on every kind of computer.

To allow a complicated file to be transferred, a new file type is proposed:

  SET FILE TYPE LABELED

Notice the spelling of "LABELED" (only one L between the E's).  When this
setting is in effect, the sending Kermit sends not only the file's data, but
also system-dependent structural information about the file.  Since this
information can be quite lengthy, it is sent as if it were file data, in data
packets preceding the actual file data, rather than in attribute packets.  All
of this information is sent in binary mode (no conversions).

The receiver of the file can elect whether to act upon the label information,
or simply store it.  Kermit programs for simple file systems need no changes,
and can still act as repositories for labeled files, to be sent back later to
the system of origin.  On the other hand, labeled file transfers between like
systems (e.g. two VAX/VMS computers) will result in the reception of a file
with all the correct characteristics.

There are two possible modes of operation.  The first (and safer) mode
requires human intervention on a per-file basis, but an automatic mode is also
possible.

DEFINITIONS

A "bare" file is a file stored on disk that does NOT contain, as part of
its contents, Kermit-constructed label information.

A "labeled" file is a file stored on disk whose contents include
Kermit-constructed label information.

FORMAT OF A LABELED FILE

This description applies to a labeled file as stored on disk and to a bare
file that has label information added to it by a sending Kermit.

  BANNER  The literal text string "KERMIT LABELED FILE:", just the twenty
          characters within the quotes including the trailing colon, in 7-bit
          ASCII.  ASCII is used even on non-ASCII systems (like IBM mainframes
          with EBCDIC).

  IDLEN   A 2-byte ASCII decimal numeric length field, with leading zeros if
          necessary, for example "02".

  SYSID   The system ID, one of the codes listed on pp.275-278 of the Kermit
      book.  This is a string of 1 to 99 ASCII characters (but typically
          1-3 characters), for example "D7" for VAX/VMS.  The length of the
          SYSID field is given by the preceding field (IDLEN).

  LBLEN   A 2-byte ASCII numeric length field, with leading zeros if
          necessary, for example "00", "02", "09", "99".

  LABEL   A label field, 1 to 99 ASCII characters.  The length is given by
          the preceding length field (LBLEN).  The LABEL field contains the
          name of the file descriptor data that follows.

  VALEN   An 8-byte ASCII numeric length field, with leading zeros if
          necessary, for example "00000512".  Zero ("00000000") is a
          permissible length for a value.

  VALUE   The value associated with the label, 0 to 99999999 bytes of
          information about the file in system-dependent format.  The labels
          and the format and layout of the associated values for each system
          type should be clearly defined and documented.

     The sequence (LBLEN, LABEL, VALEN, VALUE) may be repeated for as many
     labeled values are needed (if VALEN is zero, then VALUE is omitted).

  CONTENT The file's contents, encoded in whatever form that, in combination
          with the labeled values, allows for its eventual reconstruction in
          its original form.

All fields in a labeled file are subject to whatever encoding, prefixing, or
compression options have been negotiated by the two Kermit programs.

REQUIRED LABELS

The following labels (composed of ASCII uppercase letters) are reserved, and
are required in every labeled file:

  VERS    The operating system version, e.g. "5.3-1".  If there is no version
          to be specified, this label must still be present, but with a
          zero-length value.

  DATA    This is the final label.  It always has a zero-length value, which
          is followed immediately by the file's contents, as defined above.

EXAMPLE

A hypothetical example for VMS (ignore the indentation and line breaks;
the length fields are marked with L's):

                      LL  LL    LLLLLLLL     LL   LLLLLLLL
  KERMIT LABELED FILE:02D704VERS000000055.3-103FAB00000512<512 bytes here>
  03ACL00000723<723 bytes here>02DATA00000000<file's contents here>
  LL   LLLLLLLL                LL    LLLLLLLL

Note: FAB and ACL are not necessarily real labels.

EFFECTS ON THE KERMIT PROTOCOL

When SET FILE TYPE LABELED is in effect, the sending Kermit should include
the file type (") attribute, specifying a type of binary (B), if attribute
packets have been negotiated.  Otherwise, there is no effect on the protocol
at all.  In particular, a label-wise Kermit program can interoperate perfectly
well with another Kermit program that is completely ignorant of labeling, in
which case the latter program simply "archives" or "unarchives" the file,
labels and all (provided the user remembered to place it in binary mode).

This proposal does not rule out the system-independent type of file archiving,
based on file attribute packets, that is described in the Kermit book.
However, if the "system-dependent" attributes suggested by this proposal can
be worked out in a sufficiently generic fashion, this may lead to a more
effective type of transmission of complex files between unlike systems that
share similar types of file characteristics (block size, record format,
character set, carriage control, etc).

On the other hand, for the first pass at an implementation (for VMS), it might
make more sense to simply have a single system-dependent label, like "FAB",
whose value is simply the File Access Block, and perhaps another one like
"ACL" for its Access Control List.  The two approaches do not rule each other
out.

USER INTERFACE

When SENDING a file, the user should first determine whether it is a bare file
or a labeled file.  This can be done by visual inspection (looking at the
first 20 bytes), or from memory (e.g. because all labeled files have a
particular filetype, or are kept together in a certain directory).  Then:

  (a) If it is a bare file, use SET FILE TYPE LABELED if you want to send
      label information too.

  (b) If it is a labeled file, use SET FILE TYPE BINARY.

When receiving a file, use SET FILE TYPE LABELED if you want labels in the
incoming file to be interpreted and applied, and:

  (a) The other Kermit is sending a bare file from a like system using SET
      FILE TYPE LABELED, or:

  (b) The other Kermit is sending a labeled file, of the receiving system's
      system type, from any kind of system, without SET FILE TYPE LABELED.

The receiving Kermit program that has been given a SET FILE TYPE LABELED
command must inspect the incoming data.  The first 30-36 bytes of the first
packet contain the BANNER, IDLEN, SYSID, and the first LBLEN, and LABEL (which
should be "04VERS").  If these five items are in correct format, and the SYSID
matches the program's own, then the program will accept the file in labeled
mode.  Otherwise, it will treat it as a binary file and store all the data,
including BANNER, SYSID, LABELs, VALUEs, and all length fields.

If a receiving Kermit program has accepted the file in labeled mode, but then
encounters an unknown label or other inconsistency in the labeled file format,
it must interrupt the file transfer (by putting an X in the data field of the
first available ACK) and discard the file.  This is because it cannot be
expected to back up and undo whatever label interpretation it has already done.

It is also conceivable that "similar" systems -- such as the DEC operating
systems VMS and RSX-11 -- might be able to honor each other's labels.  This
eventuality should be allowed for, possibly with SET commands.

At the discretion of the programmer, a command such as SET FILE
LABEL-DETECTION { AUTOMATIC, MANUAL } could be installed.  If so, the default
must be MANUAL, that is, processing of labeled files occurs only if the user
asks for it explicitly.  For an arriving file, AUTOMATIC mode would detect the
BANNER, SYSID, and first LABEL and go into action as if the user had SET FILE
TYPE LABELED.  When sending a file, the program would avoid adding surrounding
label information if the user had already SET FILE TYPE LABELED.  This sort of
thing is obviously dangerous, and users should be cautioned about it.

POSTPROCESSING

Separate programs should be provided to translate a labeled file into a real
file, to be used in case the user forgot to SET FILE TYPE LABELED, or the file
was deposited by means other than Kermit.  Such a program might have two
options (or come in two forms): interpret the labels, and simply strip the
labels.

ACKS

Thanks to Terry Kennedy and Frank da Cruz for suggesting this idea, and to Joe
Doupnik, John Chandler, and Paul Placeway for many valuable suggestions.
Comments welcome!

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

Date: Mon, 27 Aug 90 10:13:45 EDT
>From: Christine M. Gianone <[e-mail]>
Subject: And ANOTHER New Test Release of MS-DOS Kermit 3.02
Keywords: MS-DOS Kermit 3.02

>From JRD's update notes since V12 #2:

48. Add recognition of IBM PC video boards STB VGA/EM Plus (Tseng 4000)
    and Everex Viewpoint EV-678, from Terry Kennedy. The list of boards known
    to Kermit for switching between 80 and 132 columns is now:
    ATI EGA Wonder
    AT&T
    Everex Viewpoint EV-659, FVGA-673, EV-678, Micro Enhancer Deluxe
    Paradise AutoSwitch EGA Mono
    STB VGA/EM (Tseng TVGA)
    STB VGA/EM Plus (Tseng 4000), VGA/EM-16, VGA/EM-16 Plus
    Tseng Labs EVA board w/132-col kit installed
    Tseng Labs UltraPAK mono/Hercules w/132 column modes
    Video 7 Vega Deluxe w/ 132X25.COM driver installed and Video 7 VGA

49. Add a facility to the keyboard translator.  Let key definition strings
    of the form {\Kverb other material} activate an existing Macro if and
    only if the verb is not in the list of those predefined for the keyboard
    translator.  If "verb" matches the name of a regular Kermit Macro execute
    the Macro and stay on the Kermit command line; thus a CONNECT command is
    needed to return to Connect mode. If verb does not match a Macro then do
    nothing and stay in Connect mode. Be aware that searching tables for the
    name of the verb uses many cpu cycles and will reduce performance.

    Examples:
        DEFINE Accumlate Receive, Connect
        SET KEY \315 {\Kaccumulate}

    Pressing the IBM PC "F1" key (code \315 above) makes the keyboard
    translator see string {\Kaccumlate}, verb "accumlate" is not in the
    predefined tables, and hence Kermit invokes the Macro named ACCMULATE.
    That Macro puts Kermit into file receive mode and when the file, or
    file group, transfer has been completed it returns to Connect mode.

        DEFINE WP Take wp30.ini, Connect
        SET KEY \316 {\Kwp}

    This makes IBM PC key "F2" invoke macro WP which in turn reads in
    and executes the contents of file WP30.INI. Kermit then returns to
    Connect mode. Nothing happens if the user has not defined Macro WP.

    Braces around the whole key definition are required so that the search
    for the verb name is done while executing Connect mode rather than when
    defining the key. If the braces are omitted then only the predefined
    keyboard verbs are available; an error will be reported if the verb is
    not one of these.

    Text sent to the host may preceed and follow the \Kverb part. To avoid
    confusion "Kverb" itself, but not the "\", may be placed in braces too,
    such as:

    DEFINE Accumulate cd c:\junkmail,Receive,Connect
    SET KEY \315 {kermit\13\send foo.bar\13\{KAccumulate}exit\13}
    the pieces:   |_______________________||............||_____|
                  string to host          do Macro    string to host

    This sends the string "Kermit<carriage return>Send foo.bar<carriage ret>"
    to the host to invoke its Kermit and asks it to send file foo.bar. It
    then invokes local Macro Accumulate to receive the file, and finally it
    sends the string "exit<carriage return>" to the host. Braces around
    KAccumlate deliniate it from the final string text.

    There is no host command which can invoke these Macros; this protects the
    PC against stray garbage text and unauthorized commands from the host.
    Files changed are MSUIBM.asm (procedure keysv) and MSYIBM.asm.

50. Reinstate Dump screen: filename on Status display. msssho, msyibm

51. Correct a misprint in the National Replacment Character sets for Spanish.
    Apparently a DEC typist inserted one accent mark too many in the table.
        char value    was        is now
    60h \96        accent        accent        just for reference
    7bh \123    accent        degree
    7ch \124    degree        n tilde
    7dh \125    n tilde        c cedilla
    7eh \126    c cedilla    tilde
    Corrections are in file mszibm.asm

52. Embellish the VT300 character set abilities by permitting National
    Replacement Character (NRC) sets to be "designated" by the host to a
    particular Gn set table, viz:

    Designator         Mnemonic       Description of Action
    ESC ( <ident>    SCS    Designates 94 byte character set <ident> to G0
    ESC ) <ident>    SCS    Designates 94 byte character set <ident> to G1
    ESC * <ident>    SCS    Designates 94 byte character set <ident> to G2
    ESC + <ident>    SCS    Designates 94 byte character set <ident> to G3

    where <ident> is:
    NRC country  <ident>        NRC country  <ident>
    British        A        Italian        Y
    Dutch        4        Norwegian/Danish ' (hex 60) or E or 6
    Finnish        5 or C        Portuguese    %6
    French        R        Spanish        Z
    French Canadian    9 or Q        Swedish        7 or H
    German        K        Swiss        =

   Example: ESC ) A  loads the British NRC set (A) into G1 (the ")" part).
   To load Latin1 into G1 use  ESC - A  because Latin1 is a 96 character set.
   NRCs are all 94 character sets.

   This embellishment does NOT turn on NRC operation in the Digital Equipment
   Corporation sense. To follow DEC usage employ SET TERM CHARACTER-SET to
   choose the country and have the host enable or disable NRCs by sending
   CSI ? 42 h  or CSI ? 42 l, respectively.
   Changes are in file mszibm.asm.

53. Minor code corrections to parsing eight bit controls introduced by item 52.
    File mszibm.

54. Incorporate support for Novell's TELAPI TCP/IP Telnet program. This
    is selected by command

            SET PORT TELAPI nnn.nnn.nnn.nnn

    where nnn.nnn.nnn.nnn is the Internet address of the remote host, in
    decimal.

        Example: SET PORT TELAPI 129.123.1.11   (machine netlab.usu.edu)

    TELAPI is a component of the Novell package LAN WorkPlace for DOS. At
    Utah State University it was run with the Novell (ex-Excelan) EXOS 205T
    Ethernet board (a smart mutiprotocol board supporting TCP with NetWare
    IPX 802.3 style packets). Novell Utility TSU.EXE is not required.

    SET PORT TELAPI must not be confused with SET PORT NOVELL(NASI); they
    use very different communications methods.

    Notes on this new faciity:

     a) Hosts not on the local network will likely require their
        Internet address and the local gateway to be specified with utility
        ROUTE, such as
            ROUTE ADD 128.59.39.2 129.123.1.254
    The first address is watsun.cc.columbia.edu, in New York City,
    and the second is that of a local gateway box (a cisco, Inc router
    at Utah State University in Logan, Utah).

     b) The communications channel is opened as an 8-bit wide BINARY
        character at a time mode, thus Unix hosts may require Line Feed
    (Control J) as a line terminator. See also item g) below regarding
    character \255.

     c) Included in this work is sending a BREAK signal as a Telnet
        "Interrupt Process" command.

     d) A status message is shown for 3 seconds if the connection cannot
        be established.

     e) Once an Internet number has been specified with SET PORT TELAPI it
        will be retained for subsequent SET PORT TELAPI commands. Thus it
    need be stated only once. SHOW COMMUNICATIONS will display the number.

     f) The presence of the host can be checked by sending the two bytes
         \255\246  which is Telnet signal "Are You There", and to which the
    host is supposed to send back a bell or visible message. This can
    be arranged easily by command SET KEY <key's ident here> \255\246
    if SET TERMINAL CHARACTER-SET TRANSPARENT is selected.
        See TCP/IP documents RFC-854 and RFC-855 for Telnet specifications.

     g) Character \255 is special in Telnet; it introduces Options negotiation.
        To send \255 as data it must be sent twice, as \255\255 or use the
    new command SET SEND DOUBLE \255 to do this for Kermit packets.
        Please be aware of this character when sending Binary files.

     h) TELAPI version 3.5 sometimes has trouble hanging up a connection. It
        will attempt creating a new one for each new session and can exhaust
    its space (defaults to two of them) when an old one persists. The
    only cure I know is to unload the TELAPI TSR (DOS command TELAPI -u)
    or reboot the machine.

     i) TELAPI version 3.5 is also notably slow in delivering characters to
        terminal emulators. Expect an effective 2400 baud rate.

     j) TELAPI uses Interrupt 14h with high numbered function calls. Beware
        of using other Int 14h trapping programs simultaneously.

     k) Kermit uses only the Internet number form of addressing for TELAPI
        because the TCP "name resolver" (conversion of a name to a number)
    is not available directly with TELAPI. Thus, full compliance with
    TCP/IP specs is not available to Kermit or other external terminal
    emulators using the TELAPI interface. The full specs recommend using
    names and letting a separate group of machines, called Name Servers,
    provide the Internet number via TCP/IP methods.

    All the changes are confined to file msxibm.asm

55. Correct a real bug: if SET LOCAL ON and while in Connect mode Control-
    PrintScreen (copy screen to printer) are active then Kermit crashes the
    system. The reason is a stack overflow when the same function ends up
    calling itself again by roundabout means. Adequate correction required
    small revisions about what is or is not echoed locally. Now almost every
    thing except DEC status reports is echoed (my real VT320 seems to do the
    same). Affected files are msyibm.asm and mszibm.asm, done on 14 August.

56. Add Enviroment and command line SET COM1 and COM2 to the list as per
    item 4 above.

57. Significant change to \%n variables defined as macro arguments. For each
    Macro invocation first save variables \%0 through \%9, clear \%0..\%9,
    define \%0 to be the name of the macro being invoked and \%1..\%9 as
    the arguments to the macro. When the macro exits restore the previous
    \%0..\%9 variables. This process nests naturally, and ARGC still
    represents the one plus the number of macro arguments. C Kermit 5A and
    MS-DOS Kermit 3.02 are now in agreement on these items.
    Previously \%0 was not affected by macro invokation and \%1..\%9 were
    not saved and restored around the macro. The new behavior may affect
    scripts written in the past. File mssset.asm

58. Add alternative command syntax:
    SET FILE COLLISION means the same as older SET FILE WARNING
    and SET FILE COLLISION DISCARD is the same as SET FILE COLL NO-SUPERSEDE.
    Changes are in mssset.asm and msssho.asm

59. Correct problems with REM LOGIN. Is the last of problems in this area?

60. Correct problems with CTS/RTS handshake timing and half duplex. Tnx to
    Brian Holley for spotting them. msxibm.asm

61. Add DESQview support call to release the cpu timeslice when in Connect
    mode and no character is available from the serial port. msyibm.asm

62. Modify the retry procedure to send a packet character to wait 60ms rather
    than 10ms between each of five attempts. This may help situations where
    a network device may be unresponsive for about 200ms between characters.
    msscom.asm

  More changes are expected.

The mstibm.boo file and the source files are in kermit/test on watsun and in
the T: area of KERMSRV.  The binary .EXE file is available on watsun only in
kermit/bin/mstibm.exe.  There is also a test 3.02 version for the DEC Rainbow,
contributed by Robert Weiner of Cooper Union.  It is in kermit/test/mstrb1.boo
and kermit/bin/mstrb1.exe.  The latest Rainbow test version tracks the non-IBM
specific portions of MS-DOS Kermit, and adds some new character translations
for screen dump and print screen.  Thanks to Joe and Robert for their
continuing work on MS-DOS Kermit!

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

Date: Mon, 27 Aug 90 14:13:12 EDT
>From: Christine M. Gianone <[e-mail]>
Subject: A New Version of Kermit for OS/2 Presentation Manager
Keywords: OS/2 Presentation Manager Kermit

Contributed by Brian R. Anderson of Burnaby, BC, Canada.  Here is the note
that accompanied Brian's submission:

"The version of Kermit contained herein is for OS/2-PM.  It was written from
scratch by the author (Brian R. Anderson) in Stony Brook Professional
Modula-2.  A two part article in the September/October 1990 issues of Dr.
Dobb's Journal describe this implementation (which is a port of an earlier
program that I wrote for DOS in Logitech Modula-2).

This program is public domain, and may be copied freely, modified/enhanced,
and distributed freely (in original or enhanced form).

Included on the disk are an executable version of the program
(PCKERMIT.EXE); 17 Modula-2 source code files (8 .DEF and 9 .MOD); icon and
resource files; make and linker response files, and the EXE definition file.
To recompile the program: M2MAKE PCKERMIT <cr>.  The program includes:

      Kermit single and multiple file transfer
      TVI950 Terminal Emulation (optimized for IBM7171/PROFS)
      Automatic renaming of files in case of name clash
      Continuous display of communications settings"

Brian indicates that this program is the starting point for a program that
will be sold commercially.  Further details are in the file O2AAAA.HLP.

The files are in the Kermit test area for now, pending reactions from the
Kermit user community:

watsun.cc.columbia.edu    BITNET KERMSRV@CUVMA    Comments
  kermit/test/o2aaaa.hlp    T:O2AAAA.HLP            "boo" encoding of program
  kermit/bin/o2aker.exe                             Executable program
  kermit/test/o2aker.boo    T:O2AKER.BOO            "boo" encoding of program
  kermit/bin/o2aker.ico                             Program icon
  kermit/test/o2aico.boo    T:O2AICO.BOO            "boo" encoding of icon
  kermit/test/o2asrc.jar    T:O2ASRC.JAR            Source code

The boo files can be decoded into the original binary files using any of the
msbpct programs available in kermit/a.  The "jar" file is a text archive of
the source files that can be picked apart with a text editor or a simple
program.  Brian's submission did not include a user manual.

Many thanks to Brian for contributing this program.

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

Date: Sat, 28 Jul 90 12:10:27 PDT
>From: rochester!ames!claris!portal!cup.portal.com![e-mail]
Subject: New Release UCPECAN Kermit V1.1
Keywords: Pecan, USCD Pascal Pecan Kermit

I am submiting a minor upgrade to UCPECAN my Kermit-UCSD (Version 1.1).

You should recieve 2 files: 1) a large (about 1400 lines) one containing
the source (UCPUPD.PAS) and a very short one containing "installation
instructions" and a brief list of changes made to V1.1 by this upgrade
(UCPUPD.UPD).  The changes are

1)  Added a new Unit (DIR.FIXES) to work around problems
    encountered with SFS. This update removes Limitation #4,
    making BINARY file transfers exact in both SFS and AFS
    implementations.

2)  Fixed a bug that caused an incorrect time to be sent in
    the attribute packet if no time was specified with the
    creation date (this bug affected both AFS and SFS).

                      R. Tim Coslet

Usenet: [e-mail]
BIX:    r.tim_coslet

[Ed. - Many thanks, R. Tim!  The new files have been installed in the Kermit
Distribution C area.  Keep up the good work!]

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

Date: Tue, 07 Aug 90 02:00:41 MEZ
>From: "Gisbert W.Selke" <[e-mail]>
Subject: MS-Kermit 3.0x and German telephones
Keywords: MS-DOS Kermit 3.0, German

Here's a (partial) solution to a problem no-one besides me seems to have had:
I'm running MS-DOS Kermit over a 1200 bps line in what is yet West Germany.
For some obscure reason, the German PTT transmits the signal to my phone that
can be used to record the fee due. (No, I never had such a gadget. Maybe some
former owner of this flat had.) Unfortunately, the tone used for this is
right within the range used for 1200 bps transmissions. So, if I'm lucky,
I get a corrupted packet every 8 to 12 minutes (for local calls - much more
often for trunk calls); if I'm in terminal mode, however, I get some 10
scrambled characters on the screen. So far, so annoying. But you ain't seen
nothing yet: some of the garbage obviously contained shift-in/-out sequences,
so that I was left with funny graphics characters all over the screen
henceforward, where ordinary 7-bit ASCII should have been. The solution came
with one of the 3.02 revisions of MS-Kermit: 'set term char ascii g1' takes
care of the odd shift!

Still, some of the garbage even throws me out of that; apparently, it loads
a different character set into gx, where x = 1..3. So, if anyone has a way
of doing away with the disturbances altogether, any help/hints/pointers will
be appreciated, with software solutions muchly preferred.

\Gisbert   c/o  <UPP101.DBNRHRZ1.BITNET>

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

Date: Mon Aug 27 10:19:29 1990 EDT
>From: Christine M Gianone <[e-mail]>
Subject: Looking for Stories

 ... of how Kermit has been used in imaging and visualization applications,
including modelling, CAD, medical imaging, and so forth, for possible
publication.  MS-DOS Kermit graphics, Kermit protocol imbedded in imaging or
CAD systems, whatever you know about ...

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

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

From cmg  Tue Sep 11 14:07:49 1990
Return-Path: <cmg>
Received: by watsun.cc.columbia.edu (5.59/FCB)
    id AA05561; Tue, 11 Sep 90 14:07:49 EDT
Date: Tue, 11 Sep 90 14:07:48 EDT
From: Christine M Gianone <[e-mail]>
To: Info-Kermit
Subject: Info-Kermit Digest V12 #4
Reply-To: [e-mail]
Queries-To: [e-mail]
Message-Id: <[e-mail]>

Info-Kermit Digest         Tue, 11 Sep 1990        Volume 12 : Number 4

  MS-DOS KERMIT:

        Next Test Release of MS-DOS Kermit 3.02
        Kermit on Novell Networks
        Feedback on MS KERMIT 3.02 of July 20
        Kermit Problems - V3.01
        MS-Kermit and VAX ALLin1
        Question about Kermit 3.01 and the 128-byte history buffer
        Kermit & WordPerfect under PCSA
        Re: MSKERMIT <-- TCP/IP --> Unix-Host

Digest submissions may be sent to [e-mail],
requests for addition to or deletion from the Info-Kermit subscriber list to
[e-mail] or to [e-mail].

Kermit files may be obtained over networks and by mail order.  On the
Internetwork, use FTP to log in to host WATSUN.CC.COLUMBIA.EDU, a SUN-4/280
running UNIX (SUNOS 4.1), IP host number 128.59.39.2.  Login as user anonymous
(note, lower case), any password, and GET or MGET (MULTIPLE GET) the desired
files.  The Kermit files are in directories kermit/a, kermit/b, kermit/c,
kermit/d, and kermit/e.  Test versions are in kermit/test.  Binaries are in
kermit/bin (use ftp in binary mode).  You can also get Kermit files over the
BITNET/EARN network; to get started send a message with text HELP to KERMSRV,
the Kermit file server, at host CUVMA.  For detailed instructions, read the
file kermit/a/aanetw.hlp (AANETW.HLP on KERMSRV).  To order by mail, request a
complete list of Kermit versions and an order form from Kermit Distribution,
Columbia University Center for Computing Activities, 612 West 115th Street,
New York, NY 10025 USA.

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

Date: Mon, 10 Sep 90 16:03:23 EDT
>From: Christine M Gianone <[e-mail]>
Subject: Next Test Release of MS-DOS Kermit 3.02
Keywords: MS-DOS Kermit 3.02

63. Correct a small problem leading to confusion in terminal emulation if an
    arriving control sequence is terminated prematurely by another. msscmd.asm

64. Add command REMOTE SET FILE COLLISION UPDATE, meaning the file receiver
    on the other side should process files with the same name as "updates"
    (whose meaning is system dependent) to existing files. A MS-DOS Kermit
    server does not recognize the command. mssser.asm

65. Another small adjustment to item 62. Move the long interval retrying of
    sending characters to be at the final launching point for BIOS comms
    channels. The intent is to compensate for a particular X.25 channel which
    rejects new characters with a failure indication; that channel is known
    to be very sluggish. This change permits character retries for Connect
    mode and scripts as well as packets. msscom.asm, msxibm.asm

66. Ensure that the graphics terminal emulation writes characters as opaque,
    when so selected, for black and white displays. msgibm.asm

67. Accomodate LATIN5/Cryillic character set of Code Page 866 as much as
    possible. The command SET TRANSFER CHARACTER-SET has the new option
    LATIN5, and if selected will force FILE CHARACTER-SET to be CP866.
    Similarly, if the FILE CHARACTER-SET is selected to be the new option
    CP866 then it will force TRANSFER CHARACTER-SET to be LATIN5.
    Warnings are issued for both cases.

    When sending a text file with TRANSFER CHARACTER-SET LATIN5 the file
    attributes packet will send "I6/144" for the file character-set
    identification (the "C" attribute) and no translations will be done.

    When receiving such a file no translation will be done, regardless of
    the currently active FILE CHARACTER-SET. Actually the file should be
    rejected unless the user has stated SET UNKNOWN-CHARACTER-SET to KEEP,
    but the code gets very messy if the rule is enforced at this time.

    The reason is for the coupling of commands is CP866 has many Cryillic
    characters in the right, high bit set, section which have no equivalents
    in other Kermit character sets and regular Code Pages. Hence, when LATIN5
    or CP866 is selected there can be no translation of characters between
    CP866 and either the other (Western European) Code Pages or the LATIN1
    character set. Thus LATIN5 or CP866 selects a Transparent file transfer
    but with a LATIN5 "I6/144" character set identification.

    For terminal emulation SET TERMINAL CHARACTER-SET TRANSPARENT will prevent
    unwanted translations and also convert the C1 controls area into printable
    characters found in CP866.
    Files affected are mssfil.asm, mssset.asm, msyibm.asm.

68. Add communications enhancement to using the Int 14h serial port
    interceptor TES from Interconnections Inc (distributed with Novell
    NetWare for VMS). The new command

        SET PORT TES <optional host name>

    invokes TES and make a connection to the indicated host. This competes
    with SET PORT BIOSn because they use some common operations.

    <optional host name>        Action
        host-name       Connect to that host, and disconnect from a previous
                        TES host if such a connection were active.
           *            Show all available TES hosts but do not connect.
        nothing         Use the current TES host name to reestablish an
                        existing connection. Most useful when switching
                        between TES and a real serial port. If no host name
                        exists then a list of available hosts is shown.

    Keyboard verb \Knethold is used to invoke the TES command interpreter
    while in Connect mode (to revise connections usually), and HANGUP breaks
    an existing connection. Sending a BREAK (ALT-B or \Kbreak) performs the
    same function for TES as \Knethold. Use this function when manual control
    of sessions is desired, such as creating multiple sessions managed by
    TES rather than by Kermit.

    These new TES operations couple closely with version 2.x of TES and will
    not work with earlier ones. Instead use SET PORT BIOS1 and the TES hot
    key with older TES's. If the TES hot key is used then \Knethold may not
    be recognized; use the hot key again to control TES. If the hot key has
    not been used then TES material is shown on the Connect mode screen.
    SHOW COMMUNICATIONS will show the current host name, as read back from
    TES itself. The apparent serial port identifier on the Connect status
    line is the letter "I".

    Note that placing a connection on hold and later returning to it may
    require pressing the \knethold or \kbreak keys and typing RESUME to make
    the TES command interpreter return control to the data stream. It's
    apparently a problem in the interpreter.

    If Kermit is exited completly then the active session is terminated, but
    held sessions are retained. Thus, to preserve sessions after Kermit has
    exited use \knethold or \kbreak to get the TES command interpreter and
    place the connection on hold manually. The session may be resumed as above.

    I am testing with TES version 2.1 beta so both sides have growing pains.
    Modifications are all in file msxibm.asm

69. Make an attempt to pass macro arguments \%0..\%9 through (around) a
    TAKE command to keep some consistency with MS-DOS Kermit 3.00 and 3.01.
    For example,
        DEFINE DIAL Take Hayes.tak      which has dialing commands
        DIAL 555-1212                   we want the number passed down to the
                                        interior of Hayes.tak as \%1.

    where file Hayes.tak (from the diskette with Chris' book) starts off as
        COMMENT - Initial setup
          def errstop echo Error: \%1\13,def \%1,hang,stop
          set speed 2400                ; *** Change to 1200 ...
          <more stuff in here>
          echo \13Dialing \%1.  Wait...\13\10  ; Dialing for the first time,
          goto dial                     ; so skip the "Redialing" message

        COMMENT - Dialing loop
        :REDIAL
          echo \13Redialing...\13\10    ; Give this message when redialing
        :DIAL
          output ATDT\%1\13             ; Dial the number
          <more stuff follows>

    Another example:
        DEFINE xxx Set term VT302,take x.tak,connect
        xxx A B C
    where file x.tak holds
        echo \%0 \%1 \%2 \%3

    This displays  XXX A B C and then enters Connect mode as a VT320 terminal.

70. Add a new element to command line variables, taken from C Kermit 5A.
    Numerical variables ARGC, COUNT, ERRORLEVEL, and VERSION can be used as
    the ascii representation of their values by the new text substitution
    operator

        \v(numerical variable)

    Soon this will be expanded to include other "named variables" such as
    TIME, DATE and so on which are also internal quantities in Kermit.

    Examples:
        ECHO The version number of this program is \v(version) today.
    which displays
        The version number of this program is 302 today.
    And DEFINE See ECHO \%0 - the num var is \v(\%1) here.
        See argc
    which displays
        SEE - the num var is 2 here.
        See version
    which displays
        SEE - the num var is 302 here.

    The expression \v(numerical variable) is replaced by it's ascii value.
    This may be used in any command. The current syntax of IF = ARGC 2 ...
    is retained for compatibility purposes but in new scripts it should be
    replaced by IF = \v(argc) 2  etc.

    If the item within the parentheses is not one of the above numerical
    variables, or if a right parenthesis does not end the variable name
    then the entire expression from \v( to the current point is discarded.
    Examples of bad syntax:
        ECHO testing \v(versions) stuff
    or
        ECHO testing \v(version stuff
    both of which display
        testing stuff

    All the changes for this item are in file msscmd.asm

 More changes are expected.

[Ed. - The Cyrillic and \v() items are not final.  An actual translation
between CP866 (Alternative Cyrillic) and ISO 8859-5 will probably be
installed before 3.02 is released.  \v(name) will probably be changed to
require the name of a builtin variable (which need not necessarily be
numeric) within the parentheses.]

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

Date: Thu, 09 Aug 90 10:22:53 EDT
>From: Doug Salane <[e-mail]>
Subject: Kermit on Novell Networks
Keywords: MS-DOS Kermit, Novell Network

I am trying to use Kermit for station to station communication on my Novell
Network.  This is an ELS Level II Network which uses Arcnet cards in a bus
topology.  I would like to use Kermit to transfer files between machines
without relying on the server.  Is this possible?

I have tried using the SET PORT NETBIOS and SET PORT NOVELL after loading the
Novell IPX workstation shell.  I get an error message that says the Network is
not available.

I'd appreciate your help. Thanks.

[From jrd - Doug, what's needed is NetBios running on top of IPX and NET3/4.
It's in the Novell NetWare collection. After that just follow the instructions
in the Kermit documentation about SET PORT NET <name>. I use Kermit that way
here, and it is also the official AT&T method of talking to an AT&T Unix
machine from a DOS PC. SET PORT NOVELL(NASI) uses the NASI/NACS async server,
not what you want at all.
        The short form of the documentation says start the Server Kermit
first (SET PORT NET, Server). No destination address is needed by the server.
Then start a client Kermit with SET PORT NET <server's NetBios name> and
issue file transfer or REMOTE commands.]

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

Date: Sat, 21 Jul 90 14:23:19 PDT
>From: [e-mail] (Leland Bruns )
Subject: Feedback on MS KERMIT 3.02 of July 20
Keywords: MS-DOS Kermit 3.02

I am forwarding some feed back on the test version of MS KERMIT version 3.02
and some comments on version 3 in general.  Please forward to the appropriate
persons.  Thank you.

ENVIRONMENT

First, my environment is a Wedge Technology 386-based PC-AT clone, with a
Video-7 VGA board.  I am compiling using MicroSoft's MASM version 5.01.  My
hosts are VAX VMS and Ultrix machines.  The PC's operating system in PC-DOS
version 3.30.

[From jrd - similar to my own environment: DELL 310, Video-7 VGA, VMS host,
PC-DOS 3.30]

I have recently copied MS KERMIT version 3.02 from the /kermit/test directory
at watsun.cc.columbia.edu.  My comments below are based on the versions dated
July 15 and July 20.  (I see there is a new version this morning, July 21, but
have not had the chance to port or test this version.)  I am comparing the
test version 3.02 to the original 3.00 distribution version.

TEKTRONIX EMULATION PROBLEMS

I see that there are significant changes to the MSGIBM.ASM module for
Tektronix emulation, and have concentrated on looking for differences there.
The one difference I would like to report is in the way GIN input apparently
works in the new version.  In the original 3.00 version, when a key was
entered at the PC, the host would receive the ASCII code for the character
entered, the 4 character xy coordinate, and one final character (I can't tell
easily from the host software I have to work with what that final character
is, as the software discards it).

The new version 3.02 test version apparently does not send the GIN report to
the host until the user has entered the desired key (at which time the
cross-hair cursors disappear) AND an additional carriage return.  Not too
surprising, the host receives an additional character which must be ignored to
continue properly.

I believe that the behavior of the original version 3.00 of MS KERMIT is
correct, while that the new test 3.02 version is incorrect.  The user should
not have to enter both the desired key plus a carriage return for each GIN
input point.  I would very much like to see the original behavior restored.

[From jrd - advice is most welcomed because my Tek docs seem to differ
about what should happen (they are not consistent either).]

FEEDBACK & ENHANCEMENT REQUEST

Since I'm taking the time to report the problem above, I'd like at the same
time to pass on some positive feedback on MS KERMIT version 3 and an
enhancement request.  I very much like the work that has gone into MS KERMIT
between versions 2 and 3.  KERMIT is unique in its universal availability, its
faithful terminal and graphics emulation, and public availability of source
code.

The latter feature, availability of source code, is important to me as I have
one minor hardware incompatibility for which I must modify each KERMIT release
as it becomes available.  Specifically, I have dedicated hardware on all four
COM ports, and on IRQ2 thru 5 (see the comments below).  In order to make use
of my 9600 Baud Telebit Trailblazer modem on COM3, IRQ5, I must create a copy
of MS KERMIT modified to use IRQ5 rather than IRQ4.

I don't think my situation is too uncommon these days, as more and more
powerful PC's become available and are equipped with more and more hardware,
requiring use of COM ports 3 and 4.  I frequently see queries posted asking
how to get around the restrictions imposed by the current MS KERMIT.  I think
many users would benefit the ability to specify the interrupt number and
address on a per port basis...just as the newer MS KERMIT versions now allow
specification of the COM port address.  Failing that, the next best thing
would be to allow the user to define the interrupt numbers and addresses in a
straightforward manner in the MSXIBM.ASM source (vs. the convoluted encoding
required at present...see my difference file below).

[From jrd - But.... If one is not using all the COM ports simultaneously then
one can use two at once if they are on different IRQ lines. Just ask Kermit to
touch the competing ports so their interrupt driver chips are taken off the
bus (as decent software should have done anyway). I am reluctant to move far
from IRQ 3 and 4 because of the interference with other peripherals (IRQ 5 is
the hard disk controller on XTs). I can't easily change things in v3.02
anwyway because of the necessary revisions to the data structures. Btw, I too
have a Trailblazer (T2500), and I avoid most serial port conflicts via a $30
RS232 A-B-C-D box; COM1 is comms, COM2 is the mouse.]

Once again, let me say how much I appreciate the work going into MS KERMIT
version 3.  Thanx in advance for your consideration of the suggestions above.

[From jrd - Thank you for the suggestions and the compliment.]

                                        Leland M. Bruns
                                        Intel Corporation
                                        [phone]
                                        [e-mail]

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

Date: Wednesday, 25 Jul 1990 13:06:12 EDT
>From: "Larry F Armbruster" <[e-mail]>
Subject: Kermit Problems - V3.01
Keywords: MS-DOS Kermit 3.01

I have experienced several problems using Kermit.  The configuration
of my system is:

  PS/2 Model 50Z with an AT&T Voice Data Multiplexer dialing into a
  DECserver 200 V3.0 (BL33) - LAT V5.1 and accessing VM/CMS through
  a DECnet/SNA Gateway into a SIM3278 session manager.  Also at times
  I access a VAX cluster.

I have redefined the PS/2 function keys to emulate the VT100/200/300 series
of terminals.

When I emulate a VT320 - the session messages (ie SYS AVL, etc) writes to
the top line of the screen thus wiping out the top line of the screen.
When I emulate a VT102 - the session messages are at the bottom of the screen.
This is only an annoyance and I can live with emulating the VT102.

The serious problem is the inability to use Kermit file transfers on either
CMS or VAX.  My computer center is aware of the CMS problem and attribute it
to the session manager.  However we cannot explain the VAX problem.  The VAX
Kermit Host (or maybe Mskermit) issues a parity error.  This is the case no
matter what parity, duplex, or flow control is used.  Any suggestionor help
is greatly apperciated.

[From jrd - since the pathway between the PC and either IBM/CMS or the VAX
goes through two external communications boxes one supposes that one or the
other box is adding its own parity, or more likely, is unable to handle a
stream of characters as long as a packet. Otherwise MS-DOS Kermit does run
fine to VAXen through common LAT boxes. Logging packets on both ends and
viewing the log files will show which machine is experiencing the troubles.]

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

Date: Wed, 15 Aug 90 08:08 CDT
>From: DEC-WOLF <[e-mail]>
Subject: MS-Kermit and VAX ALLin1
Keywords: MS-DOS Kermit 3.01, VAX/VMS, ALLin1

Hello all,

I was wondering if there were other Ms-Kermit (3.01) users who are using PCs to
communicate with a VAX and who use ALLin1, who are also experiencing problems
with printing over the printer port.  We have determined that everything works
fine when the Vax thinks the terminal type is a VT200.  If the terminal type is
NOT VT200 series than the printing is erratic or non-existent.  After
researching the problem I dicovered that Allin1 is sending the following escape
sequences for the two terminal types:

VT20O   Esc [ 5 i

VT100   Esc [ 5 i Esc [ 6 i
VT300

The Esc [ 5 i is the proper sequence to open the printer port for a VT100,
VT200, or VT300 terminal.  After calling Digital, I was told that (Esc [ 6 i)
was the escape sequence to open the printer port for the VT125 terminal.
Evidently the sloppy programmers at DEC check for VT200 ONLY and send the VT100
and VT125 sequences for other terminals.  It seems that either Kermit or the
printers are confused by the (Esc [ 6 i) sequence.  I know that Dec should just
straighten their act out but I was wondering if anyone knew how to work around
this problem from the Kermit end.  Could the (Esc [ 6 i) sequence be ignored or
stripped out by Kermit?  We plan on just changing the terminal type to VT200 on
the Vax end but it seems a bit kluging to me (normally the Vax and terminal
communicate the terminal type between each other at login).

Bill Bryson
User Services Analyst
CC_BRYSON@SWTEXAS

P.S.  Our systems personel could also patch allin1 to change the printer
scripts (i.e. not send ESC [ 6 i) but feel it is unlikely that they will (it is
considered a no-no to "mess" with Digital software).

[From jrd - MS-DOS Kermit v3.02 consumes the ESC [ 6 i and does not send it
to the printer. Yes, it's a carry over and should not be there. Here is the
entry in the file msr302.upd describing changes to version 3.02 -
15. Correct bug in transparent printing within text emulator which corrupted
    back to back escape sequences sent to the printer.]

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

Date: Fri, 27 Jul 90 17:47 EDT
>From: John W Manly <[e-mail]>
Subject: Question about Kermit 3.01 and the 128-byte history buffer
Keywords: MS-DOS Kermit 3.01, CLEAR Command

Hi there.  Another question about MS-Kermit and the use of the history buffer
in Take or Script files.

Could anyone fill me in on the relationship between the INPUT statment, the
REINPUT statement, the CLEAR command, and the 128-byte history buffer?

In particular, the manual states that REINPUT only accepts additional input
from the serial port until the history buffer is full.  How does one then
clear it out?  A CLEAR command presumably does so.  Does an INPUT operation
clear it as well, or clear it only if it's full, or anything like that?

Any help would be greatly appreciated.  Thanks.

                                 - John W. Manly
BITNET:  JWMANLY@AMHERST           Systems Manager
PHONE:   [phone]            Amherst College

[From jrd - The CLEAR command does indeed clear things: the history buffer
and the serial port receive circular buffer (preceeds the history buffer).
I agree that a separate script history buffer clearing command would be
beneficial. In the meanwhile, the history buffer can be made either larger
or smaller via the DOS command
   SET KERMIT=INPUT-BUFFER-LENGTH value
value is number of bytes (default 128)]

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

Date: Tue, 31 Jul 90 14:44 EDT
>From: Pete Kanaitis <[e-mail]>
Subject: Kermit & WordPerfect under PCSA

Recently, we have been looking at WordPerfect 5.0 under VMS and have tried
the MS-Kermit macros and DCL command procedure (ftped from watsun) to set
the IBM PC keyboard to do WP bindings.  This seems to work fine under any
asynch connection, but does not seem to work with MS-Kermit running under
PCSA.   Under PCSA, when the terminalS and terminalR macros are envoked,
the key bindings are set, the connect command gets issued, but the original
terminal session gets disconnected!  (Since we use virtual terminals, we
can re-connect back to the WordPerfect session, and resume, but only after
we re-login in)

Here's an example of what is happening:

MSKERMIT.INI has the following:

set port decnet singer
set terminal wrap on
define terminalS take C:\wp30.ini, connect
set key \2344 \KTerminalS

Then from the PC:

C>kermit
IBM-PC Kermit ...

MS-Kermit>connect

Welcome to Singer...
Username: FOOBAR
Password:

$ @PUBLIC:PCWP
What type of Graphics adapter are you using (ega, cga, vga)?  vga

$ WP FILE.EXT
Defining Function Keys for WordPerfect Products....
(After a few seconds Kermit reconnects..)
(Nothing happens. When I hit any key...)

Welcome to Singer...
Username: FOOBAR
Password:

   You have the following disconnected process:

 ...
   Connect to above listed process [YES]:

(Now you are back in WordPerfect)
(When you exit..)
Save Document? (Y/N) Yes
Exit WP? (Y/N) Yes

WP key definitions cleared...

(screen clears, back to normal)

Does anyone have any ideas?

Thank you...

Pete Kanaitis
Manager, Computational Resources
Allegheny-Singer Research Institute
[e-mail] (Internet)
X979PK0P@CMCCVB (Bitnet)

[From jrd - When WordPerfect starts up it requests a long Color Palette
report from the VT300 terminal. Kermit sends the report fine, but some
communications channels can't handle 200 some odd byte bursts. Also, the
VAX must have SET TERM/HOSTSYNC so that the VAX can XON/XOFF the terminal.
There is really nothing I can do, because on my VAX some paths just can't
cope, even when I insert massive pauses between characters. Sometimes
it's the length of the DEC Color Palette report which is the root problem.
My test copy of WordPerfect/VMS has exceeded it's 6 month lifetime, but
I recall that I could use PCSA/DECnet-DOS fine this way. The only "but" is
the VMS command SET TERM/HOSTSYNC must be stated.]

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

Date: Wed, 18 Jul 90 14:34:55 -0400
>From: [e-mail]
Subject: Re: MSKERMIT <-- TCP/IP --> Unix-Host
Keywords: MS-DOS Kermit, TCP/IP, Unix

In article <[e-mail]> you write:
>In <[e-mail]> [e-mail] (Gressel) writes:
>
>>Hello,
>
>>we tried it with an Interlan-NI5210-Card, no success!
>
>In Kermit News number 4, June 1990 Joe R. Doupnik and Christine M. Gianone
>writes:
>
>TCP/IP is a very widespread networking method linking machines locally and
>around the world.  ...

I would like to add that Wollongong's Pathway Client Plus also supports
the INT 14 service.  We use both Kermit and Procomm Plus Network Version
and they work great!

Mark Regester Information Systems & Services, NCR Peripheral Products Division
 NCR:654-8340 <[e-mail]>
[phone] <uunet!ncrlnk!ncrwic!m.regester>
 FAX:[phone]

[From jrd - Yeah! A WINning way.]

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

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

From cmg  Mon Sep 17 16:04:06 1990
Return-Path: <cmg>
Received: by watsun.cc.columbia.edu (5.59/FCB)
    id AA01766; Mon, 17 Sep 90 16:04:06 EDT
Date: Mon, 17 Sep 90 16:04:06 EDT
From: Christine M Gianone <[e-mail]>
To: Info-Kermit
Subject: Info-Kermit Digest V12 #5
Reply-To: [e-mail]
Queries-To: [e-mail]
Message-Id: <[e-mail]>

Info-Kermit Digest         Mon, 17 Sep 1990        Volume 12 : Number 5

Today's Topics:

       Announcing IBM Mainframe VM/CMS Kermit-370 Version 4.2.1
           Selecting CONTROLLER type in Kermit-370
              Announcing  KERMIT-12 Version 10g
            Kermit Proposal SET FILE TYPE
               Prime8 Help for Dividing Source
      Re: A New Version of Kermit for OS/2 Presentation Manager
            Re: Info-Kermit Digest V12 #2
            Kermit incapatability with LSE
            Kermit 3.01 Arrow Key Problem
            132 column mode in MS-Kermit?
                  Kermit & Telebits

Digest submissions may be sent to [e-mail],
requests for addition to or deletion from the Info-Kermit subscriber list to
[e-mail] or to [e-mail].

Kermit files may be obtained over networks and by mail order.  On the
Internetwork, use FTP to log in to host WATSUN.CC.COLUMBIA.EDU, a SUN-4/280
running UNIX (SUNOS 4.1), IP host number 128.59.39.2.  Login as user anonymous
(note, lower case), any password, and GET or MGET (MULTIPLE GET) the desired
files.  The Kermit files are in directories kermit/a, kermit/b, kermit/c,
kermit/d, and kermit/e.  Test versions are in kermit/test.  Binaries are in
kermit/bin (use ftp in binary mode).  You can also get Kermit files over the
BITNET/EARN network; to get started send a message with text HELP to KERMSRV,
the Kermit file server, at host CUVMA.  For detailed instructions, read the
file kermit/a/aanetw.hlp (AANETW.HLP on KERMSRV).  To order by mail, request a
complete list of Kermit versions and an order form from Kermit Distribution,
Columbia University Center for Computing Activities, 612 West 115th Street,
New York, NY 10025 USA.

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

Date: Wed, 1990 Sep 12   18:30 EDT
>From: "John F. Chandler" <[e-mail]>
Subject: Announcing IBM Mainframe VM/CMS Kermit-370 Version 4.2.1
Keywords: IBM 370 Kermit, VM/CMS Kermit
Xref: CMS Kermit, See VM/CMS Kermit, IBM 370 Kermit

This is to announce the release of Kermit-370 version 4.2.1 for CMS.  As
usual, the new version comes in VM/SP and VM/XA/SP flavors, but the
changes are the same for both.

Version 4.2.1 has several improvements over 4.2.0, the most important
being:

 1. Spurious flow-control "packets" from MS-DOS Kermit are now ignored.

 2. Overflow of the fullscreen buffer is now avoided when the receiving
    Kermit asks for 2K packets.

 3. Kermit-370 now supports transfers in LATIN2 and LATIN3 and file
    storage in CP870, CP880, and CP905.  In addition, L1, L2, and L3 are
    recognized as aliases for the three LATIN sets, and two-character
    abbreviations are accepted for the other transfer sets as well.  The
    new sets add support for Afrikaans, Albanian, Catalan, Croatian,
    Czech, Esperanto, Galician, Hungarian, Maltese, Polish, Romanian,
    Slovak, Slovene, and Turkish.

 4. Kermit-370 supports file transfers through the IBM 3174 AEA with B2
    microcode.  The support is restricted to terminals with the ASCII
    Graphics capability in three ways:

    a) The terminal type must be defined in the 3174 to support graphics
       (only the built-in VT241 and Tektronix 4205 types plus suitable
       user-defined terminal types).

    b) The line must be defined without an associated Host Addressable
       Printer.

    c) If the 3174 is owned by VTAM, the connection must be made with a
       logmode that allows the Read Partition Query (such as M2SDLCNQ).

    Kermit-370 automatically detects the B2 AEA and sets CONTROLLER
    accordingly (to AEA if graphics is allowed, to NONE if not, or to
    GRAPHICS if Query is denied).  Since the 3174 supports full 8-bit
    communication, it may be useful to configure the ports for 8-bit
    data and to set both SEND and RECEIVE PARITY to NONE in Kermit-370.

 5. Kermit-370 now uses the FILE COLLISION settings for all files in a
    group rather than just the first.

 6. Kermit-370 has three new subcommands: REMOTE MAIL, REMOTE PRINT, and
    REMOTE SUBMIT.  They transmit a file (or group of files via wild
    cards) tagged for mailing, printing, and submitting as job,
    respectively.

The new release is in the form of updates to be applied to the 4.2.0
source.  The new files are IKCKER.UPD, IKCKER.BWR, IK0AAA.HLP, and
IK0KER.UPD (the latter is only a catalog of all the updates, not the
updates themselves).  The new code has been tested on most known types
of protocol converter (many thanks to the beta testers!) to make sure
the 3174 support does not harm the existing support for Kermit file
transfer, but problems may still turn up.  Bug reports are welcome, as
usual.

A similar release 4.2.1 will soon be available for TSO and MUSIC.

                                         John

[Ed. - Thanks, John!  The new files are installed in kermit/b on watsun
and are also available from KERMSRV@CUVMA on BITNET.  This program is truly
amazing in its adaptability to the infinitely varied 3270 emulation
communications environment, and it is a groundbreaker in character set
conversion.  Let's hope that the other Kermit programs catch up in the latter
department soon.  For that to happen, we need examples and listings of the
PC, UNIX, Macintosh, etc, character sets used for all the language supported
by Latin Alphabets 1 through 5, Latin/Cyrillic, and others.  If you have them,
please send them in and we'll do our best to support them.]

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

Date: Thu, 1990 Sep 13   11:50 EDT
>From: "John F. Chandler"   <[e-mail]>
Subject: Selecting CONTROLLER type in Kermit-370
Keywords: IBM 370 Kermit

One of the improvements in release 4.2.1 is a more thorough DEBUG output
that proved very useful in bringing the support for the IBM 3174 to
completion.  This enhancement makes no difference to routine file transfer,
but it raises the possibility of determining easily the exact response of
any kind of protocol converter to the efforts of Kermit to decide which
CONTROLLER type to use.  To this end, I ask all installers of release 4.2.1
to take a few minutes and create a debug log for each (fullscreen)
environment where Kermit-370 might be used, provided, that is, that you do
not apply the optional update SC89058.  Even if you have applied SC89058 in
the past, it might be worthwhile to omit it as an experiment.  The desired
debug log is created by starting Kermit-370 and entering the subcommands SET
DEBUG I/O LONG, SET LINE, and QUIT.  I would be grateful if you would send
the resulting KER LOG along with the following information: level of VTAM
(if any) driving the session, model of front-end processor (if any) and
software, model of protocol converter (if any) and software.  These results
would be interesting even for real IBM 3270-type terminals or protocol
converters unable to support Kermit file transfers.  It is possible that the
information collected will enable Kermit to distinguish certain environments
that currently fail to trigger the correct default CONTROLLER type.

                                    John

P.S. My e-mail address is:

 Internet:    [e-mail]
 BITNET:      PEPMNT@CFAAMP

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

Date: Thu Sep 6 1990 11:00:00 EDT
>From: Charles Lasner <[e-mail]>
Subject: Announcing  KERMIT-12 Version 10g
Keywords: PDP-8, PDP-12, VT-78, DECmate, OS/8
Xref: DEC PDP, See PDP

This is a maintenance release of KERMIT-12.  A minor problem relating to
incorrect CPU identification messages has been fixed.  The problem only
appeared when the CPU was a KK-8A single-board CPU; this configuration was
previously untested.  Thanks to Johnny Billquist of Sweden for his
assistance in pinning down the problem.

KERMIT-12 operation was not affected in any other way, as only the
DECmate-specific identification is crucial; earlier PDP-8 family members
are treated in a generic fashion except for the "frill" of model
identification (all PDP-8, PDP-12, VT-78 models use software-compatible
port hardware;  all DECmates are incompatible and must be handled
individually).  We are still looking for volunteers to test the various
DECmate III and DECmate III+ configurations.

The rest of the release concerns the encoding of files into the
"ASCII-fied" format.  The format has been modified to be more robust, since
the original method has proven itself to be problematic in certain
practical circumstances (as reported in K12MIT.BWR).

The new ENCODing format is based on five-bit encoding with repeat
compression.  As much as 256 repeated 12-bit words will be expressed in a
five character field.  Any repeated 12-bit value can be compressed, as
opposed to simple zero compression, as in other common encoding schemes.
(PDP-8 files often have repeated strings of the value 7402 octal, which is
the HLT instruction.)

The only printing characters required to pass through any distribution
"path" are 0-9, A-V, X, and Z. The alphabetic characters can also be
lower-case.  All command lines are framed by ( and );  all data lines are
framed by < and >.  These characters can be changed if required, as they
are not part of the data; they could be replaced by W (w) and Y (y) if
necessary.  (Changing the framing characters requires slight modification
of the ENCODing and DECODing programs.)

The new format supports a 60-bit file checksum to ensure proper decoding at
the other end.  The former 12-bit checksum could be compromised on long
files.

The new ENCODing programs creates internal (REMARK commands stating the
ENCODed file's creation date, and the original file's creation date.  This
will aid in distribution of PDP-8 files where the user wishes to maintain
proper file dates.  The date algoritm used is the one proscribed by the
OS/8 DIRECT program. (OS/8 systems only OPTIONALLY support file dates, and
there is an eight-year "anomaly" associated with identifying the year; the
user must determine the credibility of the year portion of the date.  The
value provided by the ENCODE program for the original file creation date is
always today's year or the previous seven years as necessary; this field
will not be provided if the system doesn't support the required AIW
feature.)

Overall file size is theoretically as much as 6/5 of the original encoding
format (as the earlier format was based on six-bit encoding), but actual
size varies downward due to slightly less file overhead (wider lines mean
less CR LF; there is now less automatically generated verbiage), and the
random improvement afforded by simple repeat compression.

Virtually all K12MIT-related files are re-released at this time.  There are
several new files.  Due to the "fragile" nature of TECO macro files, the
file K12GLB.TEC is no longer being distributed directly; the file K12GLB.ENC
is the same file in the new ENCODE format.

The new files have been installed in the regular places:

BITNET/EARN       Internet
KERMSRV@CUVMA     watsun.cc.columbia.edu     Description

 K12MIT   ENC      kermit/d/k12mit.enc        Encoded binary of KERMIT-12
 K12MIT   DOC      kermit/d/k12mit.doc        Documentation file
 K12MIT   BWR      kermit/d/k12mit.bwr        Updated "beware" file
 K12MIT   DSK      kermit/d/k12mit.dsk        Description of RX02 diskettes
 K12MIT   ANN      kermit/d/k12mit.ann        Announcement of KERMIT-12
 K12MIT   UPD      kermit/d/k12mit.upd        Release update file
 K12DEC   PAL      kermit/d/k12dec.pal        Decoding program
 K12ENC   PAL      kermit/d/k12enc.pal        Encoding program
 K12PL8   ENC      kermit/d/k12pl8.enc        Encoded binary of PAL8 Ver B0
 K12CRF   ENC      kermit/d/k12crf.enc        Encoded binary of CREF Ver B0
 K12MIT   PAL      kermit/d/k12mit.pal        Main source file of KERMIT-12
 K12PCH   PAL      kermit/d/k12pch.pal        KERMIT-12 source patch file
 K12CLR   PAL      kermit/d/k12clr.pal        Memory clearing file
 K12MIT   LST      kermit/d/k12mit.lst        Symbols-only listing file
 K12PRM   PAL      kermit/d/k12prm.pal        Sample VT-78 config file
 K12GLB   ENC      kermit/d/k12glb.enc        Encoded TECO file macro
 K12ENC   DOC      kermit/d/k12enc.doc        Encoding format description

[Ed. - Many thanks, Charles.  Believe it or not, there are still quite a
few PDP-8 based systems out there, and even some PDP-12s.  You won't find
very many other new software packages that support them!]

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

Date: Thu, 6 Sep 90 08:47 CST
>From: <[e-mail]>
Subject: Kermit Proposal SET FILE TYPE
Keywords: Kermit Protocol

Please accept these remarks regarding the proposed SET FILE TYPE extension
to Kermit.

1.  The labels are transmitted in normal Data packets.  Therefore an
ignorant Kermit receiver will write them into the file as data.  This is a
MAJOR change to the protocol, which has always provided transparent file
exchange.  When reading such a file, how is a program to know that labels
have already been included?  Will these files cause problems for other
file-transfer protocols such as Xmodem?

[Ed. - No, it won't cause problems with Xmodem.  Xmodem or any other file
transfer protocol, including a Kermit program that does not know about labeled
files, will store or send a labeled file just like any other file, without
interpreting the label information.]

2.  Stored-in-File labels are incompatible with the MacBinary protocol in
    standard use on Macintosh computers.

[Ed. - That's true.  But MacBinary format cannot be adapted to other kinds
of file systems such as VAX/VMS.  Kermit can still be used to transfer
MacBinary files, and a MacBinary option will be added to Macintosh Kermit
before its next release.]

3.  The sending operator must now decide whether to send with labels or not.
    Previously, the sender had no choices to make.  We should not be adding
    complexity to the process if we can help it.

[Ed. - This is true.  However, without labels it is impossible to transfer a
complex file and retain all of its features.  Therefore this proposal
addresses only computers with complex file systems, like VAX/VMS, IBM
mainframes, etc, and does not affect other computers.  Users can continue to
use Kermit on these systems in the normal way, but now they will also have
an additional tool to let them successfully transfer files that they could
not transfer before.]

4.  Perhaps a better approach would be to use:

        SET FILE TYPE system type

    Where 'system' identifies the receiving file management system,
    (RMS, VSAM, etc.) and 'type' identifies the appropriate attributes.
    Example:

        SET FILE TYPE RMS INDEXED

    where RMS represents Vax RMS file management, and INDEXED identifies
    the incoming file as an indexed file.

    This approach requires that the sending and receiving routines be
    similarly intelligent about the information required to successfully
    transmit and write the file, but allows unintelligent intermediary
    programs (repositories, bulletin boards, etc.) to receive and send
    the files without any special settings (other than SET FILE TYPE BINARY).

[Ed. - It is a cardinal principle of Kermit or any other well-designed file
transfer protocol that any particular computer must not be required to have
knowledge about the formats and conventions of any other kind of computer.
Rather, each Kermit implementation knows only the data formats of its own
computer and those defined for the "standard intermediate representation" on
the wire.  Otherwise, hundreds of different programs would require
modifications to know about hundreds of different computers.  Not only is
this a waste of computing and human resources, but it's a moving target.]

    It also allows the following sequence to take place:

      machine 1 Kermit send  -> machine 2 Kermit receive (FILE TYPE BINARY)
      machine 2 BrandX send  -> machine 3 BrandX receive
      machine 3 Kermit send  -> machine 4 Kermit receive (FILE TYPE xxx ttt)

    Machine 1 sends the file BELIEVING that the receiver knows how to handle
    it, but only the machine 4 program needs to know.  However, machine 3
    can also use the file, if it recognizes, or is told to recognize, the
    file type.

[Ed. - The Labeled File proposal works the same way.]

    A simplification of this approach would be to use SET FILE TYPE AUTO
    which would cause the receiver to perform some recognition process
    before writing the file.

[Ed. - The labeled file proposal includes this possibility too.]

We have recently developed a Macintosh VT100 terminal emulator which
incorporates Kermit file exchange, and automatically distinguishes TEXT
documents from applications and formatted documents.  The users need only
tell the Vax to SET FILE TYPE ASCII/BINARY depending on whether they intend
to edit it on the Vax, or transfer it to another Mac.  The program pre-pends
the Macbinary header for non-text documents when sending, and recognizes it
when receiving.  I think you'll agree that the LABELED proposal only adds
complexity to our situation, and requires users to make unnecessary
decisions about the process.

[Ed. - Your application seems to be Macintosh-centered, in the sense that
you regard the VAX as a repository for Macintosh applications, which you
encode in MacBinary, but you make no provision for storing VAX applications
or complex binary VAX files on the Mac.  For your purposes, MacBinary will
do just fine.]

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

Date: Tue, 28 Aug 90 17:27:31 EDT
>From: John M. Crawford <[e-mail]>
Subject: Prime8 Help for Dividing Source
Keywords: Prime Kermit

Enclosed is a short file which provides the necessary Primos editor (ED)
tricks to divide (and then build) Kermit 8.12 for Primos. You might consider
appending it to the PRIME8.ANN file (or another) for general distribution to
Prime kermit users.

John M. Crawford      [phone]                Computing Services Center
                                                    College of Business
[e-mail]                                     1775 College Road
[e-mail]                     The Ohio State University
[e-mail]               Columbus, Ohio 43210

[Ed. - Many thanks!  Your ED file is now enshrined in PRIME8.ANN.]

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

Date: Wed, 29 Aug 90 10:23:11 PLT
>From: Wim Bonner <[e-mail]>
Subject: Re: A New Version of Kermit for OS/2 Presentation Manager
Keywords: OS/2 Kermit

The message said that the Kermit files were in the OS/2 test area pending
comments from the user community.  Is this where I make comments?

I tried the Kermit program just now.  It has an annoying habit of going full
screen.  I have a 1024x768 screen, so an 80,25 screen will fit in less than
a quarter of the screen, and leave room for much more on the screen.

I am running OS/2 1.2, and was not able to get the lights on my modem to
blink when I typed characters after Connecting.  That is normally a good
indication something is wrong.  All of the other communication programs that
I've tried work fine.

Wim Bonner - [e-mail] - V(509)335-4436

[Ed. - Thanks.  We'll collect all such comments and put them in an envelope
and send them back to the contributor.  Meanwhile, has anyone else gotten
the program to work?]

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

Date: Sat 25 Aug 90 11:51:37-CDT
>From: Rob Pettengill <[e-mail]>
Subject: Re: Info-Kermit Digest V12 #2
Keywords: MS-DOS Kermit 3.02, Macros, Variables, Scripts

The behavior of the macro positional parameters has changed in the new test
release of MSKermit 3.02.  Previously when a take script was taken in a
macro the \%n positional arguments were defined in the take script - with
this version they are undefined.

The previous behavior was reasonable for a script.  Are you tring to make
take files behave more like macros?  If so then it should be possible to
pass positional arguments to the take files explicitly.  In any case the
behavior in the current 3.02 does not seem desirable.

;rob

[Ed. - That was a mistake, which has been corrected in the latest 3.02
release.  Macro parameters are now on a call stack so if macro A calls macro
B, A's parameters are still intact when B returns.  The mistake was indeed
that a TAKE file was being treated like a macro.  In the latest edit, it is
not: if macro A TAKEs a command file, A's parameters are available to the
TAKE file, as before.]

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

Date: 29 Jul 90 23:18:00 CDT
>From: "COLLINS, STERRETT" <[e-mail]>
Subject: Kermit incapatability with LSE
Keywords: MS-DOS Kermit 3.0, LSE, VAX/VMS, Terminal Emulation

I am using MS-Kermit v3.0 on a Kaypro 286 operating MS-DOS v3.21, connecting
to a VaxCluster operating VMS v5.3 .  I have tried using the language
sensitive editor (LSE v3.0), but Kermit fails to emulate the terminal that
LSE expects.  I have tried setting terminal/nodec_crt3, which partially
corrects the problem, but still not satisfactorily.  I am not sure that LSE
does not think that every member of the VT300_Family of terminals is a Regis
terminal.  I have access to a Regis_Emulating communications software
package, which I do not normally use for licensing considerations, but
which, if I switch to that after having entered LSE using Kermit, is able to
emulate the terminal properly.

The possible answers would seem to be:

"The operating system does not successfully detect the correct terminal
characteristics."

"The Operating system does successfully detect the correct terminal
characteristics, but this information is not propperly transferred to LSE."
I only know that SHOW TERMINAL reveals that it does not have the REGIS
characteristic, but does have the SIXEL charactersitic, and the DECCRT_3
characteristic.

                                        sterrett collins
                                        physics department
                                        texas tech university

[From jrd - Another case where Kermit command SET DISPLAY 8 needs be done
to avoid clobbering the 8-bit control sequences sent by the host.]

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

Date: Mon, 23 Jul 90 19:44:42 GMT
>From: [e-mail] (Greg Seminara)
Subject: Kermit 3.01 Arrow Key Problem
Keywords: MS-DOS Kermit, Arrow Keys

Arrow keys work only sporadically when connected to a UNIX host from a DOS
PC running Kermit 3.01 if you are using a full-screen "curses" application.
Seems to be sending either the wrong ansi sequence or is sending the
sequence too fast.  If you press arrow keys with a significant pause between
each press, keys usually work OK.  Emulation is vt102 for kermit and TERM is
set to "kermit" or "vt100".  Kermit 2.32a and before work fine under
identical conditions.  - HELP!

[From jrd - your Unix host has a problem with communications.  If characters
in a control sequence are NOT sent in rapid succession then EMACS reacts
differently than expected.  In addition, some host machines apparently have
intrinsic difficulties running in true full duplex.  Unix loves to echo
arriving characters willy nilly.  So when Unix is sending a control sequence
while one is arriving from Kermit and Unix is also echoing it then Kermit
receives both sets of information with characters intermingled.  If the
sequences arrived separately then Kermit could cope.  This is pretty silly
behavior by Unix; the application should attempt supressing echos.  There is
nothing that Kermit (nor a real terminal) can do about it.]

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

Date: Thu, 30 Aug 90 14:28:57 CDT
>From: [e-mail] (Moore)
Subject: 132 column mode in MS-Kermit?
Keywords: MS-DOS Kermit, 132 Columns, Screen Settings

Greetings.

I have a very persistent user here who wants the word directly from the
horse's mouth regarding a feature of MS-Kermit:

I've always thought that EGAs cannot do 132-column mode (except by simulating
it in graphics mode).  MS-Kermit doesn't change that, right?  Isn't it the
"responsibility" of the hardware to switch modes, and then Kermit just detects
and uses that mode?

[Ed. - True.  Except that in version 3.0 and later it also supports automatic
switching between 80 and 132 column mode via the COLS80.BAT and COLS132.BAT
mechanism.  That is, if Kermit gets the escape sequence telling it to switch
modes, it will try to run the appropriate BAT file that does the PC- or
adapter-specific things required to switch modes.]

Can Kermit simulate 132-column mode by letting the user pan an 80-column
window left and right?

[Ed. - No.]

Thanks for any help.

Jim
[e-mail]

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

Date: 27 Aug 90 11:42:05 GMT
>From: mrsvr![e-mail] (Tom Shaw ct58 Ex 5084)
Subject: Kermit & Telebits
Keywords: Modems

I'm looking for anyone who has/is doing something similar to this: I am
transferring binary and ASCII files across dial-up phone lines using Telebit
Trailblazer Plus modems and kermit.  The transfers are between 2 Suns, one
running Sun OS 3.5 and the other running Sun OS 4.01.  The size of the files
range from 2500 bytes to 800kbytes.  Does anyone have any tips, traps to
avoid, benchmarks of what kind of rate I should be expecting for ASCII and
binary files or any hands on advice.  I am using kermit version 4E(72).

In the past few weeks, I've heard stories about using Telebits in Germany,
what kind of problem is there and are there any other countries I might have
a problem connecting and transfering to?

Any help would be appreciated.  Thanks

Tom

[Ed. - As you may know, Telebits have Kermit built inside them.  If you
activate this feature, Computer A actually talks Kermit protocol to Modem A,
Modem A talks high-speed error-correcting PEP protocol to Modem B and Modem B
talks Kermit protocol to Computer B.  This is all done transparently to the
Kermit programs, but you have to put the originating Telebit into "Kermit
spoof" mode.  See your Telebit manual.]

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

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


From cmg  Wed Oct 10 17:02:44 1990
Return-Path: <cmg>
Received: by watsun.cc.columbia.edu (5.59/FCB)
    id AA02736; Wed, 10 Oct 90 17:02:44 EDT
Date: Wed, 10 Oct 90 17:02:42 EDT
From: Christine M Gianone <[e-mail]>
To: Info-Kermit
Subject: Info-Kermit Digest V12 #6
Reply-To: [e-mail]
Queries-To: [e-mail]
Message-Id: <[e-mail]>

Info-Kermit Digest         Wed, 10 Oct 1990        Volume 12 : Number 6

Today's Topics:

               New Honeywell DPS-6 Superkermit
             Announcing Kermit for the Tandy 100
               CMS Kermit 4.2.1 erratum
               OS/2 PM Kermit Feedback
               OS/2 PM Kermit Feedback
              Easy Exit from Terminal Emulation
          Running MS-DOS Kermit 3.0x under DESQview
           USING MS-DOS Kermit 3.0 with MNP Modems
              MS-Kermit 4010 GIN mode by Mouse?
              Suppresing Kermit's Error Checking
              MacKermit Settings Trouble
             Larger Font for Mac Kermit 0.98(63)?
              Prime Kermit Version 8.12
              Kermit REMOTE SET Command

Digest submissions may be sent to [e-mail],
requests for addition to or deletion from the Info-Kermit subscriber list to
[e-mail] or to [e-mail].

Kermit files may be obtained over networks and by mail order.  On the
Internetwork, use FTP to log in to host WATSUN.CC.COLUMBIA.EDU, a SUN-4/280
running UNIX (SUNOS 4.1), IP host number 128.59.39.2.  Login as user anonymous
(note, lower case), any password, and GET or MGET (MULTIPLE GET) the desired
files.  The Kermit files are in directories kermit/a, kermit/b, kermit/c,
kermit/d, and kermit/e.  Test versions are in kermit/test.  Binaries are in
kermit/bin (use ftp in binary mode).  You can also get Kermit files over the
BITNET/EARN network; to get started send a message with text HELP to KERMSRV,
the Kermit file server, at host CUVMA.  For detailed instructions, read the
file kermit/a/aanetw.hlp (AANETW.HLP on KERMSRV).  To order by mail, request a
complete list of Kermit versions and an order form from Kermit Distribution,
Columbia University Center for Computing Activities, 612 West 115th Street,
New York, NY 10025 USA.

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

Date: Tue, 2 Oct 90 11:42:02 PDT
>From: [e-mail] (Frank Dreano)
Subject: New Honeywell DPS-6 Superkermit
Keywords: DPS-6 Kermit, Honeywell Kermit

I am sending you a new version of the Honeywell DPS-6 Superkermit.  This
version basically 'blows out' the server mode to provide much more
functionality, (After Joe R. Doupnik's excellent effort to support the
Honeywell DPS-6 in MS-DOS Kermit 3.02 dev. 28, I felt like I had to respond
in kind):

1) Superkermit server 'gets' and 'sends' now support wildcard filespecs.

2) MS-DOS Kermit 'remote cwd' commands are now supported.

3) MS-DOS Kermit 'remote set file type { text, binary }' commands are now
   supported.

4) A new Superkermit file type, called 'foreign', supports MSDOS *.EXE,
   *.COM, *.WKS, *.ZIP, etc. file transfers WITHOUT converting to ASCII.
   MS-DOS Kermit 'remote kermit foreign' sets Superkermit for these
   transfers.  UNIX executables, etc, are likewise supported by this new
   file type.  The 'foreign' type also works with the VIP-3 terminal
   emulator.

5) MS-DOS Kermit 'remote type [filename]' commands are now supported.

6) MS-DOS Kermit 'remote host [host command]' commands are now supported.

7) MS-DOS Kermit 'remote dir [filespec]' commands are now supported.

8) MS-DOS Kermit 'remote delete [filespec]' commands are now supported.

9) MS-DOS Kermit 'remote mesage [text]' commands are now supported.

10) MS-DOS Kermit 'remote who' commands are now supported.

NOTE:  There ARE some warnings about using these commands...  See the
       HD6KER.BWR 'beware' file for details.

I received a request to allow the Superkermit server to select either
8th-bit or image mode binary transfers.  If I didn't implement this ability
the default would always be 8th-bit (not satisfactory in all cases).  So I
have implemented two additional commands:

                'remote kermit image'
                'remote kermit prefix'

   Performed a much-needed clean up of code placing all compiler pre-
   processor code along with global/external variables and function
   prototypes in a separate file.  In addition, I have adopted your
   naming conventions for the source files:

            HD6KER.DOC -  Version 2.00 documentation.
            HD6KER.H   -  New include file described above.
            HD6KER.C   -  Kermit state switchers and heuristics.
            HD6PRI.C   -  Kermit protocol primitives.
            HD6COMP.EC -  New Kermit batch compilation JCL.

I believe the above improvements have resulted in a much more useful
Superkermit 'server' mode as well as more manageable source code.  My thanks
to Tim Ewing of Honeywell Federal Systems Incorporated (HFSI) in McLean,
Virginia for suggesting and testing some of the above changes.  I feel that
the code reorganization and additional server functionality have made this a
major release and I am calling it Version 2.00.

Frank Dreano Jr.

[Ed. - Many thanks, Frank!  The new files have been installed in the "D"
area of Kermit distribution under the names you sent them with
(kermit/d/hd6*.* on watsun).  Special thanks for adjusting the filenames.]

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

Date: Tue Oct  9 21:29:27 1990
>From: Christine M Gianone <[e-mail]>
Subject: Announcing Kermit for the Tandy 100
Keywords: Tandy 100

Apparently floating around since 1984, discovered recently and sent in by
Jay Rouman: a Kermit program, written in BASIC by Dave Straayer, for the
Tandy 100.  No documentation.  In kermit/c/ta100.bas on watsun, TA100 BAS
on CUVMA.  Thanks, Jay!

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

Date: Mon, 1990 Sep 17   20:04 EDT
>From: "John F. Chandler"   <[e-mail]>
Subject: CMS Kermit 4.2.1 erratum
Keywords: Kermit-370, CMS Kermit, IBM Mainframe

The announcement mentioned restrictions on VTAM logmodes for successful file
transfer through the IBM 3174, but the example cited was one that does *not*
work.  The logmode that is known to work is M2SDLCQ.

[Ed. - A corrected copy of IKCKER.ANN (the announcement text for CMS Kermit
4.2.1) has been installed.]

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

Date: Tue, 18 Sep 90 11:20:12 -0700
>From: [e-mail] (Alan Bishop)
Subject: OS/2 PM Kermit Feedback
Keywords: OS/2 Kermit, Modems

In article <[e-mail]> Wim Bonner writes:
>
> I am running OS/2 1.2, and was not able to get the lights on my modem to
> blink when I typed characters after Connecting.  That is normally a good
> indication something is wrong.  All of the other communication programs
> that I've tried work fine.
>
You need to play with the octs & so forth settings.  Look under the
communcations setup bit & toggle all the settings on the line that has OCTS
listed.  It works fine for me.

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

Date: Tue, 18 Sep 90 14:23:25 EDT
>From: "Robert E. Zaret" <[e-mail]>
Subject: OS/2 PM Kermit Feedback
Keywords: OS/2 Kermit

I did get the Presentation Manager version of Kermit working, but haven't
spent much time with it.  I already have the full screen OS/2 Kermit and my
monitor is strict VGA, so I have no urge for a PM version.  Thus, I wasn't
going to comment.  However, the digest I received today asked for comments,
so:

My major dissappointment is lack of VT100 support.  I assume its absence is
temporary.  I've seen enough mangled emulators to believe VT100 emulation is
not trivial, so I'ld support a decision to leave it out until other parts
are settled.  However, I have little use for a program without it.

I was able to communicate with my internal modem; the modem responded to a
query (ATS1?) and to dial commands.

I found no way to save settings.
The speed setting is labelled baud, rather than bps.
I would prefer one pull down menu for all communications settings
    (com port, bps, parity, etc.)
I didn't find a documentation file, and the program itself mentioned
    no way to get out of communication mode except by exiting the
    program completely.  I tried ctl-[, and it worked.  This sequence
    seems inconsistent with the DOS version, but I'm not sure
    consistency matters, or is even possible.
I, too, found the program insisting on using a full screen.  The
    behavior of the maximimize box (upper right corner) seems odd,
    but I'm not sure what it should do given the other problem.
I believe PM programs can find and use the user's preferences for colors,
    as set in the control box.  Definitely not a high priority.

Technical note: I'm using IBM OS/2 EE 1.2 on an IBM Model 80/311 with
an IBM 8513 monitor and an internal BusinessLand modem (not quite
all blue :-).

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

Date: Wed, 18 Apr 90 11:49:40 -0700
>From: [e-mail]
Subject: Easy Exit from Terminal Emulation
Keywords: Terminal Emulation, MS-DOS Kermit, Macros

Here is an easy way to leave terminal emulation, hangup the phone, and drop
to DOS (I put it on alt-Z):

        def terminalr hangup,exit
        set key \2348 \kterminalr

(Thanks to Joe D. for pointing this out.)

Here is why I couldn't display IBM graphic characters even though I had my
display set for 8-bit and terminal character set transparent.

Ted.

[From jrd - Alas, VT100's are really 7-bit devices and this time I have
enforced the rule, to make character set stuff behave as DEC intended. Try
SET TERMINAL VT320.]

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

Date: Sun, 16 Sep 90 16:19 MDT
>From: Joe Doupnik <[e-mail]>
Subject: Running MS-DOS Kermit 3.0x under DESQview
Keywords: MS-DOS Kermit, DESQview

Assistance in creating a DESQview .DVP configuration file (DVSETUP.TXT)
for MS-DOS Kermit.

My copy of DESQview is version 2.26 running on a 386 machine with 2MB, with
no expanded memory, but with QEMM/386. The display adapter is a Video-7
"VGA".  The tables below are similar to the DESQview screens.

Please, when configuring QEMM to load-high drivers etc always exclude video
memory.

I have been able to run two copies of MS-DOS Kermit v3.02 together, to
different destinations with different communications ports. In addition,
full graphics capability was retained.
                                                Joe D.
 ============================================================================
                        Change a Program
 Program Name............: MS-DOS Kermit v3.02
 Keys to Use on Open Menu: KE                   Memory Size (in K): 200
                                                (say 150 minimum)
 ----------------------------------------------------------------------------
 Program...: Kermit.exe
 Parameters:            (Kermit command line items, if any, go here.)
 Directory.: C:\yourdir
 ----------------------------------------------------------------------------
 Options:
                Writes text directly to screen.......: [N]      *
                Displays graphics information........: [N]      **
                Virtualize text/graphics (Y,N,T).....: [T]      ***
                Uses serial ports (Y,N,1,2)..........: [Y]
                Requires floppy diskette.............: [N]

   *   Not true, but MS-DOS Kermit is DESQview-aware and covers up nicely.
   **  Not true, naturally, but causes DESQview to put Kermit into full
       screen mode while graphics are executed and then to return to windowed
       mode after switching to text terminal emulation.
   *** Can be [Y] with the same effect as above.
 ----------------------------------------------------------------------------
                        Change a Program Advanced Options

 System Memory (in K).....:     0  Maximum Program Memory Size (in K)..:
 Script Buffer Size.......:     0  Maximum Expanded Memory Size (in K) :
 Text Pages: 1  Graphics pages: 0  Initial Mode:  3    Interrupts: 00 to FF

 Window Position:
        Maximum Height:  25     Starting Height:  20    Starting Row...:  5
        Maximum Width.:  80     Starting Width.:  40    Starting Column:  5
  (Choose your own window sizes, naturally. 132 column mode causes DESQview
   to switch to full screen.)
 ----------------------------------------------------------------------------
                                Shared Program
 Pathname..:
 Data......:
 ----------------------------------------------------------------------------
 Close on exit (Y,N,blank)......: [ ]   Uses its own colors..............: [N]
 Allow Close Window command.....: [Y]   Runs in background (Y,N,blank)...: [Y]
 Uses math coprocessor..........: [N]   Keyboard conflict (0-F)..........: [0]
 Share CPU when foreground......: [Y]   Share EGA when foreground/zoomed.: [Y]
 Can be swapped out (Y,N,blank).: [ ]   Protection level (0-3)...........: [3]
 ============================================================================

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

Date: 9 Sep 90 06:27:49 GMT
>From: [e-mail] (Timo Salmi LASK)
Subject: Using MS-DOS Kermit 3.0 with MNP Modems
Keywords: MS-DOS Kermit, Scripts, MNP Modems

In article <[e-mail]> [e-mail]
(Andrew Rossmann) writes:

> I just bought a 2400 baud MNP5 modem (ATI 2400etc/e.) I have quickly
> found out that some modems do not like the attempt to set up an MNP
> protocol. I am currently using Procomm Plus. The problem is that there is
> no way for me to have a particular entry in the dialer set the modem's MNP
> on or off (a linked script file is only called AFTER connection.) Are there
> any other communications programs out there that let you send special
> initializations to the modem BEFORE dialing?  Is there a sneaky way to do
> this in Procomm Plus??
>
Yes, I've thought about the same problem, and MS-DOS Kermit has this
feature.  With proper script programming you can have MS-DOS Kermit do
whatever initializations do wish before dialing, and then on top of that
doing the dialing from a multi-entry dialing directory.  This MS-DOS Kermit
dialing directory facility is available in the /pc/ts/tskerm24.arc MS-DOS
Kermit utilities collection downloadable by anonymous ftp from
chyde.uwasa.fi, Vaasa, Finland.  The flexibility and potential of MS-DOS
Kermit as a fully fledged communication program rather than just an
excellent terminal emulator are often underrated and little known.

....................................................................
Prof. Timo Salmi        (Moderating at anon. ftp site 128.214.12.3)
School of Business Studies, University of Vaasa, SF-65101, Finland
Internet: [e-mail] Funet: gado::salmi Bitnet: salmi@finfun

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

Date: Thu, 20 Sep 90 17:41 MDT
>From: Pete Klammer 303/556-3915 <[e-mail]>
Subject: MS-Kermit 4010 GIN mode by Mouse?
Keywords: MS-DOS Kermit, Terminal Emulation, GIN mode, Graphics, Mouse

We find that the 4010 emulation in MS-KERMIT supports GIN mode, that is,
graphical cursor position input, which is great!  For instance, the ZOOM
command in ANSYS puts up a crosshair target on our screen, which we can
position with the cursor keys.  Pretty neat.

Is it possible to get our PC mouse connected to this cursor?  The GIN mode
steps with the cursor keys are pretty small, hence slow.  It would be even
neater than the already neat that it is, if MS-KERMIT Tektronix emulation
would support a PC mouse for GIN mode.  Thanks!

/** --poko ________________________________* "cut on dashes for mailing label"
Pete Klammer [phone] FAX[phone]|[e-mail]
CU-Denver Computing Services Campus Box 169|bitnet: PKLAMMER@CUDENVER
1200 Larimer St NC2506 Denver CO 80217-3364|uucp:...!boulder!pikes!pklammer **/

[Ed. - MS-DOS Kermit does indeed support mouse movement of the graphics
cursor.  Make sure you have given the necessary DOS commands to turn the
mouse on, such as MOUSE ON and/or DEFAULT.]

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

Date: Mon, 24 Sep 90 12:01:37 CDT
>From: [e-mail] (David J. Camp)
Subject: Suppresing Kermit's Error Checking
Keywords: MS-DOS Kermit, Error Checking, Kermit Protocol, Performance
Keywords: MNP Modems

I just read the December inquiry about suppressing Kermit's error checking
to save time when using an MNP reliable connection.  You could do a raw
download.  For instance, if you are on a host that will let you simply
'type', 'cat', or 'fstype' a file, you can tell Ms-Kermit to capture the
screen and let it flow.  The MS-Kermit command is 'log session filename'.
Make sure that you have 'set flow on' and that the host will recognize the
flow control to gate the transfer.  This will not work for binary files.

I do not recommend this.  The reliability of the link goes beyond the
mode-to-modem portion of the communication.  There are several things you
can do to improve the speed of Kermit transfers.  The first is to increase
your packet size.  Recent versions of Kermit allow packets near 1000 bytes
in length.

[Ed. - Kermit's theoretical maximum packet size is 9024.  MS-DOS Kermit 3.0
supports packets up to 2000 bytes.  IBM mainframe Kermit supports packets up
to about 1700.  The forthcoming release of C-Kermit 5A (watch Info-Kermit for
an announcement) can be configured to support the full 9K.]

I usually limit myself to 500, because MNP modems doing baud rate
translation fail with larger packets in non-MNP mode.  The speed of transfer
with 500-byte packets is very nearly that with 1000-byte packets.

I did some benchmarks to compare the speed in MNP stream mode vs. MNP block
mode.  My conclusion is that the difference is small, and you are better off
using stream mode to make interaction less jumpy.  A much bigger payoff is
gained by using long packets.

Next, use sliding windows if they are available.  I have done some
benchmarks to determine the optimum number of windows, and it is 2.

[Ed. - Actually, the optimum window size varies according to the round-trip
delay of the connection and its noise characteristics.  See Kermit News #4.
For a clean and relatively direct connection with MNP modems, 2 appears to
be a good size.  Also bear in mind that, in general, the large the window
size, the smaller the maximum packet size, because most Kermit programs have
a finite total packet buffer size.]

The last thing I can recommend is to use 8-bit communications if possible.
It may be necessary to do more than just 'set parity none', but I am not
sure of this.  If you are downloading from an IBM mainframe, this will
probably not work.  -David-

[Ed. - SET PARITY NONE is usually the default, but only works if the
connection is truly 8 bits wide.  Most IBM mainframes do not give you an
8-bit path.  Neither to telnet connections, nor most public data network
connections.]

[e-mail]                 ^        Mr. David J. Camp
[e-mail]        < * >      [phone]
...!uunet!wugate!wubios!david          v        "Be kind to sinners."
"Concentration impedes Inspiration."  ---  "Depend on God, who has dominion."

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

Date: Thu, 19 Jul 90 10:34:05 MST
>From: Tom Aurand <[e-mail]>
Subject: MacKermit Settings Trouble
Keywords: MacKermit 0.98

I'm having trouble getting XON/XOFF flow control to stick in the settings
file when using MacKermit 0.98 on different SE's.  Can I patch it?  Thanks
for your help.

[From Paul Placeway - Get a copy of 0.98(63) -- the difference between edit
62 and 63 was a fix for that and saving of parity.  BTW: DON'T USE MACBINARY
MODE -- sending a file in MacBinary mode will delete the file on the Mac (yes,
that's a bug).  I suggest you disable the MacBinary button with ResEdit.]

[Ed. - 0.98(63) is available in kermit/test/ckmker.hqx.]

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

Date:  Mon, 23 Jul 90 10:36:59 -0500
>From: [e-mail] (Robert T. Harms)
Subject: Larger Font for Mac Kermit 0.98(63)?
Keywords: MacKermit 0.98(63), Fonts

I would like to use a larger font with my Mac Kermit on a Mac IIci - related
to general eye problems of mine.  I have used ResEdit to replace the VT100
built in font with a Courier 12 font.  BUT this obviously isn't enough.  (1)
The WIND resource seems to permit increasing the width of the window, but
somewhere the dimensions of the window need to be coded as well, and (2) the
cursor position is erratic with respect to character width.

Is there some way I can customize the font size using ResEdit?  Or would
you advise me to leave well enough alone?

Bob Harms       [e-mail]

[From Paul Placeway - Unfortnatly, MacKermit 0.98 has the font size
parameters hard coded into it, so you can't change the font even if you find
all the right places to patch.

This will be fixed in the next release (I have that part of the code now
working, but other parts don't yet).  (I'm getting older and blinder too...
I like to run with a 10pt font (usually Courier 10)).]

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

Date: 04 Sep 90 18:02:39 O
>From: [e-mail]
Subject: Prime Kermit Version 8.12

Yesterday I transferred a copy of PRIME Kermit Version 8.12, and new
fresh copies of Kermit Version 3.0.1 for IBM PCs. Both sources compiled
and run flawless except:

1. Generic commands issued from PC to PRIME Kermit in server mode usually
respond with unimplemented command (e.g. remote who, remote dir, remote
delete, etc.) But they are implemented in Prime KERMIT!  There seems to be a
definition problem of generic commands either on the sender (PC) or upon
reception (PRIME Kermit).

[Ed. - This is because vanilla 3.01 sends improperly formed generic
commands.  The patch file MSR301.PCH fixes this problem and, of course, it
will be fixed in 3.02.]

2. The only generic command which led to an action was remote type file
(file being a text file).  However, PRIME Kermit sends garbage between every
character from the text file !

[Ed. - Hmmm...     Could this be because PRIME uses "negative ascii"?]

3. We run PRIMOS 22.1.2 on a PRIME CPU.  At Rev 22 major changes affected
AMLC I/O (more assignable lines then ever, especially lines over Ethernet
cables, with line numbers larger than 128! Same applies to user numbers, we
have numbers up to 996 users! That means that several old interfaces to
PRIMOS, e.g. calls to DUPLX$, ASNLN$ etc have new replacements, which MUST
be used to change communication properties when either a user number or a
line number is larger than 256!  This seems to be a serious problem to all
users of PRIME Kermit 8.12 using Rev 22 and up, on larger machines, since
some of the new interfaces did not officially exist on older Prime
Revisions, and I expect that they are users which are forced to use either a
newer revision (e.g.  all TCP/IP users) or an older revision (for example
older hardware, running into performance problems when changing to rev 22).
Coding of those routines must be revision dependent, to give all Prime users
a perfect program.

Marcus C. Wagner
Department of Statistics and Computer Science
Universitaetsstrasse 5/9
A-1010 Vienna, Austria, Europe
University of Vienna

Email: since our TCP/IP connection is in experimental operation (since
two months, with some severe TCP/IP implementation errors of PRIME),
it will happen that my email address via Internet fails (host seems to be
down for the outer world) Alternatively, I am reachable via EARN/BITNET.
[e-mail] (IP)
A4421DAC@AWIUNI11  (EARN/BITNET)

Thanks to all programmers, who invested so much time to redesign the
old version of Prime Kermit, which we implemented five years ago, several
known bugs of that old version during normal file transfers vanished in
the new program, not to mention the performance gain.

[Ed. - Thanks for the comments.  They have been sent to the PRIME Kermit
developers.]

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

Date: Fri, 28 Sep 90 20:00:00 PDT
>From: [e-mail]
Subject: Kermit REMOTE SET Command
Keywords: Kermit Protocol, Remote Set, Character Sets

I'd like to suggest a small extension to the Kermit remote set command.  As
you have it defined, the REMOTE SET TRANSFER CHARACTER-SET allows setting any
transfer alphabet that has a designator.  However, there is also the option
called TRANSPARENT or NONE, i.e. suppress translation completely.  Since that
option does not have a designator, one cannot set it.  I would like to have
some kind of extension to allow setting TRANSPARENT.  Perhaps we could invent
a designator, say, 0 (zero), or perhaps some other method to guarantee that
the TRANSPARENT setting does not conflict with any possible future designator.
We could perhaps invent a new registration, kermit (K), and have TRANSPARENT
be K0.

I came up with this problem while implementing translation in my kermit, but
for time reasons the remote set isn't going to make it into my next release,
so I'm not in a gigantic rush for this, but I'd like to resolve it.

[Ed. - This is actually a tricky situation.  The idea was that TRANSPARENT
should be the default, for compatibility with the hundreds of Kermit
programs that do not support the character-set extension.  Adding a new
designator to denote TRANSPARENT might confuse Kermits that don't understand
it, including Kermits that do support the character-set extension, if that
designator were to arrive in an Attribute packet.  Incoming files bearing
the new designator might be rejected because of "unknown character set" --
clearly undesirable behavior, avoidable perhaps by having the user SET
UNKNOWN CHARACTER-SET KEEP, but how to explain this to mere mortals?  So
far, it has been an implementation decision about whether character-set
changes based on incoming attribute packets are "sticky".  If they are, this
presents the problem that there is no way for a client to tell a server to
switch from translation to transparent.  So it would appear that a decent
compromise would be to invent a new designator, say K0, for TRANSPARENT, and
to support it in REMOTE SET TRANSFER CHARACTER-SET commands, but, at least
for a time, not use it in Attribute packets.  Opinions?]

By the way, the last info I have on remote set is dated 11 Dec 89.  Was there
anything later?

[Ed. - Three additional parameters were added in Vol 11 #4: REMOTE SET FILE
{ BLOCKSIZE, RECORD-LENGTH, RECORD-FORMAT }.  The details for RECORD-FORMAT
have not yet been worked out.]

The 11 Dec info has a minor problem in that file collision discard and ask
are both 4; I presume ask should be 5, to fit the pattern.

[Ed. - Right, ASK should be 5.  Thanks.]

Bruce Cowan
KEA Systems Ltd.

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

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

From cmg  Tue Nov 20 16:21:26 1990
Return-Path: <cmg>
Received: by watsun.cc.columbia.edu (5.59/FCB)
    id AA02155; Tue, 20 Nov 90 16:21:26 EST
Date: Tue, 20 Nov 90 16:21:26 EST
From: Christine M Gianone <[e-mail]>
To: Info-Kermit
Subject: Info-Kermit Digest V12 #7
Reply-To: [e-mail]
Queries-To: [e-mail]
Message-Id: <[e-mail]>

Info-Kermit Digest         Tue, 20 Nov 1990        Volume 12 : Number 7

Today's Topics:

      Announcing IBM Mainframe MVS/TSO Kermit-370 Version 4.2.1
           Announcing CP/M Kermit Version 4.10 for Testing
         New Test Release of Microsoft Windows Kermit
         Another New Prerelease of MS-DOS Kermit 3.02
           Rainbow Kermit Updated Too (for testing)
              New Kermit for Gould/SEL 32/77 MPX
          MS-Kermit 3.02 Argument Handling, Keyboard Mapping
            Re: Kermit REMOTE SET Command
               Kermit for STRATUS/VOS?
                 Kermit vs Hypercard?

Digest submissions may be sent to [e-mail],
requests for addition to or deletion from the Info-Kermit subscriber list to
[e-mail] or to [e-mail].

Kermit files may be obtained over networks and by mail order.  On the
Internetwork, use FTP to log in to host WATSUN.CC.COLUMBIA.EDU, a SUN-4/280
running UNIX (SUNOS 4.1), IP host number 128.59.39.2.  Login as user anonymous
(note, lower case), any password, and GET or MGET (MULTIPLE GET) the desired
files.  The Kermit files are in directories kermit/a, kermit/b, kermit/c,
kermit/d, and kermit/e.  Test versions are in kermit/test.  Binaries are in
kermit/bin (use ftp in binary mode).  You can also get Kermit files over the
BITNET/EARN network; to get started send a message with text HELP to KERMSRV,
the Kermit file server, at host CUVMA.  For detailed instructions, read the
file kermit/a/aanetw.hlp (AANETW.HLP on KERMSRV).  To order by mail, request a
complete list of Kermit versions and an order form from Kermit Distribution,
Columbia University Center for Computing Activities, 612 West 115th Street,
New York, NY 10025 USA.

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

Date: Thu Nov 15 11:45:38 1990
>From: "John F. Chandler"  <[e-mail]>
Subject: Announcing IBM Mainframe MVS/TSO Kermit-370 Version 4.2.1
Keywords: IBM 370 Kermit, MVS/TSO Kermit
Xref: TSO Kermit, See MVS/TSO Kermit, IBM 370 Kermit

Kermit-370 version 4.2.1 for TSO has now been released.  For the most
part, this release matches the version 4.2.1 for CMS announced in
September, but there are some system-specific differences.

Version 4.2.1 has several improvements over 4.2.0, the most important
being:

 1. Kermit-370 supports file transfers through the IBM 3174 AEA with B2
    microcode (or higher).  The support is restricted to terminals with
    the ASCII Graphics capability in three ways:

    a) The terminal type must be defined in the 3174 to support graphics
       (only the built-in VT241 and Tektronix 4205 types plus suitable
       user-defined terminal types).

    b) The line must be defined without an associated Host Addressable
       Printer.

    c) If the 3174 is owned by VTAM, the connection must be made with a
       logmode that allows the Read Partition Query (such as M2SDLCQ).

    Kermit-370 automatically detects the B2 AEA and sets CONTROLLER
    accordingly (to AEA if graphics is allowed, to NONE if not, or to
    GRAPHICS if Query is denied).  Since the 3174 supports full 8-bit
    communication, it may be useful to configure the ports for 8-bit
    data and to set both SEND and RECEIVE PARITY to NONE in Kermit-370.

 2. Overflow of the fullscreen buffer is now avoided when the receiving
    Kermit asks for 2K packets.

 3. Kermit-370 now supports transfers in LATIN2 and LATIN3 and file
    storage in CP870, CP880, and CP905.  In addition, L1, L2, and L3 are
    recognized as aliases for the three LATIN sets, and two-character
    abbreviations are accepted for the other transfer sets as well.  The
    new sets add support for Afrikaans, Albanian, Catalan, Croatian,
    Czech, Esperanto, Galician, Hungarian, Maltese, Polish, Romanian,
    Slovak, Slovene, and Turkish.

 4. Kermit-370 has three new subcommands: REMOTE MAIL, REMOTE PRINT, and
    REMOTE SUBMIT.  They transmit a file (or group of files via wild
    cards) tagged for mailing, printing, and submitting as job,
    respectively.

 5. Spurious flow-control "packets" from MS-Kermit are now ignored.

 6. When downloading ISPF PDS members, Kermit-TSO now uses the ISPF
    modification date as the time stamp (if attributes are enabled).

 7. Kermit-370 now uses the FILE COLLISION settings for all files in a
    group rather than just the first.

 8. The format of KER.LOG for SET DEBUG I/O has been extended to give
    hexadecimal buffer dumps like those of CMS Kermit.

The new release is in the form of updates to be applied to the 4.2.0
source.  The new files are IKTKER.UPD and IKTKER.BWR.  The new code has
been tested on both IBM 7171's (demonstrating downward compatibility)
and IBM 3174's (many thanks to the beta testers!), and the CMS version
had already been tested on other types of protocol converters, but
problems may still turn up.  Bug reports are welcome, as usual.

A similar release 4.2.1 will soon be available for MUSIC.  Also, watch
for release 4.2.1 for CICS.

[Ed. - Thanks, John!  The new files are in in the B area of Kermit
distribution: iktker.ann (this message), iktker.bwr (the beware file), and
iktker.upd (the updates to be applied to the program to produce the new
version; see iktker.ins for instructions.]

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

Date: Thu, 1 Nov 90 14:18:55 EST
>From: Mike Freeman <[e-mail]>
Subject: Announcing CP/M Kermit Version 4.10 for Testing
Keywords: CP/M-80 Kermit

Just to prove that the CP/M world still exists, here is CP/M Kermit-80
Version 4.10.

New features include:

o SET COLLISION {BACKUP/DISCARD/RENAME/REPLACE}
o SET INCOMPLETE-FILES {DISCARD/KEEP}
o Many REMOTE commands, including some REMOTE SET commands
o RENAME command to rename CP/M files from within Kermit-80
o SET RECEIVE/SEND PACKET-LENGTH nn (nn <= 94)
o Many bug fixes
o Kermit-80 Version 4.10 now supports the Microbee family of
   computers (56K, 64K, 128K and 256K) manufactured by
   Microbee Systems, Ltd, of Australia.

Technical changes:

o An "I" packet is now tried before the request for files is sent
  in a GET command
o The overlay address is now 7000H
o The overlay (CPXLNK.ASM) has an added INCFLG variable to handle
  INCOMPLETE-FILES status

Syntax hints:

In REMOTE commands such as REMOTE COPY, REMOTE MESSAGE, REMOTE RENAME,
REMOTE WHO etc., where two arguments are required, the syntax is as for Vax
VMS Kermit, i.e.,

  REMOTE <command> <argument 1>
  Prompt:  <argument 2>

For example:

  REMOTE COPY <old-file>
  New file: <new-file>

The REMOTE LOGIN command has three arguments, of which the last two are
prompted for an entered on new lines.  Arguments are optional.

In commands such as REMOTE SET FILE BLOCK-SIZE which take a numeric
argument, Kermit-80 does not check the argument for validity.  Whatever is
typed is what the host sees.

The FCOPY command has been renamed COPY.

The syntax for the RENAME command is as for the COPY command, that is:
RENAME <old-filespec> <new-filespec>

More rigorous checking for wildcards is now done by both of these
commands.

SET BAUD-RATE is now SET SPEED.

The CONNECT command no longer can be abbreviated to "C"; the minimum
acceptable abbreviation is now "CON".

The option SET FILE DEFAULT has ben re-enabled.  Use a TAKE-file to set the
initial file-mode to ASCII or BINARY.

Building Kermit-80 ver. 4.10:

Kermit-80 ver. 4.10 is built using the same procedure as for version 4.09.

Many thanks to those who have contributed bug fixes, and, in particular,
to Mr. Russell Lang of Monash University, Australia, for contributing
a bug-fix and the family file for the Microbee systems.

[Ed. - Many thanks, Mike!  We hauled out our original Kermit Superbrain from
nine years ago, downloaded the system-independent hex file and the
"Brain"-dependent hex file, combined them with MLOAD, and the new version
worked perfectly.  But because CP/M Kermit runs on so many different
computers, we are installing it in the Kermit test area for now.  If you
encounter any problems with it, send e-mail to Mike at the address above.
After a decent testing interval, it will replace version 4.09 in the main
distribution area.  The Kermit test area is kermit/test on watsun, and T: on
CUVMA.  All CP/M-80 Kermit filenames start with the letters CP.  There are
more than a hundred files, so first get the file CPAAAA.HLP, which lists and
describes the files, read it, and then request the files you need.  An
updated version of MLOAD is also included as MLOAD.*.  An updated manual
will be available shortly.  Thanks again to Mike for all the work that went
into this release.]

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

Date: Fri, 19 Oct 90 18:10:57 PDT
>From: [e-mail] (William Hall)
Subject: New Test Release of Microsoft Windows Kermit
Keywords: Microsoft Windows Kermit

WIN100.EXE, a version of Kermit with VT100 and VT52 terminal emulation for
Microsoft Windows, is available on an experimental basis from the Kermit
distribution center.  Programs are available for both Windows 2.x and Windows
3.0 and replace the previously released WN100K.EXE.  Except for bug fixes, the
2.x version will not receive further enhancements.  The 3.0 version will
undergo several improvements over the next several months as time permits
including the release of all sources when legally possible.  Plans include
basic server support as well as extensions of the emulation to include VT220
and H19 as well as 8 bit character sets.  4010/4014 support and Telapi support
are also planned for the future.  Accompanying the programs is a font file
suitable for use on VGA displays which allow for proper display of bold
characters and DEC special graphics.

[Ed. - Many, thanks, Bill!  The new files are in ~kermit/test/win*.* on
watsun for Internet anonymous ftp access, and T:WIN*.* on CUVMA for BITNET
KERMSRV access.]

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

Date: Thu Nov 15 11:47:07 1990
>From: Christine M Gianone <[e-mail]>
Subject: Another New Prerelease of MS-DOS Kermit 3.02
Keywords: MS-DOS Kermit 3.02

>From Joe Doupnik's change log:

71. Expand the command line internal variable value substitution syntax
    \v(variable) to encompass internal variables:
        ARGC        PATH
        COUNT        TIME
        DATE        VERSION
        ERRORLEVEL
    Allow "?" help and <ESC> word completion on these items as well.

    Now scripts can include additional controls such as
        IF equal \v(date) 09-16-1990 echo it's \v(time) on Sunday
    Notice that \v(variable) yields a text string and cannot be combined
    with the strictly numerical IF test conditions of <, =, and >. For
    numerical tests employ the form
        IF > time 12:00 echo the time is past noon

    Some basic concepts are as follows.
    - Intrinsic (built-in) commands do not affect the \%0..\%9 variables,
      but user created commands (Macros) do create a private version of
      \%0..\%9.

    - To be a command the keyword, intrinsic or macro, must be the first word
      at the Kermit prompt. Commas in Macros start a fresh command line even
      though the Kermit prompt is usually not displayed on the screen while
      within a macro.

      Thus in the definition below of macro test
        DEFINE test echo \%0 \%1,mywords,echo test mywords \%1
      there are three commands (they start at the effective Kermit prompt):
        echo TEST <first argument><carriage return>
    mywords  becomes  whatever macro mywords is defined as<carriage ret>
    echo test mywords <first argument to test><carriage return>
            The argument to this last echo cmd is the simple text
            "test mywords" plus the first argument to test.
            In the text neither test nor mywords is replaced by
            its definition, and echo is an intrinsic command.

    - String substitution variables, \%<character> and \v(variable), are
      always immediately replaced by their definition string no matter where
      they are used outside of a DEFINE command.

    - ASSIGN is similar to DEFINE except that whereas DEFINE uses the
      definition text as a literal string ASSIGN first evaluates the text,
      i.e. it replaces \%<character> and \v(variable) items with their string,
      at the time the ASSIGN statement is executed.

72. More work on Tektronix BYPASS mode. By popular demand, ensure that BYPASS
    mode stays on (discards incoming characters) until a control character
    arrives from the host, or the screen is cleared, or the emulator is reset.
    Previous test editions of version 3.02 waited for a local control code to
    be generated. Files affected are msgibm.asm and msyibm.asm.

73. Correct tiny bug introduced by item 70. File mssker.asm
    And plug a security hole of two Control-C's in a row from a remote client
    causing server mode to exit if FIN/BYE is disabled. Files msscom.asm and
    mssser.asm.

74. Modify the action of the BYE/FINISH/LOGOUT command from an MS-DOS Kermit
    client. Previously these would complete successfully whether or not the
    server host sent an Error packet. It has been discovered that C Kermit
    version 5A sends an Error packet response if BYE has been Disabled. To
    keep things rational MS-DOS Kermit now stays active if an Error packet
    is received for these commands. Script writers may want to issue an
    extra command to EXIT Kermit regardless. An MS-DOS Kermit server returns
    an ACK with a message that the command is disabled, it logs out the user,
    it hangs up the connection, and it returns to being a server waiting for
    another customer, all if BYE is disabled.

75. Adjust the FILE TRANSFER CHARACTER-SET tables for LATIN5/Cyrillic to
    use ISO 8859-5 (Latin/Cyrillic) on the wire and presume Code Page 866
    (Alternate Cyrillic) in the machine. Modify the character set name
    from LATIN5 to CYRILLIC. Cyrillic uses an ISO 2022 announcer of ESC L.
    File mssfil.asm is changed.

76. Add to list of \v(variable) items the variables PLATFORM and SYSTEM.
    Platform returns the machine name, such as IBM-PC, and System returns
    the operating system name, MS-DOS, for MS-DOS Kermit. This is to match
    C Kermit 5A.
    In addition, add the objects PLATFORM and SYSTEM to the WRITE command;
    they may be followed by optional text:
        WRITE SESSION Platform and this is a good machine.
    FIles changed are msscmd.asm and msster.asm

77. Correct a sneaky bug regarding testing for DESQview which led to over
    writing of a few Help messages in the main body of MS-DOS Kermit/IBM-PC.
    File msyibm.asm.

78. Add numerical variable KEYBOARD to IF statements, \v(variable), and
    WRITE statements so that Take files can be tailored to fit either 88
    (so-called Old AT) or 101 (so-called Enhanced) keyboards. The value is
    either 88 (default) or 101 or 250. The determination of 88 or 101 is made
    at Kermit startup. The IBM PC version also permits the value 250 if the
    LK250 keyboard is selected (SET KEY LK250) and external driver is present
    for the Digital keyboard. Files affected are msuibm, msscmd, mssscp,
    and msster.

79. Enhancements to SET PORT EBIOS for IBM LANACS.
    - Let the baud rate be set for BIOSn and EBIOS ports for IBM-PC version.
    Initially they will show as "unknown" until set by the user. In addition
    to the speed 8 data bits and no parity are set. For EBIOS, the port
    being adjusted is really that on the asynchronous server; the local PC
    uses NetBios and EBIOS to simulate that remote port across the network.

    - Add new optional final command argument of the EBIOS server port name
        SET PORT EBIOS <local coms port, 1..4> <server port name>
    such as  SET PORT EBIOS 1 modem-2400

    If the server port name is omitted then the port name is taken from the
    EBIOS table on the client machine, such as resuming an old connection.
    This option removes the necessity of using the REDIRECT.EXE program, part
    of the LANACS package, because Kermit does a simple redirection of the
    selected local port to the named host port (and the name is persumed to
    be a unique one rather than a group name). If another type of connection
    is desired then (a) omit the sever port name in the SET PORT EBIOS cmd
    and (b) perform the redirection with REDIRECT.EXE. Each instance of SET
    PORT EBIOS <local comms port> uses its own port information of speed,
    parity, flow control, handshake, and local-echo.  msxibm.asm, msster.asm

80. On the formatted file transfer screen add " of n" to the Window slots
    line, where n is the maximum number negotiated between Kermits. msssho.asm

81. Correct bug in processing CSI ? 256 n leading to crashes. Thanks to
    Risto Laitinen. File msgibm.asm

82. Modify the strategy for DEC Autoprint, CSI ? 5 (and 4) i  from printing
    each character as it arrives to printing display lines only as the cursor
    is moved off it by an autowrap or LF, FF, or VT (otherwise do not print
    the line). Thanks to Michael Wolter for pointing out the problem. mszibm

83. Also, preserve the state of VTxxx terminal emulator printing around
    processing of DEC Set Conformance Level commands, e.g. CSI 63; 1 " p.
    Plus, correct a small bug resetting the cursor column to zero when writing
    to a host owned status line. Tnx to Michael Wolter and John E. Davis.

84. 12 Oct, two small fixes - ensure REM FILE TYPE remembers the command while
    being an MS-DOS Kermit server (mssser.asm), and cure a small \v(variable)
    bug in file msscmd.asm.

85. Correct a problem of not sending an XON following a failed RUN or PUSH
    command. An XOFF sent automatically as Kermit shells to DOS. The XOFF/XON
    pair is used to suspend host output while DOS is in charge. mssker.asm

86. 25 Oct. Fix some parser problems (Control-C handling, ASK command line
    editing) introduced with internal changes made over the past three weeks.
    Files changed are msscmd.asm and mssset.asm.

87. Modify the action of pressing the Enter key while a script INPUT command
    is in progress. Previously it meant "assume a match has occurred" so the
    script could progress. Now it means "assume a timeout has occurred" and
    report a failure status. People seem to prefer the latter approach. mssscp

88. 2 Nov. Add internal support of Microsoft compatible mouse for Tektronix
    GIN crosshairs. Both the regular cursor keys and the mouse can function
    together. Pressing either mouse button is the same as pressing the Enter
    key. The mouse driver must be active for Kermit to use it (include line
    DEVICE=path\MOUSE.SYS in file CONFIG.SYS for permanent residency, or give
    the DOS command MOUSE ON for temporary residency of the MS mouse driver).
    This addition bypasses any active mouse menu programs such as DEFAULT.COM
    during Tektronix emulation but they continue to run otherwise. MS-DOS
    Kermit uses standard Microsoft Interrupt 33h mouse calls. msgibm.asm

89. Extend automatic detection of unexpected parity in packets to include the
    first four protocol characters rather than the first two. In addition,
    perform the test only on the first good received packet of a file transfer
    group. The test is effective only if the local parity setting is NONE,
    and if another setting is detected from the host then the local setting
    is changed permanently. Files msscom, mssrcv, msssen, msssser.asm.

90. Correct some subtlities in command line parsing when a local prompt is
    offered, such as in GETting files with an overriding local name. Files
    msscmd.asm and mssker.asm.

91. Add a text cursor symbol, an 8x8 dot hollow box, in Tektronix graphics
    terminal emulation mode so we can see where we are. The box is removed
    before generating a TIFF format screen dump (default keys Control-End) and
    it is restored afterward. The box is XOR'd with the picture so that no
    information is lost. File msgibm.asm.

92. Add command SET TERMINAL GRAPHICS CURSOR {ON, OFF}, default is ON. This
    permits one to turn off the text cursor while in graphics (Tek) mode.
    The cursor is suppressed around almost all drawing and Sixel commands.

    Add command SET TERMINAL GRAPHICS COLOR <color values> which is analogous
    to the text mode command SET TERM COLOR and uses the same color values.
    Two technical notes: the background color cannot be given bold attributes,
    and the colors are stored in DEC VT340 color palette slots 0 (background)
    and 7 (foreground).

    Be wary of two side effects of colored graphics screens: most Print Screen
    programs will put a black dot on the printer paper if a dot is illuminated
    at all, and Sixel graphics normally add (OR) to the exiting dot coloring
    and hence the coloring may not be what was intended. Resetting the
    emulator restores the colors specified by these SET TERMINAL commands.
    Files msyibm.asm and msgibm.asm

93. To the mouse support add setting of the span of cursor motions to be the
    current screen dimensions, for mouse drivers which may not do this
    automatically. An internal item, no user commands. Thanks to Leland Bruns
    of Intel.

More changes are expected.

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

Date: Fri, 2 Nov 90 22:55:21 EST
>From: Robert Weiner <rweiner>
Subject: Rainbow Kermit Updated Too (for testing)
Keywords: Rainbow Kermit, DEC Rainbow, MS-DOS

The current version of DEC Rainbow 100 MS-DOS Kermit is ready for testing
and is available on watsun.cc.columbia.edu in the following files:

    ~kermit/test/mstrb1.boo        BOO Encoded MS-DOS Executable
    ~kermit/bin/mstrb1.exe        MS-DOS Executable

This version was built using the current generic MS-DOS Kermit modules which
exist on watsun.cc.columbia.edu in the ~kermit/test directory, and therefore
contains many of the bugfixes and enhancements which
have been mentioned for the IBM-PC version.

[Ed. - A version of MS-DOS Kermit 3.02 for the Heath/Zenith 100 is expected
soon too.  Watch Info-Kermit for an announcement.]

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

Date: Wed Nov  7 17:01:54 1990
>From: Christine M Gianone
Subject: New Kermit for Gould/SEL 32/77 MPX
Keywords: Gould/SEL Kermit, MPX Kermit

This is to announce a Kermit server program for the Gould/SEL 32/77 computer
with the MPX 1.5E operating system, from Barry M. Wilson, Queensland
Electricity Commision, Belmont State Control Centre, 311 Wecker Road,
Mansfield, Queensland 4122, Australia, phone [phone].

There is no user interface, it is a server only.  It supports long packets,
up to 768 bytes in and 1000 bytes out.  It handles run-length compression
encoding in incoming packets, but does not compress when sending.  There is no
further documentation.

The source files and build procedure are collected together into a single
file, kermit/d/gm3ker.jar (a "join archive") on watsun for anonymous FTP
(Internet) and GM3KER.JAR from KERMSRV at CUVMA (BITNET).

Thanks to Barry for doing the work and sending it in!

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

Date: Sun, 14 Oct 90 17:20:36 -0700
>From: [e-mail] (Merton Campbell Crockett)
Subject: MS-Kermit 3.02 Argument Handling, Keyboard Mapping
Keywords: MS-DOS Kermit 3.02

When using version 3.02 of MS-Kermit, I get an error, "?word xxxxx not usable
here.", when entering the command

        dial xxxxx

however, although an error is reported, the HAYES.TAK command file is invoked
and attempts to dial "ATDTxxxxx"--not exactly the intended operation.

The DIAL macro is the one defined in Christine Gianone's MSKERMIT.INI file.
The LOOKUP macro was modified as shown below.  The macros worked under version
3.00 and 3.01.

[Ed. - Right you are.  There were many complaints about the way Kermit's macro
arguments were handled -- they were not saved and restored across calls like
real function arguments.  Now they are.  Unfortunately this breaks the nice
LOOKUP and DIAL macros.  They must be slightly recoded to use a global
variable.  Hopefully the benefits are worth it.  Something like this,
maybe:

def lookup -
  if eq \%1 compuserve  def \%9 7654321,-
  if eq \%1 telenet     def \%9 8765432,-
  if eq \%1 fishnet     def \%9 9876543,-
  if eq \%1 hairnet     def \%9 5551234,-
  if def \%9 assign \%n \%9

;   DIAL macro to dial a number.  The argument can be either a telephone
;   number or a string defined in a lookup(x) macro.  The macro requires
;   HAYES.TAK to be in the current directory or in a defined DOS PATH.

def dial if = argc 2 assign \%n \%1,-
  if < argc 2 if not def \%n fatal {Dial what?},-
  if > argc 2 fatal {No spaces please.},-
  lookup \%n,-
  assign \%1 \%n,-
  take hayes.tak

I connect to several different office automation systems based on Unix
platforms which presume that the "terminal" is a DEC VT100 class terminal and
make heavy use of the VT100 keypad for functions and subfunctions.  I also use
EDT on IAS and VMS platforms.  The following excerpt from my MSKERMIT.INI
command file may be of interest to others with 101 key keyboards who find
MS-DOS Kermit standard mappings hard to remember or would just prefer to have
the keypad in a manner more similar to a VT100, VT200, or VT300 class
terminal.

[Ed. - Many thanks, your contribution has been added to MSIVT3.INI, our
collection VT300 keyboard mappings...]

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

Date: Wed, 1990 Oct 10   22:35 EDT
>From: "John F. Chandler"   <[e-mail]>
Subject: Re: Kermit REMOTE SET Command
Keywords: REMOTE SET, Kermit Commands, Remote Commands

> This is actually a tricky situation.  The idea was that TRANSPARENT should
> be the default, for compatibility with the hundreds of Kermit programs that
> do not support the character-set extension.
>
Let's not forget that it would be the default only for systems whose native
character set is ASCII.  Its meaning, in fact, is rather nebulous, since it
is very similar to FILE TYPE BINARY for ASCII systems.  What it means, in
short, is "use the FILE CHARACTER-SET for the TRANSFER (or vice versa)."
However, a TRANSPARENT sender cannot presume to tell the receiver what
character set to use, so the situation is, indeed, tricky.  The natural
Encoding attribute for TRANSPARENT transfers is "*!A" on all ASCII systems (or
perhaps no attribute at all), but there is *no* natural value on non-ASCII
(e.g., EBCDIC) systems.

> Adding a new designator to denote TRANSPARENT might confuse Kermits that
> don't understand it, including Kermits that support the character-set
> extension, if that designator were to arrive in an Attribute packet.
>
You bet.

> So far, it has been an implementation decision about whether character-set
> changes based on incoming attribute packets are "sticky".  If they are, this
> presents the problem that there is no way for a client to tell a server to
> switch from translation to transparent.
>
.. except, of course, REMOTE KERMIT SET TRANSF CHAR TRANSP.

> So it would appear that a decent compromise would be to invent a new
> designator, say K0, for TRANSPARENT, and to support it in REMOTE SET
> TRANSFER CHARACTER-SET commands, but, at least for a time, not use it in
> Attribute packets.  Opinions?]
>
Yes.  I would say, though, that K0 should never be allowed in A-packets.
                                           John

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

Date: 11 Oct 90 20:17:40 GMT
>From: [e-mail]
Subject: Kermit for STRATUS/VOS?
Keywords: Stratus, VOS

Looking for a version of KERMIT that runs on STRATUS and supports full set of
KERMIT commands.  Currently have a version of KERMIT that only knows how to
receive ASCII files.  Would like to have a version that supports both sending
and the receiving and can act as both the initiating and terminating end of a
KERMIT session.  Also, would like a version that supports the transportation
of binary files.

A portable version would be acceptable.

[Ed. - Good luck!  In fact, you seem to have more than we do -- our listings
don't show any entries for Stratus at all.  Anybody out there know anything
or working on anything for the Stratus?  We have a similar request from
Bill Oliver, MD, Department of Hospital Labs, UNC Hospitals,
[e-mail].]

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

Date: 30 Oct 90 18:15:13 GMT
>From: [e-mail] (Gordon Maskew Fair, III)
Subject: Kermit vs Hypercard?
Keywords: Hypercard Kermit

Has there been a stack created that will allow one to use all the
kermit, and/or xmodem, and/or ymodem commands?  If there is anything
somewhat like this I would greatly appreciate it.

Thanks in advance,

Gordon

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

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