jm59@prism.gatech.EDU (MILLS,JOHN M.) (05/10/91)
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*>)
I last assembled KERMIT in v.3.1, which was a single, fairly managable
package: I edited in the controls for my terminal, and built the *.com
with ASM and LOAD. This looks like a _quite_ different proposition,
requiring separate assemblies, linkage, and (maybe) building a library,
overlays, help files, ???.
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?
(2) Where are the hardware- and terminal-dependent parts buried?
(3) What is a good assembly and linkage sequence?
(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?
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*(.
Thanks in advance.
Respond e-mail, I guess, since this may not be of very wide interest.
Similarly, I'll forward the most pertinent responses on request to
anyone else at the level of (knowledge:ignorance) to want them.
John M. Mills, Georgia Tech/GTRI jm59@prism.gatech.edu
(404)894-8346
--
MILLS,JOHN M.
Georgia Institute of Technology, Atlanta Georgia, 30332
uucp: ...!{decvax,hplabs,ncar,purdue,rutgers}!gatech!prism!jm59
Internet: jm59@prism.gatech.eduTAGLANCE@ucs.UWPLATT.EDU (LANCE TAGLIAPIETRA) (05/11/91)
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
jm59@prism.gatech.EDU (MILLS,JOHN M.) (05/13/91)
In article <79171DA2599F004E6B@ucs.uwplatt.edu> TAGLANCE@ucs.UWPLATT.EDU (LANCE TAGLIAPIETRA) writes: >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, Thanks for all the response I got on this. Eight respondents so far, with many useful comments. I probably don't need any more advice, until I have had time to make some more mistakes. Thanks to all. When I get done, I'll be happy to post a note to that effect, and send a summary then to anyone who would like it. >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 That sounds like the best advice: When in doubt, READ THE DIRECTIONS. >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. I haven't been using MLOAD or LASM. Sounds like they are worth having. Ans: My system is a Z-80, SD-Systems, SBC-200 (or -300 .. I can't remember). 256 KBy RAM, incl. 192K as a RAMDisk. All that's generic, of course. The adaptation I meant was for my serial- port addresses and flags (SSM-I/O4 --anyone remember SSM?), and for the Adds Viewpoint terminal. That's a traditional, unbreakable CP/M _boat_anchor_, in other words. When I patched my existing Kermit source, I added conditionals for the cursor and screen control codes, sim. to the structure for the Superbrain, Heath, etc.. I expect I will now write a short definition file of some kind, or patch the *.asm for some similar industry-standard terminal. I left most of the details out here -- just wanted to say 'Thanks' to the numerous people who responded to my request. Regards --jmm-- -- MILLS,JOHN M. Georgia Institute of Technology, Atlanta Georgia, 30332 uucp: ...!{decvax,hplabs,ncar,purdue,rutgers}!gatech!prism!jm59 Internet: jm59@prism.gatech.edu