Back in the bad old days, modems were pretty darn important. While there are still a lot of modems in use for dial-out (to connect to credit card processors etc.), dial-in modems on servers are vanishing quickly.
Three issues represented most of the modem configuration problems on SCO systems:
A lot of this is covered in detail at Configuring high speed modems.
SCO Modem control ports are designated with an upper case letter: /dev/tty1A is COM1 with modem control, and /dev/tty1a is COM1 for direct connections like terminals. People would sometimes screw up and have getty's running on both of these, which caused confusion and unhappy results.
See Answer light on modem- ats0, which discusses how this works.
Setting the modem and the inittab entry to a fixed DTE speed was another area of misunderstanding. Since the modem could talk to another modem at any speed the two agreed upon, people thought they needed cycling speeds for getty. Cycling speeds are supported, but are not necessary or desired. Finally, after a hangup, getty resets the line speed to the speed indicated by anything it finds in /usr/lib/uucp/Devices that matches the port it is on, so that speed needs to match.
This was in reference to:
Date: 16 Mar 1999 23:10:35 -0500
Message-ID: http://groups.google.com/groups?selm=36F06F00.6DD46F3E%40mindspring.com&output=gplain
The newsgroup article referenced suggests modem misconfiguration, specifically guessing
.. echo enabled on a non-modem controlled port or with CD wired up (or configured up in the modem) and login is engaged in a shouting match with the modem
Modem configuration, whether dial-in or dial-out, used to be a very big deal, but it got easier as modems matured. Out of the box, more modern modems would "just work" for dial-out, and all that was necessary for dial-in was to enable auto-answer, which you could usually do with external dip switches. DTE speeds were preset to 57600; all you needed to do was set inittab and /usr/lib/uucp/Devices to match.
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