clear@cavebbs.gen.nz (Charlie Lear) (04/24/91)
System: 3B2/400, 2 x PORTS cards. I've got a Microcom QX/3296EH on contty at 9600, dialout only. Works fine. I've got three Netcomm Datalock 1234SA 2400 and one Super 5 V32 across two PORTS cards. All are used for dialin. One of the 2400s is used to dial out for Fido polling. All work fine. My troubles start with one site requiring me to poll them using uucp at 2400bps. I can't use the Microcom; as soon as the 3B2 talks to it at 2400 it locks at that speed and requires a specific command to reset it back to 9600bps. (That sucks; but that is a side issue.) I tried using the existing modem dialling out on tty12. While the Fido program has no hassles, uucp just hangs. Uutry aborts as follows: _Request (TRUE), _Switch (TRUE), _CallBack (FALSE), _MyName (), _Commands rmail _Commands rnews chdir(/usr/spool/uucp/wcccomp) conn(wcccomp) Device Type Direct wanted mlock tty12 succeeded timed out generic open timeout set interface UNIX getto ret -1 Call Failed: CAN'T ACCESS DEVICE exit code 101 Conversation Complete: Status FAILED OK, it didn't like the way the modem was set up. I tried a different (spare) modem on tty14. Same thing. I tried two more spare modems. Same thing. I pulled the plug from the Microcom, set contty to 2400bps, and tried through contty. Same thing. I dumped all the registers and settings of the Microcom and compared it with the settings of the "spare" modems. All the same. I tried Kermit. Kermit> set line /dev/tty14 [hang until ctrl-\] /dev/tty14: Interrupted System Call In desperation, I tried different combinations of RTS/CTS, DSR etc. Still exactly the same. Still the Microcom works fine on contty but nothing else. Did someone say RTFM? Well I've read TFM until my eyes grew out on stalks and started turning the pages by themselves. Someone, somewhere, must surely have had this problem before. I've already thrown one modem through the window. I'm debating whether to get the glass replaced or if I should throw the 3B2 out through it first. If nobody has any concrete solution I would very much appreciate any pointers on where to start looking. I won't waste bandwidth with entries in the Devices, Dialers, Systems, inittab and gettydefs files - if you think thats where the problem lies, let me know and I'll email what I've got. TIA One Very Frazzled And Pissed Off Bear -- -------------------------------------------------------------------------- Charlie "The Bear" Lear | clear@cavebbs.gen.nz | Kawasaki Z750GT DoD#0221 The Cave MegaBBS +64 4 642260 V32 | PO Box 2009, Wellington, New Zealand --------------------------------------------------------------------------
les@chinet.chi.il.us (Leslie Mikesell) (04/25/91)
In article <1991Apr24.130046.896@cavebbs.gen.nz> clear@cavebbs.gen.nz (Charlie Lear) writes: >System: 3B2/400, 2 x PORTS cards. >I tried using the existing modem dialling out on tty12. While the Fido >program has no hassles, uucp just hangs. Uutry aborts as follows: [and other modem problems] If you have SysVr3.1 or later, be sure you are using the M,\M, and \m fields in your Devices and Dialers files. Without them, the dialing will fail unless your modem always holds the Carrier Detect lead up. Devices entry should look like: ACU tty12,M - 2400 hayes Dialers should be something like: hayes =,-, "" \M\pATE1\r\c OK\r \EATDT\T\r\c CONNECT \m\c "" Note that you can have many entries for the same device using different speeds, and the speed field can contain a letter to create a "class" to distinguish it from other entries of the same speed. With a little work you can create dummy Systems, Devices, and Dialers entries so that you can throw modem initialization commands out a port with a simple: echo ~. |cu dummyname and it will interlock properly with current connections. >Kermit> set line /dev/tty14 >[hang until ctrl-\] >/dev/tty14: Interrupted System Call With kermit you have to "set modem" before you "set line" or the same thing will happen. If kermit knows how to dial your modem it should have worked then. >Someone, somewhere, must surely have had this problem before. I've already >thrown one modem through the window. I'm debating whether to get the glass >replaced or if I should throw the 3B2 out through it first. If nobody has >any concrete solution I would very much appreciate any pointers on where >to start looking. I must say I'm glad I was getting paid for all the time it took me to get this stuff straightened out.... Maybe I should frame the AT&T "Closed Problem Report" dated 12/16/86 that explains that they where adding the sequences to solve a customer's (my) problem. I had specifically suggested tokens for the dialer scripts - they threw in the one for Devices. I don't know if the choice of the letter had anything to do with my initial, but at least my boss refers to it as the "Mikesell" fix. Les Mikesell les@chinet.chi.il.us
gulik@motcid.UUCP (Gregory Gulik) (05/01/91)
Can people please post followups?
I'm also interested in solving the same problem on my system.
-greg
--
--
Gregory A. Gulik
mcdchg!motcid!gulik || greg@gagme.chi.il.us
|| gulik@depaul.edujrh2@cbnewsm.att.com (jay.r.harbeston) (05/03/91)
if you have SVR3.2, use the \M and \m to temporarily disable modem control during dialout, otherwise you will always get a time out.