ingoldsby@calgary.UUCP (07/15/86)
I recently acquired a copy of Kermit, written by Wes Hubert. I haven't had any success in getting it to talk to our Unix C-Kermit (which I know works) and was wondering if anyone had any pointers on how to get this thing going. The terminal program works fine, and when it is supposed to be transferring I can hear the two Kermits calling to each other if I put my ear to my modem. Unfortunately, there seems to be some difference in protocol `cause they never transfer any data and both eventually time-out. Any help would be appreciated. Terry Ingoldsby ...ihnp4!alberta!calgary!ingoldsby
pete@wlbreng1.UUCP (07/18/86)
Terry, Regarding the use of COCO kermit with C-Kermit... I have not tried the COCO implementation as yet (I did download a copy from COMPUSERVE..), but I *do* use the OS9 version HEAVILY. I know that both version 1.2 (User's Group Library - old) and 1.6 (new version - updated by Bob Larson) work very well with C-Kermit. I don't know if that's of any help to you, but I am pretty sure you're an OS9'er, as I've seen your name on the Dave Lewis NEWDISK driver.. By the way, have you (you = You || Dave) had any trouble using the NEWDISK under version 2.0?? A few of the users on CompuServe have installedf it under 2.0, and have had problems.. Initially, after cold start, they fall out of the startup shell script because no paths are set up (!!). If after this, the user MANUALLY does a chd and chx, the problem is resolved and all functions normally. Another interim fix for this is that the coco 2.0 SYSGO module contains a hook that will attempt to CHD to '/h0' if the user has one in the system. We have found that if these are patched to be '/D0' that all is fine .. Strange, eh...?? Pete Lyall Net: ....!ihnp4!wlbr!wlbreng1!pete CIS: 76703,4230 (OS9 Asst. Sysop)