Ŀ
  Installation      


        To install READROOM, simply copy all the files included in the
original distribution disk (or archive file) into a single directory.
The only files absolutely necessary to the operation of READROOM are:
        READROOM.EXE
        a configuration file
        and a READROOM.TOC file in same directory as the articles

        To install the sample files, please create a subdirectory to hold
the files in SAMPLE.ZIP.  Copy SAMPLE.ZIP into the subdirectory and then
unzip it and continue with installing the door as below.

        You will want to use a text editor to open READROOM.CNF or create
a new .CNF file.  The Configuration format is as follows:
D:\GAP
InfoMat BBS
0
0
STANDARD
0
0
0
00000.0000000000
Your Name Here
D:\HOLDING
WELCOME
EXIT
YELLOW WHITE GREEN
Publications that support the READROOM.TOC format
H:\READROOM\SAMPLE
YES
RESERVED

Each line will be explained below:

1)      This is the directory where READROOM will find the DOOR.SYS file
        created by your BBS software when a user opens a door. If you
        wish to have an environmental variable substituted in place of a
        fixed directory name, then use the following format:
                                %VARIABLE%
        where VARIABLE is the full drive\path to the DOOR.SYS file.

2)      This is the name of your BBS.

3)      This is the IRQ that should be used for the com port that you
        are using UNLESS you are using COM1 or COM2 in which case you
        will put a 0 here.

4)      This is the Base Port Address for the com port that you are
        using UNLESS you are using COM1 or COM2 in which case you will
        put a 0 here.

5)      This line is where you would indicate if you are running a
        STANDARD comm port or a DigiBoard. Your choices here are:
                    STANDARD    DIGIBOARD       INT14/EBIOS
        The Standard interface is the one that will normally be used. If
        an end user is using a DigiBoard then either the DigiBoard or
        Int14/EBIOS interface  may be  selected. Most sysops will use the
        Int14/EBIOS interface.  All  input/output  to  the  DigiBoard  is
        performed via  Interrupt 14  calls and a Device Driver (available
        from DigiBoard) handles the interface between the program and the
        board. The  DigiBoard interface  uses Direct  Programming. READROOM
        talks to the board directly without the need for a Device Driver.
        In order  to use  this interface,  a program  called RESETDIG.EXE
        must be used in the AUTOEXEC.BAT file to reset the DigiBoard once
        when the  computer is first booted. If you do not have this program
        (it is a part of the GAP Communications BBS package) then the
        Int14/EBIOS interface must be used.

6)      This is the DigiBoard Memory Window, or the address the board
        uses as a communications area between itself and the Host
        Computer. This line is used only if the Interface is set to
        DIGIBOARD. It can be set to 0 if the Interface is STANDARD or
        INT14/EBIOS.
        Valid entries are: C000, C800, D000, and D800

7)      This is the DigiBoard I/O Port Address. This line is used only
        if the Interface is set to DIGIBOARD and can be set to 0
        otherwise.
        Valid entries are: 100, 110, 120, 200, 220, 300 and 320

8)      This is the DigiBoard Channel Number. This line is required for
        the DIGIBOARD and INT14/EBIOS Interfaces. It is normally 1-8 for
        the DIGIBOARD Interface and 4-11 for the INT14/EBIOS Interface.
        The Channel Number is similar to a Port Number. It tells the
        program which of the DigiBoard Communications ports to use.

9)      This is where you will place your registration number you
        receive from Exhibit A Communications upon registering READROOM.

10)     This is where you will place your name, exactly as given to you
        when you register the program.  Case is important!

11)     This line is the full drive\path to the holding directory where
        IMPORT will look for new publications.  If you don't plan on
        using the IMPORT utility, then just leave this line blank.
        (Please see IMPORT.DOC for information on this utility)

