Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cornell!uw-beaver!blake!oregon!goes
From: goes@oregon.uoregon.edu (Jim Goes, Univ of Oregon)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Procomm in vt-100 mode
Message-ID: <762@oregon.uoregon.edu>
Date: 11 Apr 89 16:23:10 GMT
References: <2380@cps3xx.UUCP> <1316@hounx.ATT.COM> <2405@cps3xx.UUCP>
Organization: University of Oregon
Lines: 21

In article <2405@cps3xx.UUCP>, usenet@cps3xx.UUCP (Usenet file owner) writes: 
>In article <1316@hounx.ATT.COM> marty1@hounx.ATT.COM (M.B.BRILLIANT) writes:
>>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.
 --  
I do binary transfers with KERMIT on PC+TD using COM3 all the time.  You 
have to make certain both the mainframe Kermit  and MS-Kermit are 
"SET FILE TYPE BINARY".  But I assure you it works, reliably, and at 
19,200 as well.
_______________________________________________________________________________ 
Jim Goes                      |  InterNet   GOES@OREGON.UOREGON.EDU  Graduate
School of Management          |  UUCP:      {fav backbone}!uoregon!oregon!goes
University of Oregon          |  MaBell:    (503) 686-3309
________________________________________________________________________________
Grad School. Its not just a job, it's an indenture...