Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rochester!cornell!vax1!jsm
From: jsm@vax1.ccs.cornell.edu (Jonathan Meltzer)
Newsgroups: net.micro,net.micro.pc
Subject: Re: HELP with ProComm 2.3 problems please!
Message-ID: <106@vax1.ccs.cornell.edu>
Date: Mon, 25-Aug-86 21:09:57 EDT
Article-I.D.: vax1.106
Posted: Mon Aug 25 21:09:57 1986
Date-Received: Tue, 26-Aug-86 05:04:48 EDT
References: <216@octopus.UUCP> <2012@sdcsvax.UUCP>
Reply-To: jsm@vax1.UUCP (Jonathan Meltzer)
Organization: Cornell Computer Services, Ithaca NY
Lines: 30
Xref: mnetor net.micro:5917 net.micro.pc:6277

In article <2012@sdcsvax.UUCP> rick@sdcsvax.UUCP (Rick Randall) writes:
>In article <216@octopus.UUCP> pete@octopus.UUCP (Pete Holzmann) writes:
>>I grabbed a copy of ProComm 2.3 several days ago. It seems like a very nice
>>program, but also rather buggy. It has a *very* annoying tendency to lock
>>up completely, and has trouble with terminal emulations. Has anybody else
>>had and/or solved these problems?
>>
>>	- Alt-S (setup) locks up an AT every time (IBM and clone. A second
>>		clone didn't have trouble)
>>	- Kermit transfers tend to get locked up
>>	- It frequently locks up when you aren't receiving anything (goes
>>		into a receive loop at the wrong time?)
>>  ...
>
>Never had any of these problems on my PC or on my Orchid 286e
>expansion board (like an AT on the PC).  Procomm 2.3 has worked
>beautifully by and large -- definitely the best PD comm program
>I've found.  Sorry about your problems -- and I can't suggest
>remedies;  perhaps you should register and then ask for support
>from the author(s).

The only Procomm problem I've encountered is the inability to Kermit to/from
Vax UNIX. Anyone know the correct parameters?
  


Jon Meltzer
Dept. of Modern Languages and Linguistics, Cornell University
------------------------------------------------------------------------
"Disclaimer" is a trademark of Bell Laboratories.