@make(manual)
@use(database="ERCY02:SCRIBEX")
@style(font timesroman12)
@libraryfile(misc)
@modify(description, spread 1)
@string(ckoversion="1.00")
@string(NODEBUGLOG="(Debug logging is disabled.)")
@string(no="no. ")
@define(exx=example,above 2,below 1)
@define(mydesc=text,leftmargin +8, indent -8)
@define(q=t)
@define(qq=t)
@begin(text, indent 0)
@majorheading(C-Kermit for OS/2)
@centre(Version @value<ckoversion>)
@centre(by Chris Adie et al.)

@begin(format, centred)
Copyright (C) 1988 Edinburgh University Computing Service.
Portions of this document are Copyright (C) 1981, 1988 Trustees
of Columbia University in the city of New York.


Permission is granted to any individual or institution to use, copy,
or redistribute this document so long as it is not sold for
profit, and provided this copyright notice is retained.
@end(format)

@section(Introduction)
@subsection(Acknowledgements)
C-Kermit was written by Frank da Cruz, Bill Catchings, Jeff Damens and
Herm Fischer, with contributions by many others.  It was originally
written for computers running the Unix operating system, but it has been
ported to the VAX running VMS, the Apple Macintosh and the Commodore
Amiga, among others.  The program was ported to OS/2 by Chris Adie
(Edinburgh University Computing Service).

This documentation is based closely on the C-Kermit manual by Frank da
Cruz and Herm Fischer.  The section on the OS/2 file system is based on
the MS-Kermit manual, by Christine Gianone, Frank da Cruz and Joe
Doupnik.  It should be read in conjunction with a more general
description of Kermit such as "The Kermit File Transfer Protocol" by
Frank da Cruz (Digital Press, ISBN 0-932376-88-6), or the Kermit User
Guide, available in machine readable form from your nearest Kermit
distribution centre. 

@subsection<OS/2 Kermit Capabilities>
C-Kermit provides traditional (Unix-style) command line operation as
well as interactive command prompting and execution.  The command line
options provide access to a basic subset of C-Kermit's capabilities; the
interactive command set is far richer. 

C-Kermit is a protected-mode program.  It will not run in the DOS
compatability environment.  This means that it will continue running
(eg transferring files) even when it is not the foreground session. 

@i(All numbers in the C-Kermit documentation are decimal unless noted
otherwise.)

@need(32)
Summary of capabilities:
@begin<format,leftmargin +2,above 1,below 1>
@tabclear()@tabset(3.5inches,4.0inches)
Local operation:@\Yes
Remote operation:@\No
Login scripts:@\Yes (UUCP style)
Transfer text files:@\Yes
Transfer binary files:@\Yes
Wildcard send:@\Yes
File transfer interruption:@\Yes
Filename collision avoidance:@\Yes
Can time out:@\Yes
8th-bit prefixing:@\Yes
Repeat count prefixing:@\Yes
Alternate block checks:@\Yes
Terminal emulation:@\Yes
Communication settings:@\Yes
Transmit BREAK:@\Yes
Support for dialout modems:@\Yes
IBM mainframe communication:@\Yes
Transaction logging:@\Yes
Session logging:@\Yes
Debug logging:@\Yes @value(NODEBUGLOG)
Packet logging:@\Yes
Act as server:@\Yes
Talk to server:@\Yes
Advanced server functions:@\Yes
Local file management:@\Yes
Command/Init files:@\Yes
Long packets:@\Yes
Sliding Windows:@\No
File attributes packets:@\No
Command macros:@\No
Raw file transmit:@\No
@end<format>
 
@subsection(Requirements)

C-Kermit will run on a computer with an 80286 or 80386 processor running
OS/2 version 1.0 or higher.  It runs in character mode - in other words it
is not a Presentation Manager application.  However, it will run in a
Presentation Manager window as a character application.  Normally, though,
you would run it from the command processor (CMD.EXE) prompt.

@subsection(The Serial Port)
Naturally, a serial port (COM1 or COM2) is required.  The OS/2 Standard
Edition comms port device driver must be loaded using a line like one of
the following in the CONFIG.SYS file:

@begin(example)
@tabset(2 inches)
@\DEVICE=COM01.SYS
@i(or)@\DEVICE=COM02.SYS
@end(example)

COM01.SYS is used for PC/AT - type machines, while for PS/2s COM02.SYS
must be used.  C-Kermit @i'will not work' if this device driver is not
loaded.  (It provides the Category 1 IOCTLs which are used extensively
within the program.)

The connecting cable and the modem (or other computer, PAD etc to which
your computer is connected) must satisfy the requirements of your
computer's RS232 interface.  In particular, the computer will provide
two output control signals (RTS and DTR), and may expect to see signals
on four input lines (DCD, DSR, CTS, RI).  The precise behaviour of these
lines is software configurable (for instance by using the OS/2
'@q(MODE)' command), and C-Kermit makes no attempt to impose a
particular method of using them. 

By default, the DTR and RTS line will both go ON when C-Kermit opens the
comms port, and they will go OFF when it is closed.

The default behaviour for the input lines is that DSR and CTS must be ON
to enable the port to work.  If the modem you are connected to does not
provide these signals, you can 'loop back' the RTS output signal from
the computer to DSR and CTS, using a suitably modified cable.  An alternative
is to use the MODE command to disable the DSR and CTS inputs.  To do this,
type a command similar to the following at the OS/2 CMD prompt:
@begin(example)
MODE COM1:9600,N,8,1,OCTS=OFF,ODSR=OFF,IDSR=OFF
@end(example)
You can check the effect using:
@begin(example)
MODE COM1
@end(example)
which reports the current settings of COM1.  Note that on some machines,
C-Kermit may appear to work even although DSR and CTS are not connected
to anything, nor disabled using '@q(MODE)'.  This is because unconnected
input lines tend to 'float high'.  Although this situation may not cause
any problems, it is not good practice - you should explicitly disable
the inputs as above. 

The '@q(MODE)' utility also allows you to change the baud rate, parity,
number of data bits and number of stop bits.  C-Kermit provides
facilities for changing the baud rate and parity too (see later in this
manual), but when it starts up, it resets the parity to none and the
number of data bits to 8.  Any changes to baud rate and parity will
remain in effect after C-Kermit terminates.

If you change the parity within C-Kermit, it will ajust the number of data
bits to cope.  There is no way of changing the number of stop bits within
C-Kermit: use '@q(MODE)' to do this.

@subsection(Emergency Exit)
@begin(quotation)
@i(EMERGENCY EXIT:)@index<Emergency Exit>
The Control-C key cannot be used to terminate C-Kermit.  The Control-Break
key will always work, but it takes you back to the Program Selector rather
than the CMD.EXE command interpreter from which Kermit was invoked.
@end(quotation)
@newpage
@section(The OS/2 File System)

The features of the OS/2 file system of greatest interest to Kermit users are
the form of the file specifications, and the formats of the files themselves.
Note that the following discussion refers to the MS-DOS compatible file
system supported by initial versions of OS/2.  Installable file systems
are not covered here - they are significantly different, and the extent to
which C-Kermit will work under such file systems is unknown (because no
installable file system has been released at the time of writing).
 
@subsection(File Specifications)
 
OS/2 file specifications are of the form
 
@exx(@c[DEVICE@q(:\)PATHNAME@q(\)NAME@q(.)TYPE])
 
where @c{DEVICE} stands for a single character identifier (for instance, @q(A) for
the first floppy disk, @q(C) for the first fixed disk, @q(D) for a RAM disk
emulator) followed by a colon ('@q(:)'), @c[PATHNAME] is up to 63 characters
of identifier(s) (up to 8 characters each) surrounded by backslashes
('@q(\)'), @c[NAME] is an identifier of up to 8 characters, and @c[TYPE] is an
identifier of up to 3 characters in length.  Device and pathname may be
omitted.  The first backslash in the pathname may be omitted if the
specified path is relative to the current directory.  In the path field,
'@q(.)' means the current directory, '@q(..)' means the parent directory.

Pathname is normally omitted, but can be specified in all C-Kermit
commands.  Device and directory pathnames, when omitted, default to
either the user's current disk and directory, or to the current
directory search path as specified in the PATH environment variable,
depending on the context in which the file name appears. 
 
When this document says that a file is searched for "in the current
path," it means that C-Kermit looks on the current disk and directory
first, and if the file is not found, then the directories listed in the
PATH environment variable are searched.  If the PATH environment
variable is empty, Kermit looks only at the current disk and directory. 
 
@i[NAME.TYPE] is sufficient to specify a file on the current disk and
directory, and only this information is sent along by C-Kermit with an
outgoing file (by default).
 
The device, path, name, and type fields may contain uppercase letters,
digits, and the special characters '@q[-]' (dash), '@q[_]' (underscore),
'@q[$]' (dollar sign), '@q[&]' (ampersand), '@q[@hash()]' (number sign),
'@q[@@]' (at sign), '@q[!]' (exclamation mark), '@q[']' (single quote),
'@q[()]' (parentheses), '@q[{}]' (curly braces), '@q[^]' (caret or
circumflex), '@q[~]' (tilde), and '@q[`]' (accent grave).  Normally, you
should confine your filenames to letters and digits for maximum
transportability to non-OS/2 systems (by default, C-Kermit will
translate filenames being sent by converting non-alphanumeric characters
to '@q(X)').  When you type lowercase letters in filenames, they are
converted automatically to uppercase.  There are no imbedded or trailing
spaces.  Other characters may not be included; there is no mechanism for
"quoting" otherwise illegal characters in filenames.  The fields of the
file specification are set off from one another by the punctuation
indicated above (ie colon, backslash and dot). 
 
The name field is the primary identifier for the file.  The type, also
called the extension or suffix, is an indicator which, by convention,
tells what kind of file we have.  For instance @q[FOO.BAS] is the source of
a BASIC program named FOO; @q[FOO.OBJ] might be the relocatable object
module produced by compiling @q[FOO.BAS]; @q[FOO.EXE] could be an executable
program produced by loading @q[FOO.OBJ], and so forth.  @q[.EXE] is
the normal suffix for executable programs. 
 