12)     This is the name of the file (including path if not in same
        directory where READROOM.EXE is located) you wish to show users
        when they first enter this door.  If you don't wish to utilize
        this feature, leave this line blank. The door expects the file
        to follow normal display file conventions. The normal, ASCII
        version of the welcome screen is identified in the configuration
        file(WELCOME). If you wished to have an ANSI text or [ANSIART] file
        available to show color callers, then it would be named
        WELCOMEG. If you wished to have a RIP file available for callers
        using a RIP capable term program, that file would be named
        WELCOMER. WELCOME must exist, however, before READROOM will look
        for either WELCOMEG or WELCOMER.

13)     This is the name of the file (including path if not in same
        directory where READROOM.EXE is located) you wish to show users
        when they leave this door.  If you don't wish to utilize this
        feature, leave this line blank. Uses the same naming conventions
        as outlined in 12 above.

14)     This line is for sysop defined colors. Presently, there are the
        areas that you can define colors for: command prompts, menu
        numbers and titles. To select a color scheme other than the
        default, just separate the colors by a space. First color is for
        the command prompts, the second is for menu numbers and the last
        one is for titles.
        Valid choices are: BLACK, BLUE, RED, GREEN, YELLOW, MAGENTA,
                           CYAN and WHITE

Multi-Node operation:
        If you wish each node to have IDENTICAL publication configurations,
        line 15 should be as follows:
@H:\READROOM\PUBS.DAT
        Where the first character on the line must be @ symbol followed
        immediately by the full path/filename of the publication configuration
        file.  To create a publication configuration file, simply follow repeat
        the lines 15-18 described in Single Node Operation below.

Single Node operation:
        Repeat each of the following lines for each publication you plan
        on offering.

15)      This is the description you wish to show up on the publication
        menu.  This line should be no longer than 60 characters.

16)      The full drive and path to the directory that contains the
        READROOM.TOC file (below) for this publication as well as all of
        the articles to be viewed in this publication.

17)     YES or NO, depending on whether you wish to allow users to download
        the file named in the READROOM.TOC file (below).  If you run a multi-
        node system and since this flag is set in the configuration file, you
        may allow users on a private node to d/l the file while not allowing
        those on the public node to do so.  The choice is up to you.
        If, in order to save HD space, you would rather have READROOM
        look in a directory other than the publication directory defined
        above, you may substitute the full drive\path for this directory
        in place of YES.
        For more information on setting up the system to allow
        downloads, please see Appendix C at the end of this document.

18)     Advanced Features Line.
          If you don't wish to utilize the Advanced Features, please
          leave this line blank or use the RESERVED key word.
          The Advanced Features line, if enabled, must consist of at
          least 3 words.
                1. NOLOG or the full drive\path\filename of the log file
                   for this publication.  This log will track those who
                   open this publication.
                2. Minimum security level neccessary to open this pub-
                   lication.  If you wish to disable this feature, enter
                   a 0.
                3. File template to be used by IMPORT utility.  Please
                   see IMPORT.DOC for more details.  If you are not
                   planning on using this feature, or wish to disable it
                   on a pub by pub basis, just add NO as the third
                   option.  Please make sure it is uppercase.
        NOTE: As additional features are added to READROOM door, they
        will probably be defined by options specified on this line.

Repeat lines 15 through 18 for each publication you wish to offer up to a
maximum of 99 publications.  If you enter more than 99, only the first
99 will be used.


        Next, you will need to create a directory that will hold the
articles you wish to have displayed.  You will need to have a seperate
directory for each publication you intend to display with READROOM door.
In this directory you will place:
        1)  Articles to be viewed
        2)  Archived version of the articles above (optional)
        3)  READROOM.TOC
The READROOM.TOC acts as an index to the articles available that
READROOM door needs to run.  Having this file separate from the
configuration file should make life easier for sysops running multi-node
systems and whose publications change frequently.

Any publication support the READROOM.TOC format will be all set to run
under the READROOM door. All you will need to do is update the
configuration(s) files as shown above, create the directory to hold the
publication and then unarchive the publication into its directory.

To transfer publications in other formats to the READROOM.TOC format,
please see the file RDRMTOC.SPC for the format specifications.



