[File MSSAAA.HLP]

Instructions for Building MS-Kermit 2.30 (1 Jan 1988)
-----------------------------------------------------

To assemble any of the Kermit modules, file MSSDEF.H must be on the
default disk.

 MSSDEF.H    Symbol definitions for all modules
 MSSCMD.ASM  Command parser
 MSSCOM.ASM  Communications (packets, system-independent)
 MSSFIL.ASM  File i/o
 MSSFIN.ASM  Dummy module to specify end of data segment
 MSSKER.ASM  Main program
 MSSRCV.ASM  Receive module
 MSSSCP.ASM  Script module
 MSSSEN.ASM  Send module
 MSSSER.ASM  Server module
 MSSSET.ASM  Set command module
 MSSTER.ASM  Terminal emulation (system-independent)

The program needs an MSX module (system-dependent i/o, interrupt handling,
etc) for the desired system, plus an MSU modle (keyboard translator), plus an
MSY module (terminal emulation) for the same system (if there is one), and
possibly an MSZ module (in case the MSY module got too big).  The MSX and MSY
file may come with associated .HLP or .BWR files, which you should read.  Also,
if you can't find the MSU, MSX and MSY modules for your system, read file
MSAAAA.HLP, which lists the naming conventions.

ASSEMBLING:

For version 2.29 of Kermit-MS, most common assemblers, including any version
of IBM or Microsoft MASM, can be used without any special switches. Bascially,
each .ASM file is assembled independently to produce a .OBJ file. Note that
the standard header file MSSDEF.H must be present with the .ASM file during
assembly. Users of MS MASM version 1.0+ should be aware that many bugs exist
in that early release; Kermit-MS assembles correctly under MS MASM v1.25 and
later; version 5 was used on the release files. Consistent versions of MASM
and LINK should be used together; check the file dates. A typical command is

        A>masm msscom;

LINKING:

Once all the required object modules exist, they may be linked together to
produce Kermit.  The MSSFIN module must come LAST.  For example, for the
IBM PC version:

A>link

   Microsoft Object Linker V2.00
(C) Copyright 1982 by Microsoft Inc.

Object Modules [.OBJ]: msscmd msscom mssfil mssker mssrcv mssscp +
msssen mssser mssset msster msgibm msuibm  msxyibm mszibm mssfin
Run File [MSSCMD.EXE]: Kermit;          (or other convenient name)

A>

If a convenient Link command file is used, such as MSVIBM.LNK below, then the
appropriate command is just

        A>link @msvibm.lnk


USING MAKE:

Makefiles (for those who have the Microsoft DOS version of the UNIX 'make'
program) to build each version of MS-DOS Kermit are in MSVxxx.MAK. MSVIBM.MAK
builds the IBM version, MSVRB.MAK builds the Rainbow 100 version, etc.  To
execute a makefile, type the command "make msvxxx.mak", where xxx is ibm, rb1,
etc.  The makefiles show the assembly, link, and BOO steps.  Even if you don't
have a 'make' program, they will show you which files are necessary for which
version.  The advantage of using "make" is that only those steps that are
necessary will be performed -- e.g. .ASM files will not be reassembled if
there is already a corresponding .OBJ file with a later creation date.

USING DOS BATCH:

There are also MSS*.BAT file which can also be used to assemble and link
MS-DOS Kermit for * = IBM, RB1, GEN, etc.

THE LINK STEP:

Both the makefile and the batch file rely on the presence of an MSVxxx.LNK
Linker command file for each implementation.  For instance, here is MSVIBM.LNK
for the IBM PC family:

msscmd+msscom+mssfil+mssker+mssrcv+mssscp+msssen+mssser+
mssset+msster+msgibm+msuibm+msxibm+msyibm+mszibm+mssfin
msvibm;

[End of MSSAAA.HLP]