OS/2 allows a group of files to be specified in a single file
specification by including the special "wildcard" characters, '@q[*]' and
'@q[?]'.  A '@q[*]' matches any string of characters from the current position
to the end of the field, including no characters at all; a '@q[?]' matches
any single character.  Here are some examples:
@begin(description)
@tabclear()@tabset(1.5 inches)
@q[*.BAS]@\All files of type BAS (BASIC source files) in the current directory.
 
@q[FOO.*]@\Files of all types with name FOO.
 
@q[F*.*]@\All files whose names start with F.
 
@q[*.?]@\All files with types exactly one character long, or with no type at all.
@end(description) 
Wildcard  notation  is used on many computer systems in similar ways, and it is
the mechanism most commonly used to instruct Kermit to send a group of files.
 
You should bear in mind that other (non-OS/2) systems may use different
wildcard characters.  For instance VMS and the DEC-20 use '@q[%]' instead of
'@q[?]' as the single character wildcard; when using C-Kermit to request a
wildcard file group from a Kermit-20 server, the OS/2 '@q[?]' must be
replaced by the DEC-20 '@q[%]'. 
 
 
@subsection(File Formats)
 
OS/2 systems store files as streams of 8-bit bytes, with no particular
distinction among text, program code, and binary files.  ASCII text
files consist of lines separated by carriage-return-linefeed sequences
(CRLFs), and this conforms exactly to the way Kermit represents text
files during transmission.
 
OS/2 (unlike CP/M) knows the exact end of a file because it keeps a byte
count in the directory, so one would expect no particular confusion in
this regard.  However, certain MS-DOS and OS/2 programs continue to use the CP/M
convention of terminating a text file with a Control-Z character.  This
may cause problems when the file is transferred elsewhere, since other
systems may object to the Control-Z.  By default, therefore, C-Kermit
treats the first Control-Z it finds in the file as being equivalent to
end-of-file.  The Control-Z is not transmitted to the other system.  Of
course, this leads to problems when transferring non-text files, when we
@i(do) want any Control-Zs in the file to be sent.  To achieve this, the
C-Kermit '@q(set file type binary)' command may be used.  The opposite, '@q(set
file type text)', is the default. 
 
Non-OS/2  systems  may  be  confused  by  nonstandard  ASCII  files  sent  by
C-Kermit:
@begin(itemize)
Files  containing  any  of  the 8-bit "extended ASCII" characters may
need conversion (or translation) to 7-bit ASCII.
 
Files produced by word processing programs like Word Perfect or Wordstar
may contain special binary formatting codes, and could need conversion
to conventional 7-bit ASCII format prior to transmission, using commonly
available "exporter" programs. 

Spreadsheet or database files usually need special formatting  to  be
meaningful  to  non-OS/2 recipients (though they can be transmitted
between OS/2 and MS-DOS systems with Kermit).
 
BASIC programs are normally saved in a binary "tokenized" form.   Use
BASIC's "@q(,a)" option to save them as regular ASCII text, as in
@begin(example) 
         save"foofa",a
@end(example)
@end(itemize) 
In  general,  when  attempting  to transfer non-text files between OS/2 and a
different kind of system, consult the Kermit manual for that system.
 
 
@newpage
@section(File Transfer)
 
When C-Kermit is transferring a file, the screen (stdout) is continously updated to
show the progress of the file transer.  A dot is printed for every four data
packets, other packets are shown by type:
@begin(description,leftmargin +6, indent -2, spread 0)
I@\Exchange Parameter Information
 
R@\Receive Initiate
 
S@\Send Initiate
 
F@\File Header
 
G@\Generic Server Command
 
C@\Remote Host Command
 
N@\Negative Acknowledgement (NAK)
 
E@\Fatal Error
 
T@\Indicates a timeout occurred
 
Q@\Indicates a damaged, undesired, or illegal packet was received
 
@q<%>@\Indicates a packet was retransmitted
@end(description)
You may type certain "interrupt" commands during file transfer:
@begin(description,leftmargin +16,indent -12,spread 0)
Control-F:@\Interrupt the current File, and go on to the next (if any).
 
Control-B:@\Interrupt the entire Batch of files, terminate the transaction.
 
Control-R:@\Resend the current packet.
 
Control-A:@\Display a status report for the current transaction.
@end(description)
These interrupt characters differ from the ones used in other Kermit
implementations to avoid conflict with commonly used Unix shell interrupt
characters.  This reason, of course, is not valid under OS/2, and in
a future version of C-Kermit for OS/2 it is hoped to rectify this.
 
@begin(quotation)
@i(CAUTION:)@index(Warning)@index<File Warning>
If Control-F or Control-B is used to cancel an incoming file,
and a file of the same name previously existed, @i(and) the "file warning"
feature is not enabled, then the previous copy of the file will disappear.
@end(quotation)
 
The Emergency Exit key (Control-Break) can be used to terminate Kermit
in the middle of a file transfer.  This will not terminate the transfer
gracefully (it is a 'brute force' method), so the remote Kermit system
may be left in an undefined state.
 
@newpage
@section(Command Line Operation)

The C-Kermit command line syntax conforms to the @ux(Proposed Syntax Standards
for Unix System Commands) put forth by Kathy Hemenway and Helene Armitage of
AT&T Bell Laboratories in @i(Unix/World), Vol.1, No.3, 1984.  The implications
of this for specifying command-line options are:
@begin(itemize,spread 0)
An option name is a single character.
 
Options are delimited by '@q(-)'.
 
Options with no arguments may be grouped (bundled) behind one delimiter.
 
Options which take an argument must not have the argument omitted.
 
Arguments immediately follow options, separated by whitespace.
 
The order of options does not matter.
 
A '@q(-)' preceded and followed by whitespace means standard input.

A group of bundled options may end with an option that has an argument.
@end(itemize) 
The following notation is used in command descriptions:
@begin(description,leftmargin +8,indent -8)
@i(fn)@\An OS/2 file specification, possibly containing the "wildcard"
characters '@q[*]' or '@q[?]'.
 
@i(fn1)@\An OS/2 file specification which may not contain '@q[*]' or '@q[?]'.
 
@i(rfn)@\A remote file specification in the remote system's own syntax, which
may denote a single file or a group of files.
 
@i(rfn1)@\A remote file specification which should denote only a single file.
 
@i(n)@\A decimal number between 0 and 94.
 
@i(c)@\A decimal number between 0 and 127 representing the value of an
ASCII character.
 
@i(cc)@\A decimal number between 0 and 31, or else exactly 127,
representing the value of an ASCII control character.
 
@q([ ])@\Any field in square braces is optional.
 
@q({x,y,z})@\Alternatives are listed in curly braces.
@end(description)
 
C-Kermit command line options may specify any combination of actions and
settings.  If C-Kermit is invoked with a command line that specifies no
actions, then it will issue a prompt and begin interactive dialog.  Action
options specify either protocol transactions or terminal connection.
@subsection(Command Line Options) 
@begin<description,leftmargin +8,indent -8>
@q(-s )@i(fn)@\Send the specified file.
If @i(fn) is '@q[-]' then kermit sends from standard input, which may
come from a file:
@example(kermit -s - < foo.bar)
or a parallel process:
@example(dir *.txt | kermit -s -)
You cannot use this mechanism to send
console typein.  If you want to send a file whose actual name is '@q(-)'
you can precede it with a path name, as in
@example(kermit -s .\-)
The argument @i(fn) may contain wildcards.  For instance,
@example(kermit -s ck*.h)
will send all the files matching the specification '@q(ck*.h)'.
 
@q(-r)@\Receive a file or files.  Wait passively for files to arrive.
 
@q(-k)@\Receive (passively) a file or files, sending them to standard
output.  This option can be used in several ways:

@begin(mydesc)
@q(kermit -k)@*Displays the incoming files on your screen.
 
@q(kermit -k > )@i(fn1)@*Sends the incoming file or files to the named file,
@i(fn1).  If more than one file arrives, all are concatenated together
into the single file @i(fn1).
 
@q(kermit -k | command)@*Pipes the incoming data (single or multiple
files) to the indicated command, as in
@example'kermit -k | sort > sorted.txt'
@end(mydesc)
 
@q(-a )@i(fn1)@\If you have specified a file transfer option, you may give
an alternate name for a single file with the @q(-a) ("as") option.  For
example,
@example'kermit -s foo -a bar'
sends the file @q(foo) telling the receiver that its name is @q(bar).
If more than one file arrives or is sent, only the first file is
affected by the @q(-a) option:
@example'kermit -ra baz'
stores the first incoming file under the name @q(baz).
 
@q(-x)@\Begin server operation.
@end(description)
 
Before proceeding, a few words about remote and local operation are
necessary.  Kermit (in general, not just C-Kermit) is "local" if it is
running on PC or workstation that you are using directly, or if it is
running on a multiuser system and transferring files over an external
communication line -- not your job's controlling terminal or console. 
Kermit is remote if it is running on a multiuser system and transferring
files over its own controlling terminal's communication line, connected
to your PC or workstation. 
 
C-Kermit running under OS/2 is always used in local mode, with the
serial port at the back of the machine designated for file transfer and
terminal connection.  Which serial port to use is determined by the
@q(-l) command-line option:
 
@begin(description,leftmargin +8,indent -8)
@q(-l )@i(dev)@\Line  -- Specify a serial line to use for file
transfer and terminal connection, as in
@example'kermit -l com2'
The default line is COM1.
@end(description)
 
There are a number of other options associated with the use of the serial
port:
 
@begin(description,leftmargin +8,indent -8)
@q(-b )@i(n)@\Baud  -- Specify the baud rate for the line given in the
@q(-l) option, as in
@example'kermit -l com2 -b 9600'
It is good practice to include this with the @q(-l) option, since the
current speed of the serial port might not be what you expect.
 
@q(-p )@i(x)@\Parity -- @i(x) may be one of @q(e),@q(o),@q(m),@q(s),@q(n)
(even, odd, mark, space, or none).  If parity
is other than none, then the 8th-bit prefixing mechanism will be
used for transferring 8-bit binary data, provided the opposite
Kermit agrees.  The default parity is none.
 
@q(-t)@\Specifies half duplex, line turnaround with XON as the handshake
character.
@end(description)
 
The following command line options access a remote Kermit server:
 
@begin(description,leftmargin +8,indent -8)
@q(-g )@i(rfn)@\Actively request a remote server to send the named file
or files; @i(rfn) is a file specification in the remote host's own syntax.
 
