wolfer@ihuxy.ATT.COM (Wolfson) (09/08/88)
Recently, I posted a problem I was having with the cu command failing. Since then, I have received many suggestions on how to solve the problem. The problem has been solved, and thanks to everyone who provided help. I tried virtually every suggestion, or combination, thereof, and here is what finally worked: 1) Set up through Hardware Preferences window to use line 1 for voice and line 2 for data. Then, connected the phone jack to line 2, and left line 1 disconnected. Previously, I had used only line 1 for data, and line 2 for nothing, and had the jack connected to line 1 since I don't have a telephone connected to the Unix PC. 2) Logged on, entered unix, and typed: cu -d -s 1200 -l /dev/ph1 phone# The -d was for just in case it failed, but it worked fine. I concluded that you can't use cu without both lines "connected" to something in "Hardware Preferences", but you CAN use the AT&T Phone Manager. "Yes, I DID first try to connect the jack to line 2", change the Hardware Pref. so that according to the computer, I had data coming into line 2, and nothing in line 1, but the system wouldn't let me do this. It gave me some sort of error message saying that to use line 2 you have to have something connected to line 1 also. What, exactly does this mean? Does cu always try to go through line 2 no matter what? Why do you have to have something connected to line 1 (at least in the preferences, to fool the computer) in order to use line 2 ? Interesting... In case anyone is interested: 20M HD 1 M RAM 3.5 software. -------------------------------------------------------------------- Paul Wolfson "They float. Everything down here floats... att!ihuxy!wolfer and you'll float, too..."
thad@cup.portal.com (09/17/88)
I've been using ph0 (line 1) for DATA only, and discovered that what one MUST do is assure that it's setup for DATA. Look at the top of your screen, and if the display shows [VOICE:1] you must either run phtoggle or go to the CALL SCREEN and alter the setting there. Annoying, to say the least. Am going to put phtoggle in /etc/rc and see if this solves the problem. While on this subject, has anyone locate the UNIX-PC docs for the L.sys file? Been using the O'Reilly books (Managing/Using UUCP/Usenet) and, though very good, some of the stuff doesn't seem to work on the UNIX-PC: For example (in L.sys) foo Wk2310-0600 ph0 1200 ... foo Sa0000-2359 ph0 1200 ... foo Su0000-1600 ph0 1200 ... foo Su2310-2359 ph0 1200 ... bar Wk2310-0600 tty000 2400 ... bar Sa0000-2359 tty000 2400 ... bar Su0000-1600 tty000 2400 ... bar Su2310-2359 tty000 2400 ... For mail to foo, the time restrictions are obeyed. For mail to bar, it ALWAYS states "WRONG TIME TO CALL (bar)" in the /usr/spool/uucp/LOGFILE even at 3AM on a Saturday. Similarly, have attempted to setup usage of an external modem to call THE STORE at 2400 baud (since 1200 is too expensive); can never get thru using the latest store disk (on tty000; but ph0 works fine). Attempted debugging using cu -l /dev/tty000 -d 201-957-4646 shows connection being made, but no success using the STORE program from the UA. Has anyone connected to THE STORE using OTHER than the OBM? Thad Floryan [thad@cup.portal.com (OR) ...!sun!portal!cup.portal.com!thad]
thad@cup.portal.com (09/20/88)
Uh oh. Then those "loose pages" done did become lost (re: 3.51 docs for L.sys and friends). I *KNOW* I saw the L.sys format back in December (and, yes, I've bought TWO copies of the 3.51 software and development set). I've 6 linear feet of AT&T UNIX PC docs here, and there isn't a decent index to anything. L.sys doesn't show in any of the permuted indices either. Oh for on-line (e.g. machine readable) docs that could be grep'd. I'll keep looking. Thanks for confirming the docs DO exist; I never throw anything out, so they must be here. Thad Floryan [thad@cup.portal.com (OR) ...!sun!portal!cup.portal.com!thad]