JD> I notice a "Logon Baud" statement in MAX.CTL which controls minimum
 JD> logon baud rates to Maximus.  What I'm wondering is how I can display
 JD> the TOOSLOW.BBS file differently for each node?
This is untested, so -you- get to test it.  
Change your "Uses TooSlow" statement to this:
Uses TooSlow    C:\Max\Misc\Tooslo%k
Now, assuming you have tasks one and two, create two "tooslow.mec" files,
called tooslo01 and tooslo02.  Mecca them.  (Note:  That's "zero one" and
"zero two", not capital "oh-1", etc..)
Maximus -should- now show tooslo01.bbs for node one, and so on.
(Note:  This also works for doing separate ECHOTOSS.LOG files for each node,
which can be a handy way to handle tossing on a multiline BBS.)
Now further, I don't see what is causing Max to hangup on "tooslow" nodes,
since it's not in the "tooslow.mec" file, so it must be internal.  For that
part, you're on your own.  Sorry.  (Scott?)
--gary
--- Maximus v3.01               
---------------