Xref: utzoo comp.unix.xenix:4664 comp.unix.wizards:14363 Path: utzoo!attcan!uunet!lll-winken!lll-lcc!ames!ucsd!rutgers!deimos!eecea!terry From: terry@eecea.eece.ksu.edu (Terry Hull) Newsgroups: comp.unix.xenix,comp.unix.wizards Subject: Re: problems with Telebit and dialTBIT.c Keywords: xenix386 Trailblazer-Plus_model_T2000 Message-ID: <544@eecea.eece.ksu.edu> Date: 27 Jan 89 16:14:29 GMT References: <5367@turnkey.TCC.COM> Reply-To: terry@eecea.eece.ksu.edu(Terry Hull) Followup-To: comp.unix.xenix Organization: Kansas State University, Manhattan Lines: 33 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