kseshadr@quasar.intel.com (02/22/91)
I'm trying to get a uucp connection working, using a Microvax II GPX running Ultrix 4.1 and a Telebit Trailblazer Plus modem. My uucico connects to the other site with no problems, goes through the entire exchange but then has problems closing the connection. It seems to take a few minutes for uucp to actually figure out that the connection is no longer up. When I start up uucico after about a minute, it still attempts to send an OO to the remote system. I suspect that there may be a problem with the DTR, DSR, DCD asserts from the Telebit. I'm interested in seeing what people are using for S51, S52, S53, S54 and S58 values (and any others that may have some bearing on this problem..). The first uucico also gives me a "fopen of /usr/spool/uucp/LCK.LSTAT failed" error message just before sending the OO, and attempting to close the ACU. My field service guy from Digital has suggested that it may be a problem with trying to use the tty device as a shared line, and that some terminal controllers may not be capable of supporting this feature. I'd appreciate any inputs... Thanks, Kishore Seshadri kseshadr@mipos3.intel.com ----------------------------------------------------------------------------- Kishore Seshadri,(speaking for myself) <kseshadr@mipos3.intel.com> Intel Corporation <..!intelca!mipos3!kseshadr> Plus ca change, plus c'est la meme chose.
das@trac2000.ueci.com (David Snyder) (02/23/91)
In article <2644@inews.intel.com>, kseshadr@quasar.intel.com writes: > I'm trying to get a uucp connection working, using a Microvax II GPX running > Ultrix 4.1 and a Telebit Trailblazer Plus modem. lot 'o stuff deleted. > I'm interested in seeing what people are using for > S51, S52, S53, S54 and S58 values (and any others that may have some bearing > on this problem..). Here's ours... E1 F1 M1 Q6 T V1 W0 X3 Y0 &P0 &T4 Version GA2.00 S00=001 S01=000 S02=043 S03=013 S04=010 S05=008 S06=002 S07=040 S08=002 S09=006 S10=007 S11:070 S12=050 S18=000 S25=005 S26=000 S38=000 S41=000 S45=000 S47=004 S48=000 S49=000 S50=000 S51:254 S52:002 S54:003 S55=000 S56=017 S57=019 S58:002 S59=000 S60=000 S61=150 S62=003 S63=001 S64=000 S65=000 S66=000 S67=000 S68=255 S69=000 S90=000 S91=000 S92=000 S93=008 S94=001 S95=000 S96=001 S100=000 S101=000 S102=000 S104=000 S105=001 S110:001 S111:030 S112=001 S121=000 S130=002 S131:001 S150=000 S151=004 S152=001 S153=001 S154=000 S155=000 S160=010 S161=020 S162=002 S163=003 S164=007 S255=000 DAS -- David A. Snyder @ UE&C - Catalytic in Philadelphia, PA UUCP: ..!uunet!trac2000!das INTERNET: das@trac2000.ueci.com
time@tbomb (02/23/91)
In article <2644@inews.intel.com>, kseshadr@quasar.intel.com writes: > I'm interested in seeing what people are using for > S51, S52, S53, S54 and S58 values (and any others that may have some bearing > on this problem..). I always use no flow control, since I do not use hardware flow control. This is register 58. Here are my settings: E1 F1 M1 Q0 T V1 W0 X3 Y0 &P0 &T4 Version GE7.00-T2500SA S00=001 S01=000 S02=043 S03=013 S04=010 S05=008 S06=002 S07=040 S08=002 S09=006 S10=007 S11:050 S12=050 S18=000 S25=005 S26=000 S38=000 S41=000 S45=000 S47=004 S48=000 S49=000 S50=000 S51:254 S52:002 S54:003 S55=000 S56=017 S57=019 S58:000 S59=000 S61:090 S62=003 S63=001 S64=000 S65=000 S66=000 S67=000 S68=255 S69=000 S90=000 S91=000 S92:001 S93=008 S94=001 S95:002 S96=001 S97:001 S98:000 S100=000 S101=000 S102=000 S104=000 S105=001 S106:001 S107:000 S110:000 S111:030 S112=001 S121=000 S130:003 S131:001 S150=000 S151:000 S152:000 S153:000 S154=000 S155=000 S157=000 S158=000 S160:000 S161:000 S162:000 S163:000 S164:000 S169=000 S255=000 ------------------------------------------------------------- Tim Endres | time@ice.com ICE Engineering | uupsi!ice.com!time 8840 Main Street | Voice FAX Whitmore Lake MI. 48189 | (313) 449 8288 (313) 449 9208