home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 3 Comm
/
03-Comm.zip
/
KERMIT.ZIP
/
READ.ME
< prev
Wrap
Text File
|
1991-10-20
|
7KB
|
159 lines
------------------------------------------------------------------
Oberon Software
518 Blue Earth Street
Mankato, MN 56001
Voice: 507/388-7001 CIS: 72510,3500
BBS: 507/388-1154 GEnie: B.FLOWERS
FAX: 507/388-3099 MCI Mail: oberon/413-5847
------------------------------------------------------------------
Kermit.Exe -- Notes 8/12/90, Brady Flowers, Oberon Software
Addenda on 10/28/90, Brady Flowers
Addenda on 10/20/91, Brady Flowers
Copyright (c) 1990, 1991, Oberon Software, Mankato, MN
------------------------------------------------------------------
Kermit.Exe is a standalone Kermit protocol that was quickly pieced
together from some Kermit souce code written between 1981 and 1983
at Columbia University and bearing the names Bill Catchings, Bob Cattani,
Chris Maio, and Frank da Cruz, and modified on 7/13/83 by Jim Guyton of
the Rand Corporation. I then sprinkled a few "#ifdef OS2"'s into it.
The intent was to create a sample, external protocol for TE/2 but
it is possible to use the protocol driver in other situations as long
as the following requirements are met:
* CommPak2.Dll, version 0.99 or greater must be located somewhere
on your LIBPATH.
* The calling process must be able to pass the communications port
handle to kermit on the command line.
------------------------------------------------------------------
Command line syntax is:
kermit [-]p{s|r} <porthandle> [<filename(s)>]
'p' is REQUIRED, it triggers acceptance of the porthandle
's' for SEND file(s)
'r' for RECEIVE files(s)
Note: Either 's' or 'r' (but not both) MUST be specified
<filename(s)> must be specified when sending files, of course. On
receive they need to be specified only if the name or path
needs to be changed in transit (Kermit WILL send full path
names!). If, for instance, you want to use the default name
for the first file and change the name of the second, you
must place two filenames on the command line but you can
specify "*" as a place holder for the first. You cannot
otherwise use wildcard filespecs when sending or receiving.
------------------------------------------------------------------
Running Kermit.Exe as an External Protocol with TE/2
Place the following two entries into a TE/2 external programs file,
either TE2.XEX or an alternate file (if you don't know what this means,
please refer to the TE/2 Documentation, VIII. Customization, D. TE2.XEX).
0x0011,1
Kermit Upload
<d:\Path>\kermit.exe
-ps %h %?[Enter File(s) for Kermit Upload:]
0x0011,1
Kermit Download
<d:\Path>\kermit.exe
-pr %h %?[Enter File(s) for Kermit Download:]
Replace "<d:\Path>" with the actual drive and path information for
kermit.exe on your system.
When you are ready to transfer a file, make sure that the external
programs file containing these lines is loaded (if you used TE2.XEX, it
is loaded by default, otherwise type Alt-J to display the External
Programs menu, type 'N' to load a new file, and specify the name of
your alternate file). Inform the host of the desired action, when the
host indicates that it is ready to send/receive, type Alt-J to invoke
the External Programs menu and select Kermit Upload/Download, you will
be prompted for the file names.
You can abort a Kermit transfer in progress by pressing the ESCape key.
A couple words of warning, because Kermit transmits the full filename
specified with no translation, if a path is specified and the file is not
renamed, that path must exist on the receiver for the transfer to work.
Also, Kermit will happily overwrite any existing file without a word;
make sure you get the name of the received file right!
------------------------------------------------------------------
Source Code
When the CommPak/2 Toolkit becomes available, the source for Kermit.Exe
will be released with it as an example of accessing the dynamic link
library functions.
------------------------------------------------------------------
Addenda and Errata
10/28/90
This update of Kermit.Exe addresses one small bug which would cause
a protection violation under certain conditions. This Kermit has
proven to be rather slow, this version will NOT improve the protocol
effiency or throughput.
10/20/91
Recompiled and linked to take advantage of (and to make sure that it
is compatible with) the lastest release of COMMPAK2.DLL (Version 0.99).
------------------------------------------------------------------
You don't have TE/2!?
TE/2 is a telecommunications program for OS/2 protected mode.
Supported file transfer protocols are: XModem, XModem-1K, YModem,
YModem-G, ZModem, and Ascii. Supported terminal emulations include:
TTY, ANSI-BBS, IBM 3101, and VT100. Other features include multiple,
200 entry dialing directories, call logging, extensive facility for
running external programs/protocols, split screen chat mode,
assignable function keys, and more.
A version of TE/2 is distributed as a Shareware Product of Oberon
Software and is available on CompuServe, GEnie, and many OS/2 BBSes
around the world (including the Oberon BBS, the number for which is
to be found at the beginning of this document). Oberon Software also
offers and enhanced, registered version of TE/2. The registered
version contains a very robust script language, CompuServe B+
protocol, and other enhanced features.
For information on ordering or registering TE/2 please contact
Oberon Software by one of the methods given above.
------------------------------------------------------------------
Disclaimer
You use Kermit.Exe at your own risk. Kermit.Exe is not guaranteed to
be error free. Oberon Software and Brady Flowers will not be liable for
any damages or loss to property, business, or data arising from the use,
misuse, or inability to use this software. Your use of this software
constitutes your agreement to these terms.
Kermit.Exe, TE/2, CommPak/2, and this document are all subject to
change with respect to each other and in no way imply a commitment on
the part of Oberon Software.