@q(-f)@\Send a 'finish' command to a remote server.
@end(description)
The following command line options are to do with connecting to the remote
system as a terminal: 
@begin(description,leftmargin +8,indent -8)
@q(-c)@\Establish a terminal connection over the specified or default
communication line, before any protocol transaction takes place.
Get back to the local system by typing the escape character
(normally Control-@q<]>) followed by the letter '@q(c)'.
 
@q(-n)@\Like @q(-c), but @i(after) a protocol transaction takes place;
@q(-c) and @q(-n) may both be used in the same command.  The use of @q(-n)
and @q(-c) is illustrated below.
@end(description)
 
Several other command-line options are provided:
@begin(description,leftmargin +8,indent -8)
@q(-i)@\Specifies that files should be sent or received exactly "as is" with no
conversions.  This option is necessary for transmitting binary files, and is 
equivalent to the '@q(set file type binary)' interactive command.
 
@q(-w)@\Write-Protect -- Avoid filename collisions for incoming files.
 
@q(-e @i<n>)@\Extended packet length -- Specify that C-Kermit is allowed to
receive packets up to length @i<n>, where @i<n> may be between 10 and some
large number, like 1000, depending on the system.  The default maximum length
for received packets is 90.  Packets longer than 94 will be used only if the
other Kermit supports, and agrees to use, the "long packet" protocol extension.
 
@q(-q)@\Quiet -- Suppress screen update during file transfer, for instance
to allow a file transfer to proceed in the background.
 
@q(-d)@\Debug -- Record debugging information in the file @q(debug.log) in
the current directory.  Use this option if you believe the program
is misbehaving, and show the resulting log to your local
Kermit maintainer. @value(NODEBUGLOG)
 
@q(-h)@\Help -- Display a brief synopsis of the command line options.

@q(-u @i<d>)@\File handle -- The argument @i<d> is the numerical value of
an open file handle which Kermit will use for its communication line.  This
option is for use only by other programs which interface with Kermit, not for
typing in the command line (so it's not described in the help information from
@q(-h)). Further details are given in the Appendix.
@end(description)
The command line may contain no more than one protocol action option (ie only
one of: @q(-s), @q(-a), @q(-r), @q(-k), @q(-x), @q(-g), @q(-f)).
 
Files are sent with their own names, except that lowercase letters are
raised to upper, drive specifiers and pathnames are stripped off, and
non-alphanumeric characters (excepting the dot) are changed to '@q(X)'. 
Incoming files are stored under their own names.  If @q(-w) was
specified, a "generation number" is appended to the name if it has the
same name as an existing file which would otherwise be overwritten.  If
the @q(-a) option is included, then the same rules apply to its
argument.  The file transfer display shows any transformations performed
upon filenames. 
 
During transmission, files are encoded as follows:
@begin(itemize)
Control characters are converted to prefixed printables.
 
Sequences of repeated characters are collapsed via repeat counts, if
the other Kermit is also capable of repeated-@|character compression.
 
If parity is being used on the communication line, data characters with
the 8th (parity) bit on are specially prefixed (provided the other Kermit
is capable of 8th-bit prefixing; if not, 8-bit binary files cannot be
successfully transferred).
@end(itemize)
 
@subsection(Command Line Examples)
 
@exx(kermit -l com1 -b 1200 -cn -r)
This command connects you to the system on the other end of COM1 at
1200 baud, where you presumably log in and run Kermit with a '@q(send)'
command.  After you escape back, C-Kermit waits for a file (or files) to
arrive.  When the file transfer is completed, you are reconnected to
the remote system so that you can logout.
 
@exx(kermit -l com2 -b 9600 -cntp m -r -a foo.bar)
This command is like the preceding one, except the remote system in this
case uses half duplex communication with mark parity.  The first file
that arrives is stored under the name @q(foo.bar).
 
@exx(kermit -nf)
This command would be used to shut down a remote server and then connect
to the remote system, in order to log out or to make further use of it.
The @q(-n) option is invoked @i(after) @q(-f) (@q[-c] would have been invoked
before).  This example assumes that the remote server is connected to COM1
(Kermit's default comms port), and that the current baud rate of the port
is acceptable to the remote server.
 
@exx(kermit -wx)
This command starts up C-Kermit as a server.  
Incoming files that have the same names as existing files are given
new, unique names.
 
@exx(kermit -l com2 -b 9600)
This command sets the communication line and speed.  Since no action is
specified, C-Kermit issues a prompt and enters an interactive dialog
with you.  Any settings given on the command line remain in force during
the dialog, unless explicitly changed (eg in this case by '@q(set line)'
or '@q(set speed)' commands). 

@exx(kermit)
This command starts up Kermit interactively with all default settings. The
serial line used will be COM1, and the speed used will be the current speed
of COM1.

A final example shows how a (hypothetical) OS/2 compression utility might be used to speed
up Kermit file transfers:
@begin(example)
compress < file | kermit -is -     @i[(sender)]
kermit -ik | uncompress > file     @i[(receiver)]
@end(example)
 
@subsection(Exit Status Codes)
 
C-Kermit returns an exit status of zero, except when a fatal error is
encountered, when the exit status is set to one.  This can be used in a batch
file, to take some action depending on whether the operation was successful.
For instance, suppose the file @q(SEND.CMD) contains the following:
@begin(example)
echo Sending %1 out port %2
kermit -ql COM%2 -b 9600 -s %1
if ERRORLEVEL 1 goto badend
echo Transferred succcessfully!
goto end
:badend
echo Transfer problems!
:end
@end(example)
To send a file @q(FOO.BAS), you could type:
@exx(send foo.bas 2)
to send it to another computer running Kermit, connected to port COM2.  
If the transfer completed OK, you would get the message '@q(Transferred
successfully!)'.
@newpage
@section(Interactive Operation)
 
C-Kermit's interactive command prompt is "@q(C-Kermit>)".  In response to this
prompt, you may type any valid interactive C-Kermit command.  C-Kermit executes
the command and then prompts you for another command.  The process continues
until you instruct the program to terminate.
 
Commands begin with a keyword, normally an English verb, such as
'@q(send)'.  You may omit trailing characters from any keyword, so long
as you specify sufficient characters to distinguish it from any other
keyword valid in that field.  Certain commonly-@|used keywords (such as
'@q(send)', '@q(receive)', '@q(connect)') also have special non-@|unique
abbreviations ('@q(s)' for '@q(send)', '@q(r)' for '@q(receive)',
'@q(c)' for '@q(connect)'). 
 
Certain characters have special functions during typein of interactive
commands:
@Begin(Description,leftmargin +8,indent -4)
@q(?)@\Question mark, typed at any point in a command, will produce a
message explaining what is possible or expected at that point.  Depending on
the context, the message may be a brief phrase, a menu of keywords, or a list
of files.
 
@q(ESC)@\(The Escape key) -- Request completion of the current
keyword or filename, or insertion of a default value.  The result will be a
beep if the requested operation fails.
 
@q(BS)@\(Backspace) -- Delete the previous character from the command.
 
@q(^W)@\(Control-W) -- Erase the rightmost word from the command line.
 
@q(^U)@\(Control-U) -- Erase the entire command.
 
@q(^R)@\(Control-R) -- Redisplay the current command.
 
@q(SP)@\(Space) -- Delimits fields (keywords, filenames, numbers) within
a command.  The tab key may also be used for this purpose.
 
@q(CR)@\(Carriage Return or Enter) -- Enters the command for execution.  LF (Linefeed or Control-J)
or FF (formfeed or Control-L) may also be used for this purpose.
 
@q(^)@\(Circumflex) -- Enter any of the above characters into the command,
literally.  To enter a @q(^), type two of them in a row (@q[^^]).
A circumflex at the end of a command line causes the next line to be treated
as a continuation line; this is useful for readability in command files,
especially in the 'script' command.
@end(description)
You may type the editing characters (@q[BS], @q[^W], etc) repeatedly, to
delete all the way back to the prompt.  No action will be performed until the
command is entered by typing carriage return, linefeed, or formfeed.  If you
make any mistakes, you will receive an informative error message and a new
prompt -- make liberal use of '@q[?]' and '@q(ESC)' to feel your way through the
commands.  One important command is '@q(help)' -- you should use it the first time
you run C-Kermit.
 
A command line beginning with a percent sign '@q(%)' is ignored.  Such
lines may be used to include illustrative commentary in Kermit command dialogs.
 
Interactive C-Kermit accepts commands from files as well as from the keyboard.
When you start C-Kermit, the program looks for a file @q(CKERMIT.INI) in
the current PATH, and executes any commands it finds there.
The commands in @q(CKERMIT.INI) must be
in interactive format, not in the command-@|line format.  A '@q(take)' command is
also provided for use at any time during an interactive session, to allow
interactive-format commands to be executed from a file; command files may be
nested to any reasonable depth.
 
Here is a brief list of C-Kermit interactive commands:
@begin(format,spread 0)
@tabclear()@tabset(1.5inches,2.0inches,2.5inches)
@>@q(%)@\  Comment
@>@q(!)@\  Execute an OS/2 command, or start up CMD.EXE.
@>@q(bye)@\  Terminate and log out a remote Kermit server.
@>@q(close)@\  Close a log file.
@>@q(connect)@\  Establish a terminal connection to a remote system.
@>@q(cwd)@\  Change Working Directory.
@>@q(dial)@\  Dial a telephone number.
@>@q(directory)@\  Display a directory listing.
@>@q(echo)@\  Display arguments literally.
@>@q(exit)@\  Exit from the program, closing any open files.
@>@q(finish)@\  Tell remote Kermit server to exit, but not log out.
@>@q(get)@\  Get files from a remote Kermit server.
@>@q(help)@\  Display a help message for a given command.
@>@q(log)@\  Open log file: debugging, packet, session, transaction.
@>@q(quit)@\  Same as 'exit'.
@>@q(receive)@\  Passively wait for files to arrive.
@>@q(remote)@\  Do some file management on a remote Kermit server.
@>@q(script)@\  Execute a login script with a remote system.
@>@q(send)@\  Send files.
@>@q(server)@\  Begin server operation.
@>@q(set)@\  Set various parameters.
@>@q(show)@\  Display values of 'set' parameters.
@>@q(space)@\  Display current disk space usage.
@>@q(statistics)@\  Display statistics about most recent transaction.
@>@q(take)@\  Execute commands from a file.
@end(format)
 
