gm@trsvax (11/26/85)
If you have System III (Xenix 3.0), in /usr/lib/uucp there are several files and commands to aid in getting a non-RS modem to work with uucico and cu.s3 . The files are: dial - The default dialer program (linked to dialTRS) dialHAYES - dialer for the Hayes 300/1200/2400, etc. dialVADIC - dialer for Radcal-Vadic modems dialTRS - dialer for Radio-Shack modems (linked to dial) dial.c - source to the Hayes dialer, which should be easy to modify link_dial - a shell script to compile and link any new dialers you may write. So if you have a Hayes (or Hayes-clone) modem, just re-link dial to dialHAYES and change the L-devices entries to /dev/ttyxx rather than /dev/cuxx. One of the problems you may have been having is the fact that the default cu (/bin/cu) is actually the Version 7 cu. This does not support non-RS modems; however, cu.s3 (the system III cu) does use /usr/lib/uucp/dial to figure out what to tell the modems. The reason we distribute two cu's is the fact that the System III cu will grab whatever the first matching device in /usr/lib/uucp/L-devices and use that baud rate, reguardless what you told it on the command line. So when you re-link for another modem, you need to re-arrange L-devices so that the baud rate you will be using most often is at the top. [This information is provided by an individual and should not be assumed to come from Tandy Corp/Radio-Shack. Tandy has no obligation to support this information in any way. Because of it's high resolution, the Compact Disk may reveal limitations of the original master, except in Arkansas.] George Moore Tandy System Software (gm@trsvax.UUCP)
iv@trsvax (11/26/85)
/* Written 4:03 pm Nov 19, 1985 by isrnix.UU!hal in net.micro.trs- */
/* ---------- "Getting around the Tandy Device Dri" ---------- */
The kernel oriented device-drivers for ports A and B, the cul0 and 1,
even on the latest version of Xenix 3.0 for the 6000 or the upgraded 16b,
still expect you to be using Tandy/Radio Shack Modems, and if you are not,
they intend for it to be awkward as possible to get around.
[ . . . ] They have kept it almost
imposible for the beginning system users, and awkward for the rest of us.
My question, is why ?
Hal Fuquay
/* End of text from net.micro.trs- */
Now, to answer Hal's question, the reason Tandy did not offer support
for multiple modems is because the /dev/cua? driver was in the KERNEL,
and it is very hard to code a reasonably sized modem pseudo-driver
that handles more than 1 modem type. I know, because I wrote the
driver in question. Naturally, our merchandising folk wanted support
for our own modems, and so that's what I coded it for. To offer more
than one modem type would entail having the user relink the kernel,
and that was ruled out-of-the-question. (Can you imagine trying to
explain to a novice/first-time user how to relink the kernel? No
thank you!)
The solution to this problem, as you may have read in another note, is
to do the dialing externally as we did with our XENIX 3.0 release.
[This information was provided by an individual and is not nor should
be construed as being provided by Radio Shack or Tandy Corporation.
Radio Shack and/or Tandy Corporation have no obligation to support the
information provided. The author will, however, cheerfully accept
mail. This note will dial out in 5 seconds. Good luck, Hal.]
IV (aka John Elliott IV)
Tandy Systems Software; Fort Worth, TX
... {convex!ctvax,microsoft}!trsvax!iv
... cu-arpa.trsvax!iv@Cornell.ARPAperl@rdin.UUCP (Robert Perlberg) (12/08/85)
/* Written 4:03 pm Nov 19, 1985 by isrnix.UU!hal in net.micro.trs- */ /* ---------- "Getting around the Tandy Device Dri" ---------- */ [ . . . ] They have kept it almost imposible for the beginning system users, and awkward for the rest of us. My question, is why ? Hal Fuquay /* End of text from net.micro.trs- */ >for our own modems, and so that's what I coded it for. To offer more >than one modem type would entail having the user relink the kernel, >and that was ruled out-of-the-question. (Can you imagine trying to >explain to a novice/first-time user how to relink the kernel? No >thank you!) > > IV (aka John Elliott IV) > Tandy Systems Software; Fort Worth, TX Give me a break! Just because something is too difficult for a novice to use does not mean that it should not be included with a system. The real answer to Hal's question of 'Why?' is more than obvious to anyone who's had much experience with Tandy products -- they make it hard for you to use non-Tandy stuff so you're forced to buy Tandy junk. Plain and simple. Robert Perlberg Resource Dynamics Inc. New York {philabs|delftcc}!rdin!perl