Hi, Mike-

 MT> You're probably right, because I backed them out when 
 MT> they broke other utils. Docs claims to support them, 
 MT> but offers them to the users as numbered areas inst ead 
 MT> of text. I did keep longer_than_9_char_full_tags, and 
 MT> they are offered by number in the door.

I did some more research in the docs and mulled over previous conversations
in here.  To the best of my knowledge, yes, it's the way I have the message
areas set up.  However, due to the extremely low number of users I have
(less than 20), I doubt I'm going to go through and change four networks'
worth of areas for a couple of users.  I know Blue Wave is nice and its
features are good, but since my BBS is mainly used as a "backup"
board by a majority of my users, I think I'm just going to pass on setting
up the door.

Perhaps if I had more users that depended on it, I'd do so.  That was one
nice feature of the Ezycom BBS software that I was running at one time-it
could automatically generate BW packets without the door.

I've had this setup running for so long that I've memorized all of the
message bases; it's easier for me to rememeber FIDO.Bluewave than it is
message area 179 or some such.

But, like I said, if I got more active users that wanted BW, I'd set it up.
 From the discussions I've had with my users, they seem content with
Maximus's QWK setup.  What really drives me nuts about it is that instead
of using the echotag, Maximus uses a shortened (basically chopped) version
of the area description.

Later,
Sean


--- Maximus/2 3.01