The 'set' parameters are:
@begin(format,spread 0)
@tabclear()@tabset(1.5inches,2.0inches,2.5inches)
@>@q(block-check)@\  Level of packet error detection.
@>@q(delay)@\  How long to wait before sending first packet.
@>@q(duplex)@\  Specify which side echoes during '@q(connect)'.
@>@q(escape-character)@\  Prefix for "escape commands" during '@q(connect)'.
@>@q(file)@\  Set various file parameters.
@>@q(flow-control)@\  Communication line full-duplex flow control.
@>@q(handshake)@\  Communication line half-duplex turnaround character.
@>@q(incomplete)@\  Disposition for incompletely received files.
@>@q(line)@\  Communication line device name.
@>@q(modem-dialer)@\  Type of modem-dialer on communication line.
@>@q(parity)@\  Communication line character parity.
@>@q(prompt)@\  The C-Kermit program's interactive command prompt.
@>@q(receive)@\  Parameters for inbound packets.
@>@q(retry)@\  Packet retransmission limit.
@>@q(send)@\  Parameters for outbound packets.
@>@q(speed)@\  Communication line speed.
@>@q(terminal)@\  Terminal parameters.
@end(format)
 
The 'remote' commands are:
@begin(format,spread 0)
@tabclear()@tabset(1.5inches,2.0inches,2.5inches)
@>@q(cwd)@\  Change remote working directory.
@>@q(delete)@\  Delete remote files.
@>@q(directory)@\  Display a listing of remote file names.
@>@q(help)@\  Request help from a remote server.
@>@q(host)@\  A command to the remote host in its command language.
@>@q(space)@\  Display current disk space usage on remote system.
@>@q(type)@\  Display a remote file on your screen.
@>@q(who)@\  Show who's logged in, or get information about a user.
@end(format)
 
Most of these commands are described adequately in the Kermit User Guide or the
Kermit book.  Special aspects of certain C-Kermit commands are described
below.
@string[STXTBS="@tabclear()@tabset(1.2 inches, 3 inches)"]
@subsection<The 'send' command>
@value(STXTBS)
@begin(format)
Syntax:@\@q<send >@i(fn)
@i(or)@\@q<send >@i(fn1)@q< >@i<rfn1>
@end(format)
Send the file or files denoted by @i(fn) to the other Kermit, which should be
running as a server, or which should have been given the '@q<receive>' command.  Each file
is sent under its own name (as described above, or as specified by the '@q(set
file names)' command).  If the second form of the '@q<send>' command is used, i.e.
with @i(fn1) denoting a single OS/2 file, @i(rfn1) may be specified as a name
to send it under.  The '@q<send>' command may be abbreviated to '@q<s>', even though
'@q<s>' is not a unique abbreviation for a top-level C-Kermit command.
 
The wildcard characters '@q[*]' and '@q[?]' are accepted in
@i(fn).  If '@q[?]' is to be included, it must be prefixed by '@q[^]' to
override its normal function of providing help.  '@q[*]' matches any
string, '@q[?]' matches any single character.  When @i(fn) contains
'@q[*]' or '@q[?]' characters, there is a limit to the number of files
that can be matched, which varies depending on the length of the file
names involved.  If you get the message '@q"Too many files match"' then
you'll have to make a more judicious selection.
 
@subsection<The 'receive' command>
@value(STXTBS)
@begin(format)
Syntax:@\@q<receive>
@i<or>@\@q<receive >@i<fn1>
@end(format)
Passively wait for files to arrive from the other Kermit, which must be given
the '@q<send>' command -- the '@q<receive>' command does not work in conjunction with a
server (use '@q<get>' for that).  If @i(fn1) is specified, store the first incoming
file under that name.  The '@q<receive>' command may be abbreviated to '@q<r>'.
If the second form of the command is given, and @i(fn1) contains a path
specification, then that path must exist -- C-Kermit will not create a
directory for the file. 
 
@subsection<The 'get' command>
@value(STXTBS)
@begin(format)
Syntax:@\@q<get >@i<rfn>
@i<or>@\@q(get)
@\@i(rfn)
@\@i(fn1)
@end(format)
Request a remote Kermit server to send the named file or files.  Since a
remote file specification (or list) might contain spaces, which normally
delimit fields of a C-Kermit command, an alternate form of the command is
provided to allow the inbound file to be given a new name: type '@q<get>' alone
on a line, and you will be prompted separately for the remote and local
file specifications, for example
@Begin(Example)
C-Kermit>@ux(get)
 Remote file specification: @ux(profile exec)
 Local name to store it under: @ux(profile.ibm)
@End(Example)
As with '@q<receive>', if more than one file arrives as a result of the '@q<get>'
command, only the first will be stored under the alternate name given by
@i(fn1); the remaining files will be stored under their own names if possible.
If a '@q[?]' is to be included in the remote file specification, you must
prefix it with '@q[^]' to suppress its normal function of providing help.
 
If you have started a multiline '@q<get>' command, you may escape from its
lower-@|level prompts by typing a carriage return in response to the prompt,
e.g.
@Begin(Example)
C-Kermit>@ux(get)
 Remote file specification: @ux(foo)
 Local name to store it under: @i<(Type a carriage return here)>
(cancelled)
C-Kermit>
@End(Example)
 
@subsection(The 'server' command)
 
The '@q<server>' command places C-Kermit in "server mode" on the currently selected
communication line.  All further commands must arrive as valid Kermit packets
from the Kermit on the other end of the line.  The OS/2 C-Kermit server can
respond to the following commands:
@begin(format,spread 0,above 1,below 1)
@tabclear()@tabset(2.25inches)
@u<Command>@\@ux<Server Response>
  @q(get)@\  Sends files
  @q(send)@\  Receives files
  @q(bye)@\  Attempts to log itself out
  @q(finish)@\  Exits to level from which it was invoked
  @q(remote directory)@\  Sends directory lising
  @q(remote delete)@\  Removes files
  @q(remote cwd)@\  Changes working directory
  @q(remote type)@\  Sends files to your screen
  @q(remote space)@\  Reports about its disk usage
  @q(remote help)@\  Lists these capabilities
  @q(remote host)@\  Execute an OS/2 command
@end(format)
Note that the '@q<remote host>' command should be used with great care.  It should
only be used to invoke OS/2 commands which produce their output through
stdio, and which require no keyboard interaction.  Commands such as
'@q(copy)' and '@q(rename)' are OK (although they may sometimes produce output
on stderr, which will appear on the screen of the OS/2 system).  It is not
possible to use the '@q<remote host>' command to run a word proccessor, for
instance.

@subsection(The 'remote', 'bye', and 'finish' commands)
 
C-Kermit may itself request services from a remote Kermit server.  In
addition to '@q<send>' and '@q<get>', the following commands may also be sent from
C-Kermit to a Kermit server:
 
@begin(mydesc)
@q<remote cwd [@i(directory) ]>@*
If the optional remote directory specification is
included, you will be prompted on a separate line for a password, which will
not echo as you type it.  If the remote system does not require a password
for this operation, just type a carriage return.

@q<remote delete @i(rfn)>@*
delete remote file or files.
 
@q<remote directory [@i(rfn) ]>@*
directory listing of remote files.
 
@q<remote host @i(command)>@*
issue a command in the remote host's own command language.
 
@q<remote space>@*
disk usage report from the remote host.
 
@q<remote type @i(rfn)>@*
display remote file or files on the screen.
 
@q<remote who [@i(user) ]>@*
display information about who's logged in.
 
@q<remote help>@*
display remote server's capabilities.

@q<bye @i(and) finish>@*
When connected to a remote Kermit server, these commands
cause the remote server to terminate; '@q<finish>' returns it to Kermit or system
command level (depending on the implementation or how the program was invoked);
'@q<bye>' also requests it to log itself out.
@end(mydesc)
@subsection(The 'log' and 'close' commands)
@value(STXTBS)
@begin(format)
Syntax:@\@q<log {debugging, packets, session, transactions} [@i(fn1) ]>
@\@q(close {debugging, packets, session, transactions} )
@end(format) 
C-Kermit's progress may be logged in various ways.  The '@q<log>' command
opens a log, the '@q<close>' command closes it.  In addition, all open logs
are closed by the '@q<exit>' and '@q<quit>' commands.  A name may be specified for
a log file; if the name is omitted, the file is created with a default
name as shown below.
 
@begin(mydesc)
@q<log debugging>@*
This produces a voluminous log of the internal workings of
C-Kermit, of use to Kermit developers or maintainers in tracking down suspected
bugs in the C-Kermit program.  Use of this feature dramatically slows down the
Kermit protocol.  Default name: @q(debug.log). @value(NODEBUGLOG)
 
@q<log packets>@*
This produces a record of all the packets that go in and out of
the communication port.  This log is of use to Kermit maintainers who are
tracking down protocol problems in either C-Kermit or any Kermit that
C-Kermit is connected to.  Default name:  @q(packet.log).
 
@q<log session>@*
This log will contain a copy of everything you see on your screen
during the '@q<connect>' command, except for local messages or interaction with
local escape commands.  Default name:  @q(session.log).
 
@q<log transactions>@*
The transaction log is a record of all the files that were
sent or received while transaction logging was in effect.  It includes time
stamps and statistics, filename transformations, and records of any
errors that may have occurred.  The transaction log allows you to have
long unattended file transfer sessions without fear of missing some
vital screen message.  Default name:  @q(transact.log).
@end(mydesc)

The '@q<close>' command explicitly closes a log, e.g. '@q<close debug>'.
 
@i<Note:>  Debug and Transaction logs are a compile-time option; C-Kermit may
be compiled without these logs, in which case it will run faster, it will
take up less space on the disk, and the commands relating to them will not
be present.
 
@subsection(Local File Management Commands)
OS/2 Kermit allows some degree of local file management from interactive
command level:

@begin(mydesc)
@q<directory [@i(fn) ]>@*
Displays a listing of the names, sizes, and dates of files
matching @i(fn) (which defaults to '@q[*.*]').  Equivalent to '@q(dir)'.
 
