sandy@turnkey.TCC.COM (Sanford 'Sandy' Zelkovitz) (01/25/89)
I am still having problems with the Telebit modem running under SCO Xenix
386 version 2.3.1! Here are the changes that I made:
1) I added the following line to the Devices file:
ACU tty1A - 1200-19200 /usr/lib/uucp/dialTBIT
2) I made a new entry in /etc/gettydefs to reflect the 19200 baud (EXTA)
rate (which is mostly the same as entry 3 (1200) but I added CTSFLOW
and RTSFLOW. I made another entry, as a test case, with only CTSFLOW.
3) I setup configuration A, on the TBIT, to run without flow control so
that I can talk to it with cu.
4) I switched to configuration B and ran /usr/lib/dialTBIT -z /dev/tty2a 19200.
5) The program just hung and the only way out was to kill the process.
6) I switched over to configuration A and ran cu. When I did an at&n2, it
turned out that dialTBIT did set the configuration in properly since it
matched EXACTLY what SCO had listed in the source listing of the dialer.
7) When I enabled the port, it seems that getty must look at the Devices file
since it was calling the dialer with a -hx0 option. This is when the
complete SCO setup fell flat on its face! The dialer, it seemed, could NOT
communicate with the modem properly and the only way out was to disable
the port, kill the dialer process, and switch over to configuration A,
which was exactly the same as SCO's but without flow control. This
seemed to work just fine.
Therefore, I have the following questions:
1) Does SCO's drivers REALLY support flow control or is this just a joke
on the users?
2) Has anyone had any luck running this without any changes and what was
your gettydefs entry, etc.
Sandy
--
Sanford <sandy> Zelkovitz XBBS 714-898-8634
UUCP: ....att!hermix!alphacm!sandy ....trwrb!ucla-an!alphacm!sandy
....uunet!turnkey!alphacm!sandy ....ucbvax!ucivax!icnvax!alphacm!sandy
DATA: 714-898-8634 VOICE: 714-894-7898jbayer@ispi.UUCP (Jonathan Bayer) (01/27/89)
In article <5367@turnkey.TCC.COM> sandy@turnkey.TCC.COM (Sanford 'Sandy' Zelkovitz) writes: >I am still having problems with the Telebit modem running under SCO Xenix >386 version 2.3.1! Here are the changes that I made: > I am running a trailblazer+ on the same type of system. I have the following settings: I use the standard gettydefs entry A the Devices entry is: ACU tty2D - 9600-19200 dialTBIT \D You definitely need the flow control. Yes it works, although I did get the flow control patch from SCO. The patch # is xnx105, RTS/CTS handshaking supplement. I always use configuration A. I set the modem to its default state by using ATZ AT&W I ran /usr/lib/dialTBIT -z /dev/tty2a 19200. Hope this helps. JB -- Jonathan Bayer Beware: The light at the end of the Intelligent Software Products, Inc. tunnel may be an oncoming dragon 19 Virginia Ave. ...uunet!ispi!jbayer Rockville Centre, NY 11570 (516) 766-2867 jbayer@ispi
terry@eecea.eece.ksu.edu (Terry Hull) (01/28/89)
In article <5367@turnkey.TCC.COM> sandy@turnkey.TCC.COM (Sanford 'Sandy' Zelkovitz) writes: >I am still having problems with the Telebit modem running under SCO Xenix >386 version 2.3.1! Here are the changes that I made: > > [description deleted] I have had problems with hardware flow control as well. I am using my TB+ mostly for dial out, but here is what I'm doing. 1) For outgoing uucp, I set the modem for hardware flow control and UUCP spoofing to connect to another TB modem. I set dialTBIT for XON/XOFF when connecting to a 1200 baud modem. 2) For outgoing cu, I use XON/XOFF at both 1200 baud and 19.2 KB 3) Incoming cu works OK with XON/XOFF. BTW, I have specified XON flow control in the gettydefs. 4) When I add RTSFLOW and CTSFLOW to the gettydefs (with a CORRECT cable) the modem will answer and connect, but I never get a prompt from the computer. If I change to XON flow control it works. I intend to attack this problem next week by attaching a terminal to the serial port and trying to make the hardware handshaking work. The only thing I have found so far is that you probably should not use the sane stty parameter when trying to enable hardware flow control because sane tries to set XON/XOFF. I was trying to use SANE together with RTSFLOW/CTSFLOW when I was having the problems. -- Terry Hull Department of Electrical and Computer Engineering Kansas State University INTERNET: terry@eecea.eece.ksu.edu Manhattan, KS 66502 UUCP: rutgers!ksuvax1!eecea!terry
larry@tapa.UUCP (Larry Pajakowski) (01/29/89)
[ comments about flow control ] I ran into a problem like this some months ago and found 2 problems. First my driver for the Digiboard 8i was out of date and didn't support flow control and Second and more important flow control is only supported on "modem" ports like tty1A (not tty1a) etc. This is documented. After that I've had no problems with XON/XOFF and use the TB+ as well as a LaserJet that way. Larry
larry@tapa.UUCP (Larry Pajakowski) (01/30/89)
In the last art. I wrote about flow my brain was very out of sync. I was trying to get hardware flow control to work not XON/XOFF which I eventually did. That is how we operate our TB+. Thanks to another poster who jogged my memory on this. Larry