ProBoard BBS Documentation

The Choice of Professionals

User Tools

Site Tools

Trace: • description • registration • sidebar
doormud

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision		Previous revision
doormud [2021/10/26 09:52] – created admindoormud [2023/11/18 15:55] (current) – massacre
Line 9: Line 9:
    (In this example we will assume C:\PB\DMUD)    (In this example we will assume C:\PB\DMUD)
  
-2. You must first run the door in local mode by executing "dmud32d.exe -l".  The game will +2. You must first run the door in local mode by executing "dmud32d.exe -l".  The game will   automatically finish its installation the first time you run it in local mode.
-   automatically finish its installation the first time you run it in local mode.+
  
 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 DMUDD32.EXE that NFU will execute along with its needed parameters. 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 DMUDD32.EXE that NFU will execute along with its needed parameters.
Line 27: Line 26:
    c:\netfoss\nfu.exe c:\pb\node1 "c:\pb\dmud\dmudd32.exe -N 1 -D c:\pb\node1"    c:\netfoss\nfu.exe c:\pb\node1 "c:\pb\dmud\dmudd32.exe -N 1 -D c:\pb\node1"
  
-If your BBS software automaticly sets the current directory as the node's dropfile directory before executing a door, you can shorten the size of the first parameter by replacing the path to the dropfile diretory shown above in parameter 1 with just a ".", telling NFU to use the current directory to read door.sys from and to create the door32.sys in, like so:+If your BBS software automatically sets the current directory as the node's dropfile directory before executing a door, you can shorten the size of the first parameter by replacing the path to the dropfile directory shown above in parameter 1 with just a ".", telling NFU to use the current directory to read door.sys from and to create the door32.sys in, like so:
    c:\netfoss\nfu.exe . "c:\pb\dmud\dmudd32.exe -N *# -D c:\pb\node*#" *D    c:\netfoss\nfu.exe . "c:\pb\dmud\dmudd32.exe -N *# -D c:\pb\node*#" *D
  
 You can also shorten the second parameter by replacing the path (only) to the DOOR32.SYS file (without the filename) with the "$" character like so: You can also shorten the second parameter by replacing the path (only) to the DOOR32.SYS file (without the filename) with the "$" character like so:
    c:\netfoss\nfu.exe . "c:\pb\dmud\dmudd32.exe -N *# -D $" *D    c:\netfoss\nfu.exe . "c:\pb\dmud\dmudd32.exe -N *# -D $" *D
 +
 +----
 +Thank you to Mike Ehlert for his instructions in the NetFoss User Guide!!
 +[[https://pcmicro.com/netfoss/]]
doormud.1635213177.txt.gz · Last modified: 2021/10/26 09:52 by admin

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki