Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!lll-tis!ames!hao!husc6!m2c!ulowell!hawk.ulowell.edu!boneill
From: boneill@hawk.ulowell.edu (SoftXc Coordinator)
Newsgroups: comp.sys.ibm.pc
Subject: ProComm Plus Kermit Problem (was Re: ProComm Plus DEL/BS)
Message-ID: <5108@swan.ulowell.edu>
Date: 26 Feb 88 13:56:45 GMT
References: <2944@swan.ulowell.edu> <2945@swan.ulowell.edu> <2212@isis.UUCP> <996@nscpdc.NSC.COM>
Sender: news@swan.ulowell.edu
Reply-To: boneill@hawk.ulowell.edu (SoftXc Coordinator)
Distribution: na
Organization: University of Lowell, CS Dept.
Lines: 25

In article <996@nscpdc.NSC.COM> rickr@nscpdc.NSC.COM (Rick Riverman) writes:
>
>
>My preliminary tests of ProcommPlus show that it won't transfer files to
>a UNIX system using Kermit.  Procomm 2.42 does this just fine.  If you attempt
>to transfer a file to a UNIX system with Kermit set to receive, ProcommPlus
>will NOT terminate the kermit receiver when the transfer is complete.  This
>is quite an inconvenience because you are left with a UNIX connection stuck
>in kermit protocol that must time out before you can continue.
>
>So much for Capitalists...

That's funny, I haven't had that problem at all, and I use kermit transfers
all the time. You'd might want to check out your kermit setup on ProComm
Plus and make sure it is compatible with the kermit settings on your UNIX
system. An older version of kermit on one system gives a termination message
like this when completed:

Transfer terminated with this message from remote host:

But otherwise nothing was different.

============================================================================
Brian O'Neill					University of Lowell
boneill@hawk.cs.ulowell.edu - boneill@hawk.UUCP ...!ulowell!hawk!boneill
MS-DOS Software Exchange Coordinator - E-mail for details