home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
ccdos
/
ccsaaahlp.txt
< prev
next >
Wrap
Text File
|
2020-01-01
|
4KB
|
97 lines
CCSAAA.HLP July 1991
INSTRUCTIONS FOR BUILDING CC-DOS KERMIT 2.32 FROM SOURCE CODE
-- Quanfang Zhang, Zhejiang University, P.R. China
CC-DOS Kermit is written in assembly language for the Microsoft MASM
assembler. To assemble any of the Kermit modules, file CCSDEF.H must be on
the default disk. The source modules are:
CCSDEF.H Symbol definitions for all modules
CCSCMD.ASM Command parser
CCSCOM.ASM Communications (packets, system-independent)
CCSFIL.ASM File i/o
CCSKER.ASM Main program
CCSRCV.ASM Receive module
CCSSCP.ASM Script module
CCSSEN.ASM Send module
CCSSER.ASM Server module
CCSSET.ASM Set command module
CCSTER.ASM Terminal emulation (system-independent)
CCSFIN.ASM Final module
CCXIBM.ASM System-dependent i/o, interrupt handling,etc
CCYIBM.ASM Terminal emulation
CCZIBM.ASM The CCY module got too big
CCGIBM.ASM Tektronix emulator for use with CC Kermit/IBM.
CCUIBM.ASM Keyboard translator
CCHKOS.ASM DOS status check
The program needs an CCX module (system-dependent i/o, interrupt handling,
etc) for the desired system, plus an CCU modle (keyboard translator), plus an
CCY module (terminal emulation) for the same system (if there is one), and
possibly an CCZ module (in case the CCY module got too big). The CCX and CCY
file may come with associated .HLP files, which you should read. Also,
if you can't find the CCU, CCX and CCY modules for your system, read file
CCAAAA.HLP, which lists the naming conventions.
ASSEMBLING:
For version 2.32 of CC-DOS Kermit, Microsoft MASM 5.0 or later, or compatible
assemblers, must be used. Some of Kermit's modules have too many symbols for
earlier MASM versions. MASM can be used without any special switches. Each
.ASM file is assembled independently to produce a .OBJ file. Note that the
standard header file CCSDEF.H must be present with the .ASM file during
assembly. Compatible versions of MASM and LINK should be used together; check
the file dates. A typical command is
A>masm ccscom;
LINKING:
Once all the required object modules exist, they may be linked together to
produce Kermit. For example, for the IBM PC version:
C>link
Microsoft Overlay Linker V3.61
Copyright (C) Microsoft Corp 1983-1987. All rights reserved.
Object Modules [.OBJ]: cchkos ccscmd ccscom ccsfil ccsker ccsrcv ccsscp +
ccssen ccsser ccsset ccster ccgibm ccuibm ccxibm ccyibm cczibm ccsfin
Run File [CCHKOS.EXE]: Kermit; (or other convenient name)
C>
If a convenient Link command file is used, such as CCVIBM.LNK below, then the
appropriate command is just
A>link @ccvibm.lnk
USING MAKE:
Makefile (for those who have the Microsoft DOS version of the UNIX 'make'
program) to build CC-DOS Kermit is in CCVIBM.MAK. To
execute a makefile, type the command "make ccvibm.mak". The makefile shows
the assembly, link, and BOO steps. 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 is also a CCVIBM.BAT file which can also be used to assemble and link
CC-DOS Kermit.
THE LINK STEP:
Both the makefile and the batch file rely on the presence of an CCVIBM.LNK
Linker command file for each implementation. For instance, here is CCVIBM.LNK
for the IBM PC family:
cchkos+ccscmd+ccscom+ccsfil+ccsker+ccsrcv+ccsscp+ccssen+ccsser+
ccsset+ccster+ccgibm+ccuibm+ccxibm+ccyibm+cczibm+ccsfin
ccvibm;
[End of CCSAAA.HLP]