LORD 5.02 FP for Windows - Legend of the Red Dragon, Free Pascal port
=====================================================================

The Windows (64-bit) build of LORD FP: a DOOR32.SYS door for Windows BBSes
such as Synchronet and Mystic.  It is the same game as the Linux version -
a line by line port of Deuce's lord.js - and uses the same game files, so
SYSOP.TXT covers the options, the forest event scripts and the set-up
program.  This file covers what is different on Windows.

Other Places runs DOS LORD 4.06 In-Game Modules (IGMs) in DOSBox-X, which is
included (the dosbox folder).

Needs 64-bit Windows 10, 11 or Server 2016 or later.


FILES
-----
  lord.exe      the game
  lordcfg.exe   the set-up program (like LORD's LORDCFG.EXE)
  dosbox\       DOSBox-X, for DOS IGMs, and LSFOSSIL.COM, a FOSSIL driver
                for IGMs that need one
  DOSPROMPT.BAT a DOS prompt in the game folder, for setting up IGMs
  SYSOP.TXT     options, LADY scripts, the set-up program, IGM details
  The rest is as SYSOP.TXT lists: the .lrd screens, LORDTXT.DAT, LORD.LDY,
  and LORD 4.06's own files.


INSTALLING
----------
1. Unzip into a folder of its own, e.g. C:\sbbs\xtrn\lordfp or
   C:\mystic\doors\lordfp.  Keep the dosbox folder next to lord.exe.

2. Run lordcfg.exe once.  It makes lord.ini; look through 1 (Game
   options) while you are there.

3. Try it on this PC: open a Command Prompt in the folder and type

     lord -l -u YourName

   (or  lord 0  to play as node 0, as with LORD 4.06).

Windows may warn that lord.exe is from an unknown publisher the first
time: the programs are not signed.  The BBS does the networking, so no
firewall rule is needed.


RUNNING
-------
  lord -d <DOOR32.SYS, or the folder it is in> [-r rows] [-p gamedir]

  A Windows BBS hands a door the caller's connection in DOOR32.SYS:
  line 1 is the connection type (2 = telnet) and line 2 its socket
  handle.  lord.exe talks to the caller through that socket and leaves
  it open when the player quits, so they go back to the BBS.

  -d  DOOR32.SYS, or the node folder holding it (door32.sys in any case
      is found).  Other drop files are read too, but on Windows only
      DOOR32.SYS carries the connection: use DOOR32.SYS.
  -r  the caller's screen rows (DOOR32.SYS has none; default 24).
  -p  the game folder; default is the folder lord.exe is in.
  -i  show what was read from the drop file and stop.

  Connection type 1 (a serial port) is not supported; 0 (local) plays
  in the console window.


SYNCHRONET (Windows)
--------------------
  SCFG > External Programs > Online Programs (Doors) > a section >
  add a program:

    Name                        LORD - Legend of the Red Dragon
    Internal Code               LORDFP
    Start-up Directory          C:\sbbs\xtrn\lordfp
    Command Line                C:\sbbs\xtrn\lordfp\lord.exe -d %n -r %r
    Multiple Concurrent Users   Yes
    Native Executable           Yes
    I/O Method                  Socket
    Use Shell or New Context    No
    BBS Drop File Type          Mystic  DOOR32.SYS
    Place Drop File In          Node Directory

  %n is the node folder (where DOOR32.SYS goes) and %r the caller's
  screen rows.  With I/O Method Socket, Synchronet passes the caller's
  socket in DOOR32.SYS.  (Older Synchronet versions have "Intercept I/O"
  instead: set it to No.)


MYSTIC (Windows)
----------------
  In the menu editor, add a menu item to the doors menu:

    Command   D3  (Exec DOOR32 door)
    Data      C:\mystic\doors\lordfp\lord.exe -d %P

  %P is the node's temp folder, where Mystic writes door32.sys.  Give
  the item a hot key and menu text as for your other doors.


OTHER BBSES
-----------
  Any Windows BBS that can run a DOOR32.SYS door: run lord.exe with -d
  and the path of the DOOR32.SYS it writes (or the folder).


OTHER PLACES (DOS LORD IGMs)
----------------------------
  As SYSOP.TXT describes, with DOSBox-X in place of dosemu: for each visit
  lord.exe starts dosbox\dosbox-x.exe with no window, with

    C:\LORD   the game folder (as LORD sits on a DOS BBS)
    D:        the node folder (DOOR.SYS)
    COM1      connected to the caller, LSFOSSIL.COM loaded for it

  and runs the IGM's command from 3RDPARTY.DAT.  If the player hangs up,
  the IGM sees the carrier drop and has 15 seconds to save and leave.

  Setting up an IGM:

  1. Unzip it into a folder of its own in the game folder, e.g. VAULT.
  2. Run lordcfg.exe, choose O (Other Places), then D (DOS prompt).  A
     DOSBox-X window opens at C:\LORD, the game folder.  (Double-clicking
     DOSPROMPT.BAT opens the same prompt.)
  3. Run the IGM's set-up program there, e.g.  CD VAULT  then  VAULTCFG.
     Give it C:\LORD\ as LORD's folder.  Many IGMs offer to add
     themselves to Other Places (3RDPARTY.DAT); let them.  Type EXIT to
     close the window and go back to lordcfg, which shows the list again.
  4. If it didn't add itself: in Other Places press A and add it, with
     the DOS command line as the IGM's docs give it (* = node number),
     e.g.  C:\LORD\VAULT\VAULT.EXE * C:\LORD\ 1

  [IGM] in lord.ini (or lordcfg > 1):
    DOSBoxCommand  how DOSBox-X is started: %x DOSBox-X, %c the
                   DOSBOX.CONF made for each run, %n the node.  Take out
                   -silent to watch an IGM in a window (for testing).
    DOSBoxCycles   DOSBox-X's speed for IGMs: fixed 10000 (a fast 386),
                   auto, or max
    DOSBoxFossil   1 = load LSFOSSIL.COM first (most IGMs want a FOSSIL)

  MAINT.BAT runs in DOSBox-X once a day, as SYSOP.TXT describes.


DOSBox-X
--------
  The dosbox folder has DOSBox-X (GPL); SOURCE.TXT in it says where its
  source is.