GG> Change your "Uses TooSlow" statement to this:
 GG> Uses TooSlow    C:\Max\Misc\Tooslo%k
I thought of that, but the display of TOOSLOW.BBS is controlled by Min Logon 
Baud which is not task specific.  I think Jim Brown had the right answer, 
which is to use the [iftask] token.
Jim suggested using it in LOGO.MEC, which I did, and is works just fine.  But 
giving this more thought I think combining both your suggestions would be the 
answer.  I suspect the TOOSLO%k.BBS file gets displayed after the user logs 
in which is one of the drawbacks of using the [iftask] token in the LOGO.MEC. 
 You don't really know who it is that is continually logging in at 300 baud. 
:-)
 GG> Now further, I don't see what is causing Max to hangup on "tooslow" 
nodes,
 GG> since it's not in the "tooslow.mec" file, so it must be 
 GG> internal.  
Actually, neither did I, so I put an [enter] token at the bottom of the 
TOOSLOW.MEC file so the user would have time to jot down the nodes which 
allow callers at lower speeds followed by a [hangup].
The other thing I'd be curious about is when the TOOSLOW.MEC file would be 
displayed.  As I mentioned above, I'm assuming it's after the user logs in.  
Easy enough to test.
Thanks.
--- Maximus 3.01
---------------