Multi-Node Installation ----------------------- The PCBoard documentation recommends that a unique \PCB base directory be created for each node that you are running. The suggested setup and what I'll use as an example is: C:\PCB - Node 1 base PCB directory C:\PCB2 - Node 2 base PCB directory D:\PCB3 - Node 3 base PCB directory E:\PCBx - Node x base PCB directory 1. Create a KMAIL sub-directory to hold the KMAILxxx distribuation archive files. This directory is not node specific and you only need one of them. (See note later about the KMAIL.OVR file). 2. Create a "unique" \KWORK sub-directory for each node you have. Some examples are: C:\KWORK1 or C:\PCB\KWORK - Node 1 C:\KWORK2 or C:\PCB2\KWORK - Node 2 D:\KWORK3 or D:\PCB3\KWORK - Node 3 C:\PCB\KWORK \ C:\PCB2\KWORK > This would also be a valid technique. D:\PCB3\KWORK / If you have room for everything on one drive, then the following would be possible: C:\KMAIL\KWORK1 C:\KMAIL\KWORK2 C:\KMAIL\KWORK3 ***CAUTION*** ***CAUTION*** All files are erased in the WORK directory during the mail packet creation process. DO NOT use an existing directory that has good stuff in it! 3. This item is the same as in the KMAIL.DOC file. 4. Create a "unique" KMAILx.CNF for each node you are running. This is a standard ASCII text file, parameters start in column 1. The .CNF files should be placed in the KMAIL sub-directory that was defined in step #1 above. On a multi-node system is it suggested that the .CNF files be called something like (KMAIL1.CNF, KMAIL2.CNF, ..... KMAILx.CNF). LINE 1: Defines the comm port interface. LINE 2: Defines the location of the node specific Kwork directory. LINE 3: Optional, defines the location of a holding directory if you choose to provide pre-zipped packets for callers. (The need for this is described in step 10). Detailed Description: --------------------- Line #1 should specify either INTERRUPT or FOSSIL. INTERRUPT - Use this for standard COMx communication. FOSSIL - Use this for connunication with FOSSIL drivers. Line #2 is the path\name of a "unique" scratch work directory. If the sub-directory does not exist, it will be created. Line #3 is optional. If the pre-zip function (explained later) is used, this line points to the holding sub-directory. It may be any name, but I recommend something like KHOLD. Multi-node systems MUST share the same KHOLD sub-directory in order for pre-zip packets to be located from any node. Sample KMAILx.CNF - It gets a little complicated to show all variations. Just remember, line #2 points to the node specific KWORK directory that you defined in step 2 above. KMAIL1.CNF KMAIL3.CNF ---------- ---------- INTERRUPT INTERRUPT Line 1 C:\PCB\KWORK D:\PCB3\KWORK Line 2 <-- Must be unique for each node! D:\KHOLD D:\KHOLD Line 3 Optional, must NOT be the same as line 2. Multi-node systems must share the same sub-directory. (explained in step 10). ******************************************************************** ** Warning ** Warning ** Warning ** Warning ** Warning ** ******************************************************************** * * * ALL FILES ARE ERASED IN THE WORK DIRECTORY DURING PROCESSING. * * MAKE SURE THE AREA YOU SPECIFY IS A SCRATCH AREA! * * * ******************************************************************** ** Warning ** Warning ** Warning ** Warning ** Warning ** ******************************************************************** 5. You will now need to create a KMAIL batch file for each node. Each KMAIL batch file is unique to the node it is running on. Basically, the job of the KMAIL batch file is to load the Kmail program and identify the appropriate .CNF file to use. The .CNF is read by Kmail to determine the correct \KWORK area. The Kmail batch files are to be placed into the base \PCBx directory of each node. The batch files MUST all have the same name, but since each is located in a unique directory, that is not a problem. The format of the Kmail command is as follows: KMAIL KMAILx.CNF C:\PCBx ³ ³ ³ ÀÄÄÄÄÄ> The location of where to find PCBOARD.DAT ³ for this node. This is normally the base ³ PCB directory of the node in question. ³ ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ> The name of the specific .CNF file for the node in question. NODE 1 NODE 3 -------- ---------- Echo off Echo Off SET KMAIL= SET KMAIL= C: C: CD\Kmail CD\Kmail ==> KMAIL KMAIL1.CNF C:\PCB ==> KMAIL KMAIL3.CNF C:\PCB3 ==> C: ==> D: ==> CD\PCB ==> CD\PCB3 Board Board ===> As you can see, this portion of each KMAIL batch file is unique to the node it is running on and needs to be customized to match the configuration of your system. Please double check everything. There is no end to the grief and misery caused by an error here. 6. This and the rest of the items are the same as in KMAIL.DOC NOTE: Some multi-taskers or network programs will report a share violation trying to open KMAIL.OVR unless the attributes for KMAIL.OVR are set to "readonly". Beginning with KMAIL280, the KMAIL.OVR file will be distributed with the "readonly" attribute enabled. Should the need arise for you to set the readonly attribute you can do so with the Dos ATTRIB command. The syntax is: ATTRIB +R KMAIL.OVR