Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!stephsf!wengland
From: wengland@stephsf.stephsf.com (Bill England)
Newsgroups: comp.mail.uucp
Subject: BAD READ (expected 'C' got FAIL)
Message-ID: <370@stephsf.stephsf.com>
Date: 4 Oct 90 00:57:41 GMT
Organization: Stephen Software Systems, Inc., Tacoma WA
Lines: 42


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.COM