You need the following files to build Amiga Kermit from scratch: Common-C Kermit modules: CKCDEB.H Debugging header file CKCFN2.C More protocol functions CKCFNS.C Protocol functions CKCKER.H Common header file CKCMAI.C Main Kermit program CKCPRO.C Protocol parser AMIGA Kermit modules: CKICMP.COM Command file used by CKIKER.MAK CKICON.C CONNECT command files CKIEXT.C EXTRAs, not yet implemented CKIFIO.C AMIGA File IO CKIKER.BLD This text CKIKER.BWR Beware file for Amiga Kermit CKIKER.MAK The MAKE file for building Amiga Kermit CKILNK.COM ALINK options file CKITIO.C AMIGA Terminal IO Unix Kermit modules: CKUCMD.C Unix command parser CKUCMD.H Command parser header file CKUUS2.C More Unix user interface CKUUS3.C Still more Unix user interface CKUUSR.C Unix user interface CKUUSR.H Unix user interface header file The file CKIKER.MAK will build Kermit for you, but you must define some device names first. The following should be ASSIGNed from the CLI: SRC: The disk that contains the Kermit source files (all those listed above) OBJ: The disk where object modules will be stored (can be the same as SRC:) EXE: The disk where the executable will be placed (can be the same as SRC:) WB: The Workbench disk (contains the C (command) sub-directory) LC: The Lattice C disk For example, put the Workbench disk in drive DF0: and type 1> ASSIGN WB: DF0: to assign the device WB: to be the disk currently in the drive. For two disk systems, it is best to make SRC:, OBJ:, and EXE: be the same disk, and LC: be a separate disk. For one disk systems, see the hints at the end of this file. Once you have assigned the device names, type 1> EXECUTE SRC:CKIKER.MAK and then sit back and let it compile and link. With a two-disk system, you should have WB: in one drive and SRC: in the other, then swap LC: for WB: when it requests it. For a single-drive system, you will have to do a little swapping at the beginning, while it loads commands into RAM:, then you should only have to swap twice per compiled file. The complete procedure takes about an hour. You should see some compiler warnings, but don't let these bother you. They are in the CKU*.C files, which I did not want to change any more than I had to. You should build Kermit on a freshly booted machine, with nothing in RAM. The make file will copy the commands it needs into RAM for fast access, and will use the RAM area for compiling. Don't try to start other processes while Kermit is compiling or linking, as it needs most of a 512K Amiga's memory. Good luck, and happy AMIGA-ing! Davide P. Cervone University of Rochester DPVC@UORDBV.BITNET (BITNET) rochester!ur-tut!dpvc (UUCP) -------------------------------------------------------------------------------- Hints for one-disk systems: The AMIGA Kermit build procedure uses the following files on the Lattice C disk. For one disk systems, you can make a copy of Lattice C, remove the files not listed here, and use the modified disk as OBJ: and EXE: devices. This should reduce the number of disk swaps you will need to do. 1> DIR DF0: OPT A lib (dir) amiga.lib c.o lc.lib c (dir) Alink LC1 LC2 t (dir) include (dir) clib (dir) macros.h libraries (dir) dos.h workbench (dir) icon.h startup.h workbench.h workbenchbase.h exec (dir) devices.h interrupts.h io.h libraries.h lists.h memory.h nodes.h ports.h tasks.h types.h graphics (dir) clip.h copper.h gels.h gfx.h gfxbase.h gfxmacros.h layers.h rastport.h regions.h text.h view.h intuition (dir) intuition.h intuitionbase.h resources (dir) cia.h disk.h misc.h potgo.h lattice (dir) ctype.h fcntl.h stdio.h hardware (dir) blit.h devices (dir) console.h input.h inputevent.h keyboard.h keymap.h serial.h timer.h .info Disk.info