ProBoard BBS Documentation

The Choice of Professionals

User Tools

Site Tools

Trace: • start
paths

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
paths [2022/04/30 03:05] – adminpaths [2022/04/30 03:27] (current) – admin
Line 1: Line 1:
 ====== Paths ====== ====== Paths ======
  
-Text Files ..................  +**Text Files**
-                              Directory where ProBoard's textfiles are +
-                              stored (drive included!).+
  
-RIP Files ................... Directory where ProBoard's RIP files are +Directory where ProBoard's textfiles are stored (drive included!).
-                              stored (drive included!).+
  
-RIP Icons ................... Directory where ProBoard's RIP icons are +**RIP Files**
-                              stored (drive included!).+
  
-Menus ....................... Directory where ProBoard's menus are stored +Directory where ProBoard's RIP files are stored (drive included!).
-                              (drive included!).+
  
-Message Base ................ Directory where the message base will be +**RIP Icons**
-                              stored (drive included!). +
-  +
-Uploads ..................... Directory where the users' uploads will be +
-                              stored (drive included!).+
  
-Private Uploads ............. Directory where personal files are stored. +Directory where ProBoard's RIP icons are stored (drive included!).
-                              (for file exchanges between users).+
  
-Nodelist Directory .......... Directory where the nodelist is located. +**Menus**
-                              For use by the nodelist compiler. Leave +
-                              this field blank if you do not have a +
-                              nodelist.+
  
-PEX Files ................... Directory where the PEX files will be +Directory where ProBoard's menus are stored (drive included!).
-                              stored.+
  
-Editor Command .............. The external editor's filename and path +**Message Base**
-                              (eg. C:\GEDIT\GEDIT.EXE).  You can also +
-                              specify a PEX file here by using a "@" as +
-                              the first character.+
  
-                              You can also use shell options here.+Directory where the message base will be stored (drive included!).
  
-                              It appears that if you are using GEdit +**Uploads**
-                              v2.00 or v2.01 that you will need to write +
-                              an RA 1.1x style EXITINFO.BBS file to make +
-                              GEdit work with ProBoard 2.16 and higher. +
-                              This is done with the Menu Function 7 "*E" +
-                              parameter.  Refer to Menu Function 7 for +
-                              more info.+
  
-                                 Example: *SGEDIT\GEDIT.EXE -N*#*E +Directory where the users' uploads will be stored (drive included!).
-                                 Example: @MYEDIT  (for a PEX file).+
  
-                              If you are not using an external editor, +**Private Uploads**
-                              leave this field blank and ProBoard will +
-                              default to it's internal line editor (you +
-                              can also use ProBoard's internal fullscreen +
-                              editor by enabling the next option).+
  
-                              NOTE: this command will be ignored if +Directory where personal files are stored. (for file exchanges between users).
-                                    ProBoard's internal fullscreen editor +
-                                    is enabled with the next option.+
  
-Use internal fullscreen ..... Set this to "Yes" to enable the built-in +**Nodelist Directory**
-editor                        fullscreen editor instead of the external +
-                              editor defined in "Editor Command".  When +
-                              the internal fullscreen editor is enabled, +
-                              the external editor will be ignored.+
  
 +Directory where the nodelist is located. For use by the nodelist compiler. 
 +Leave this field blank if you do not have a nodelist.
  
-External Chat ............... Path to your external chat program.  If one +**PEX Files**
-                              is defined here it will be executed instead +
-                              of ProBoard's internal chat routine.  You +
-                              can specify either a  chat door (.EXE) or a +
-                              chat PEX (.PEX) file here.+
  
-                              If you want to specify an .EXE file, enter +Directory where the PEX files will be stored.
-                              the full path to the program.  (see example +
-                              below).+
  
-                              If you want to specify a PEX file, you must +**Editor Command**
-                              place a "@" character before the command +
-                              line.  (see example below).+
  
-                              You can also use the "Shell" (Menu Function +The external editor's filename and path (eg. C:\GEDIT\GEDIT.EXE).  You can also 
-                              7) parameters (like *X etc.) or the text +specify a PEX file here by using a "@" as the first character.
-                              macros (@<...>@).+
  
-                              To use the built-in chat routine in +You can also use shell options here.
-                              ProBoard, leave this line blank.+
  
 +It appears that if you are using GEdit v2.00 or v2.01 that you will need to write
 +an RA 1.1x style EXITINFO.BBS file to make GEdit work with ProBoard 2.16 and 
 +higher. This is done with the Menu Function 7 "*E" parameter.  Refer to Menu 
 +Function 7 for more info.
  
-                            Examples: +     Example: *SGEDIT\GEDIT.EXE -N*#*E 
-                            ─────────+     Example: @MYEDIT  (for a PEX file).
  
-                            *E*SGCHAT.EXE D E    (.EXE chat door) +If you are not using an external editor, leave this field blank and ProBoard will 
-                             @TheChat            (.PEX chat door)+default to it's internal line editor (you can also use ProBoard's internal fullscreen 
 +editor by enabling the next option). 
 + 
 +NOTE: this command will be ignored if ProBoard's internal fullscreen editor 
 +is enabled with the next option. 
 + 
 +**Use internal fullscreen editor** 
 + 
 +Set this to "Yes" to enable the built-in editor fullscreen editor instead of the external 
 +editor defined in "Editor Command".  When the internal fullscreen editor is enabled, 
 +the external editor will be ignored. 
 + 
 +**External Chat** 
 + 
 +Path to your external chat program.  If one is defined here it will be executed instead 
 +of ProBoard's internal chat routine.  You can specify either a  chat door (.EXE) or a 
 +chat PEX (.PEX) file here. 
 + 
 +If you want to specify an .EXE file, enter the full path to the program.  (see example 
 +below). 
 + 
 +If you want to specify a PEX file, you must place a "@" character before the command 
 +line.  (see example below). 
 + 
 +You can also use the "Shell" (Menu Function 7) parameters (like *X etc.) or the text 
 +macros (@<...>@). 
 + 
 +To use the built-in chat routine in ProBoard, leave this line blank. 
 + 
 +     Example: *E*SGCHAT.EXE D E    (.EXE chat door) 
 +     Example: *@TheChat            (.PEX chat door)
  
paths.1651259114.txt.gz · Last modified: 2022/04/30 03:05 by admin

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki