hsgj@batcomputer.TN.CORNELL.EDU (Dan Green) (06/14/86)
I just succeeded in downloading Amiga Kermit and getting the thing to
run and compile. The file transfer is great, just what you would expect
from kermit. There is no terminal emulation (not even ANSI Console)
but it is ok for just up and downloading.
I know everyone must think kermit is old hat, but I had a hard time
figuring out which files were actually needed, so I thought I would
post a list of source files that you need to compile to make kermit.
By the way, the .boo was not useful because if you only have screen capture
then there is too much noise to un-booify it.
FILES NEEDED (request from KERMSRV@CUVMA (bitnet) )
ckcmai.c ckitio.c ckicmp.com
ckcpro.c ckifio.c ckilnk.com
ckcfns.c ckicon.c ckiker.mak
ckcfn2.c ckiext.c
ckucmd.c ckcker.h (its about 400K of source)
ckuusr.c ckcdeb.h
ckuus2.c ckuusr.h
ckuus3.c ckucmd.h
Notes:
The .com files are "execute" batch files. They assume that you have
made some assignments. The ones you have to make are:
assign SRC: <disk with source files>
assign OBJ: <where you want object files to go>
assign EXE: <where you want executable Kermit to go>
assign LC: <lattice c disk>
assign WB: <workbench disk>
You type "execute ckiker.mak" to actually compile everything. Oh yeah,
I got an error in ckuusr.h cause it was trying to #include <pwd.h>. I
couldn't find pwd.h in the kermit directories. The include was bracketed
inside an #ifndef vax11c, so I threw caution to the winds and just
commented out the #include. Everything looks like it is going ok, though.
Note that the executable Kermit is about 113 K.
SUGGESTION FOR FUTURE AMIGA WORKBENCH (OS) ENHANCEMENTS:
This is my dream: While compiling kermit above, I noticed that for each
module it read in LC1 from disk, did pass 1, read LC2 from disk, did pass2,
and then had to read in LC1 and LC2 from disk for every module compile.
The dream is whether these could be "locked" in so that they would never
have to be read from disk again, but could be memory resident. I have
noticed that the Amiga *does* do this to some extent - If you do a lot
of copies, for example, it only reads the copy program in once. It appears
that the "locking" only exists for the last file read, so that in the
lattice case, LC1 will be overwritten by LC2 meaning that you have to
read both from disk every time.
So the dream is to have more then one file be lockable, this locking
either selected by the user, or done LRU or FIFO. NOTE: I dont think
more memory is the answer (I have 512K) cause if I do a copy, assign,
copy, the second copy has to be re-read from disk. And copy is only a
K or two big.
Another Note: The solution is not to put goop on RAM: The Amiga has
the *BEST* RAM: system I have ever encountered, but if, say I put LC1
and LC2 on RAM: then it would have to have two copies of the prog in
menory at one time - one copy on RAM:, the other in executing memory.
With LC1 being >> 100K, this is a no no!
Well it was just a dream. I apologize for the length of this posting.
Oh, I want to thank those who helped me with my requester nighmare.
=RJ Mical= - I am buying your Intuition manual tomorrow! (If I can find it)
PS: (Yes, more text before I go away). I am all thumbs at doing these
downloads and re-creations. If anyone is in worse shape then me (e.g. an
amputee...) and cannot get kermit, then, for a limited time only!, I
will copy the sources and executable onto a disk for you. But you have
to send me a disk and a US-mailer. Send E-Mail if you want my US Mail
address...
--
Dan Green ARPA: hsgj%vax2.ccs.cornell.edu@cu-arpa.cs.cornell.edu
~~~~~~~~~ BITNET: hsgj@cornella
UUCP: {decvax,ihnp4,allegra}!cornell!batcomputer!hsgjkim@mips.UUCP (06/15/86)
> I just succeeded in downloading Amiga Kermit and getting the thing to > run and compile. > > FILES NEEDED (request from KERMSRV@CUVMA (bitnet) ) > ckcmai.c ckitio.c ckicmp.com > ckcpro.c ckifio.c ckilnk.com > ckcfns.c ckicon.c ckiker.mak > ckcfn2.c ckiext.c > ckucmd.c ckcker.h (its about 400K of source) > ckuusr.c ckcdeb.h > ckuus2.c ckuusr.h > ckuus3.c ckucmd.h > > I will copy the sources and executable onto a disk for you. But you have > to send me a disk and a US-mailer. Send E-Mail if you want my US Mail > address... Sounds like an ideal candidate for one of the next "Fish Disks" and/or "Amicus Disks". What say, Fred? /kim -- UUCP: {decvax,ucbvax,ihnp4}!decwrl!mips!kim DDD: 408-720-1700 x231 USPS: MIPS Computer Systems Inc, 930 E. Arques Av, Sunnyvale, CA 94086 CIS: 76535,25
fnf@unisoft.UUCP (Fred Fish) (06/16/86)
In article <510@mips.UUCP> kim@mips.UUCP writes: [deleted stuff about C-kermit] >Sounds like an ideal candidate for one of the next "Fish Disks" and/or >"Amicus Disks". > >What say, Fred? Right you are, and yes, one of the disks to be released in the next few days (#26 or possibly #27) will have C-kermit. I've acquired source from several different people over the last few weeks, but wasn't able to get the right combination that would produce a working version under any version of Lattice or Manx C until just recently. -Fred =========================================================================== Fred Fish UniSoft Systems Inc, 739 Allston Way, Berkeley, CA 94710 USA {ucbvax,lll-lcc}!unisoft!fnf (415) 644 1230 TWX 11 910 366-2145 ===========================================================================
daveh@cbmvax.cbm.UUCP (Dave Haynie) (06/16/86)
> SUGGESTION FOR FUTURE AMIGA WORKBENCH (OS) ENHANCEMENTS: > > This is my dream: While compiling kermit above, I noticed that for each > module it read in LC1 from disk, did pass 1, read LC2 from disk, did pass2, > and then had to read in LC1 and LC2 from disk for every module compile. > The dream is whether these could be "locked" in so that they would never > have to be read from disk again, but could be memory resident. I have > noticed that the Amiga *does* do this to some extent - If you do a lot > of copies, for example, it only reads the copy program in once. It appears > that the "locking" only exists for the last file read, so that in the > lattice case, LC1 will be overwritten by LC2 meaning that you have to > read both from disk every time. > > Dan Green ARPA: hsgj%vax2.ccs.cornell.edu@cu-arpa.cs.cornell.edu > ~~~~~~~~~ BITNET: hsgj@cornella > UUCP: {decvax,ihnp4,allegra}!cornell!batcomputer!hsgj If the time of loading becomes a critical factor, and you don't want to store anything in the RAM disk, you could first run the LC1 pass on everything, producing ".q" files, then run the LC2 pass, which will remove the ".q" and create ".o" files. This way, each of the compiler passes would remain in memory as long as needed. -- /\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\ Dave Haynie {caip,ihnp4,allegra,seismo}!cbmvax!daveh "As a dreamer of dreams and a travellin' man, I had chalked up many a mile." "I read dozens of books about heros and crooks, and I learned much from both of their styles.." -Jimmy Buffett These opinions are my own, though for a small fee they be yours too. \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/