| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | V.34 test #4 |
RS> *IF* the double send has been seen between a PAIR OF RS> SPIRITS, and thats been by a reliable observer like Dave RS> Hatch who understands how to distinguish between double RS> sending and line errors, by pausing the sending system, PE> The reliable observer who couldn't even PE> remember he had seen it more than once? RS> Peoples recollection of what happened almost THREE RS> YEARS ago can indeed leave something to be desired. PE> It's a significant thing. Yes, but we KNOW peoples memorys are unreliable over that sort of time. Says nothing useful whatever about whether they can reliably analyse a config with a pair of Spirits which appear to be exhibiting double sending, to prove it really is double sending, by pausing, or that it happened on more than one occasion. AND it jogged his memory when his message was reread to him. No matter how furiously you and Trev try to sweep the evidence under the carpet, we DO have reliable evidence of double sending between a pair of Spirits and thats COMPELLING evidence that the Spirit does have a double send problem, COZ THERE AINT NO OTHER MODEM PRESENT. PE> And the wording of the claim says a hell of a lot too. Bullshit it does, particularly the first message reporting that observation is fine, clearly spelling out the use of pausing to establish it really was double sending. RS> Thats why it can be handy to keep the messages they wrote AT RS> THE TIME and when you do, its STILL the COMPELLING evidence RS> that the double send problem is in the Spirit, COZ THERE AINT RS> NO OTHER MODEM PRESENT EXCEPT A SPIRIT. It really is that basic. RS> No amount of your proclaiming on datascopes will change that. PE> YES Rod, *IF* that was what Dave Hatch really saw, Only a fool would dispute he did after those messages of his WRITTEN AT THE TIME are reread. No matter how furiously you try to sweep that evidence under the carpet, IT AINT GUNNA GO AWAY. PE> then YES, there is a fault in the Spirit. And thats ALL I ever said, that WHEN its seen with JUST a pair of Spirits, its COMPELLING evidence that the Spirit has a double send problem. No matter how furious you sweep, that evidence aint gunna go away. PE> A fault that occurs so rarely I've never seen it myself, despite doing PE> Spirit->Spirit calls for 2 years. Yes, there is indeed a rare bug. Thats just a comment on the circumstances that produces the timing that makes the Spirit exhibit its double send bug. Says nothing useful whatever about whether IT HAS ONE. Yes, we know damned well that a tiny change in the timing in the Binkley behind the Spirit will make it go away FOREVER too. STILL proves SWEET FUCK ALL about whether the Spirit has a problem tho. PE> So rare that it isn't even worth fixing. You dont know that, and its NOT true when a Maestro is receiving the file. PE> The Maestro bug is COMPLETELY different. PE> It is reproducible by anyone, happens every time. You dont KNOW that when a file is flowing from the Spirit to the Maestro, THAT YOU ARE SEEING A FAULT IN THE MAESTRO. In fact since the Maestro isnt even sending the fucking file, and the Binkley behind the Spirits timing eliminates it forever, ITS MOST FUCKING UNLIKELY. Particularly when the receiving modem in my case says its not asking for blocks to be sent twice. You are desperately clutching at straws Paul. I've binned the rest of this shit, if you dont have the mental horsepower to grasp the basic stuff above, there aint any point in trying to get the more complex stuff below thru you thick skull. @EOT: ---* Origin: afswlw rjfilepwq (3:711/934.2) SEEN-BY: 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™.