I run 80+ doors on my system at any given time, and I have found that many
SYSOPs have had "less than successful" attempts at running door programs.
Here are some tips in Q&A format that may help you along...
-----------------------------------------------------------------------------
Q: There are lots of good doors out there, but they're configured for BBS
   packages other than the one I'm running. I want to run them, but my BBS
   won't generate the right files that they need!

A: Find a Door Conversion Program! DoorMaster is *MY* favorite and will
   convert from (and to) more BBS formats then I care to list here!
   It comes with excellent instructions for set up, and will have you
   running virtually ANY DOOR you want in a matter of minutes!
-----------------------------------------------------------------------------
Q: When I run a door, it prompts me for the path to a run-time module...
   What's a run time module and where do I get it??

A: Odds are the author wrote the door using QuickBASIC. Read the set up docs
   carefully for a part that says you need BRUN##.EXE. (THE ## will be the
   version of QuickBASIC they used to write the door.) For example, *MY*
   doors require BRUN45.EXE in order to run, since I wrote them with Quick-
   BASIC V4.5. Most BBSes have a BRUN library for you to get the module
   you need.
-----------------------------------------------------------------------------
Q: I downloaded BRUN45.EXE, but the door hangs asking for the path until I
   type it in on my end. My callers are REALLY getting frusterated and it's
   costing my BBS "down time"! How do I fix this???

A: Either put a copy of the BRUN module in the same directory as the door, or
   in a directory accessed by your PATH command.
-----------------------------------------------------------------------------
Q: Okay, I have the BRUN module in the same directory and the door plays
   just fine, but when my caller exits the door, the BBS drops carrier on
   them!

A: You have a "standard" BRUN module. You need one that's "patched" for
   BBS use. Contact the SYSOP of the BBS you downloaded the door from,
   a SYSOP who's run many doors in the past, or the BBS that the door author
   calls frequently to ask for a patched module. Make sure you know which
   module (BRUN30, BRUN40, BRUN45, etc) you need!
-----------------------------------------------------------------------------
Q: Why don't you authors just build the module right into the program??

A: Well, actually, we COULD, but it would add 60-70K to the program size
   which would increase the time it takes to Up- and Download the door so
   fewer people would try it. Plus, if you already have a BRUN module,
   it's a waste of time to transfer another. SYSOPs generally enjoy the
   smaller sized QUALITY doors and get new BRUN modules as they come out.
-----------------------------------------------------------------------------
Q: How can I become a registered Beta Site?

A: Most authors who write quality doors are SWAMPED with requests for
   people to test their door. 80-90% of the time, the requester is looking
   for a free registration, more than wanting to help debug. Contact the
   author and mail him/her a description of your BBS (size, hours, max baud,
   any special equipment or software, BBS software being run, number of
   callers, type of computer, etc) and if they agree to let you beta a door,
   make sure to send them bug reports!
-----------------------------------------------------------------------------