Before high speed internet, we were stuck with expensive T1's or slo-o-o-w modems. A 56K network was a heck of a lot better than a 38.4!
For quite a few years, my High Speed Modems for SCO Unix (and other modem tips) was the most popular page here by far - I doubt it gets any hits at all now other than from search engines.
From: "Brian K. White" <linut@squonk.net> Newsgroups: comp.unix.sco.misc Subject: Re: GETTY with fast modems SCO 5.0.5 Date: Tue, 16 Nov 1999 08:31:36 -0500 Message-ID: <38315CB8.DE709EB5@squonk.net> Cache-Post-Path: firth.squonk.net!unknown@dialup-102.squonk.net Global Fusion wrote: > > Anyone been able to get getty to run at 38K or faster? > My SCO 505 returns getty bad speed errors and getty respawns, > even though the modems connect OK. I have both incoming getty and outgoing ppp working at 57600 between computer & modem, and as high as the modem is capable of at any given moment between modem & modem, on sco 5.0.5
Here is how I'm getting it, this is not the be-all end-all, and I don't actually know as much as I'd like about how it all works, it's just working great here for a fact and back when I first got the system I had the same exact question as you just asked and I lived without for a couple months because the sco on-line docs are a little hard to figure out at first how to get what you want/need out of them, though they are pretty complete. So, Here... This is for a 33.6 modem on COM1 other ports (like a digiboard) would not only require different entries in the files, but in at least one case, different files to edit altogether. In some cases I show the whole file, so as to avoid you making duplicate entries in files by simply adding what you see here to the end, but in some cases I only show the lines that should be added, if the file is large and I'm sure you don't already have a line that would conflict. It should be apparent which is which when you open your existing fils in an editor. Don't make any assumptions about the importance of whitespace. Trailing spaces on the ends of lines are sometimes bad, cutting & pasting sometimes fills the whole line with spaces so watch it. newlines may not be unimportant between lines, leave them if they are shown here. sometimes the order in which lines appear is important. basically don't assume *anything* :) on top of all that, be aware that some lines are supposed to be much longer than 74 characters, and the text in email almost always gets wrapped somewhere between 70 and 80. I'll try and explain later the important bits of the interactions between the files so you can sense what you can and should change and what you should not. /etc/conf/init.d/sio: ------ Se1a:234:off:/etc/getty tty1a m Se2a:234:off:/etc/getty tty2a m Se2A:234:off:/etc/getty -t60 tty2A 3 Se1A:234:respawn:/etc/getty -t60 tt1A 5M ------ /etc/inittab: ------ Se1a:234:off:/etc/getty tty1a m Se2a:234:off:/etc/getty tty2a m Se2A:234:off:/etc/getty -t60 tty2A 3 Se1A:234:respawn:/etc/getty -t60 tt1A 5M ------ /etc/gettydefs: ------ # # M1-M5: dialin on Multitech 33.6 modem #
1M # B2400 HUPCL # B2400 CS8 SANE HUPCL TAB3 ECHOE CTSFLOW -ORTSFL #\r\n(2400)login: # 1M 2M # B9600 HUPCL # B9600 CS8 SANE HUPCL TAB3 ECHOE CTSFLOW -ORTSFL #\r\n(9600)login: # 2M 3M # B19200 HUPCL # B19200 CS8 SANE HUPCL TAB3 ECHOE CTSFLOW -ORTSFL #\r\n(19200)login: # 3M 4M # B38400 HUPCL # B38400 CS8 SANE HUPCL TAB3 ECHOE CTSFLOW -ORTSFL #\r\n(38400)login: # 4M 5M # B57600 HUPCL # B57600 CS8 SANE HUPCL TAB3 ECHOE CTSFLOW -ORTSFL #\r\n(57600)login: # 5M ------ /usr/lib/uucp/Devices: (remove or comment any other lines that talk about tty1A. particularly, the first line shown heremust be the first non-comment line in the file that has tty1A in it) ------ ACU tty1A - 57600 MultiModem_MT2834ZDXb Direct tty1a - 57600 direct ------ /usr/lib/uucp/default/MultiModem_MT2834ZDXb ------ MDM_SETUP=AT&F&E1Q2&D3X0 MDM_SPEAKER=ATM0 MDM_DIALCMD=ATDTW MDM_HANGUP=ATH MDM_DIALIN=ATS0=1 ------ And lastly there needs to be a symlink from /usr/lib/uucp/MultiModem_MT2834ZDXb to /usr/lib/uucp/default/MultiModem_MT2834ZDXb for outgoing ppp to an ISP add: /etc/ppphosts: ------ 0.0.0.0:0.0.0.0 attach=SquonkNet uucp=SquonkNet conf=10 flow=rtscts debug=0 mask=255.255.255.0 ------ /usr/lib/uucp/Systems: (don't have to remove or comment the other line you may have here) ------ SquonkNet Any ACU 57600 2921145 host: ppp login: myusername Password: mypassword modem Never Direct 57600 - - - ------ if you are installing on COM2, change all references to tty1A and tty1a to tty2A and tty2a if you are installing on a digiboard, then instead of /etc/conf/init.d/sio you'd edit /etc/conf/init.d/epca, as well as change use some other tty besides tty1A the "5M" used in /etc/conf/init.d/sio and /etc/inittab corresponds to the "5M" from /etc/gettydefs all instances of "MultiModem_MT2834ZDXb" can be replaced with anything else listed in /usr/lib/uucp/default, or you could copy one of those files to a new name and edit it to suit. legal parameters for these files are shown in "man atdialer" the desired state you want the modem to be in , which determines what you need to look-up in your modems manual, is: Terse, verbale result codes ATV1 = verbal ATX0 = just say "CONNECT" don't say "CONNECT 31200 LAPM" reste modem if dtr drops (AT&D2) don't echo commands (ATE0) if you need to type AT commands into your modem to set it up initailly and then store the defaults with AT&W0, you can do so after making the above changes by typing "cu modem" to get out of "cu" type "~." (no quotes) and then [return] You might also need to adjust some tunable kernel parameters using "configure" such as TTYHOG and NCLIST if you get a lot of errors on the connection. see "man configure" all cases of 57600 can be replaced with higher or lower numbers, so long as they all match all cases of SquonkNet would be replace with whatever you feel like calling your ISP you connect to the isp by typing "pppattach SquonkNet" and waiting until "ifconfig ppp0" shows that the connection is up. in this line from /usr/lib/uucp/Systems: SquonkNet Any ACU 57600 2921145 host: ppp login: myusername Password: mypassword everything after the phone number (2921145) is a simple expect-->send chat script wait for "host:" respond with "ppp" wait for "login:" respond with "myusername" waite for "Password:" respond with "mypassword" and obviously would need to be tailored for your isp. I *think* that's most everything necessary to get started. this is distilled from my having visited and interpreted /Unixart/quickppp.html for the most part along with other documents on Tony's site and of course the sco on-line docs -- Brian~
More Articles by Tony Lawrence
Have you tried Searching this site?
Unix/Linux/Mac OS X support by phone, email or on-site: Support Rates
This is a Unix/Linux resource website. It contains technical articles about Unix, Linux and general computing related subjects, opinion, news, help files, how-to's, tutorials and more. We appreciate comments and article submissions.
Many of the products and books I review are things I purchased for my own use. Some were given to me specifically for the purpose of reviewing them. I resell or can earn commissions from the sale of some of these items. Links within these pages may be affiliate links that pay me for referring you to them. That's mostly insignificant amounts of money; whenever it is not I have made my relationship plain. I also may own stock in companies mentioned here. If you have any question, please do feel free to contact me.
Specific links that take you to pages that allow you to purchase the item I reviewed are very likely to pay me a commission. Many of the books I review were given to me by the publishers specifically for the purpose of writing a review. These gifts and referral fees do not affect my opinions; I often give bad reviews anyway.
We use Google third-party advertising companies to serve ads when you visit our website. These companies may use information (not including your name, address, email address, or telephone number) about your visits to this and other websites in order to provide advertisements about goods and services of interest to you. If you would like more information about this practice and to know your choices about not having this information used by these companies, click here.
Click here to add your comments
Don't miss responses! Subscribe to Comments by RSS or by Email
Click here to add your comments
If you want a picture to show with your comment, go get a Gravatar