RMF%ADMIN@UNCAEDU.BITnet (04/25/87)
From: RMF%ADMIN%UNCAEDU.BITNET@wiscvm.wisc.edu First you live ..... Ribbit .... ..... then you die ...... croak! In hoping to get the latest and greatest version of C-Kermit from Columbia University running on my trusty AMIGA, I had the following adventure. #set humor_mode on First I pulled over the CKIKER.BOO and CKIBOO.C files and all the necessary documentation. Wonderful I thought. So I start compiling the CKIBOO file to create C-Kermit. I try and compile the C file and find numerous errors, drat! I said. Well I fix the errors and get it working. I make the Kermit program (takes about 7 minutes), run it, and get the message, 'file is not an object module.' well I said, maybe I didn't get that quite right. So I pulled of the BASIC version of CKIBOO and run it. What! errors again!, double DRAT! Well I'll fix the errors and run it to build KERMIT again. *GASP* It took about an hour and a half!, now I know why I no longer speak BASIC. Now I said run that sucker again, well it still isn't an object module! OK, OK, brute force time, I pull over all the sources required to build KERMIT and try again. WHAT!!! I can't use MANX!! good lord what is this world coming to! Where is that Lattice disk, I know its here somewhere, ah here it is, I'll just blow off the dust, cough, cough, boy there was a lot there. Now then onward we go. I shove I Lattice C, execute the command procedure and .... pause for affect .... I get a cute requester up that says stack space exhausted!, well I've seen this before from a USEnet posting, I know that Lattice won't run under SHELL 205M (thanks Steve Drew), so bye bye shell. I start compiling KERMIT and find I'm missing modules. This is now a crusade!! Well after pulling off the missing modules I get back at it. Finally its all compiled and I'm ready to link it. How nice there's a WITH file included. Gentleman start your ALINK....stall stall more errors! IT seems that my version of C uses the startup module named C.O not LSTARTUP.OBJ (I think one is AMIGA C and the other is LATTICE C but I couldn't tell you difference. I'm ready, its all done, it looks *marvelous* if I do say so myself. I savor the moment, stare at my achievement, even pat myself on the back, hey this was no easy take I tell myself. Ok on to the testing. 1) kermit The disk whirrs for about 30 seconds, and just when I figure that the C-Kermit> prompts is going to come up I get rudely interrupted.. EXCUSE ME, THIS IS YOUR AMIGA SPEAKING, "SOFTWARE ERROR - TASK HELD", "FINISH ALL DISK ACTIVITY .." Well I give up. This is going to take major thought and I can't justify it when VT100 (thanks Dave Wecker) does a fine job. #set humor_mode off So ends my adventure with C-KERMIT. I just thought I'd share this with you. I'm sure there's a moral here somewhere, but I'll let you find it. Note, this is not a knock against KERMIT or its developers or maintainers. It is my feeling that this version of C-KERMIT will compile under the developers version of AMIGA/LATTICE C. KERMIT is a marvelous file transfer program for the many micros out there, and the people at Columbia and everyone else involved in KERMIT development should be patted on the back. /Russ ----- Russell M Forster DECnet: RMF @ { Admin | Comus | Stasis | Ins } BITnet: RForster @ UncaEdu.BITnet ARPA: Oc.Russ @ CU20B.Columbia.Edu -------