wengland@stephsf.stephsf.com (Bill England) (10/04/90)
This is an intermitant problem. A log and debug uucico shows the following;
------
wengland uunet uunetN0500 (10/3-17:41:55,915,2) BAD READ (expected 'C' got FAIL)
wengland uunet uunetN0500 (10/3-17:41:55,915,2) FAILED (conversation complete tt
y1A 172)
----
Login Successful: System=uunet
msg-ROK
Rmtname uunet, Role MASTER, Ifn - 5, Loginuser - uucp
rmesg - 'P' got Ptfg
wmesg 'U'g
Proto started g
*** TOP *** - role=1, setline - X
Request: stephsf!D.steph744ddad --> uunet!D.steph744ddad (mmdf)
setline - S
wrktype - S
wmesg 'S' D.steph744ddad D.steph744ddad mmdf - D.steph744ddad 0666 mmdf
rmesg - 'S' got SY
PROCESS: msg - SY
SNDFILE:
-> 679 / 3.166 secs, 214 bytes/sec
rmesg - 'C' alarm 1
alarm 2
alarm 3
-----
This problem _never_ occures when using the Tbit in Pep mode.
It occures about 75% of the time when using the tbit at 2400 baud.
It only seems to be a problem with mail and not news.
It has never failed with 'S' or other types, only 'C'.
( Tbit echo suppresion is turned on. I don't believe it would
affect this problem though. )
Thanks for any suggestions/comments ...
Bill England
wengland@stephsf.COMcs00chs@unccvax.uncc.edu (charles spell) (10/23/90)
What is usually the cause of the 'BAD READ (expected 'C' got FAIL)'
message from BNU (g protocol forced)?
Thanx in advance...
uunet!mcnc!unccvax!cs00chs
--
.--------------------------. ... |On the border of your mind lies a place
|uunet!mcnc!unccvax!cs00chs| (") |where dreams and reality are one...I will
`--------------------------'-w-U-w-|take you there, for I am the subject...
\%\%\%\%\%\%\%\%\%\%\%\%\%\%\%\%\%\|the subject of your imagination. -Aldo Nova