@q<cwd @q[directory-name]>@*
Changes Kermit's working directory to the one given.  The directory specification
may be preceeded by a drive specifier, in which case that becomes the current
drive.  This command affects only
the Kermit process and any processes it may subsequently create.

@q<space>@*
Display information about disk space and/or quota in the current
directory and device.  Equivalent to '@q(chkdsk)'.
 
@q<! [@i(command) ]>@*
The command is executed by the OS/2 command interpreter CMD.EXE.  If no command
is specified, then CMD.EXE itself is started; terminating it by typing
'exit' will return you to C-Kermit command level.  Use the '@q(!)' command
to provide file management or other functions not explicitly provided by
C-Kermit commands.  The '@q(!)' command has certain peculiarities:
@begin(itemize,spread 0)
At least one space must separate the '@q(!)' from the @i(command).
 
A '@q(cd)' or '@q(chdir)' (change directory) command executed in this manner will have no effect
on returning to Kermit -- use the C-Kermit '@q(cwd)' command instead.
@end(itemize)
@end(mydesc)
 
@subsection(The 'set' Command)
@value(STXTBS)
@begin(format)
Syntax:@\@q<set @i(parameter [parameter] value)>
@end(format) 
Since Kermit is designed to allow diverse systems to communicate, it is
often necessary to issue special instructions to allow the program to adapt
to peculiarities of the another system or the communication path.  These
instructions are accomplished by the '@q<set>' command.  The '@q<show>' command may
be used to display current settings.  Here is a brief synopsis of settings
available in the current release of C-Kermit:
 
@begin(mydesc)
@q<block-check {1, 2, 3}>@*
Determines the level of per-packet error detection.
"1" is a single-@|character 6-bit checksum, folded to include the values of all
bits from each character.  "2" is a 2-character, 12-bit checksum.  "3" is a
3-character, 16-bit cyclic redundancy check (CRC).  The higher the block check,
the better the error detection and correction and the higher the resulting
overhead.  Type 1 is most commonly used; it is supported by all Kermit
implementations, and it has proven adequate in most circumstances.  Types 2 or
3 would be used to advantage when transferring 8-bit binary files over noisy
lines.
 
@q<delay @i(n)>@*
How many seconds to wait before sending the first packet after a
'@q<send>' command, in remote mode only.  It is irrelevant for OS/2 Kermit, since
it is always in local mode.
 
@q<duplex {full, half}>@*
For use during '@q<connect>'.  Specifies which side is doing
the echoing; '@q<full>' means the other side, '@q<half>' means C-Kermit must echo
typein itself.
 
@q<escape-character @i(cc)>@*
For use during '@q<connect>' to get C-Kermit's attention.
The escape character acts as a prefix to an 'escape command', for instance to
close the connection and return to C-Kermit or OS/2 command level.
The normal escape character is Control-@q<]> (29).
 
@q<file {display, names, type, warning}>@*
Establish various file-related parameters:

@begin(mydesc)
@q<display {on, off}>@*
Normally '@q<on>'; when in local mode, display progress of file
transfers on the screen (stdout), and listen to the keyboard for
interruptions.  If '@q<off>' (equivalent to '@q(-q)' on command line)
none of this is done, and the file transfer may proceed in the
background oblivious to any other work concurrently done at the console
terminal. 
 
@q<names {converted, literal}>@*
Normally '@q<converted>, which means that outbound filenames have path
specifications stripped and non-alphanumeric characters
changed to @q(X)'s (except for the dot).  '@q<literal>' means that none of these
conversions are done; therefore, any directory path appearing in a
received file specification must exist and be write-accessible.
When literal naming is being used, the sender should not use path
names in the file specification unless the same path exists on the
target system and is writable.
 
@q<type {binary, text} [{7, 8}]>@*
@begin<multiple>
The file type is normally text, which
means that any control-Z in a file being transmitted is treated as an
end-of-file mark.  Binary means transmit file contents without
conversion.  Binary ('@q(-i)' in command line notation) is necessary for
binary files. 
 
The optional trailing parameter tells the bytesize for file transfer. 
It is 8 by default.  If you specify 7, the high order bit will be
stripped from each byte of sent and received files.  This is useful for
transferring text files that may have extraneous high order bits set in
their disk representation (e.g.  Wordstar or similar word processor
files).
@end<multiple>
 
@q<warning {on, off}>@*
Normally '@q(off)', which means that incoming files will silently overwrite
existing files of the same name.  When '@q(on)' ('@q(-w)' on command line)
Kermit will check if an arriving file would overwrite an existing file;
if so, it will construct a new name for the arriving file, of the form
@q(FZZ)@i(n)@q(.BAR), where @q(FZZ.BAR) is the name they share and @i(n) is
a "generation number"; if @q(FZZ.BAR) exists, then the new file will be
called @q(FZZ00001.BAR).  If @q(FZZ.BAR) and @q(FZZ00001.BAR) exist, the
new file will be @q(FZZ00002.BAR), and so on.  If the common name were
more than 6 characters long (eg @q(GOODDATA.DAT)), then the new name for the
arriving file would be @q(GOODD001.DAT) and so on. 

@begin(quotation)
@i(CAUTION:)  If Control-F or Control-B is used to cancel an incoming file,
and a file of the same name previously existed, @i(and) the "file warning"
feature is not enabled, then the previous copy of the file will disappear.
@end(quotation)
@end(mydesc)
 
@q<flow-control {none, xon/xoff}>@*
Normally '@q<xon/xoff>' for full duplex flow control.
Should be set to '@q<none>' if the other system cannot do xon/xoff flow control, or
if you have issued a '@q<set handshake>' command.  If set to '@q(xon/xoff)', then
'@q(handshake)' should be set to '@q(none)'.  This setting applies during both terminal
connection and file transfer.
 
@q<incomplete {discard, keep}>@*
Disposition for incompletely received files.
If an incoming file is interrupted or an error occurs during transfer,
the part that was received so far is normally discarded.  If you '@q(set
incomplete keep)' then such file fragments will be kept.
 
@q<handshake {xon, xoff, cr, lf, bell, esc, none}>@*
Normally '@q(none)'.  Otherwise,
half-duplex communication line turnaround handshaking is done, which means
Kermit will not reply to a packet until it has received the indicated handshake
character or has timed out waiting for it; the handshake setting applies only
during file transfer.  If you '@q(set handshake)' to other than '@q(none)', then '@q(flow)'
should be set to '@q(none)'.
 
@q<line [@i(dev) ]>@*
The device name for the communication line to be used for file transfer and
terminal connection, e.g. @q(COM2).  If you omit the device name,
Kermit will revert to its default device, @q(COM1).
 
@q<modem-dialer {direct, hayes, racalvadic, ventel, ...}>@*
The type of modem dialer on the communication line.  '@q(direct)' indicates
either there is no dialout modem, or that if the line requires carrier
detection to open, then 'set line' will hang waiting for an incoming
call.  '@q"hayes"', '@q"ventel"', and the others indicate that '@q<set line>' (or
the '@q(-l)' argument) will prepare for a subsequent '@q<dial>' command for the
given dialer.  Support for new dialers is added from time to time, so
type '@q<set modem ?>' for a list of those supported in your copy of Kermit. 
See the description of the '@q(dial)' command. 
 
@q<parity {even, odd, mark, space, none}>@*
Specify character parity for use in
packets and terminal connection, normally '@q(none)'.  If other than '@q(none)', C-Kermit
will seek to use the 8th-bit prefixing mechanism for transferring 8-bit binary
data, which can be used successfully only if the other Kermit agrees; if not,
8-bit binary data cannot be successfully transferred.
 
@q<prompt [@i(string) ]>@*
The given string will be substituted for '@q(C-Kermit>)' as
this program's prompt.  If the string is omitted, the prompt will revert to
'@q(C-Kermit>)'.  If the string is enclosed in double quotes, the quotes will
be stripped and any leading and trailing blanks will be retained.
 
@q<send @i(parameter)>@*
Establish parameters to use when sending packets.  These will be in effect
only for the initial packet sent, since the other Kermit may override these
parameters during the protocol parameter exchange (unless noted below).

@begin(mydesc)
@q<end-of-packet @i(cc)>@*
Specifies the control character needed by the other
Kermit to recognize the end of a packet.  C-Kermit sends this character at the
end of each packet.  Normally 13 (carriage return), which most Kermit
implementations require.  Other Kermits require no terminator at all, still
others may require a different terminator, like linefeed (10).
 
@q<packet-length @i(n)>@*
Specify the maximum packet length to send.  Normally 90.
Shorter packet lengths can be useful on noisy lines, or with systems or front
ends or networks that have small buffers.  The shorter the packet, the higher
the overhead, but the lower the chance of a packet being corrupted by noise,
and the less time to retransmit corrupted packets.  This command overrides
the value requested by the other Kermit during protocol initiation unless the
other Kermit requests a shorter length.
 
@q<pad-character @i(cc)>@*
Designate a character to send before each packet.
Normally, none is sent.  Outbound padding is sometimes necessary for
communicating with slow half duplex systems that provide no other means of
line turnaround control.  It can also be used to send special characters
to communications equipment that needs to be put in "transparent" or
"no echo" mode, when this can be accomplished in by feeding it a certain
control character.
 
@q<padding @i(n)>@*
How many pad characters to send, normally 0.
 
@q<start-of-packet @i(cc)>@*
The normal Kermit packet prefix is Control-A (1); this
command changes the prefix C-Kermit puts on outbound packets.  The only
reasons this should ever be changed would be: Some piece of equipment somewhere
between the two Kermit programs will not pass through a Control-A; or, some
piece of of equipment similarly placed is echoing its input.  In the latter
case, the recipient of such an echo can change the packet prefix for outbound
packets to be different from that of arriving packets, so that the echoed
packets will be ignored.  The opposite Kermit must also be told to change the
prefix for its inbound packets.
 
@q<timeout @i(n)>@*
Specifies the number of seconds you want the other Kermit
to wait for a packet before timing it out and requesting retransmission.
Defaults to 10 seconds.
@end(mydesc)
 
@q<receive @i<parameter>>@*
Establish parameters to request the other Kermit to use when sending packets.

