PE> Or the same bug that is in Rockwell's code, occasionally 
PE> occurs in the Spirit too.

 RS> Thats most unlikely because the only time it could be a bug 
 RS> in the Rockwell code is if it actually requests each block 
 RS> twice in error. And it would then be showing the RE error 
 RS> indicator, showing its requesting retransmissions. It 
 RS> doesnt.

The bug in the Rockwell code occurs because the way the bug works is that
it asks for the resend without make RE flash.  Don't tell me a bug like
this couldn't occur, any bug could occur.  I agree it's more likely to be
Digicom, but there is no way you can say it is conclusive.  

PE> It's not conclusive until you have a trace.  Very likely, 
PE> but not conclusive.

 RS> I cant see that when the receiving Rockwell system doesnt 
 RS> think its seeing errors. It really is conclusive that its 
 RS> seen between a pair of Spirits.

You mean your Rockwell modem doesn't report that it is asking for a resend,
yet another bug in your crappy Rockwell code.  Until someone does a trace,
and see who is REALLY violating protocol, you can't conclusively point the
finger.  Sure I'd give you good odds that it isn't the Rockwell, but how
about this.  Would you be willing to bet me $1 million (against my 1c) that
Rockwell is in no way to blame for this problem (ie not violating protocol
AT ALL) so there is nothing for Rockwell to fix?  Conclusive?  No!  Highly
probable?  Most certainly!

PE> The problem happens with MNP4 too, just not so frequently.  
PE> No-one can be sure of just what's going on until there's a 
PE> trace.

 RS> Even thats not true. With the MNP4 bug, you can look at the 
 RS> code and see how it can arise and fix the bug without doing 
 RS> a trace.

What are you talking about Rod?  If you can do that with MNP4 you can do it
with V42 as well.  BFN.
Paul

---