≪ View Page

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
conference_setup:doors [2024-01-17 16:35] – stimpyconference_setup:doors [2024-01-25 10:41] (current) – [Using One Batch File For All Nodes] stimpy
Line 18: Line 18:
 If you load PCBSetup, and select a conference to edit you will see the following fields at the bottom of your display: If you load PCBSetup, and select a conference to edit you will see the following fields at the bottom of your display:
  
-||**Menu Listing**|**Path/Name List File**|    +| |**Menu Listing**|**Path/Name List File**|    
 |**Doors**|C:\PCB\GEN\DOORS|C:\PCB\GEN\DOORS.LST| |**Doors**|C:\PCB\GEN\DOORS|C:\PCB\GEN\DOORS.LST|
 |**Bulletins**|C:\PCB\GEN\BLT|C:\PCB\GEN\BLT.LST| |**Bulletins**|C:\PCB\GEN\BLT|C:\PCB\GEN\BLT.LST|
 |**Scripts**|C:\PCB\GEN\SCRIPT|C:\PCB\GEN\SCRIPT.LST| |**Scripts**|C:\PCB\GEN\SCRIPT|C:\PCB\GEN\SCRIPT.LST|
 |**Directories**|C:\PCB\GEN\DIR|C:\PCB\GEN\DIR.LST| |**Directories**|C:\PCB\GEN\DIR|C:\PCB\GEN\DIR.LST|
-|**Download Paths (listing only)**||C:\PCB\GEN\DLPATH.LST|+|**Download Paths (listing only)**| |C:\PCB\GEN\DLPATH.LST|
  
 The two fields that relate to door operation are the following: The two fields that relate to door operation are the following:
  
-||**Menu Listing**|**Path/Name List File**|+| |**Menu Listing**|**Path/Name List File**|
 |**Doors**|C:\PCB\GEN\DOORS|C:\PCB\GEN\DOORS.LST| |**Doors**|C:\PCB\GEN\DOORS|C:\PCB\GEN\DOORS.LST|
  
Line 200: Line 200:
 Now, lets say in the ND.CFG file is the following: Now, lets say in the ND.CFG file is the following:
  
-    C:\PCB\NODE3\PCBOARD.SYS ;location of PCBOARD.SYS +    C:\PCB\NODE3\PCBOARD.SYS    ;location of PCBOARD.SYS 
-    5                        ;number of times game can be played per day +    5                           ;number of times game can be played per day 
-    400                      ;points per win+    400                         ;points per win
  
-If you could use environment variables in other files, the solution would be easy enough, you would replace the C:\PCB\NODE3\PCBOARD.SYS in the ND.CFG file to say %PCBDRIVE%%PCBDIR%\PCBOARD.SYS.  However, you cannot do that because environment  variables cannot  be  read  in  from configuration files.  Therefore, you need another alternative.+If you could use environment variables in other files, the solution would be easy enough, you would replace the C:\PCB\NODE3\PCBOARD.SYS in the ND.CFG file to say %PCBDRIVE% %PCBDIR%\PCBOARD.SYS. However, you cannot do that because environment variables cannot be read in from configuration files. Therefore, you need another alternative.
  
 At this point you need to create a configuration file for each node.  You will want to come up with some sort of naming convention. Since the original config file was called ND.CFG you may want to simply tack on the node number to each config file (e.g. ND1.CFG, ND2.CFG, ND3.CFG).  By naming them with the node numbers in the filename we will be able to use the PCBNODE environment variable. The most important thing to remember is that you should remain consistent in your naming conventions. If you do not, you will not be able to use environment variables. At this point you need to create a configuration file for each node.  You will want to come up with some sort of naming convention. Since the original config file was called ND.CFG you may want to simply tack on the node number to each config file (e.g. ND1.CFG, ND2.CFG, ND3.CFG).  By naming them with the node numbers in the filename we will be able to use the PCBNODE environment variable. The most important thing to remember is that you should remain consistent in your naming conventions. If you do not, you will not be able to use environment variables.