IJ> The author of Mystic was putting the blame on me for not bing able to
 IJ> get some
 IJ> doors running.  I'm not a programmer, but as an end user, I really see
 IJ> only 3
 IJ> BBSes still being supported, Mystic, Synchronet and WINS.  I'm not sue
 IJ> why
 IJ> Synchronet and WINS have a robust support for doors where as Mystic, in

Thats not what happened at all.  You couldn't get a door working, and instead
of coming here and posting your setup and asking for help, you posted a bunch
of bullshit messages insulting Mystic for not working (and you're still doing
it).

You still haven't posted your setup after MANY requests and any effort to
help you ends up with an incredibly ignorant response of "listen... its setup
right okay ive been doing this forever mystic doesnt work".  You're helpless.

Please clarify the "robust door support" Mystic is lacking. 
Mystic runs any
fossil or door32 door just the same as everything else does.  In fact, Mystic
CREATED the door32 stuff that WINS and Synchronet use.

Setting up a door in Windows is trivial on all three systems, and it takes a
close enough amount of time on each of them that its not even worth discussing.

The fact is that you came here with some pre-determined weird thing in your
brain about doors and Mystic, while refusing to take responsibility for your
own configuration.  It seems to me that no reason or logic or effort to help
you is going to change anything.

Maybe you should consider not using Mystic at all.

--- Mystic BBS v1.12 A34 (Windows/32)