Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!brl-adm!rutgers!clyde!cuae2!ihnp4!houxm!whuts!tes
From: tes@whuts.UUCP (STERKEL)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Kermit and Procomm
Message-ID: <1139@whuts.UUCP>
Date: Wed, 17-Dec-86 15:10:34 EST
Article-I.D.: whuts.1139
Posted: Wed Dec 17 15:10:34 1986
Date-Received: Fri, 19-Dec-86 05:19:16 EST
References: <75800005@uiucdcsp>
Organization: AT&T Bell Laboratories
Lines: 32
Summary: are your using the latest Kermits?

In article <75800005@uiucdcsp>, vanzandt@uiucdcsp.cs.uiuc.edu writes:
> 
> 
> 	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...
>         usenet		ihnp4!uiucdcs!vanzandt
I became a reluctant expert in kermit/ProComm last month.
This was my solution:

1.  Make certain that you are using ProComm 2.4.2
    (not 2.4)
2.  Make certain that your Kermit on the UNIX (tm) end
    is the latest (are you running UNIX (tm)?, if not
    replace UNIX with "other".
3.  If you are an AT&T employee, ctrmkrmt.c from the
    CTRM 1.10 package (free from your local product
    center) works excellently.

After much trial and error, this worked.  I really do not know
why, but suspect that the various versions of Kermit are not
*really* downward compatible.  The ProComm people stated that
there is no difference between 2.4.0 and 2.4.2 kermit processors;
I have test results that indicated differently.

best wishes,
-- 
    -----                   Terry Sterkel
  -====----            AT&T Bell Laboratories
  ---------    {harvard|allegra|ulysses|ihnp4}!whuts!tes
    -----         [opinions are obviously only my own]