Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!shadooby!accuvax.nwu.edu!tank!eecae!cps3xx!usenet
From: usenet@cps3xx.UUCP (Usenet file owner)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Procomm in vt-100 mode
Message-ID: <2405@cps3xx.UUCP>
Date: 7 Apr 89 19:22:48 GMT
References: <2380@cps3xx.UUCP> <1316@hounx.ATT.COM>
Reply-To: cook@frith.UUCP (Tom Cook CPS 311 W88)
Organization: Engineering, Michigan State University, E. Lansing
Lines: 15

In article <1316@hounx.ATT.COM> marty1@hounx.ATT.COM (M.B.BRILLIANT) writes:
>From article <2380@cps3xx.UUCP>, by usenet@cps3xx.UUCP (Usenet file owner):
>> I would check which com port you are using your modem on.  From what I
>> understand, Procomm does not allow binary transfers when on com port 3.
>
>I can quash that theory.  I have a 1200 baud modem on an XTurbo clone,
>so there may be other hardware considerations, but as a general
>statement it is not true.  I have an internal modem hardware-configured
>as COM3 and I've used XMODEM for binary transfers with ProComm 2.4.2.

I stand corrected!  The problem with COM3 concerned KERMIT transfers
only.  I did not make this clear.  I also have had no problems using
XMODEM in COM3 with procomm.

Greg