This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
menu_function_overview [2021/10/26 21:34] – admin | menu_function_overview [2023/11/02 11:23] (current) – massacre | ||
---|---|---|---|
Line 13: | Line 13: | ||
This function makes ProBoard jump to menu <menu name>. | This function makes ProBoard jump to menu <menu name>. | ||
- | Option /M can be used to define one single menu for several message | + | Option /M can be used to define one single menu for several message areas. You could jump to a ' |
- | areas. You could jump to a ' | + | |
- | /M=3, to make message area 3 active for the selected menu. Please refer | + | |
- | to function 23 (Read messages) for more information about this option. | + | |
Option /F works exactly the same, but applies to file areas. | Option /F works exactly the same, but applies to file areas. | ||
- | It is possible to protect a menu with a password by using the /P= option. | + | It is possible to protect a menu with a password by using the /P= option. For example: "SysOp / |
- | For example: "SysOp / | + | |
- | " | + | |
to the menu. | to the menu. | ||
- | It is also possible to select the next available message or file areas | + | It is also possible to select the next available message or file areas with the use of the following parameters. |
- | with the use of the following parameters. | + | |
/M=+ (set next accessible Message Area) | /M=+ (set next accessible Message Area) | ||
Line 49: | Line 43: | ||
DATA: <menu name> [/M=<nr msgarea> | DATA: <menu name> [/M=<nr msgarea> | ||
- | This function is largely the same as the Menu Function 1 (it even has the | + | This function is largely the same as the Menu Function 1 (it even has the same parameters), |
- | same parameters), | + | |
- | onto an internal stack. ProBoard will jump back to this menu when | + | |
- | returning from menu <menu name> (by executing Menu Function 3). | + | |
Data examples: | Data examples: | ||
Line 70: | Line 61: | ||
DATA: (none) | DATA: (none) | ||
- | This function makes ProBoard go back to the previous menu if you used | + | This function makes ProBoard go back to the previous menu if you used Menu Function 2. |
- | Menu Function 2. | + | |
Line 79: | Line 69: | ||
DATA: <menu name> [/M=<nr msgarea> | DATA: <menu name> [/M=<nr msgarea> | ||
- | This function performs the same tasks as Menu Function 1, but will clear | + | This function performs the same tasks as Menu Function 1, but will clear the existing menu stack, thus preventing the user from returning to the previous menu. |
- | the existing menu stack, thus preventing the user from returning to the | + | |
- | previous menu. | + | |
Data examples: | Data examples: | ||
Line 99: | Line 87: | ||
DATA: < | DATA: < | ||
- | This function displays a file to the user with the extension .ANS or | + | This function displays a file to the user with the extension .ANS or .ASC, depending on the user's ANSI-setting. The file must be stored in ProBoard' |
- | .ASC, depending on the user's ANSI-setting. The file must be stored in | + | |
- | ProBoard' | + | |
- | extension (max. eight characters). If ProBoard doesn' | + | |
- | file, it will look for the .ASC file. | + | |
Line 119: | Line 103: | ||
DATA: <command line> | DATA: <command line> | ||
- | With this function, you can instruct ProBoard to execute an external | + | With this function, you can instruct ProBoard to execute an external program. This program has to do its own serial I/O, so ordinary programs will only work if run locally. |
- | program. This program has to do its own serial I/O, so ordinary programs | + | |
- | will only work if run locally. | + | |
- | Parameter <command line> needs full path and filename (.COM or .EXE | + | Parameter <command line> needs full path and filename (.COM or .EXE extension included), and may contain some special codes. |
- | extension included), and may contain some special codes. | + | |
- | will (at run-time) be replaced by a value or a string. | + | |
Special codes: | Special codes: | ||
+ | (*) | ||
** Replaced by an asterisk (' | ** Replaced by an asterisk (' | ||
- | |||
*# Replaced by the node number. | *# Replaced by the node number. | ||
- | + | | |
- | | + | |
- | | + | |
- | | + | |
*! Freezes ProBoard' | *! Freezes ProBoard' | ||
- | + | | |
- | | + | *A Writes a user's handle (alias) to DORINFOx.DEF instead of his/her real name. |
- | | + | |
- | + | ||
- | *A Writes a user's handle (alias) to DORINFOx.DEF instead of | + | |
- | | + | |
*B Current baud rate. | *B Current baud rate. | ||
- | + | | |
- | | + | *D Writes a full 52-line DOOR.SYS drop file to the current directory before shelling. |
- | | + | *E Writes an RA 1.1x EXITINFO.BBS to the current directory before shelling and reads it back afterwards. |
- | | + | |
- | + | ||
- | *D Writes a full 52-line DOOR.SYS drop file to the current | + | |
- | | + | |
- | + | ||
- | *E Writes an RA 1.1x EXITINFO.BBS to the current directory | + | |
- | | + | |
- | | + | |
- | | + | |
*F User's first name. | *F User's first name. | ||
- | |||
*G Indicates whether user has ANSI (1) or ASCII (0) set. | *G Indicates whether user has ANSI (1) or ASCII (0) set. | ||
- | + | | |
- | | + | |
- | | + | |
*I Maximum user-inactivity (seconds). | *I Maximum user-inactivity (seconds). | ||
+ | *J Displays configured BBS name. | ||
+ | *K Displays current version of ProBoard. | ||
*L User's last name. | *L User's last name. | ||
- | |||
*M ProBoard' | *M ProBoard' | ||
- | |||
*N Shell will NOT be logged in PROBOARD.LOG. | *N Shell will NOT be logged in PROBOARD.LOG. | ||
- | |||
*O (not zero!) is replaced by the path of the current file area. | *O (not zero!) is replaced by the path of the current file area. | ||
- | |||
*P Com-port used by ProBoard (1-8). | *P Com-port used by ProBoard (1-8). | ||
- | |||
*Q Don't let user know that ProBoard is shelling (!). | *Q Don't let user know that ProBoard is shelling (!). | ||
- | |||
*R User's record number in USERS.BBS. | *R User's record number in USERS.BBS. | ||
- | |||
*S ProBoard' | *S ProBoard' | ||
- | |||
*T Time left for the user today (minutes). | *T Time left for the user today (minutes). | ||
- | + | *U Displays current user's handle (alias). | |
- | *V Disables adding 2 to the graphics capability line in | + | *V Disables adding 2 to the graphics capability line in DORINFOx.DEF when the user has AVATAR enabled. |
- | | + | *W Runs the shell in a window , so the status on the last line will not be cleared. This option only works with programs that send their output to the standard output device (no direct screen writes). |
- | + | *X ALWAYS SWAP to disk/EMS, even if swapping is disabled in ProCFG. | |
- | *W Runs the shell in a window , so the status on the last line | + | |
- | | + | |
- | | + | |
- | | + | |
- | + | ||
- | *X ALWAYS SWAP to disk/EMS, even if swapping is disabled in | + | |
- | | + | |
*Y DO NOT SWAP to disk/EMS. | *Y DO NOT SWAP to disk/EMS. | ||
- | + | | |
- | | + | *_ (asterisk underscore) Tells ProBoard not to write underscores instead of spaces when writing a user's last name in DORINFOx.DEF. For example, users name is Harvey Van Hooten. Without this parameter, users name will be written to DORINFOx.DEF as follows: |
- | | + | |
- | | + | |
- | | + | |
- | | + | |
- | | + | |
- | + | ||
- | *_ (asterisk underscore) Tells ProBoard not to write underscores | + | |
- | | + | |
- | | + | |
- | | + | |
- | | + | |
HARVEY VAN_HOOTEN | HARVEY VAN_HOOTEN | ||
- | + | | |
- | | + | |
- | | + | |
HARVEY VAN HOOTEN (with no underscore in last name) | HARVEY VAN HOOTEN (with no underscore in last name) | ||
- | + | | |
- | | + | *1 Installs a timer-function when shelling, which continuously redisplays the user's status line on the first screenline. This can be used with ALL programs. |
- | | + | *2 Same as *1, but uses the bottom screenline (try this with QuickEd or GEdit!) |
- | | + | |
- | + | ||
- | *1 Installs a timer-function when shelling, which continuously | + | |
- | | + | |
- | | + | |
- | | + | |
- | + | ||
- | *2 Same as *1, but uses the bottom screenline (try this with | + | |
- | | + | |
Suppose ProBoard is in directory D:\PB. | Suppose ProBoard is in directory D:\PB. | ||
- | Data example: *Q*STEST.EXE *B | + | |
- | ProBoard will execute D: | + | ProBoard will execute D: |
- | happening. | + | |
To execute a batch file, you have to use the following syntax: | To execute a batch file, you have to use the following syntax: | ||
- | " | + | |
- | < | + | |
- | When shelling, ProBoard writes a standard DORINFOx.DEF file, where x | + | When shelling, ProBoard writes a standard DORINFOx.DEF file, where x stands for the node-number. An RA-compatible EXITINFO.BBS file and a DOORWAY-compatible DOOR.SYS can also be created by specifying the *E |
- | stands for the node-number. An RA-compatible EXITINFO.BBS file and a | + | and/or *D options. All these files are created in the directory where ProBoard is started from. |
- | DOORWAY-compatible DOOR.SYS can also be created by specifying the *E | + | |
- | and/or *D options. All these files are created in the directory where | + | |
- | ProBoard is started from. | + | |
Line 254: | Line 165: | ||
DATA: (none) | DATA: (none) | ||
- | This function shows information about ProBoard' | + | This function shows information about ProBoard' |
- | have a registered copy of ProBoard, the SysOp' | + | |
- | shown. With this function, you can show off to your users that you're a | + | |
nice SysOp: one that registered! | nice SysOp: one that registered! | ||
Line 273: | Line 182: | ||
DATA: (none) | DATA: (none) | ||
- | Shows a bar graph of the average system usage per hour. From the day you | + | Shows a bar graph of the average system usage per hour. From the day you install ProBoard, it will keep track of a usage rate per hour and per day. If you want to change the usage values, just edit the values using ProCFG. |
- | install ProBoard, it will keep track of a usage rate per hour and per | + | |
- | day. If you want to change the usage values, just edit the values using | + | |
- | ProCFG. | + | |
Line 284: | Line 190: | ||
DATA: (none) | DATA: (none) | ||
- | This function allows the user to make a request to chat with the SysOp. | + | This function allows the user to make a request to chat with the SysOp. The user will be prompted for a reason why he wants to chat. The minimal length of this reason must be 5 characters. |
- | The user will be prompted for a reason why he wants to chat. The minimal | + | |
- | length of this reason must be 5 characters. | + | |
- | user to enter 5 spaces as a reason for chatting. | + | |
- | answer, the status line will start flashing, indicating that the users | + | |
wants to chat. You can view the reason for the chat by pressing <F8>. | wants to chat. You can view the reason for the chat by pressing <F8>. | ||
- | You can define your own page-tune by creating a RemoteAccess- compatible | + | You can define your own page-tune by creating a RemoteAccess- compatible description file. The format of this file is described in the reference section. |
- | description file. The format of this file is described in the reference | + | |
- | section. | + | |
Line 301: | Line 201: | ||
DATA: < | DATA: < | ||
- | This function executes a questionnaire. A questionnaire is a common | + | This function executes a questionnaire. A questionnaire is a common ASCII-file containing several commands to be executed by ProBoard. A questionnaire scriptfile has an extension .Q-A, and the user's answers will be stored in a file with the same filename, but with extension .ASW. Starting from version 1.15, you can write very powerful questionnaires by |
- | ASCII-file containing several commands to be executed by ProBoard. A | + | |
- | questionnaire scriptfile has an extension .Q-A, and the user's answers | + | |
- | will be stored in a file with the same filename, but with extension .ASW. | + | |
- | Starting from version 1.15, you can write very powerful questionnaires by | + | |
using the ProBoard SDK. | using the ProBoard SDK. | ||
Line 311: | Line 207: | ||
- | ASK < | + | |
+ | eg: Ask 10 1 | ||
- | eg: Ask 10 1 | + | Asks the user something. The user has < |
- | Asks the user something. The user has < | ||
- | the answer will be stored in the variable <number of variable> | ||
- | maximum number of variables in ProBoard is 20. | ||
- | |||
- | |||
- | CHANGECOLOR < | ||
+ | CHANGECOLOR < | ||
eg: ChangeColor 3 | eg: ChangeColor 3 | ||
- | Changes the color in which the following text will be displayed. | + | Changes the color in which the following text will be displayed. |
- | number < | + | |
- | works only for users who use ANSI. | + | |
- | CLEARSCREEN | + | |
Well, what do you think? | Well, what do you think? | ||
- | DISPLAY "< | + | |
eg: Display "Hi there!" | eg: Display "Hi there!" | ||
- | Displays a string < | + | Displays a string < |
- | quotes; a ' | + | |
- | IF <number of variable> | ||
+ | IF <number of variable> | ||
eg. If 1 = " | eg. If 1 = " | ||
- | Directs the .Q-A file according to the user's answers. | + | Directs the .Q-A file according to the user's answers. |
- | is met, all commands after the IF-statement will be executed, until an | + | |
- | ENDIF is encountered. | + | |
- | ENDIF | + | |
Ends an IF-statement. | Ends an IF-statement. | ||
Line 363: | Line 248: | ||
- | GETCHOICE < | + | |
eg: GetChoice YN 1 | eg: GetChoice YN 1 | ||
Line 370: | Line 254: | ||
- | OUTPUTANSWER ["< | + | |
eg: OutputAnswer "Name: " 1 | eg: OutputAnswer "Name: " 1 | ||
- | Writes ["< | + | Writes ["< |
- | .ASW-file. < | + | |
- | POSTINFO | + | |
- | Writes a header to the .ASW-file. The header contains some general | + | Writes a header to the .ASW-file. The header contains some general information about the user (" |
- | information about the user (" | + | |
- | QUIT | + | |
Ends execution of the questionnaire script. | Ends execution of the questionnaire script. | ||
- | SETFLAG < | + | |
eg: SetFlag C ON | eg: SetFlag C ON | ||
- | Sets/clears user flag < | + | Sets/clears user flag < |
- | possible to use the QuickBBS/RA flags (A1-D8) | + | |
- | SETSECURITY < | + | |
eg: SetSecurity 20 | eg: SetSecurity 20 | ||
Line 404: | Line 282: | ||
- | CAPITALISE [On|Off] | + | |
eg: Capitalise On | eg: Capitalise On | ||
- | Changes the way input from the user is displayed. When ON, all characters | + | Changes the way input from the user is displayed. When ON, all characters typed will be converted to uppercase. |
- | typed will be converted to uppercase. | + | |
- | DISPLAYFILE < | + | |
eg: DisplayFile TEST | eg: DisplayFile TEST | ||
Line 419: | Line 294: | ||
- | EXEC < | + | |
eg: Exec " | eg: Exec " | ||
- | Execute a shell. It is identical to function 7. Note that you MUST use | + | Execute a shell. It is identical to function 7. Note that you MUST use quotes (") if the command contains any spaces. |
- | quotes (") if the command contains any spaces. | + | |
- | LISTANSWER < | ||
+ | LISTANSWER < | ||
eg: ListAnswer 4 | eg: ListAnswer 4 | ||
Line 434: | Line 306: | ||
- | MENUCMND <num> [data] | + | |
eg: MenuCmnd 11 " | eg: MenuCmnd 11 " | ||
- | Execute any menu command. If the data field contains spaces, you MUST use | + | Execute any menu command. If the data field contains spaces, you MUST use quotes ("). |
- | quotes ("). | + | |
- | WAITENTER | ||
+ | WAITENTER | ||
eg: WaitEnter | eg: WaitEnter | ||
Line 454: | Line 323: | ||
- | Prompts the user for a name (or part of a name) and goes looking for it | + | Prompts the user for a name (or part of a name) and goes looking for it in the name fields of USERS.BBS. If the user doesn' |
- | in the name fields of USERS.BBS. If the user doesn' | + | |
- | he presses < | + | |
- | uses a built-in "fuzzy search" | + | |
- | users even if you misspell their name. | + | |
Line 467: | Line 332: | ||
- | Displays information about the current time, time online, remaining time, | + | Displays information about the current time, time online, remaining time, etc. |
- | etc. | + | |
Line 476: | Line 340: | ||
DATA: < | DATA: < | ||
- | Displays an ANS/ | + | Displays an ANS/ |
- | press < | + | |
Line 524: | Line 387: | ||
Example: "Ask /Q" | Example: "Ask /Q" | ||
- | This will ask the user if they want to enable or disable screen | + | This will ask the user if they want to enable or disable screen clearing and ProBoard will not display: " |
- | | + | |
- | | + | |
- | Note: Leaving the data field blank is the same as specifying the " | + | Note: Leaving the data field blank is the same as specifying the " |
- | | + | |
Line 537: | Line 397: | ||
DATA: < | DATA: < | ||
- | Allows the user to decide whether scrolling should pause when the screen | + | Allows the user to decide whether scrolling should pause when the screen is full. |
- | is full. | + | |
In the data field, you can enter these parameters: | In the data field, you can enter these parameters: | ||
Line 552: | Line 411: | ||
Example: "Ask /Q" | Example: "Ask /Q" | ||
- | This will ask the user if they want to enable or disable the More? | + | This will ask the user if they want to enable or disable the More? prompt, and ProBoard will not display: "Page Pausing is now enabled/ |
- | | + | |
- | | + | |
- | Note: Leaving the data field blank is the same as specifying the " | + | Note: Leaving the data field blank is the same as specifying the " |
- | | + | |
┌───────────────────────────────────────────────────────────────────────┐ | ┌───────────────────────────────────────────────────────────────────────┐ | ||
Line 578: | Line 434: | ||
Example: "Ask /Q" | Example: "Ask /Q" | ||
- | This will ask the user if they want to enable or disable ANSI, and | + | This will ask the user if they want to enable or disable ANSI, and ProBoard will not display: "ANSI codes enabled/ |
- | | + | |
- | Note: Leaving the data field blank is the same as specifying the " | + | Note: Leaving the data field blank is the same as specifying the " |
- | | + | |
Line 590: | Line 444: | ||
DATA: < | DATA: < | ||
- | Searches all the message areas for messages addressed to the user that | + | Searches all the message areas for messages addressed to the user that have not yet been received by him/ |
- | have not yet been received by him/ | + | |
- | new mail, which the user does not have read access to, it will inform the | + | |
user, and the SysOp. | user, and the SysOp. | ||
This function also checks for personal files addressed to the user. | This function also checks for personal files addressed to the user. | ||
- | Specifying the [/F] option will force ProBoard to check only for new | + | Specifying the [/F] option will force ProBoard to check only for new personal files. |
- | personal files. | + | |
- | Specifying the [/M] option will force ProBoard to check only for new | + | Specifying the [/M] option will force ProBoard to check only for new personal mail. |
- | personal mail. | + | |
ProBoard will also find mail addressed to a users alias. | ProBoard will also find mail addressed to a users alias. | ||
Line 611: | Line 461: | ||
DATA: < | DATA: < | ||
- | Allows the user to read a message. | + | Allows the user to read a message. |
- | ranging from 1 to 10,00), then only messages from message area < | + | |
- | be read. If <*> is specified, only messages from the active area can be | + | |
- | read (refer to the goto/gosub menu functions and to function 49). If <0> | + | |
- | is specified, only messages from areas selected in the combined boards | + | |
- | can be read. When reading messages in combined message areas, messages | + | |
- | are read "per area", not in the order of the message number. | + | |
The user has several options when reading messages: | The user has several options when reading messages: | ||
| | ||
- | |||
| | ||
- | + | New : New messages not read by the user. Messages are read per area. If you have new messages in Area 1 and 5, ProBoard will first show all new messages in Area 1, then all new messages in Area 5. | |
- | New : New messages not read by the user. Messages are read | + | |
- | | + | |
- | | + | |
- | | + | |
| | ||
- | |||
| | ||
- | |||
When a message is read, the user has the following options: | When a message is read, the user has the following options: | ||
| | ||
- | |||
| | ||
- | |||
| | ||
- | |||
| | ||
- | |||
| | ||
- | + | Reply : Reply to this message. | |
- | Reply : Reply to this message. | + | |
- | | + | |
- | | + | |
- | | + | |
| | ||
the next message (if any). | the next message (if any). | ||
- | |||
| | ||
- | + | Forward | |
- | Forward | + | |
- | | + | |
| | ||
- | |||
| | ||
- | |||
| | ||
- | |||
+ / - : Show the next/ | + / - : Show the next/ | ||
- | + | Original | |
- | Original | + | |
- | | + | |
┌───────────────────────────────────────────────────────────────────────┐ | ┌───────────────────────────────────────────────────────────────────────┐ | ||
Line 716: | Line 537: | ||
Optional parameters: | Optional parameters: | ||
- | ──────────────────── | ||
/L The user will be logged off after writing this message. | /L The user will be logged off after writing this message. | ||
- | |||
/N Writes a netmail message to the destination address specified. | /N Writes a netmail message to the destination address specified. | ||
This could also be used to send netmail to a UUCP gateway. | This could also be used to send netmail to a UUCP gateway. | ||
- | |||
/T The " | /T The " | ||
It is not necessary to use quotes (") when the username does | It is not necessary to use quotes (") when the username does | ||
not contain spaces. | not contain spaces. | ||
- | |||
/S The subject of the message is automatically specified. | /S The subject of the message is automatically specified. | ||
not necessary to us quotes (") when the subject does not | not necessary to us quotes (") when the subject does not | ||
contain spaces. | contain spaces. | ||
+ | | ||
Examples: | Examples: | ||
- | ───────── | ||
- | |||
/ | / | ||
Fidonet node number 1:282/30. | Fidonet node number 1:282/30. | ||
- | |||
/ | / | ||
- | |||
/ | / | ||
- | |||
/ | / | ||
already filled in. The user will not be able | already filled in. The user will not be able | ||
Line 792: | Line 604: | ||
a) < | a) < | ||
- | |||
Filename + date + size + description will be displayed in the | Filename + date + size + description will be displayed in the | ||
appropriate colors. | appropriate colors. | ||
- | |||
- | |||
b) <+> < | b) <+> < | ||
- | |||
The <+> will cause the description to be placed at the same | The <+> will cause the description to be placed at the same | ||
horizontal cursor position and in the same color as the description | horizontal cursor position and in the same color as the description | ||
from (a). This line will be displayed when searching for files. | from (a). This line will be displayed when searching for files. | ||
- | |||
- | |||
c) <!> < | c) <!> < | ||
- | |||
The description will be placed at the left of the screen, in the same | The description will be placed at the left of the screen, in the same | ||
color as the descriptions above. This line will be displayed when | color as the descriptions above. This line will be displayed when | ||
searching for files. | searching for files. | ||
- | |||
- | |||
d) <;> < | d) <;> < | ||
- | |||
Same as in (c), but the color is white. | Same as in (c), but the color is white. | ||
- | |||
- | |||
e) < | e) < | ||
- | |||
Same as in (d), but this line will NOT be displayed when searching | Same as in (d), but this line will NOT be displayed when searching | ||
for files. | for files. | ||
- | + | | |
Example: | Example: | ||
Line 835: | Line 633: | ||
| | ||
| | ||
- | Best BBS program in the world [c1] | + | Best BBS program in the world [c1] |
| | ||
(made possible by Burger King in the USA) [c2] | (made possible by Burger King in the USA) [c2] | ||
| | ||
- | [c1] stands for color 1, [c2] stands for color 2. | + | |
If a file area is configured as being CD-ROM, the file listing should | If a file area is configured as being CD-ROM, the file listing should | ||
Line 872: | Line 670: | ||
| | ||
< | < | ||
- | |||
' | ' | ||
| | ||
Line 878: | Line 675: | ||
The parameter < | The parameter < | ||
+ | (*) | ||
| | ||
| | ||
Line 886: | Line 683: | ||
Examples: | Examples: | ||
+ | (*) | ||
| | ||
* -C All non-CD-ROM areas. | * -C All non-CD-ROM areas. | ||
Line 897: | Line 694: | ||
You can also specify several other parameters: | You can also specify several other parameters: | ||
- | ────────────────────────────────────────────── | ||
- | |||
- | /A .......................... Allows the user to download ANY file | ||
- | accessible by DOS. When using this option, | ||
- | the full path and filename must be | ||
- | specified. | ||
- | remote SysOps. | ||
- | |||
- | / | ||
- | but the file < | ||
- | sent to the user (useful for textfiles | ||
- | describing all the files on the BBS). | ||
- | Parameter < | ||
- | path name. (eg. / | ||
- | be combined with the </T> option (see | ||
- | below). | ||
- | |||
- | / | ||
- | The following example would download the | ||
- | file PB_220.ZIP directly from file area | ||
- | #13. e.g. / | ||
- | |||
- | / | ||
- | < | ||
- | |||
- | /I .......................... Ignore DL kbytes. | ||
- | |||
- | / | ||
- | |||
- | / | ||
- | format for each line is: <D/U> < | ||
- | < | ||
- | |||
- | /N .......................... No log. Don't log anything. | ||
- | |||
- | |||
- | /P .......................... Download all personal files for the user. | ||
- | |||
- | /Q .......................... Start download right away without prompting | ||
- | the user. You must use the /F= and the /K= | ||
- | parameters so ProBoard knows what file to | ||
- | send, using what protocol when using this | ||
- | option. | ||
- | |||
- | |||
- | /T .......................... Allow the user to download the specified | ||
- | file without checking the users remaining | ||
- | time left. Refer to "Free Files" for more | ||
- | details. | ||
- | download the latest version of ProBoard and | ||
- | you don't care about the time it takes or | ||
- | how much time they have left. In the data | ||
- | line put the path and file name followed by | ||
- | the </T> parameter. | ||
- | this is as follows: | ||
- | C: | + | /A .......................... Allows the user to download ANY file |
+ | accessible by DOS. When using this option, | ||
+ | the full path and filename must be | ||
+ | specified. | ||
+ | remote SysOps. | ||
+ | / | ||
+ | but the file < | ||
+ | sent to the user (useful for textfiles | ||
+ | describing all the files on the BBS). | ||
+ | Parameter < | ||
+ | path name. (eg. / | ||
+ | be combined with the </T> option (see | ||
+ | below). | ||
+ | / | ||
+ | The following example would download the | ||
+ | file PB_220.ZIP directly from file area | ||
+ | #13. e.g. / | ||
+ | / | ||
+ | < | ||
+ | /I .......................... Ignore DL kbytes. | ||
+ | / | ||
+ | / | ||
+ | format for each line is: <D/U> < | ||
+ | < | ||
+ | /N .......................... No log. Don't log anything. | ||
+ | /P .......................... Download all personal files for the user. | ||
+ | /Q .......................... Start download right away without prompting | ||
+ | the user. You must use the /F= and the /K= | ||
+ | parameters so ProBoard knows what file to | ||
+ | send, using what protocol when using this | ||
+ | option. | ||
+ | /T .......................... Allow the user to download the specified | ||
+ | file without checking the users remaining | ||
+ | time left. Refer to "Free Files" for more | ||
+ | details. | ||
+ | download the latest version of ProBoard and | ||
+ | you don't care about the time it takes or | ||
+ | how much time they have left. In the data | ||
+ | line put the path and file name followed by | ||
+ | the </T> parameter. | ||
+ | this is as follows: | ||
A Small hint regarding free files: if you want one particular area to be | A Small hint regarding free files: if you want one particular area to be | ||
Line 976: | Line 758: | ||
** Important ** | ** Important ** | ||
- | ─────────────── | ||
ProBoard uses a highly optimized index to find your files when users want | ProBoard uses a highly optimized index to find your files when users want | ||
to download them. Be sure to run PBUTIL FI (File Index) at least once a | to download them. Be sure to run PBUTIL FI (File Index) at least once a | ||
Line 1003: | Line 784: | ||
called UPLOAD.LOG. | called UPLOAD.LOG. | ||
- | | + | |
- | | + | |
Line 1010: | Line 791: | ||
─────────────────────────────────── | ─────────────────────────────────── | ||
- | /D .......................... Do not ask user for upload descriptions. | + | |
- | + | / | |
- | / | + | / |
- | + | / | |
- | / | + | format for each line is: U O < |
- | + | /N .......................... No log. Do not log anything. | |
- | / | + | /P .......................... Upload private files. |
- | format for each line is: | + | contains "/ |
- | + | personal file to another user. In this | |
- | U O < | + | case the upload will be placed in the |
- | + | private upload directory (specified in | |
- | /N .......................... No log. Do not log anything. | + | ProCFG). |
- | + | /Q .......................... Start upload right away, without prompting | |
- | /P .......................... Upload private files. | + | the user. You must specify a / |
- | contains "/ | + | this to work. |
- | personal file to another user. In this | + | |
- | case the upload will be placed in the | + | |
- | private upload directory (specified in | + | |
- | ProCFG). | + | |
- | + | ||
- | /Q .......................... Start upload right away, without prompting | + | |
- | the user. You must specify a / | + | |
- | this to work. | + | |
Line 1154: | Line 926: | ||
" | " | ||
- | Note: Leaving the data field blank is the same as specifying the " | + | Note: Leaving the data field blank is the same as specifying the " |
- | | + | |
Line 1254: | Line 1025: | ||
Valid area selection parameters are: | Valid area selection parameters are: | ||
- | ──────────────────────────────────── | ||
X Current Area | X Current Area | ||
Line 1265: | Line 1035: | ||
Other valid parameters are: | Other valid parameters are: | ||
- | ─────────────────────────── | ||
- | /MG ......................... Makes the user select a message group if | + | |
- | they haven' | + | they haven' |
- | + | / | |
- | / | + | areas belonging to message group < |
- | areas belonging to message group < | + | /N .......................... ProBoard will run even faster since it will |
- | + | not check for waiting mail (no " | |
- | /N .......................... ProBoard will run even faster since it will | + | displayed indicating new mail) if you |
- | not check for waiting mail (no " | + | specify this parameter. |
- | displayed indicating new mail) if you | + | if your BBS has many large message areas, |
- | specify this parameter. | + | in particular, Squish or JAM. Remember, |
- | if your BBS has many large message areas, | + | ProBoard can be configured for 10,000 |
- | in particular, Squish or JAM. Remember, | + | message areas so a full " |
- | ProBoard can be configured for 10,000 | + | each area can be time consuming. |
- | message areas so a full " | + | |
- | each area can be time consuming. | + | |
Examples: | Examples: | ||
- | ───────── | + | (*) |
* -E All non-echomail areas | * -E All non-echomail areas | ||
1-20 50-60 Areas 1..20 and 50..60 | 1-20 50-60 Areas 1..20 and 50..60 | ||
Line 1312: | Line 1079: | ||
Valid parameters are: | Valid parameters are: | ||
- | ───────────────────── | + | |
- | /H .......................... Show the user's handle (alias) instead of | + | their real name. |
- | their real name. | + | < |
- | + | ||
- | < | + | |
Line 1358: | Line 1123: | ||
Valid parameters are: | Valid parameters are: | ||
- | ───────────────────── | ||
- | /H .......................... Will show the users handle (alias) instead | ||
- | of their real name to the users on other | ||
- | nodes, when prompting them to engage in a | ||
- | chat. | ||
- | < | + | /H .......................... Will show the users handle (alias) instead |
- | their alias when prompting users on other | + | of their real name to the users on other |
- | nodes to engage in a chat. | + | nodes, when prompting them to engage in a |
+ | chat. | ||
+ | | ||
+ | their alias when prompting users on other | ||
+ | nodes to engage in a chat. | ||
Line 1379: | Line 1143: | ||
Valid parameters are: | Valid parameters are: | ||
- | ───────────────────── | ||
- | |||
- | /FG ......................... Makes a user select a file group if they | ||
- | haven' | ||
- | |||
- | /FG=0 ....................... Makes the user always have to select a file | ||
- | group. | ||
- | / | + | /FG ......................... Makes a user select a file group if they |
- | group number < | + | haven' |
+ | /FG=0 ....................... Makes the user always have to select a file | ||
+ | group. | ||
+ | | ||
+ | group number < | ||
Line 1452: | Line 1213: | ||
Important | Important | ||
- | ───────── | + | |
Any PEX files that were written for versions of ProBoard prior to 2.00 | Any PEX files that were written for versions of ProBoard prior to 2.00 | ||
will have to be recompiled with the new 2.1x SDK before they can run | will have to be recompiled with the new 2.1x SDK before they can run | ||
Line 1495: | Line 1256: | ||
now enabled/ | now enabled/ | ||
- | Note: Leaving the data field blank is the same as specifying the " | + | Note: Leaving the data field blank is the same as specifying the " |
- | | + | |
Line 1522: | Line 1282: | ||
now enabled/ | now enabled/ | ||
- | Note: Leaving the data field blank is the same as specifying the " | + | Note: Leaving the data field blank is the same as specifying the " |
- | | + | |
Line 1535: | Line 1294: | ||
<graph type> | <graph type> | ||
- | |||
/ | / | ||
- | |||
/ | / | ||
quotes) is replaced by the number of days/weeks | quotes) is replaced by the number of days/weeks | ||
Example: | Example: | ||
- | ──────── | + | |
Hourly /N=14 / | Hourly /N=14 / | ||
Speed /N=60 / | Speed /N=60 / | ||
Line 1594: | Line 1351: | ||
enabled/ | enabled/ | ||
- | Note: Leaving the data field blank is the same as specifying the " | + | Note: Leaving the data field blank is the same as specifying the " |
- | | + | |