PD> Definitely NOT.  In fact FLOATLOCK would have very limited usage with 
 AC> most
 PD> modems locked at a constant speed.

 PD> Floatlock keeps a locked speed for /REL (/ARQ) connections, but drops 
 AC> the rate
 PD> down to the line speed for a non MNP connection.

 AC> Thanks. :-) This all makes me glad I`m using Xenolink. :-)

FLOATLOCK was good for avoiding the delay inherent in /REL connections.
Because the BBS is running at a higher speed than the modem, then say aa
user wanted to abort a textfile being sent.  He sends back a CTRL-X or an S
or whatever character is needed to stop the text.  But the BBS itself has a
large chunk of that text in THE MODEM, and that is needed to be sent before
the abortion has any effect at the caller's screen.

These days, I'd say, most users are used to the inherent delay, but for
those of us only just upgrading to 9600 after being at 2400 for years,
FLOATLOCK would have been great.  It's just a pity that no BBS software
spawnable from TrapDoor ever took advantage of it....

The lovely thing about TrapDoor is configurability.  But that only seems to
confuse newbies:  What on earth is relevant and what doesn't really matter
at all?   TrapDoor is full of such keywords! :-)

  Mea Culpa,
 Peter Deane

--- Plutonic 2.15 #1