frank@rsoft.bc.ca (Frank I. Reiter) (03/22/90)
The other day I had to connect two SCO 386 Xenix systems together for
uucp and login access and rather than the way I usually do it I wired
a null-modem cable like so:
1 1
2 3
3 2
4 5
5 4
7 7
8 20
20 8
My idea was to enable tty1A (modem control device) rather than tty1a (the
usual way of doing this) so that if a user was cu'ed into the second system
and he/she ended cu without logging out it would seem to that system as though
carrier were lost when the first system dropped DTR.
What I got instead was a strange buffering kind of problem where I'd have to
type a few characters before I'd see any output (and then I'd see all of it).
The password prompt would not appear until I'd typed the first character of the
password, etc.
When I diabled tty1A and enabled tty1a (no change to the wiring or calling
system) everything worked fine.
Has anybody else encountered (dare I ask solved?) this problem?
--
_____________________________________________________________________________
Frank I. Reiter UUCP: {uunet,ubc-cs}!van-bc!rsoft!frank
Reiter Software Inc. frank@rsoft.bc.ca, a2@mindlink.UUCP
Surrey, British Columbia BBS: Mind Link @ (604)576-1214, login as Guest