Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!uakari.primate.wisc.edu!ginosko!uunet!medsys!root From: root@medsys.uucp (Superuser) Newsgroups: comp.unix.xenix Subject: Telebit and Xenix Message-ID: <1989Oct10.221028.593@medsys.uucp> Date: 10 Oct 89 22:10:28 GMT Distribution: na Organization: Med-Systems, Kingport, Tennessee Lines: 226 Here is a summary of the mail and news traffic received regarding use of a Telebit Trailblazer with SCO Unix/Xenix. It would appear to me that there are problems with Unix 3.2 gettydefs configuration. The EXTA and EXTB designations have apparently gone by the boards, yet B. Templeton appears to be using them to acheive 19200 baud. My current modem entry for 19200 is: 4 # B19200 HUPCL ECHOE CR1 NL1 # B19200 CS8 SANE HUPCL TAB3 ECHOE IXON IXOFF IXON IXOFF IXANY #\r\n( For BBS log in as "bbs" , password: "bbs" )\r\n@!login: # 3 It appears that the speed IS being set, but only when I edit the /etc/inittab file by hand. The "uuinstall" utility does not work correctly, and in fact, does not display any of the 19200 or 38400 baud entries using option #4 -- Mode:Speeds defined in /etc/gettydefs. Also, even though the "stty" tells me I am connected at 19200, uucico tells me in xferstats that it's running 50% slower. (Do I need a stopwatch??) The xferstats comparisons are as follows (using same modem settings): Xenix 2.3.2 uunet!root M (9/21-23:52:14) (C,4924,35) [tty1A] <- 67062 / 62.060 secs, 1080 bytes/sec uunet!root M (9/21-23:53:07) (C,4924,37) [tty1A] <- 51960 / 48.520 secs, 1070 bytes/sec uunet!root M (9/21-23:53:37) (C,4924,39) [tty1A] <- 25703 / 24.640 secs, 1043 bytes/sec Unix 3.2 uunet!root M (10/8-23:18:09) (C,5942,19) [tty1A] <- 14995 / 28.840 secs, 519 bytes/sec uunet!root M (10/8-23:18:37) (C,5942,21) [tty1A] <- 27042 / 47.100 secs, 574 bytes/sec uunet!root M (10/8-23:19:29) (C,5942,23) [tty1A] <- 54296 / 94.060 secs, 577 bytes/sec Much of the info below does not specifically pertain to Unix 3.2 but it may be of some help to others configuring modems in Xenix. ***** Date: Sat, 30 Sep 89 06:57 PDT From: Kayvan Sylvan Internet: kayvan@Transact.COM -*- UUCP: ...!{apple,pyramid,mips}!mrspoc!kayvan I use the following configuration: Every site that uses Telebits is listed in my Systems file as 19200 baud. In my Devices file I have: # # Modems # Put the low-speed-only modem(s) first so that they will be attempted # first for low speed calls. # ACU ttyA11 - 1200-2400 hayes2400 ACU ttyA9 - 19200 tbblaze ACU ttyA9 - 2400 tb2400 ACU ttyA9 - 1200 tb1200 ACU ttyA10 - 19200 tbblaze ACU ttyA10 - 2400 tb2400 ACU ttyA10 - 1200 tb1200 # In order to reset the telebit mode settings, uncomment the following # lines and do: # disable ttyA9 # disable ttyA10 # cu -lttya9 -s19200 -x5 666 # cu -lttya10 -s19200 -x5 666 #ACU ttya9 - 19200 tbreset #ACU ttya10 - 19200 tbreset # Then, I use the following Dialers entries for dialing out. Since I use all 3 modems as dialin/out lines, I have the corresponding "&dialer" entries as well. tbreset is my fake dialer entry for resetting the modem configuration. # Telebit dialers # tb1200, tb2400, tbblaze for 1200, 2400 and 19200 baud. tb1200 =W-, "" A\pA\pA\pT OK ATM0S50=2DT\T CONNECT\s1200 tb2400 =W-, "" A\pA\pA\pT OK ATM0S50=3DT\T CONNECT\s2400 tbblaze =W-, "" A\pA\pA\pT OK ATM0S51=5S111=30S50=255DT\T CONNECT\sFAST &tb1200 =,-, "" A\pA\pA\pT OK ATHQ6S50=0S0=1 OK &tb2400 =,-, "" A\pA\pA\pT OK ATHQ6S50=0S0=1 OK &tbblaze =,-, "" A\pA\pA\pT OK ATHQ6S51=255S50=0S0=1S111=255 OK # This entry will reset the Telebit modem to desired modes tbreset =,-, "" A\pA\pA\pT OK ATHQ6S45=255S50=0S51=255S52=2S53=3S54=3 OK ATS58=2S66=0S68=255 OK ATS0=1S111=255S92=0S95=0S61=0S255=1 OK AT&W1 OK ATZ OK I found that this works very well for me and allows dialin/out access (which I don't think dialTBIT would). ***** Date: Sun Oct 1 06:28:35 1989 From: cs.utexas.edu!albion.utah.edu!rel.mi.org!bob@uunet.UUCP (Bob Leffler) bob@rel.mi.org or {uunet!edsews, rutgers, sharkey}!rel!bob Here's my setup: 6 # EXTA HUPCL OPOST CR1 ECHOE NL1 # EXTA CS7 PARENB SANE HUPCL TAB3 ECHOE IXANY #\r\nlogin: # 5 E1 F1 Q4 T V1 X1 Version BB4.00 S00=001 S01=000 S02=128 S03=013 S04=010 S05=008 S06=002 S07=040 S08=002 S09=006 S10=007 S11=070 S12=050 S45=000 S47=004 S48=000 S49=000 S50=000 S51=004 S52=001 S53=004 S54=004 S55=000 S56=017 S57=019 S58=003 S59=000 S60=000 S62=003 S63=001 S64=000 S65=000 S66=000 S67=000 S68=255 S90=000 S91=000 S92=001 S95=000 S100=000 S101=000 S104=000 S110=000 S111=255 S112=001 S121=000 Since my throughput typically is between 900-1300 cps, it appears to be dependent on the other machine. Between my AT running Xenix/286 2.2.1 and a Sun 3/280 at the office, I usually get around 1300 cps. I am having problems with getty thinking there is an inbound call. I have the internal T18PC modem. The symptoms are that ungetty can't disable the port (line in use error), the modem won't answer the line on inbound calls, and the getty process on that port can't be killed. The only way I've been able to resolve the situation is to reboot. Needless to say, that gets old real quick. I've be experimenting with DTR/DSR to see what are the effects, but whatever the settings are, it doesn't appear to stop the problem from happening. Perhaps when SCO starts shipping Xenix/286 2.3, modem control might get better. :^) ***** Date: Sun, 1 Oct 89 18:16:33 EDT From: watmath!looking.on.ca!brad@uunet.UUCP (Brad Templeton) Tee-hee. Tee-hee. You fell into the same trap as I did. Do it again and time it with your stopwatch. Your new uucico is just as fast, it just *reports* times that are twice as long, througputs that are thus half as good. Scared me for a while, too. ***** Date: Mon Oct 2 21:40:52 1989 From: milhow1!how@uunet.UUCP Mike Howard uunet!milhow1!how or milhow1!how@uunet.uu.net I have been running SCO Xenix 286 2.3.1 and have been getting around 350 characters/second. I recently received the support suplement which upgrades 2.3.[01] to 2.3.2 and replaced my uucico with the 2.3.2 uucico and am back to 850 or so cps. [I have my TB+ speed locked at 9600 baud rather than 19.2 out of fear of my antique 8 port async board]. It turns out that 2.3.1 uucico is a Large model 8086 binary and 2.3.2 uucico is a 80386 binary. Your speed difference between Xenix and Unix could be the result of some brain dead inefficiency like this rather than the TB setup. BTW - I my dialer is not the stock SCO dialer, but rather a hack job I did on dialHA12.c prior to getting the uucp which handled TB's. I put in a couple of features for programming the registers on a call by call basis, so have never used their dialer. ***** Date: 3 Oct 89 18:58:52 GMT From: terry@eecea.eece.ksu.edu (Terry Hull) Work: terry@eecea.eece.ksu.edu, rutgers!ksuvax1!eecea!terry Well, I called SCO support today and found out their drivers break when you try to use them at 19200 baud. They told me if I backed off to 9600 things world work. I was also told there would be a SLS fix coming for the problem. No time frame was given though. I guess that means that all you TB+ people out there had better be ready to go to 9600 when you upgrade to UNIX 3.2. ***** Date: 5 Oct 89 21:34:41 GMT From: brad@looking.on.ca (Brad Templeton) Well, I don't have rtsflow or ctsflow set in the gettydefs line. (I do have a problem with getty where it insists that dialing in logins come in with 0 parity, which is a pain -- the istrip isn't working) Here's the gettydefs line p # EXTA HUPCL ISTRIP # EXTA CS8 SANE HUPCL TAB3 ECHOE IXANY #(Telebit 19200) login: # 3 The trick might be in my telebit registers, which are a bit different from SCO's setup. But they work with dialTBIT and uugetty. E0 F1 M1 Q0 T V1 X3 Version BA4.00 S00=001 S01=000 S02=043 S03=013 S04=010 S05=008 S06=004 S07=040 S08=002 S09=006 S10=007 S11=070 S12=050 S45=000 S47=004 S48=000 S49=000 S50=000 S51=005 S52=002 S53=001 S54=001 S55=003 S56=017 S57=019 S58=002 S59=000 S60=000 S61=045 S62=003 S63=001 S64=000 S65=000 S66=000 S67=000 S68=255 S90=000 S91=000 S92=000 S95=000 S100=000 S101=000 S102=000 S104=000 S110=255 S111=255 S112=001 S121=000 Every once in a while I will get strange behaviour on dial-OUT when the relay will click on and off quickly 4 times in a row, but that's rare and everything seems to be working otherwise. Just fine at 19.2k Right now I have the modem connected to a standard COM1. But it also worked connected to my smart card Intellicon port, which I plan to switch it over to shortly. ***** -- __ __| __ __ LaVerne Olney -- Med-Systems |/^\/^\ /__) / | (__ \ / (__ Medical Office Management Software | | | \__ \__| ___) \/ ___) Kingsport, TN 37660 U.S.A. Unix BBS: 615-288-3957 / UUCP: uunet!medsys!laverne