zjat02@apctrc.trc.amoco.com (Jon A. Tankersley) (09/28/89)
Anybody noticed a degradation TB+ uucp spoofing as the OS release from Sun come out? My TB+ was working fine with 3.5, got itermittent errors with 4.0.1 and now fails quite often with 4.0.3 running 19200KB. Anybody else noticed this? Anybody found a way around it? Bodes grim for SunOS 4.1. Sun recommended using 9600 KB for the modem connection, and that did help somewhat, dropping back down to the intermittent level of 4.0.1. Errors seem to be protocol errors. Here is a trace: r short 2 want 3 rcount = 0 xcount = 0 Unfortunately, it happens somewhere deeep in the connection usually and I don't run with -x on my uucico. And the TB+ registers: E1 F1 M1 Q6 P V1 X1 Version BA3.01 S00=000 S01=000 S02=043 S03=010 S04=010 S05=008 S06=002 S07=040 S08=002 S09=006 S10=007 S11=050 S12=050 S45=255 S47=004 S48=000 S49=000 S50=255 S51=255 S52=002 S53=001 S54=003 S55=000 S56=017 S57=019 S58=000 S59=000 S60=000 S61=045 S62=003 S63=001 S64=000 S65=000 S66=000 S67=000 S68=255 S90=000 S91=000 S92=000 S95=000 S100=000 S101=000 S102=000 S104=000 S110=255 S111=030 S112=001 S121=000 N0: N1: N2: N3: N4: N5: N6: N7: N8: N9: -tank- -tank- #include <std/disclaimer.h> /* nobody knows the trouble I .... */ tank@apctrc.trc.amoco.com ..!uunet!apctrc!tank