@begin(mydesc)
@q<end-of-packet @i(cc)>@*
Requests the other Kermit to terminate its packets with
the specified character.
 
@q<packet-length @i(n)>@*
Specify the maximum packet length to that you want the
other Kermit to send, normally 90.  If you specify a length of 95 or greater,
then it will be used if the other Kermit supports, and agrees to use, the
Kermit protocol extension for long packets.  In this case, the maximum length
depends upon the systems involved, but there would normally be no reason for
packets to be more than about 1000 characters in length.  The '@q<show
parameters>' command displays C-Kermit's current and maximum packet lengths.
 
@q<pad-character @i(cc)>@*
C-Kermit normally does not need to have incoming packets
preceded with pad characters.  This command allows C-Kermit to request the
other Kermit to use @i(cc) as a pad character.  Default @i(cc) is NUL, ASCII 0.
 
@q<padding @i(n)>@*
How many pad characters to ask for, normally 0.
 
@q<start-of-packet @i(cc)>@*
Change the prefix C-Kermit looks for on inbound
packets to correspond with what the other Kermit is sending.
 
@q<timeout @i(n)>@*
Normally, each Kermit partner sets its packet timeout interval
based on what the opposite Kermit requests.  This command allows you to
override the normal procedure and specify a timeout interval for OS/2 Kermit to
use when waiting for packets from the other Kermit.  If you specify 0, then no
timeouts will occur, and OS/2 Kermit will wait forever for expected packets to
arrive.
@end(mydesc)
 
@q<speed {0, 110, 150, 300, 600, 1200, 2400, 4800, 9600, 19200}>@*
The baud rate for
the external communication line.  '@q<set baud>' is a synomym for '@q<set speed>'.
19200 baud may not be available, depending on your communications hardware.
 
@q<terminal @i(parameter  value)>@*
Used for specifying terminal parameters.  Currently, '@q<bytesize>' is
the only parameter provided, and it can be set to 7 or 8.  This controls
the width of the data path between the console and the remote system when
C-Kermit is in connect (ie terminal emulation) mode.  It's 7 by default.
@end(mydesc)
 
@subsection(The 'show' Command)
@value(STXTBS)
@begin(format)
Syntax:@\@q<show {parameters, versions}>
@end(format) 
The '@q<show>' command with the default argument of '@q<parameters>' displays
the values of all the '@q<set>' parameters described above.  If you type
'@q<show versions>', then C-Kermit will display the version numbers and
dates of all its internal modules.  You should use the '@q<show versions>'
command to ascertain the vintage of your Kermit program before reporting
problems to Kermit maintainers.
 
@subsection(The 'statistics' Command)
The statistics command displays information about the most recent Kermit
protocol transaction, including file and communication line i/o, timing
and efficiency, as well as what encoding options were in effect (such as
8th-bit prefixing, repeat-@|count compression).
 
@subsection(The 'take' and 'echo' Commands)
@value(STXTBS)
@begin(format)
Syntax:@\@q<take >@i<fn1>@*
@\@q<echo >@i<[text to be echoed]>
@end(format) 
The '@q<take>' command instructs C-Kermit to execute commands from the named
file.  The file may contain any interactive C-Kermit commands, including
'@q<take>'; command files may be nested to any reasonable depth, but it may
not contain text to be sent to a remote system during the '@q<connect>' command.
This means that a command file like this:
@begin(example)
set speed 9600
connect
login myuserid
mypassword
@i<etc>
@end(example)
will @i(not) send "login myserid" or any of the following text to the remote
system.  To carry on a canned dialog, use the '@q<script>' command, described
later.
 
The '@q(%)' command is useful for including comments in take-command files.
It may only be used at the beginning of a line.
 
The '@q<echo>' command may be used within command files to issue greetings,
announce progress, ring the terminal bell, etc.
This command simply displays its text
argument (almost) literally at the terminal; the argument may contain octal
escapes of the form @qq(\ooo), where @q(o) is an octal digit (0-7), and there
may be 1, 2, or 3 such digits, whose value specify an ASCII character, such as
@qq(\007) (or @qq(\07) or just @qq(\7)) for beep, @qq(\012) for newline, etc.
 
Take-command files are in exactly the same syntax as interactive commands.
Note that this implies that if you want to include special characters like
question mark or circumflexes that you would have to quote with @q(^) when
typing interactive commands, you must quote these characters the same way
in command files.  Long lines may be continued by ending them with a single
@q(^).
 
Command files may be used in lieu of command macros, which have not been
implemented in this version of C-Kermit.  For instance, if you commonly
connect to a system called 'B' that is connected to com2 at 4800 baud,
you could create a file called @q(b) containing the commands
@begin(example)
% C-Kermit command file to connect to System B thru com2
set line com2
set speed 4800
% Beep and give message
echo \007Connecting to System B...
connect
@end(example)
and then simply type '@q<take b>' (or '@q<t b>' since no other commands begin with
the letter 't') whenever you wish to connect to system B.  Note the
comment lines and the beep inserted into the '@q<echo>' command.
 
@index<IBM>
For connecting to IBM mainframes, a number of '@q<set>' commands are required;
these, too, can be conveniently collected into a '@q<take>' file like this one:
@begin(example)
% Sample C-Kermit command file to set up current line
% for IBM mainframe communication
%
set parity mark
set handshake xon
set flow-control none
set duplex half
@end(example)
 
Note that no single command is available to wipe out all of these settings
and return C-Kermit to its default startup state; to do that, you can either
restart the program, or else make a command file that executes the necessary
'@q<set>' commands:
@begin(example)
% Sample C-Kermit command file to restore normal settings
%
set parity none
set handshake none
set flow-control xon/xoff
set duplex full
@end(example)
 
An implicit '@q<take>' command is executed upon your @q(CKERMIT.INI) file when C-Kermit
starts up, upon either interactive or command-line invocation.  The @q(CKERMIT.INI)
file should contain '@q<set>' or other commands you want to be in effect at all
times.  For instance, you might want override the default action when incoming
files have the same names as existing files -- in that case, put the command
@example(set file warning on)
in your @q(CKERMIT.INI) file.
 
Errors encountered during execution of take files (such as failure to complete
dial or script operations) cause termination of the current take file, popping
to the level that invoked it (take file, interactive level, or the command
interpreter).
 
You may also use the redirection mechanism to cause
C-Kermit to execute commands from a file:
@example(kermit < cmdfile)
or you can even pipe commands in from another process:
@example(genkcmds | kermit)
 
@subsection(The 'connect' Command)
 
The '@q<connect>' command ('@q<c>' is an acceptable non-unique abbreviation)
links your terminal to another computer as if it were a local
terminal to that computer, through the device specified in the most recent '@q<set
line>' command.  All characters you type at your keyboard are sent out the
communication line (and if you have '@q<set duplex half>', also displayed on your
screen), and characters arriving at the communication port are displayed on
the screen.  Current settings of speed, parity, duplex, and flow-@|control are
honored, and the data connection is 7 bits wide unless you have given the
command '@q<set terminal bytesize 8>'.  If you have issued a '@q<log session>' command,
everything you see on your screen will also be recorded to your session log.
This provides a way to "capture" files from remote systems that don't have
Kermit programs available.
 
To get back to your own system, you must type the escape character, which is
Control-@|@q<]> (@q(^])) (unless you have changed it with the '@q<set escape>'
command), followed by a single-@|character command, such as '@q<c>' for "close
connection".  Single-@|character commands include:
@begin(description,leftmargin +8,indent -6,spread 0.4)
@q(c)@\Close the connection
 
@q(b)@\Send a BREAK signal for about 1 second
 
@q(0)@\(zero) send a null
 
@q(?)@\Display help information about these options
 
@q(h)@\Hangup the phone
 
@q(^])@\Send Control-@q<]> itself (whatever you have defined the
escape character to be, typed twice in a row sends one copy of it).
@end(description)
Uppercase and control equivalents for (most of) these letters are also
accepted.  A space typed after the escape character is ignored.  Any other
character will produce a beep.

In connect mode, C-Kermit emulates a DEC VT102 terminal.  See the section
"Terminal Emulation" for details of how the emulation works.

Note that when in interactive command mode, C-Kermit reads its keyboard
input from stdin and writes its screen output to stdout, allowing command-line
redirection to be used as described in the previous section.  @comment(This
isn't quite true, but let's not split hairs.)  However,
in connect mode, keyboard input is obtained through the KBD subsystem, and
screen output is through the VIO subsystem.  It is therefore impossible to
redirect terminal I/O.
 
@subsection(The 'dial' command)
@value(STXTBS)
Syntax:@\@q(dial )@i(telephone-number-string)
 
@index<Modems>@index<Dialout Modems>
This command controls dialout modems; you should have already issued a '@q<set
line>' and '@q<set speed>' command to identify the terminal device, and a '@q<set
modem>' command to identify the type of modem to be used for dialing.  In the
'@q<dial>' command, you supply the phone number and the Kermit program feeds it to
the modem in the appropriate format and then interprets dialer return codes and
modem signals to inform you whether the call was completed.  The
telephone-@|number-@|string may contain imbedded modem-@|dialer commands, such
as comma for Hayes pause, or '@q(&)' for Ventel dialtone wait and '@q(%)' for
Ventel pause (consult your modem manual for details).
 
At the time of this writing, support is included for the following modems:
@begin(itemize,spread 0)
AT&T 7300 Internal Modem
 
Cermetek Info-Mate 212A
 
Concord Condor CDS 220
 
DEC DF03-AC
 
DEC DF100 Series
 
DEC DF200 Series
 
General DataComm 212A/ED
 
Hayes Smartmodem 1200 and compatibles
 
Penril
 
Racal Vadic
 
US Robotics 212A
 
Ventel
@end(itemize)
A number of these modems are not generally found connected to PCs.  The most
common modem type used with an OS/2 system is "Hayes compatible".
Support for new modems is added to the program from time to time; you
can check the current list by typing '@q<set modem ?>'.
 
The device used for dialing out is the one selected in the most recent '@q<set
line>' command.
 
