I operate a 2-Node Bulletin Board System using PCBoard v15.2/M.

  There are many Doors available which are NOT multi-node capable, so I
was using a separate version of these doors on each node. But, that
takes up a lot of disc space. So, I developed a series of Batch files to
block a second node from opening a non-multi-node door, if it is being
used by another node. The following is how to do it:

        STEP 1: Create a directory called PROTECTS. I placed in my C:
root directory. Example: C:\PROTECTS.

        STEP 2: Create a subdirectory under PROTECTS called BATCHES.
        Example: C:\PROTECTS\BATCHES.

        STEP 3: For each door which is NOT multi-node capable, you must
create two batch files in the directory from which you call the doors in
the DOORS.LST file. I use C:\PCB.
I will use a door called PLAY for examples. PLAY would be the first
batch file. As you know, you use NO extension on a batch file calling a
door in PCBoard. PLAY3 would be the second batch file.
        Here is an example of what PLAY would contain:

ECHO ON
C:
CD\PROTECTS     ;Change to the C:\PROTECTS directory
PLAYCHG         ;Run a Batch file called PLAYCHG.BAT. (Instructions on
                ;this Batch file coming up later!

        Here is an example of what PLAY3 would contain:

ECHO ON
C:
CD\PROTECTS             ;Chance to the C:\PROTECTS directory
ANN ANN%PCBNODE%.CFG    ;Run ANN.EXE. (Further info on ANN.EXE coming up
                        ;later!

        STEP 4: In your PROTECTS directory, you must create a batch file
called PLAYCHG.BAT. Here it IS necessary to use the .BAT extension!

        Here is an example of what PLAYCHG.BAT would contain:

ECHO ON
C:
CD\PCB                  ;Change to your PCB Directory
RENAME PLAY. PLAY2.     ;Rename the PLAY batch PLAY2
RENAME PLAY3. PLAY.     ;Rename the PLAY3 batch PLAY.
C:
CD\PCB\DOORS\PLAYGAME   ;Change to the directory which contains the door
                        ;files.
PLAY PLAY%PCBNODE%.CFG  ;Run the door program
C:
CD\PCB                  ;After the door is closed, change to the PCB
                        ;directory again.
RENAME PLAY. PLAY3.     ;Rename the PLAY batch PLAY3.
RENAME PLAY2. PLAY.     ;Rename the PLAY2 batch PLAY.
                        ;If you do not Swap or Shell to the door, you
                        ;must recall BOARD.BAT here.

        STEP 5: Create the above batch files for each of your
NON-Multi-Node doors. Remember, I am using PLAY as an example. Each
batch file must be different. I have included my batch files for use as
examples!

        STEP 6: You must create two ANNOUNCE files. One ASNI and one
ASCII using TheDraw or some other ANSI editor. The screens you create
would advise a user the door which they accessed is in use on another
node, and to 'Try Again Later'. The ANSI ANNOUNCE file MUST be named
ANNOUNCE.ANS. The ASCII ANNOUNCE file MUST be named ANNOUNCE.ASC.
        NOTE: When creating the ANNOUNCE screens, start 4-lines from the
top and use a maximum 15 lines!

You MUST also create a CFG file for each of your nodes, for the ANNOUNCE
program. The ANN.EXE, my ANN.CFGs and my ANNOUNCE.ANS and ANNOUNCE.ASC
files are included. It would also be a good idea to make ANN.EXE
Read-Only to avoid share violations if two nodes should happen to call
ANN.EXE at the same time!

        STEP 7: To guarantee the proper batch files are available even
if your system freezes or crashes, you MUST place a Batch file in your
Events which corrects any problems created by a system freeze or crash.
Call it BATCHES.BAT. This Batch file would delete any leftover XXX2
batch files and re-copy the XXXX and XXXX3 Batch files into your PCB
directory. A copy of my BATCHES.BAT is included!

        STEP 8: After you have created ALL your XXXX. and XXXX3. Batch
files, copy them all into your C:\PROTECTS\BATCHES directory. I run 6
Events daily, and I run BATCHES.BAT in each Event.

        Now, when a Node is using a NON-Multi-Node door, any other Node
opening the same door would see the ANNOUNCE screen advising the user
the Door is being used by another Node and to 'Try Again Later'

        Included is the ANN.EXE program and example XXXX and
XXXX3 Batch files used on my system.

        If you have any questions or ideas on how this procedure can be
simplified, leave me a Message on SALT AIR or call my system at (814)
452-6900 or (814) 452-4429.

        I hope this is helpful!

DON SHRIVER
Window on Window BBS
Erie, PA