Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!rutgers!clyde!cbatt!ihnp4!inuxc!pur-ee!uiucdcs!uxc.cso.uiuc.edu!crimmins From: crimmins@uxc.cso.uiuc.edu Newsgroups: comp.sys.ibm.pc Subject: Re: Kermit and Procomm Message-ID: <174200009@uxc.cso.uiuc.edu> Date: Tue, 16-Dec-86 12:15:00 EST Article-I.D.: uxc.174200009 Posted: Tue Dec 16 12:15:00 1986 Date-Received: Thu, 18-Dec-86 04:23:59 EST References: <75800005@uiucdcsp> Lines: 29 Nf-ID: #R:uiucdcsp:75800005:uxc.cso.uiuc.edu:174200009:000:1284 Nf-From: uxc.cso.uiuc.edu!crimmins Dec 16 11:15:00 1986 /* Written 1:38 pm Dec 15, 1986 by vanzandt@uiucdcsp.cs.uiuc.edu in uxc.cso.uiuc.edu:comp.sys.ibm.pc */ > > Would someone please explain (in full detail) to me how to get >Procomm 2.4 to do Kermit transfers. I can get Xmodem to work fine, I can >get Kermit to Kermit to work fine, I just can't get Procomm to Kermit to >work... It seems that you do not have your parity set the same on both sides, or your packet lengths are not the same. On the Procomm side, I have usually selected a packet lenght of 90. My guess, however, is that the parity is set different on the two programs. Even if your host is set for no parity, your Kermit might be looking for even parity. Look at the status screen on Kermit to verify that it is set the same as Procomm. The parity on Procomm will always correspond to what you are communicating at. I have had no problems using Procomm to transfer vi Kermit to and from uiucuxc. If you need more help, contact me at the address below or call our office at 244-0608. Good Luck! ---- Dan Crimmins University of Illinois at Urbana-Champaign Computing Services Office - Micro Consulting Dept. ARPA: crimmins@uiucuxc.cso.uiuc.edu BITNET: crimmins@uiucuxc.bitnet CSNET: crimmins@uiucuxc.csnet UUCP: {ihnp4,pur-ee,convex}!uiucdcs!uiucuxc!crimmins