Example:
@begin(example)
@tabclear()@tabset(40)
@ux<kermit -l com1 -b 1200>
C-Kermit>@ux<set modem-dialer hayes>@\@i(hint: abbreviate) set m h
C-Kermit>@ux<dial 9,5551212>
Connected!
C-Kermit>@ux<connect>@\@i(hint: abbreviate) c
@i(logon, request remote server, etc.)
@ux<^]c>@\@i(escape back)
C-Kermit> ...
C-Kermit>@ux<quit>@\@i(hint: abbreviate) q
@end(example)
this disconnects modem, and hangs up the line.
 
@comment[  This is not true at present.
In general, C-Kermit requires that the modem provide the "carrier detect" (CD)
signal when a call is in progress, and remove that signal when the call
completes or the line drops.  If a modem switch setting is available to force
CD, it should normally not be in that setting.  ]
C-Kermit requires that the modem track the computer's "data terminal
ready" (DTR) signal.  If a switch setting is available to simulate DTR
asserted within the modem, then it should normally not be in that
setting.  Otherwise the modem will be unable to hang up at the end of a
call. 
 
For Hayes @index<Hayes Modem> dialers, two important switch settings are
@value(no)1 and @value(no)6.  Switch @value(no)1 should be normally be
UP so that the modem can act according to your computer's DTR signal. 
Switch @value(no)6 should normally be UP so carrier-@|detect functions
properly (but put it DOWN if you have trouble with the UP position). 
Switches @value(no)2 (English versus digit result codes) and @value(no)4
(Hayes echoes modem commands) may be in either position. 
 
@subsection(The 'script' Command)
@value(STXTBS)
Syntax:@\@q(script )@i(expect send [expect send] . . .)
 
"expect" has the syntax: @i(expect[-send-expect[-send-expect[...]]])
 
The '@q<script>' command carries on a "canned dialog" with a remote system, in
which data is sent according to the remote system's responses.  The typical use
is for logging in to a remote system automatically.
 
C-Kermit's script facility operates in a manner similar to that commonly
used by the Unix UUCP system's '@q(L.sys)' file entries.  A login script
is a sequence of the form:
@example(@i<expect send [expect send] . . .>)
where @i(expect) is a prompt or message to be issued by the remote site, and
@i(send) is the string (names, numbers, etc) to return, and expects are
separated from sends by spaces.  The send may also be the keyword EOT, to send
Control-D, or BREAK, to send a break signal.  Letters in sends may be prefixed
by '@q[~]' to send special characters, including:
@begin(description,leftmargin +10,indent -10,spread 0)
@q(~b)@\backspace
 
@q(~s)@\space
 
