thad@cup.portal.com (Thad P Floryan) (06/11/89)
In light of the recent interest about 19200 baud for the serial port(s) on the UNIXPC, I'd like to pass along another tip that I'd almost forgotten: AFTER you change the two occurrences of ``B19200'' to be ``EXTA'' in the /etc/gettydefs for the 19200 baud entry, you can alter: /usr/lib/ua/RS232a.form by adding ``Name=19200'' to the end of the list in the "Speed" menu data and then "19200" baud will appear in all the menus for the "RS232 Setup" and for the "RS232 Expansion Setup" in the "Hardware Setup" menu in the "Office of install." If you're still using the UA, the above will make life more pleasant if you're reluctant to manually alter /etc/inittab (which only seems to get modified by using the "RS232 [Expansion] Setup" or by running ``phtoggle''). Reiterating another note from the past: up to and including 3.51, the driver for tty000 will NOT permit a BREAK to be input (such as would be used for a linked baud selection in /etc/gettydefs) but a BREAK can be sent out from the UNIXPC. Allegedly the 3.51a fixdisk corrects this problem (of a BREAK not being recognized on input to tty000; the EIA/COMBO board drivers do NOT have the problem). Question: is the 3.51a fixdisk still available? If so, who does one call? If the disk isn't available anymore, can someone send me a copy (in exchange for postage, blank disk, etc) and I'll make copies for distribution here in Silicon Valley. Were the 3.51b or 3.51c (or ???) fixdisks ever released? Thad Floryan [ thad@cup.portal.com (OR) ..!sun!portal!cup.portal.com!thad ]
nichiren@glyph.UUCP (Andy Heffernan) (06/13/89)
In article <19373@cup.portal.com> thad@cup.portal.com (Thad P Floryan) writes: [ blah blah ] >If you're still using the UA, the above will make life more pleasant if you're >reluctant to manually alter /etc/inittab (which only seems to get modified >by using the "RS232 [Expansion] Setup" or by running ``phtoggle''). I've been wondering about this. My /etc/inittab gets reset everytime I reboot, no matter how I change it. (Of course, every once in a while syscon gets linked to tty000, but that's another mystery.) This annoys me quite a bit, since the way I have things set up, the machine hangs a getty on my phone line which I don't want. (1 phone line into port 2, calls out, only.) Who keeps changing the damn thing, and why? Why? Why? Why? Why? (hysterics) This all makes me ask, How much of this magic stuff (smgr, what's a smgr?) can I kill off, given that I don't care about the windows and mice; I don't care about making notes of all my voluminous phone calls (they're ALL wrong numbers), but I do want to call out via UUCP; I don't need to be shown if the machine is "Working" or not (I can hear it grumbling to itself when it is); I'd love to grab those extra 2-3 lines on the screen; etc. How much? How much? How much? (hysterics) *snif* *snif* ...I just want a normal machine...., boo hoo hoo hoo... >Thad Floryan [ thad@cup.portal.com (OR) ..!sun!portal!cup.portal.com!thad ] -- ------------------------------------------------------------------------- Andy Heffernan uunet!glyph!nichiren [1222 - 1282] -------------------------------------------------------------------------
thad@cup.portal.com (Thad P Floryan) (06/13/89)
Here I am, answering my own questions again! :-) To begin: I'm also as quick to compliment as I am to criticize. I called the AT&T Hotline today (Monday, June 12) and after a very pleasant conversation with JoAnn concerning the problem with ``BREAK'' not being recognized by tty000 under 3.51, she gave me a "ticket number" and informed me to expect a return call momentarily. Talk about efficiency! They already had my phone number, etc. from the warranty cards, and the person who called back within MINUTES is *ALSO* a UNIXPC owner/user. Apparently there isn't a 3.51b "fixdisk", and the 3.51a "fixdisk" has been ordered for me and shipped from King of Prussia. (And I didn't even have to tell them I own some AT&T stock! :-) I'll make copies of the fixdisk available to any attending member of the AT&T Computer Users' Group meetings who also attends the UNIXPC SIG; at the next meeting (June 21) I'll be demo'ing remote login setup (for the UNIXPC) and "all you wanted to know about uucp." Time permitting: HD upgrades, bad-block sparing, and whatever else comes up will also be discussed. Thad Floryan [ thad@cup.portal.com (OR) ..!sun!portal!cup.portal.com!thad ]