Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!uwvax!husc6!yale!cmcl2!lanl!myxm
From: myxm@lanl.ARPA (Mike Mitchell)
Newsgroups: net.micro,net.micro.pc
Subject: Re: HELP with ProComm 2.3 problems please!
Message-ID: <6863@lanl.ARPA>
Date: Wed, 27-Aug-86 16:12:10 EDT
Article-I.D.: lanl.6863
Posted: Wed Aug 27 16:12:10 1986
Date-Received: Wed, 27-Aug-86 21:22:40 EDT
References: <216@octopus.UUCP> <2012@sdcsvax.UUCP>
Organization: Los Alamos National Laboratory
Lines: 23
Xref: mnetor net.micro:5930 net.micro.pc:6299

> 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?
> >
> 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).

I'll have to agree about Procomm. It is one of the nicest pieces of
software that has come through public domain. The problems you are
experiencing could either be related to some background software that
you are loading at boot or since you say it is a compatible, you might
even want to suspect the BIOS. I don't know how dependant Procomm is on
the BIOS, but I have had it hang on me when I had background serial port
monitor running and start Procomm up.

Mike Mitchell
myxm@lanl.ARPA