TIP: Click on subject to list as thread! ANSI
echo: locsysop
to: Jeff Green
from: Paul Edwards
date: 1996-04-20 18:12:12
subject: finally!

I finally figured out what the problem was with your modem and
the 3 seconds delay.  What happened was in the old bink, after
getting the "CONNECT" message, it goes and sets the baud rate,
and when it does that, it clears the input and output buffers
too, for good measure.

Well, your system was sending the x'f1' so fast, and there were
so many connect messages, that it arrived basically at the same 
time that the modem was putting out the "CONNECT" message, so the 
x'f1' was received by binkley at the same time as the connect 
message, and then proceeded to get flushed.

The new binkley doesn't flush the buffers when a connect is made.
Also, on the old bink, when using a short connect string, it
managed to get the connect string, flush the buffers and set the
baud rate, faster than you could send an x'f1' in, so you were
actually getting fast connects (you probably didn't notice them).
The same thing applies to Bob's connects.

The reason you had the problem but not the other guys?  You must
have been connecting faster, perhaps just at your end.  You were
using MNP4, they tended to use V42, so maybe that's what made the
difference.

Anyway, I've applied the fix to my old code, although I haven't
actually tested it.  And since I'm running with the new code,
you're getting fast connects now anyway.  BFN.  Paul.
@EOT:

---
* Origin: X (3:711/934.9)

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