Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!rutgers!orstcs!prism!linb
From: linb@prism.cs.orst.edu (Ben Lin)
Newsgroups: comp.sys.apple2
Subject: Re: Proterm Speed Problem
Message-ID: <19243@orstcs.CS.ORST.EDU>
Date: 7 Jul 90 05:30:28 GMT
References: <BURNS.90Jul6092818@bobcat.gatech.edu>
Sender: usenet@orstcs.CS.ORST.EDU
Reply-To: linb@prism.CS.ORST.EDU (Ben Lin)
Distribution: usa
Organization: Oregon State Univ. -- Computer Science
Lines: 30

In article <BURNS.90Jul6092818@bobcat.gatech.edu> burns@gatech.edu (James E. Burns) writes:
>
>I have recently been trying to connect an Apple II GS with a 
>NeXT machine via a null-modem cable.  It works great at 300,
>1200 & 2400 baud, but I can't get it to work at higher speeds
>
>If I match the 'on-line' speed in Proterm to the NeXT setting at
>300, 1200, or 2400 everything works as expected.  If I mismatch the
>speeds I get garbage (as expected).  If I set Proterm's speed to
>4800, 9600 or 19200 & leave the NeXT at 2400, I get effective
>communication at 2400 (i.e., the Apple's speed can't seem to go
>above 2400).  If the NeXT is set to a matching speed above 2400
>I get garbage.

I use Kermit myself and have done quite a bit of transferring over
null modem, but I recall that recently someone else was having similar
problems with ProTerm.  If you're using the Hayes 2400 driver, even if
you tell ProTerm to go faster, it will still only go at 2400 baud.  I
believe ProTerm includes a null modem option on the list of modems
(under I)nstall hardware), which will go up to 19200.  Alternatively,
if that doesn't work, try a different program - both Kermit and
ReadyLink have worked for me. 

>jim burns
>Internet :  burns@CC.GATech.edu  
>uucp:	...!{akgua,allegra,hplabs,ihnp4,linus,seismo,ulysses}!gatech!cc!burns

ben
---
linb@prism.cs.orst.edu