@q(~q)@\'@q[?]'(trapped by Kermit's command interpreter)
 
@q(~n)@\linefeed
 
@q(~r)@\carriage return
 
@q(~t)@\tab
 
@q(~')@\single quote
 
@q(~~)@\tilde
 
@q(~")@\double quote
 
@q(~x)@\XON (Control-Q)
 
@q(~c)@\don't append a carriage return
 
@q(~d)@\delay approx 1/3 second during send
 
@q(~)@i(o[o[o]])@\an octal character
 
@q(~w)@i([d[d]])@\wait specified interval during expect, then time out
@end(description)
As with some UUCP systems, sent strings are followed by @q(~r) unless they have
a @q(~c).
 
Only the last 7 characters in each expect are matched.  A null @i(expect),
e.g. @q(~0) or two adjacent dashes, causes a short delay before proceeding
to the next send sequence.  A null expect always succeeds.
 
As with UUCP, if the expect string does not arrive, the script attempt
fails.  If you expect that a sequence might not arrive, as with UUCP,
conditional sequences may be expressed in the form:
@example(@i<-send-expect[-send-expect[...]]>)
where dashed sequences are followed as long as previous expects fail.
Timeouts for expects can be specified using @q(~w); @q(~w) with no
arguments waits 15 seconds.
 
@i(Expect/send) transactions can be easily be debugged by logging
transactions.  This records all exchanges, both expected and actual.
The script execution will also be logged in the session log, if that is
activated.
 
Note that '@q[^]' characters in login scripts, as in any other C-Kermit
interactive commands, must be doubled up.  A line may be ended with a
single '@q[^]' for continuation.
 
Example:
 
Using a Hayes-compatible modem, dial up a PAD, simulating pressing CR
four times to get the '@q(PAD>)' prompt.  (Note how '@q(~0)' stands for a null
expect string @i(and) for a null send string - ie just send a carriage
return.) Call a VAX system named 'ERCVAX'.  Get the @q(..name:) prompt, and
respond with the user name and password.  Notice that the '@q(^)'
character is used to continue the script command onto the next line. 
@begin(example)
set modem hayes
set line com2
set baud 1200
dial 0319871234
script ~0 ~0 ~0 ~0 ~0 ~0 ~0 ~0 PAD> CALL~sERCVAX ^
name: SMITH word: SECRET
@end(example)
Note that '@q<set line>' is issued @i<after> '@q<set modem>', but @i<before>
'@q<set baud>' or other line-@|related parameters.  @comment(Why? Is this true
for OS/2?)
 
@subsection(The 'help' Command)
@value(STXTBS)
@begin(format)
Syntax:@\@q(help)
@i(or)@\@q(help )@i(keyword)
@i(or)@\@q(help {set, remote} )@i(keyword)
@end(format)
Brief help messages or menus are always available at interactive command
level by typing a question mark at any point.  A slightly more verbose form
of help is available through the '@q<help>' command.  The '@q<help>' command with
no arguments prints a brief summary of how to enter commands and how to
get further help.  '@q<help>' may be followed by one of the top-level C-Kermit
command keywords, such as '@q<send>', to request information about a command.
Commands such as '@q<set>' and '@q<remote>' have a further level of help.  Thus you
may type '@q<help>', '@q<help set>', or '@q<help set parity>'; each will provide a
successively more detailed level of help.
 
 
@subsection(The 'exit' and 'quit' Commands)
 
These two commands are identical.  Both of them do the following:
 
@begin(itemize,spread 0)
Relinquish access to any communication line assigned via '@q<set line>'.
 
Hang up the modem, if any, by dropping DTR.
 
Close any open logs or other files.

Exit the program.
@end(itemize)
After exit from C-Kermit, your current directory will be the same as when
you started the program.  The '@q<exit>' command is issued implicitly whenever
C-Kermit halts normally, e.g. after a command line invocation.

@newpage
@section(Terminal Emulation)

When you issue a '@q(connect)' command the first time after starting Kermit,
the screen clears and the cursor is positioned at the top left-hand
corner.  You can log into the remote host computer as normal.  In this
mode, the PC emulates a DEC VT102 terminal, so any control codes or escape
sequences received from the host will be actioned appropriately.

The 25th line on the screen is used as a status line,
giving the name of the comms port, the current baud rate
and how to obtain help.

Some keys on the VT102 keyboard have no direct equivalent on the PC
keyboard.  The following table shows the mapping which obtains between
VT102 keys and PC keys.  Note that the @q(Alt) @i(n) combinations use
the number keys along the top row of the keyboard, not the numeric
keypad.

@begin(verbatim)
@tabclear @tabset(2 inches)@need(22)
@ux(VT102)@\@ux(IBMPC)

Delete@\Del
PF1@\F1
PF2@\F2
PF3@\F3
PF4@\F4
Keypad 0@\Alt 0
Keypad 1@\Alt 1
Keypad 2@\Alt 2
Keypad 3@\Alt 3
Keypad 4@\Alt 4
Keypad 5@\Alt 5
Keypad 6@\Alt 6
Keypad 7@\Alt 7
Keypad 8@\Alt 8
Keypad 9@\Alt 9
Keypad minus@\F5 or F6
Keypad comma@\F7 or F8
Keypad dot@\F9
Keypad enter@\F10
No Scroll@\Home
@end(verbatim)

The PC's '@q(Home)' key (equivalent to the VT102 '@q(No Scroll)' key)
freezes the data on the screen.  It is typically used when listing a
long file, to prevent information being scrolled off the top of the
screen.  Note that the Control-S and Control-Q (Xon/Xoff) keys should
not be used for this purpose if '@q(flow)' is set to '@q(xon/xoff)',
because they interfere with the correct operation of the comms device
driver flow control.  When the '@q(Home)' key is pressed, an '@q(xoff)'
will be sent automatically when the device driver's receive buffer fills
up, and an '@q(xon)' will be sent as it empties after the '@q(Home)' key
has been pressed a second time to unfreeze the screen.  All other keys
are ignored when the screen is frozen.  The status line indicates when
the emulator is in this state. 

Information which scrolls off the top of the screen is not in fact lost,
but is stored in an "extended display buffer", which can be examined by
pressing the '@q(PgUp)' key.  The extended display buffer can contain a number
of screenfulls of data, and the '@q(PgUp)' and '@q(PgDn)' keys can be used to
range freely through this data.  If any other key is pressed while the
extended display buffer is visible, the current screen contents are 
redisplayed and the keystroke is sent to the host.  The '@q(PgUp)' and '@q(PgDn)'
keys may be used even when the host is still sending data.  If Xon/Xoff flow
control is in effect, no data will be lost.

The following VT102 features are not implemented:
@begin(itemize)
Smooth scrolling

132-column mode

Alternate character ROM

LED lamps
@end(itemize)
The VT102 keyboard autorepeat mode is always enabled. 

When in connect mode, typing the escape character (Control-@q(])) followed by
a @q<?> for help will display a "pop-up" help window, indicating the options
available.  These options are detailed in the section on the connect
command.  If @q(^]c) is typed to close the connection, the screen is restored
to its state when the '@q(connect)' command was issued.  A subsequent
'@q(connect)' will re-display the VT102 screen.

The control codes and escape sequences recognised by the VT102 emulation
are listed below.  For full details of the effects of these codes, please
consult the VT102 manual.

@begin(verbatim)
@tabclear @tabset(1.4 inches,2 inches)
ENQ@\5@\Send answerback message "OS/2 Kermit"
BEL@\7@\Sound beep
BS@\8@\Cursor left
TAB@\9@\Cursor to next tab stop
LF@\10@\Cursor down
VT@\11@\As LF
FF@\12@\As LF
CR@\13@\Cursor to left margin
SO@\14@\Select G1 character set
SI@\15@\Select G0 character set
CAN@\24@\Cancel escape sequence
SUB@\26@\As CAN
ESC@\26@\See below
Others@\@\Ignored

ESC 7@\Save cursor position
ESC 8@\Restore cursor position
ESC D@\Index
ESC E@\Next line
ESC H@\Set tab at current column
ESC M@\Reverse index
ESC Z@\Identify terminal
ESC c@\Reset
ESC =@\Enter application keypad mode
ESC >@\Exit application keypad mode
ESC @hash() 3@\Double height and width emulation - top half of line
ESC @hash() 4@\Double height and width emulation - bottom half of line
ESC @hash() 5@\Single height and width
ESC @hash() 6@\Single height and double width emulation
ESC @hash() 8@\Screen alignment display
ESC ( @i(g)@\G0 designator - @i(g) = A,B or 0 only
ESC ) @i(g)@\G1 designator - @i(g) = A,B or 0 only
ESC [ @i(Pn) A@\Cursor up
ESC [ @i(Pn) B@\Cursor down
ESC [ @i(Pn) C@\Cursor right
ESC [ @i(Pn) D@\Cursor left
ESC [ @i(Pl) ;@i(Pc) H@\Direct cursor address
ESC [ @i(Pl) ;@i(Pc) f@\Direct cursor address
ESC [ @i(Pn) c@\Identify report - response is ESC [ ? 6 ; 2 c
ESC [ 3 g@\Clear all tabs
ESC [ 0 g@\Clear tabs at current column
ESC [ ? @i(Pn) h@\Set DEC private mode - modes supported as shown below
ESC [ ? @i(Pn) l@\Reset DEC private mode - modes supported as shown below

    mode no.        mode            set           reset

        1           Cursor key      Application   Cursor
        2           ANSI/VT52       N/A           VT52
        5           Screen          Reverse       Normal
        6           Origin          Relative      Absolute
        7           Wraparound      On            Off

ESC [ @i(Pn) h@\Set mode - modes supported as shown below
ESC [ @i(Pn) l@\Reset mode - modes supported as shown below

    mode no.        mode            set           reset

        2           Keyboard lock   On            Off
        4           Insert          Insert        Replace
       20           Newline         CR LF         CR

ESC @i(Pn) i@\Printer/screen on/off - 4 to 7 supported
ESC [ 5 n@\Status report
ESC [ 6 n@\Cursor position report
ESC [ @i(Pn) x@\Request terminal parameter
ESC [ @i(Pn) ;@i(Pn) r@\Set top and bottom margins
ESC [ 0 J@\Erase to end of screen
ESC [ 1 J@\Erase from beginning of screen
ESC [ 2 J@\Erase all of screen
ESC [ 0 K@\Erase to end of line
ESC [ 1 K@\Erase from beginning of line
ESC [ 2 K@\Erase all of line
ESC [ @i(Pn) L@\Insert blank lines
ESC [ @i(Pn) M@\Delete lines
ESC [ @i(Pn) @@@\Insert blank characters
ESC [ @i(Pn) P@\Delete characters
ESC [ @i(Ps) ;@i(Ps) ; ..;@i(Ps) m@\Character attributes or
ESC [ @i(Ps) ;@i(Ps) ; ..;@i(Ps) }@\Character attributes, as below:
0       Default settings
1       High intensity
4       Underline
5       Blink
7       Reverse
8       Invisible
30-37   sets foreground colour to be as shown
        30      black
        31      red
        32      green
        33      yellow
        34      blue
        35      magenta
        36      cyan
        37      white
40-47   sets background colour to be as shown
        40      black
        41      red
        42      green
        43      yellow
        44      blue
        45      magenta
        46      cyan
        47      white
@end(verbatim)
Note that the default character set for both G0 and G1 is '@q(A)', ie the UK
character set.

The following escape sequences are recognised when the emulator is put into
VT52 mode by receiving the sequence @q(ESC [ ? 2 l).

@begin(verbatim)
ESC A@\Cursor up
ESC B@\Cursor down
ESC C@\Cursor right
ESC D@\Cursor leftup
ESC F@\Enter graphics mode
ESC G@\Exit graphics mode
ESC H@\Cursor to home
ESC I@\Reverse line feed
ESC J@\Erase to end of screen
ESC K@\Erase to end of line
ESC Y @i(l c)@\Direct cursor address
ESC Z@\Identify
ESC =@\Enter application keypad mode
ESC >@\Exit application keypad mode
ESC <@\Enter ANSI mode
@end(verbatim)
The escape sequences below are accepted but ignored.
@begin(verbatim)
ESC O @i(x)@\where @i(x) is any character
ESC ? @i(x)@\where @i(x) is any character
ESC [ @i(Pn) q@\Load LEDs
@end(verbatim)

@newpage
@section(C-Kermit Restrictions and Known Bugs)

If you find any bugs which are not documented here, please send details to
the author:
@tabclear @tabset(1 inch)
@begin(format)
@\Dr C J Adie
@\Edinburgh University Computing Service
@\Main Library
@\George Square
@\Edinburgh
@\EH8 9LJ
@\United Kingdom
@end(format)
or (preferably) by electronic mail on the Janet network to:
@q(C.J.Adie@@UK.AC.EDINBURGH)

@begin(enumerate, spread 1)
@ux(Server breakout):
There is no way of stopping server operation from the keyboard, short of
Control-Break.

@ux(Debugging log):
There is very little debugging information logged from the OS/2-specific
parts of the program (it was developed using Codeview).

@ux(Set Delay):
This should default to zero.  Currently it has no effect.

@ux(Dial):
The @q(DIAL) appears not to work.  The author has no convenient access
to a dial-out modem, so is not able to test it out properly.  It is
impossible to terminate the dialling process short of pressing
Control-Break. 

@ux(Keyboard handling):
In interactive command mode (as opposed to connect mode), the keyboard has only
the natural key-to-ascii-code mapping.  This means that (for instance) the
Del key does not produce code 127, but a code of 0 followed by 224.  A keyboard
remapping feature (perhaps incorporating key macros) would be useful in many
ways.
@blankspace(1)
In connect mode, it would be more logical to use the @q(Scroll Lock)
key as the equivalent of the VT102 @q(No Scroll) key, but this means writing
a keyboard monitor, as @q(Scroll Lock) is not placed in the keyboard input
buffer.

@ux(Terminal emulation):
If the host sends the escape sequence to put the terminal into 132-column mode,
and subsequently sends data which would appear in the rightmost 52 columns,
this may mess up the existing data on the screen.  Really the emulator
should ignore any data for these columns.

@ux(Answerback):
We should have a '@q(set terminal answerback ...)' command to let us change
the VT102 answerback message.

@ux(Character set):
We should have a '@q(set terminal characterset)' to allow the default character
set to be either the UK or the US set.  At present, the default is UK.

@ux(File type):
The way Control-Z is handled could be better.  There should be no '@q(set file
type {binary, text})'; instead we want a '@q(set ctrlz {on, off})' rather like
Kermit-MS.  A better display of progress of a transfer is needed, and the
interrupt keystrokes should conform to the usual Kermit conventions.

@ux(Hangup):
There should be a '@q(hangup)' command (as well as the @q(^]h) escape
sequence), which would drop DTR and RTS, thus hanging up a call through
a modem.

@ux(Login Scripts):
The present login scripts implementation follows the Unix conventions of
UUCP's '@q(L.sys)' file, rather than the normal Kermit 'INPUT/@|OUTPUT'
style. 

@end(enumerate)

@appendix(Invoking C-Kermit from Another Program)

If you are writing a communications program and wish to incorporate the Kermit
protocol within it, one way is to use the OS/2 function call @q(DosExecPgm) to
call up C-Kermit.  You would supply the instructions for Kermit using
command-line options, and Kermit would do the transfer, returning back to your
program when it had finished.

The only problem with this scenario is that you might already have opened up 
the COM port within your program, so that when Kermit tries to do the same it
gets an error code back from @q(DosOpen).  The @q(-u) command line option
gets round this problem.  It uses the fact that a child process inherits the
open file handles of its parent.  @q(-u) takes one numeric parameter which is
the handle of the COM port in question, and it must occur in front of any other
command-line parameter which accesses the COM port.  The following is a
complete C program written using the Microsoft C compiler version 5.1 and the
Microsoft OS/2 Software Development Toolkit, which illustrates how to use the
@q(-u) command-line option.

@begin(verbatim)
@hash()define	INCL_BASE
@hash()include <os2.h>
/*
 *	Example of how to use the C-Kermit -u option to invoke
 *	Kermit from another program under OS/2.
 */
main(int argc, char *argv[]) {
HFILE	ttyfd;
USHORT	action;
int	err,i;
char	failname[80];
char	args[80];
RESULTCODES	res;
struct dcb {			/* Device control block */
	USHORT write_timeout;
	USHORT read_timeout;
	BYTE flags1, flags2, flags3;
	BYTE error_replacement;
	BYTE break_replacement;
	BYTE xon_char;
	BYTE xoff_char;
} ttydcb;

	/*** Open a file ***/
	if (err=DosOpen(argv[1],&ttyfd,&action,0L,0,1,0x0012,0L)) {
		printf("Error %d opening %s\n",err,argv[1]);
		exit(1);
	}
	if (err=DosDevIOCtl(&ttydcb,NULL,0x0073,1,ttyfd)) {
		printf("Error %d from IOCTL on %s\n",err,argv[1]);
    		exit(1);
	}
	ttydcb.flags3 &= 0xF9;
	ttydcb.flags3 |= 0x04;	/* Read "some" data from line */
	DosDevIOCtl(NULL,&ttydcb,0x0053,1,ttyfd);

	/*** Call kermit ***/
	strcpy(args,"ckoker");
	i = strlen(args);
	args[i++]=0;
	sprintf(&args[i],"-u %d -q -s test.c",ttyfd);
	i += strlen(&args[i]);
	args[i++]=0;
	args[i++]=0;
	if (err=DosExecPgm(failname,80,EXEC_SYNC,args,NULL,&res,
						    "KERMIT.EXE")) {
		printf("Error %d executing Kermit\n",err);
		exit(1);
	}
	
	/*** Print out return code ***/
	printf("Termination code %d\n",res.codeTerminate);
	printf("Result code %d\n",res.codeResult);

	/*** Close the file ***/
	if (err=DosClose(ttyfd)) {
		printf("Error %d closing %s\n",err,argv[1]);
	}
}
@end(verbatim)
@end(text)