JD> Jim suggested using it in LOGO.MEC, which I did, and is works just
 JD> fine.  But giving this more thought I think combining both your
 JD> suggestions would be the answer.  I suspect the TOOSLO%k.BBS file
 JD> gets displayed after the user logs in which is one of the drawbacks
 JD> of using the [iftask] token in the LOGO.MEC.  You don't really know
 JD> who it is that is continually logging in at 300 baud. :-)
 JB> If you would like to know who is logging in, move the 
 JB> [iftask] stuff into Welcome.mec. That one is displayed 
 JB> after the user has logged in.
I thought of that but it occurred to me that the WELCOME.MEC file doesn't get 
displayed to users unless they've logged in at least 10 times.  I've gotta go 
throught the session limits and session section of my MAX.CTL again, but it 
just may be that the TOOSLOW.MEC doesn't get automatically displayed by 
Maximus anyways (that is unless it's linked from somewhere else).  I thought 
this would be odd as well given there's an entry in MAX.CTL which points to 
it.
I set the minimum login baud to 1200, fired up my old 386 workhorse with the 
old 14.4 Courier dual-standard full lenth modem and gave the old AT&N1 
command to dial out at 300 baud just for the heck of it.
I successfully logged in at 300 baud and no TOOSLOW.BBS was displayed.  I 
know I must have made a mistake somewhere, but I'll get to the bottom of it.
It's the little things in this hobby that make it interesting.
--- Maximus 3.01
---------------