Operation instructions for Dnd Door v4.9a r1.0:

  Installing Dnddoor
  ------------------
  Create a subdirectory on your disk and copy the Dnddoor .Zip files.

  Separate the compressed .Zip files with the PKware utility. Example:

     Cd \
     Md Dndoor50
     Copy Dndoor50.zip \Dndoor50
     Cd \Dndoor50
     Pkunzip *

  Run Dndcnvt.exe to create the data files,  or upgrade older data files
  to the new record lengths. Older edited data files will not be altered
  unless they need to be converted. Store your original data files first
  in case of a bad conversion run.  Read Readme.txt before  starting the
  conversion process.

  Operating Dnddoor
  -----------------
  To start the Dnddoor put the node number after the Dnddoor command:
  For example:

     Dnddoor.exe /1

  The  Dnddoor  reads  the RBBS door information  file from  the default
  directory  the  program was booted from.  Dnddoor  reads the door file
  content for  v17.4 named DORINFOx.DEF,  or for  v17.5 named DINFxx.DEF
  where x or xx is replaced with the node number. The door file contents
  are as follows:

     ADVENTURE RBBS   (The bbs name)
     JIM              (Sysop first name)
     OWNER            (Sysop last name)
     COM1:            (Comm port 1 - 8, 0 for workstation)
     9600 BAUD,N,8,1  (Baud rate, parity, data bits, stop bits)
      1               (Network type)
     JOHN             (User first name) (Or "SYSOP" and,
     DOE              (User last name)  (blank for local)
     MPLS, MN.        (City, state)
      2               (Graphics, 0=ASCII, 1=IBM characters, 2=ANSI)
      10              (Security level)
      60              (Minutes remaining)
     -1               (Fossil used)

  To start Dnddoor in local mode where  no .def files are required,  add
  the /L switch to the command line, for example:

     Dnddoor /L

  this causes  Dnddoor to ignore any door files,  and allows the Dnddoor
  to be distributed as a  single .exe program.  Although doing this will
  require  the sysop or  user to  create their own  data files  with the
  internal  !edit  feature of Dnddoor if they are not  also  distributed
  with Dnddoor.

  The Dnddoor  can  also connect to the modem carrier without the use of
  the door  file required for the  port number  and  modem baud  rate by
  using the /P and /B switches on the command line. The /P specifies the
  comm port to over-ride, and /B for the modem  baud rate to  over-ride.

  For example:

     Dnddoor /P:1 /B:9600

  will attempt  to connect to the modem at comm 1 (port 0), and at modem
  baud 9600. Doing this will allow modem access from the command line.

  Note:  Although multiple partitions of Dnd Door can be used,  the game
  itself is not multiplayer. i.e. you cannot fight other online players.

  Installing RBBS Batch Files
  ---------------------------
  The RBBS Menu5 door menu file must contain the programs to call in the
  file imbedded in uppercase surrounded by spaces.

  An example RBBS Menu5 file could be:

  +--------------------------------------------------------------------+
  |                                                                    |
  |                        rbbs door programs                          |
  |                                                                    |
  |  The adventure door: type DNDDOOR to begin..                       |
  |                                                                    |
  +--------------------------------------------------------------------+

  Then RBBS sysops must configure their BBS for doors,  edit the various
  batch files  (Rbbs.bat, Rbbstm.bat, Rctty.bat, etc.)  for  calling the
  Dnddoor.  The batch file to call Dnddoor from RBBS must  also copy the
  door information file to the Dnddoor directory.  Dnddoor  accepts node
  numbers in the range of 0 to 9, A to Z, or 10 to 99.

  An example Dnddoor.bat file for RBBS 17.4 contents:

     Cd\dndoor50
     Copy \rbbs\dorinfo%1.def
     Dnddoor /%1

  An example Dnddoor.bat file for RBBS 17.5 contents:

     Cd\dndoor50
     Copy \rbbs\dinf%1.def
     Dnddoor /%1

  Using Fossil
  ------------
  Place the  Fossil driver in Config.sys  upon bootup.  Before  starting
  Dnddoor,  activate  X00  with the XU utility:  Xu port:0:on  and  note
  the port number is one less than the comm number,  for example, comm 1
  is port 0.  Now when Dnddoor  starts and uses the Fossil routines, X00
  takes care of buffering the  transmit and receive characters  from the
  modem.

  Dnddoor.bat could also include the Fossil instructions:

     Cd\dndoor50
     Copy \rbbs\dorinfo%1.def
     Xu port:0:on
     Dnddoor /%1
     Xu port:0:off

  Problems With Dnddoor
  ---------------------
  At high speeds the Dnddoor drops characters received from the modem.

     The Dnddoor  has no interrupt handling,  therefore  the Dnddoor can
     only get the modem  input as fast as the program can poll the state
     of the modem.  Solution is  to  add a device driver which  gets and
     stores the modem i/o. Try installing BNU, or the X00 device driver,
     turn on Fossil activity for the Dnddoor port, then run Dnddoor.

  When  more than one  Dnddoor  is  loaded at the same time,  some files
  do not get updated between each Dnddoor partition.

     The Dnddoor  gets and reads records from the same data files at the
     same time. Solution is to load share.exe before starting any multi-
     partition software. Then  all partitions which   have Dnddoor  will
     share file records.  Dnddoor is not  actually a multiuser game even
     though multiple partitions can be run at the same time.

  The Dnddoor locks up during startup without any error message.

     Try  increasing  the files= statement in Config.sys and reboot. The
     Dnddoor needs 20  file handles per process.  Set the files= command
     in config.sys to 20 multiplied  by the  number of Dnddoor processes
     plus 4 files for Dos. Also try installing share.exe in Autoexec.bat
     or in  Config.sys with the install= command.  Although share.exe is
     usually  required in some  versions of Dos,  it  is  not needed  in
     windows 95 or 98 because windows loads sharing modules by default.

  The Dndoor quits with a message about requiring more Ems.

     Ems  is  expanded  memory  and  is needed  to  operate  the program
     correctly.  Normally all  that is required to start Ems is to place
     the device drivers for Ems in the Config.sys file in the root drive
     of C: such as:

        DEVICE=C:\DOS\HIMEM.SYS
        DEVICE=C:\DOS\EMM386.EXE AUTO RAM

     Additionally, the following should also be added:

        DOS=HIGH,UMB
        BUFFERS=20,8
        FILES=255
        LASTDRIVE=H
        FCBS=16
        STACKS=16,32

-end-
