Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!ucsd!dog.ee.lbl.gov!ucbvax!ucs.UWPLATT.EDU!TAGLANCE
From: TAGLANCE@ucs.UWPLATT.EDU (LANCE TAGLIAPIETRA)
Newsgroups: comp.os.cpm
Subject: Re: KERMIT 4.11 Installation (Help Wanted)
Message-ID: <79171DA2599F004E6B@ucs.uwplatt.edu>
Date: 11 May 91 13:18:00 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 74

Hello,
 
writes jm59@prism.gatech.EDU (MILLS,JOHN M.):
>After reading the post that KERMIT had just been re-released for
>CP/M, I downloaded all the files that looked appropriate from
>watsun..., and that's quite a few!  About 500KB of cp*.asm and cp*.hlp,
>with a few stray items still sitting on our file system waiting
>to be brought down.  (I got some reading in last night, even at
>2400 Bd. [8*>)
 
From reading the rest of your post, it seems you left out the most
important file for the moment, CPKERM.DOC.  This file is the
documentation for Kermit-80.  It was also updated for the new
release. It explains how to use kermit, and how to install it
on your system, even re-assembling if necessary.  CPKERM.PS is
cpkerm.doc on postscript format and prints a nicely formatted
Kermit-80 manual.
 
If you system is one of those supported (you never did mention
what system you were trying to get kermit to support in your
post) all you need to do is mload the overlay for your system
cpxxxx.hex with the system independent file cpsker.hex.  The
mload program is available from the kermit server along with
its documentation.
 
>Has anyone out there put this package, or another recent, similar
>release together?  I would like to know:
>(1) Which modules do I _not_ need?
 
This is described in cpkerm.doc.
 
>(2) Where are the hardware- and terminal-dependent parts buried?
 
The hardware and terminal dependent parts are buried in the system
specific overlay file.
 
>(3) What is a good assembly and linkage sequence?
 
Kermit-80 is designed to be assembled with the LASM public domain
assembler. It can also be assembled with m80, but I have not tried
this as I don't have m80.  Since you should be able to use the
system independent hex file as you got it from the server, only one
assembly should be needed if your system is not already one of those
supported. The hex file created by lasm.com is then merged with the
system independent file with mload.com.  Lasm.com is the asm.com
assembler with a LINK command added which allow chaining of files
at assembly time.  It is also 2K smaller than asm.com.
 
>(4) I also ftp'd two hex files: kernel and generic sections.  How do
>    I patch them together (ddt?), and what functions will I have/
>    not have in the generic hex patch?
 
Mload.com is used to merge the system independent and system dependent
hex files into one executable .com file.  Mload and its documentation
are available from the kermit server and simtel20. If your system is
covered by one of the system dependent hex files, you do not need to
re-assemble.
 
>I expect to use M80 and L80 to accomplish the assembly and link, as
>they are mentioned in the kernel source header, and I have them.
>Been a _long_ time since I tried to _use_ them, tho... [8*(.
 
Lasm.com is available from the same place you got the other kermit
sources.  It is also available on simtel20, along with its sources.
 
I hope this helps.
 
>Thanks in advance.
>
>John M. Mills, Georgia Tech/GTRI       jm59@prism.gatech.edu
>(404)894-8346
>
 
Lance Tagliapietra   taglance@ucs.uwplatt.edu