HOW TO USE CKIKER.BOO
                     -=-=-=-=-=-=-=-=-=-=-

                 Stephen Walton, 15 January 1992

A bit of background first:  a BOO file, or a .BOO file, is a way of
translating an arbitrary binary file into a series of characters.
Unlike a Unix uuencode file, a BOO file is carefully designed to survive
intact translations between different character sets, in particular from
EBCDIC (IBM mainframes) to ASCII (everyone else) and back.

The file CKIKER.BOO in this directory is the BOO'd version of the
executable of C Kermit for the Amiga.  You need an "un-boo'er" program
to translate CKIKER.BOO into the Kermit executable.  Once this is done,
you simply type Kermit at a CLI prompt to run the program.

There are three techniques to convert CKIKER.BOO into the executable program
Kermit, depending on what you have available:

1.  If you have a C compiler (any one will do), get the file CKIPCT.C
Compile and link it with the AMIGA symbol defined;  either edit the
source or use the -DAMIGA symbol from the command line.  Now, assuming
you call the executable ckipct, the command

1>ckipct ckiker.boo

will, in a few minutes, produce a working Kermit executable.

2.  If you don't have a C compiler, but can drop back to AmigaDOS 1.3
and run AmigaBasic, the Basic version of the MS/DOS un-boo'er, namely
MSBPCT.BAS, will run with almost no change on the Amiga.  You must add a
CLEAR, 50000 statement near the beginning of the program to get some
work space, and you'll also need to change the name of the default input
file from MSIIBM.BOO to CKIKER.BOO.  Unfortunately, AmigaBasic will not
run on the Amiga 3000, so find a friend with a 500, 1000, or 2000.

3.  By far the slowest technique is to use the Amiga REXX version of the
un-BOO program, CKIPCT.REXX. This is so slow, even on an Amiga 3000,
that I have also provided a BOO file of the CKIPCT.C program as CKIPCT.BOO.
Thus, the recommended technique in this case is as follows:

1>rx ckipct.rexx ckipct.boo
1>rename ckipct.rexx ckipct.save
1>ckipct ckiker.boo

The first command will run ckipct.rexx as a Rexx program over the BOO file
of ckipct.  This will take several minutes.  The second step renames the
REXX file as a saved file;  this prevents the REXX script from being run
instead of the executable.  Finally, the third step runs the ckipct executable
to produce a Kermit executable.