car32596@uxa.cso.uiuc.edu (Radically Saved) (02/27/91)
I just recently (i.e. yesterday) downloaded, uncompressed, and unarchived
the KERMIT 3.87 software on a //c running under Prodos. Everyting seems fine,
except that several of the programs crash when they start and others when they
exit. Specifically, the configure kermit program dies when it tries to exit
with some sort of Prodos "BYE" command. However, Prodos doesn't seem to recog-
nize that command and complains. Is there such a command in a few versions of
Prodos (and there are a lot of versions...) or should it have been installed
by another routine in the KERMIT startup software?
Also, some SYS programs, such as READ.ME and INSTALL.KERMIT, crash shortly
after they are loaded into memory by Prodos, without any output beyond the
usual display when machine code crashes.
Beyond these few problems, everything seems to work. I can BRUN KERMIT
directly, and it works fine. Has anyone else had these problems, or is it
just me? Better yet, does anyone have any solutions?
Thanks in advance
Collin Richbill@braille.uwo.ca (W.B. Carss (519) 438-0344) (02/27/91)
In article <1991Feb26.224915.15637@ux1.cso.uiuc.edu> car32596@uxa.cso.uiuc.edu (Radically Saved) writes: > > I just recently (i.e. yesterday) downloaded, uncompressed, and unarchived >the KERMIT 3.87 software on a //c running under Prodos. Everyting seems fine, >except that several of the programs crash when they start and others when they >exit. Specifically, the configure kermit program dies when it tries to exit >with some sort of Prodos "BYE" command. However, Prodos doesn't seem to recog- >nize that command and complains. Is there such a command in a few versions of >Prodos (and there are a lot of versions...) or should it have been installed >by another routine in the KERMIT startup software? > Also, some SYS programs, such as READ.ME and INSTALL.KERMIT, crash shortly >after they are loaded into memory by Prodos, without any output beyond the >usual display when machine code crashes. > Beyond these few problems, everything seems to work. I can BRUN KERMIT >directly, and it works fine. Has anyone else had these problems, or is it >just me? Better yet, does anyone have any solutions? I am using Kermit on my hard drive. In my Kermit directory I only have two .SYS files, KERMIT.SYSTEM and INSTALL.KERMIT. I have a different "BYE" which I like better. I am not sure why you are "BRUNN'ing" Kermit, I think it should be a .SYS file as I mentioned above. I might guess that unpacking the whole works again may be in order. Also, the "BYE" that comes with Kermit is a .SYS program which, once run, continues to operate (i think) until you shut the system down or start up another version of ProDOS. Because I am running Kermit on my hard drive I am not sure about this next comment, but it seems to me that all of the appropriate Kermit files should fit on one ProDOS disk (the DOS 3.3 files all do), so I am also not sure why you are having to swap disks? If the Kewrmit "BYE" is functioning, what you should get when you leave Kermit is a list of possible .SYS files that you can exicute by placing the highlighted cursor on the file and pressing return. Clearly this may cause a little bit of a problem if you only have one disk i.e. the Kermit disk, so i am not really sure what to say about that. Hopefully someone with a little more knowledge than I will comment about it. I hope some of this helps. -- Bill Carss bill@braille.uwo.ca