The DOS version (LORDFP.ZIP) is a replacement LORD.EXE for LORD 4.06. It plays like LORD (it is a port of lord.js) and uses LORD 4.06's own files, so an existing LORD 4.06 game, its players and its In-Game Modules carry on. The zip is a complete game: it holds all of LORD 4.06's stock files as well, so nothing else is needed. On Synchronet for Linux it runs under dosemu2 for Synchronet, the same way LORD 4.06 does; it also runs on any real DOS BBS.

1. Make the game directory and unzip the zip into it:

   mkdir /sbbs/xtrn/lordf
   cd /sbbs/xtrn/lordf
   unzip /path/to/LORDFP.ZIP

2. Run the setup program under de:

   $ de
   C:\> E:
   E:\> CD \LORDF
   E:\LORDF> LORDCFG

   The first run writes LORD.INI with the default game options. Check them with 1, then set up each BBS node with N:

   • Drop file type: DOORSYS (matches GAP DOOR.SYS in SCFG)
   • Drop file location: D:\ (the node directory)
   • COM port: leave it to the drop file

This writes NODE1.DAT, NODE2.DAT and so on. Set up as many nodes as your BBS has.

1. Still at the DOS prompt, type START 0 to try the game on the local screen. Node 0 is the sysop's local node and needs no setup.
2. Add the door in SCFG:

^ Setting ^ Value ^

- Log in and play. START.BAT loops: when a player enters an IGM, LORD ends with errorlevel 254, START.BAT runs the IGM and then starts LORD again, which puts the player back where they were.

1. Unzip everything into an empty directory, e.g. C:\LORD.
2. Run LORDCFG.EXE. Check the game options (1), and set up each BBS node (N): the drop file type, where the BBS writes it, and the COM port.
3. Type START 0 to play on the local screen.
4. Have the BBS run START.BAT <node> from the LORD directory. Edit the top lines of START.BAT if the BBS doesn't change to it first.

LORD 4.06's own README.NOW, LORD.DOC and TROUBLE.TXT are included; where they say LORD.DAT or LORDCFG's (S)etup, this LORDCFG uses LORD.INI and N.

Skip this for a new install. If you already run LORD 4.06 and want to keep its players, LORD FP can replace its programs: it uses LORD 4.06's player file, mail, news, node files and IGM list as they are.

1. Back up the LORD directory.
2. Rename LORD.EXE to LORD406.EXE and LORDCFG.EXE to LORDC406.EXE.
3. From the zip, copy only LORD.EXE, LORDFP.STR, LORDCFG.EXE, LORDTXT.LRD, FLOOKS.TXT, MLOOKS.TXT and GSTART.LRD. Leave out the LORD 4.06 files: your game already has them, perhaps changed (START.BAT, 3RDPARTY.DAT, LORD.LDY …). Copy LORDTXT.DAT only if yours is missing.
4. Run LORDCFG and check the game options and the node setup (N).

Nothing else changes: START.BAT <node> runs the game as before, NODE<n>.DAT says where each node's drop file is, and 3RDPARTY.DAT lists the In-Game Modules. A LORD 4.06 player is picked up from PLAYER.DAT the first time they play. To go back to LORD 4.06, rename LORD406.EXE and LORDC406.EXE back.

Files the game creates are on Data files.

• Registration. LORD 4.06 checks its own registration code, so it is entered with LORDC406.EXE. Option G in LORDCFG explains how.
• Daily maintenance. After LORD's own daily maintenance, the first login of the day runs MAINT.BAT from the game directory, if there is one. IGMs put their upkeep there, for example The Pawn Shop's PSETUP /M. LORD 4.06 does the same.
• Memory. The game needs about 600K of conventional memory.
• The port. The COM port comes from the drop file, else COMPORT in NODE<n>.DAT. A FOSSIL driver is used when one is loaded, otherwise the UART directly.
• DOS commands first in the game options adds commands to the top of the IGM batch file (for example SHARE).