TIP: Click on subject to list as thread! ANSI
echo: locsysop
to: Rod Speed
from: Paul Edwards
date: 1993-11-06 07:37:22
subject: connects

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 a 
RS> trace.

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

 RS> In the case of the MNP4 you can look at the code which 
 RS> exhibits the fault and the new version which does not and 
 RS> see where the difference is in the code. And see that that 
 RS> change eliminates the problem. So you are absolutely sure, 
 RS> without using a trace, that the code change is responsible 
 RS> for the double sending.

There is no "new version" of MNP4 that works, the double sending
occurs with MNP4, about 5-10 minutes into a transmission.  CURRENTLY.  BFN.

Paul

---
* Origin: Ten Minute Limit (3:711/934)

SOURCE: echomail via fidonet.ozzmosis.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.