[comp.sys.next] Problems at 1200 Baud...

kaplan@m.cs.uiuc.edu (08/03/89)

Hi there,, 
	I'm hoping someone out there can help with an irritating problem
thats forcing me to use my next serial ports at 300 baud.

I have a usrobotics 1200/300 baud courier modem.  I have used it for at
least a year with a dumb terminal and it works fine.  I've now got it
connected to the NeXT.  The problem is that when I try establish a serial
connection out of /dev/cua using it, I get random garbage instead of output
from the computer.  The link establishes fine, and echoes my (slowly typed)
characters just fine, but seems to drop chars when anything of any
magnitude (like a login message (I'm not kidding)) is printed.  If i dial
up at 300 baud then everything works 95% fine. (ie only occasionally
dropped chars).

This is with cu/tip.

What am I doing wrong here?  I notice the defaults in /etc/remote assume
hayes modems.  Is this a critical factor.

I know my cabling should be ok, i'm using a mac cable that works perfectly
from the mac.  just tested it.  The parity/etc should be ok cause the modem
works fine with my regular old ascii terminal.  and it works fine at 300
baud.  But at 1200 baud the world goes to pieces.  HELP!!

any suggestions gratefully appreciated...

Simon Kaplan
University of Illinois Computer Science
kaplan@cs.uiuc.edu
uunet!uiucdcs!kaplan

rokicki@polya.Stanford.EDU (Tomas G. Rokicki) (08/04/89)

In article <61300013@m.cs.uiuc.edu>, kaplan@m.cs.uiuc.edu writes:
> The problem is that when I try establish a serial connection
> seems to drop chars when anything of any magnitude (like a login message

For the other datapoint, I'm running a 9600 baud serial line between
a NeXT and an Amiga very happily, although I wish I could go to 38,400
on the cube.

-tom