john@wa3wbu.UUCP (John Gayman) (02/12/88)
Before I gave my first impressions of the Telebit Trailblazer running under Microport Sys V/AT. I have put together a list of exactly how I have everything set up. It may save someone a few steps anyway. I've been running the modem for several days and have been extremely impressed with the response. I am still running all my News feeds late at night so the interrupt problems at 9600 baud have not been a concern at all. I do plan to implement an intelligent serial card sometime soon which should enable 9600 baud UUCP to run while other serial services are running. I am currently running 2.3U with Microports HonneyDanBer UUCP. Because of the fact that Microports HDB doesn't appear to support the "Dialers" file, the configuration has to be "modified" slightly as you will note below. These are the register settings I currently have set in the modem. Version 4.0 of the firmware appears to be the latest being supplied by Telebit: E0 F1 M0 Q6 T V1 X1 Version BA4.00 S00=001 S01=000 S02=043 S03=013 S04=010 S05=008 S06=002 S07=060 S08=002 S09=006 S10=007 S11=090 S12=050 S45=000 S47=004 S48=000 S49=000 S50=000 S51=255 S52=002 S53=004 S54=003 S55=000 S56=017 S57=019 S58=000 S59=000 S60=000 S61=055 S62=003 S63=001 S64=001 S65=000 S66=000 S67=000 S68=255 S90=000 S91=000 S92=001 S95=000 S100=000 S101=000 S102=000 S104=000 S110=001 S111=030 S112=001 S121=000 N0: N1: N2: N3: N4: N5: N6: N7: N8: N9: The following are some entries from my /usr/lib/uucp/Systems. These examples cover a couple different types of connects. Systems n3dmc & uunet are at 9600 and use the modem in PEP mode. ka3adu is a normal 2400 baud line with a Hayes at the other end. The reason for the extra stuff is that because Microport doesn't support the "dialers", we must configure the modem in the Systems file. In the area of login/password, I've found that putting delays in between each character seems to increase the reliability of the login being interpreted correctly. n3dmc SaSu,Wk0200-0600 Direct 9600 tty0 "" BREAK "" A\dA\dA\dT OK ATS50=255DT13335551212 CONNECT\sFAST--CONNECT\sFAST "" ogin:-BREAK-ogin:-BREAK-ogin:-BREAK-ogin:-BREAK-ogin: mylogin ssword: mypassword uunet SaSu,Wk0100-0630 Direct 9600 tty0 "" BREAK "" A\dA\dA\dT OK ATS50=255DT13335551212 CONNECT\sFAST--CONNECT\SFAST "" ogin:--ogin: x\dx\dx\dx\dx\dx\r ssword: x\dx\dx\dx\dx\dx\dx\dx\r ka3adu Any Direct 2400 tty0 "" BREAK "" A\dA\dA\dT OK ATS50=3DT5551212 CONNECT\s2400 "" ogin: mylogin ssword: mypassword This is the gettydefs entries that I've added for the modem. It was recommended to me to use these slightly modified entries and I havnt experimented with the stock ones. I mean, these work. :-) I then made the entry in /etc/inittab to specify "9600M" as the getty speed on startup. 9600M# B9600 HUPCL PARENB CS7 OPOST ONLCR # B9600 HUPCL SANE IXANY TAB3 #login: #2400M 2400M# B2400 HUPCL PARENB CS7 OPOST ONLCR # B2400 HUPCL SANE IXANY TAB3 #login: #1200M 1200M# B1200 HUPCL PARENB CS7 OPOST ONLCR # B1200 HUPCL SANE IXANY TAB3 #login: #9600M This is the Devices file. Again, I had to specify "direct" for the modems so that dialing could be done manually in the Systems file. Direct tty0 - 1200 Direct tty0 - 2400 Direct tty0 - 4800 Direct tty0 - 9600 This may seem like a lot of work but it's really quite simple. I beleive you could use this method with conventional UUCP. The main reason for going to HDB is to make use of the Dialers file, unfortunately this is a problem. It sometimes takes a little thinking to configure a new site in the Systems file, but I have now about 10 sites entered and working reliably at anywhere from 1200-9600 baud. Once you see the method used for spoofing a dialer, its easy to make changes. It actually quite neat. I mean you can if you wish, make register changes on a per-call basis if you have calls requiring special needs. I hope this information is of use. John -- John Gayman, WA3WBU | UUCP: uunet!wa3wbu!john 1869 Valley Rd. | ARPA: wa3wbu!john@uunet.UU.NET Marysville, PA 17053 | Packet: WA3WBU @ AK3P
mike@cimcor.UUCP (Michael Grenier) (02/15/88)
From article <489@wa3wbu.UUCP>, by john@wa3wbu.UUCP (John Gayman): > > > > Before I gave my first impressions of the Telebit Trailblazer running > under Microport Sys V/AT. I have put together a list of exactly how I > have everything set up. I looked over the list John provided us but I'm lost over one point. I running a MultiTech 224E, 2400 baud modem with MNP 5 error correction which means that it incorporates compression on the fly like the Telebit. My maximum throughput then is nearly 4800 baud on text files. I can set up the microport box for 4800 baud and let the modem do the baud adjustments for me but heres where I run into a problem. If the modem starts talking to something around 2400 or 1200 baud then the transmit buffers will overflow in the modem ( duh, really?). OK, there are two types of flow control I can use. The first is the obvious Xon, Xoff which works fine for text files but is dubious when I'm using XMODEM or other binary file transfers (I'm assuming that the UUCP g-protocol is also binary). The other method is to use hardware handshaking. This modem uses CTS to signal the Microport box to stop transmitting and uses RTS to allow the Microport box to signal the modem to stop sending to it. It seems according to Microport's tech support that their serial drivers don't support hardware handshaking - which can't be too tough if IBM can do it in their BIOS :-). How can I make used of the speed advantages of this MNP5 modem and still allow it to handle calls from 1200 and 2400 baud modems. -Mike {rutgers, amdahl, ihnp4}!bungia!cimcor!mike