DoorParty is an InterBBS Game Server using a modified version of Manning's Telnet Door which automatically logs the user into their Server and directly into the desired door using the BBS Sysops pre-assigned credentials. You can join for free at http://wiki.throwbackbbs.com/doku.php?id=start.

How to install DoorParty for ProBoard:

Before installing DoorPartry, make sure you register for an account. Here is the information from DoorParty on how to join:

• If you're looking to sign up to DoorParty, I've moved the application process to the BBS. I figured this gives it a more “authentic” feel to the spirit of DoorParty, and also simplifies the entire thing for everyone.

• You can find it here using the fTelnet app on the BBS website http://www.throwbackbbs.com/, or telnet://bbs.throwbackbbs.com with your favorite installed telnet terminal.

• Once you create an account on the BBS, the application form and info can be found on the main menu as: # % apply for DoorParty!

• Logon to Throwback and hit '#' from the main menu

Once you have been accepted to DoorParty, create and download your custom install package:

• In order to get your custom package, please log onto Throwback BBS (telnet://bbs.throwbackbbs.com) where you signed up. If you've been approved, you'll have a new menu option in the DoorParty application main menu that says:

• –>.P. Custom Connect Package

• You can download your custom package there.

1. Extract the DoorParty zip file (dpConnect_windows.zip) that you downloaded from Throwback at http://www.throwbackbbs.com/ to a directory/folder. (In this example we will assume C:\dpConnect_windows).

2. Create a folder: c:\doorparty and copy the following files from c:\dpConnect_windows into it:

• c:\dpConnect_windows\bbs_files\*.* (All files)
  • DoorParty.exe
  • RMLib.dll
  • <Your System Code>_DP.bat
• c:\dpConnect_windows\doorparty-connector\*.* (All files)
  • doorparty-connector.exe
  • doorparty-connector.ini

• You will not have to edit ANY DoorParty files if you properly configured your DoorParty customized installer files.

3. In ProCfg, configure your door to run a Command Line such as this example, which will run NFU.EXE and pass the path-only of your BBS Nodes dropfile directory, as well as the BBSLINK.BAT that NFU will execute along with its needed parameters. Say for example, that your BBS software is ProBoard and your BBS directory structure is

 C:\PB  (main BBS directory)
 C:\PB\NODE1   (Node 1 dropfile directory)
 C:\PB\NODE2   (Node 2 dropfile directory)

ProBoard BBS uses the following Door Command Line macros:

 (*#) is replaced by the Node number
 (*D) tells ProBoard to create a DOOR32.SYS drop file, and is filtered out. 
 (*U) tells ProBoard to use the user's handle. 

So the following type-7 Command Line could be configured for this door in ProCfg: So the following type-7 Command Line could be configured for this door in ProCfg:

 c:\netfoss\nfu.exe c:\pb\node*# "c:\doorparty\sil_dp.bat *# *U" *D

Note that for node 1, the above command line would be translated by the BBS as so:

 c:\pb\nfu.exe c:\pb\node1 "c:\doorparty\sil_dp.bat 1 Massacre c:\pb\node1\DOOR32.SYS"

Note: the *D in this example is only used to tell ProBoard to create a DOOR32.SYS drop file.

Avoid these common mistakes:

• Don't leave out the quote marks on the Command Line passed to NFU. NFU requires two parameters (1: The dropfile path to the door.sys, 2: the full command line to execute), and this second parameter must be in quotes if it contains its own set of parameters.
• Do not include the name of DOOR32.SYS in parameter 1, just the path where it is located NFU will read the DOOR.SYS dropfile here, and will create the DOOR32.SYS dropfile in the same directory before executing the Command Line in parameter 2.
• DoorParty requires NOT ONLY the path to a DOOR32.SYS file, it also requires the DOOR32.SYS filename to be included in the node path.