This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
doorparty [2023/07/22 21:06] – created massacre | doorparty [2023/11/18 15:55] (current) – massacre | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== DoorParty ====== | ====== DoorParty ====== | ||
- | 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:// | + | DoorParty is an InterBBS Game Server using a modified version of Rick Parrish of R&M Software's Telnet Door which automatically logs the user into their Server and directly into DoorParty |
- | How to install | + | How to install |
- | 1. Extract BBSlink | + | Before installing DoorParty, make sure you register for an account. Here is the information from DoorParty on how to join from their website: |
+ | |||
+ | * 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 | ||
- | 2. Edit your BBSLINK.BAT file, and fill in the 3 codes provided by the BBSLink admin. While you are editing this batch file, you will need to add a " | + | * You can find it here using the fTelnet app on the BBS website http://www.throwbackbbs.com/ |
- | | + | |
- | If you are running | + | |
- | 3. In your BBS software, 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 | + | * 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 '#' | ||
+ | |||
+ | 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 | ||
+ | |||
+ | * –>.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:// | ||
+ | |||
+ | 2. Create a folder: c: | ||
+ | * c: | ||
+ | * DoorParty.exe | ||
+ | * RMLib.dll | ||
+ | * <Your System Code> | ||
+ | * c: | ||
+ | * doorparty-connector.exe | ||
+ | * doorparty-connector.ini | ||
+ | |||
+ | 3. You will not have to edit ANY DoorParty files if you properly configured your DoorParty customized installer files. | ||
+ | |||
+ | 4. 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 | ||
| | ||
| | ||
Line 20: | Line 45: | ||
(*D) tells ProBoard to create a DOOR32.SYS drop file, and is filtered out. | (*D) tells ProBoard to create a DOOR32.SYS drop file, and is filtered out. | ||
(*U) tells ProBoard to use the user's handle. | (*U) tells ProBoard to use the user's handle. | ||
+ | | ||
+ | The batch file should already be named correctly in the zip file. | ||
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: | ||
- | So the following type-7 Command Line could be configured for this door in ProCfg: | + | c: |
- | c: | + | |
Note that for node 1, the above command line would be translated by the BBS as so: | Note that for node 1, the above command line would be translated by the BBS as so: | ||
- | | + | |
Note: the *D in this example is only used to tell ProBoard to create a DOOR32.SYS drop file. | Note: the *D in this example is only used to tell ProBoard to create a DOOR32.SYS drop file. | ||
Line 33: | Line 59: | ||
* 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. | * 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. | * 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. | ||
+ | |||
+ | ---- | ||
+ | Thank you to Mike Ehlert for his instructions in the NetFoss User Guide!! | ||
+ | [[https:// |