                             BreNet
                         By Bryan Beals
                           Written at
                        The Game Grid BBS
                   (714)528-7459 300-14.4 8N1


What is BreNet?

     BreNet is a door that exchanges Barren Realms Elites inter-BBS
mail packets with out the need on a mailer like INTER-MAIL.  The
concept is very similar to QWK echo mail.  The BBS calls up the Hub
(BBS #1) uploads their mail packet and downloads new mail packet.

!!!Note This doc is for the setup of the league hubs (BBS#1)
calling in information can be found in NODES.TXT also in this
archive!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Requires:
---------
DSZ (unregistered version works fine)
Brun45.exe (run time unit can be downloaded off most BBS systems)


Setting up BRE for use with BreNet.
----------------------------------

1. Unzip BRE and set up a inter-bbs game as explained in the BRE
docs.

2. When setting up your mailer type in BRE chose NONE.

3. As for node addresses make them up (just make sure you give each
node a different # and make you node #1 is the Nodelist.)

4. Make sure to make the Inbound and Outbound directories different
and not used for ANYTHING else.

5. After all the Nodes are Entered into the nodelist run a        
  BRE REQUEST and a BRE PLANETARY to create the 1st days files.

Setting up BreNet.
------------------

1. Unzip BreNet into its own directory (something like c:\brenet)

2. Setup the BreNet config file.  (See BRENET.CFG for info)

3. Run the SETUP program and configure the nodes.

To run the program just type BRENET.EXE BRENET.CFG


Nightly Maintenance.
--------------------

1. Unzip all the nodes uploaded mail packets in the BRENET\IN dir
that will be created after the 1st time you run BRENET, into you
BRE inbound dir.

2. Delete the old ZIP files.

3. Run a BRE REQUEST then a BRE PLANETARY

4. If you would like score files for the league type BRSCORES.


Distribution.
------------

The Files for BreNet may be uploaded to any bbs as long as its in
its full and complete form!  If you would like to put it on a CD
disk or other package please contact Bryan Beals at the Address on
the regasion form.

Disclaimer
----------

The writer Bryan Beals takes no responsibility for any damage this
program may do to your system. I make no guarantee  about this
program other than it will take up disk space

Fossil Driver Support
---------------------
DoorFrame supports the use of Fossil drivers.  To tell your Door to
use the Fossil driver instead of the standard COM ports, just put
/FD on the command line when running the door. For example:
     MYDOOR MYDOOR.CFG /FD
indicates that a Fossil driver is present and should be used. If no
Fossil driver is detected, DoorFrame will print a message to that
effect and exit the door gracefully.

Environment Variables
---------------------
DoorFrame supports COM 1-4 on the standard IRQ's - COM1/COM3 = IRQ4
and COM2/COM4 = IRQ3. If you wish to use a non-standard IRQ, add
the IRQ number after the configuration filename. Let's assume your
Door is called FOOBAR and you want to use COM1 and IRQ5. The
command line passed to your Door would be:
    FOOBAR FOOBAR.CFG /5  or
    FOOBAR FOOBAR.CFG /%IRQ%  for the environment variable. The /5
tells DoorFrame to use IRQ5 rather than the standard IRQ4 that is
normally used with COM1. No /x parameter is needed for the standard
IRQ's.

When specifying the location of the system file on line 1 of the
doors .CFG file, you may use the environment variables %pcbdrive%,
%pcbdir%, %pcbnode%, and %wcnodeid%. Some examples:
 PCBoard: 
   USERS.SYS in C:\PCB           - %pcbdrive%%pcbdir%\USERS.SYS   
USERS.SYS in C:\PCB\NODE1     -
%pcbdrive%%pcbdir%\NODE%pcbnode%\USERS.SYS

 Wildcat!:
   USERINFO.DAT in C:\WC\NODE1   - C:\WC\NODE%wcnodeid%

Non-PCBoard systems may use the PCB environment variables by
setting them in either AUTOEXEC.BAT or in the batch that runs the
door. For example:  SET PCBDRIVE=C:
 SET PCBDIR=\BBSDIR
 SET PCBNODE=1

486DX CPU's
-----------
The math coprocessor in 486DX CPUs cannot handle floating point
math which all MicroSoft Basic's use. This can show up as an ERROR
5, a keyboard  timeout, etc.

Fortunately there is an easy fix for this problem. Simply place the
following line in the AUTOEXEC.BAT file:

SET NO87=ON

