<page-footer>
Page <page#>
<page-header>
SYSTEM UTILITIES                LOG-ON MESSAGE UTILITY                 PRIME 2.2
<page-break>System Log-On Messages


Fig. 11.0

1) Prelog on Msg....... Off  Msg#0
2) Post log on Msg..... Off  Msg#0
3) Pre new user Msg.... Off  Msg#0
4) Post new user Msg... Off  Msg#0

S)ave Changes  L)oad Parms   Q)uit


     This utility will allow you to set the system up to read special messages in certain situations.  These special messages may be created by using the Special Editor found in the [*] SysOp Menu on your system.  These messages MUST be stored in the COMMON directory; #5.

     1) Pre log on Msg.
          Setting the Pre Logon Msg. on, and entering a message number, will result in that message being read as soon as someone connects to the system.  This file will be read before the system asks for the password.

     2) Post log on Msg.
          The message entered here will be read just before the system checks for E-Mail.  This is a good spot to use for any of your system announcements, which is just general notes you want to get to all your users at once.

     3) Pre new user Msg.
          This message will be read right after a caller enters the New command to receive a password.  This is a good spot to put a general overview of your system.

     4) Post new user Msg.
          This message is read directly after the password is issued.  This is an excellent spot for you to explain your system rules to your new users.

Make sure you Save your changes to make them effective.

<page-header>
SYSTEM UTILITIES                 GLOBAL TEXT EDITOR                    PRIME 2.2
<page-break>Edit Global Text


Fig 12.0

                    [V]iew Messages        [E]dit Messages
                    [L]oad Message File    [S]ave Message file
                    [Q]uit To Sys Util


     This utility will allow you the ability to edit a few "Global Text" elements.  These text elements are requests for, or responses to input.  Your system will give these responses fairly often so they are considered to be global.  There are 13 text elements.  They are listed next.

     0 - cmds=
     1 - Command (?=Menu)
     2 - Invalid Command
     3 - [RETURN] to Continue
     4 - Is this correct? (Y/N):
     5 - X = Abort    ^S = Pause
     6 -         
     7 - Thanks for Calling!@Please call again soon!
     8 - [Q]uit to Basic@[U]ser Utilities@[S]ystem Utilities@[R]eturn to the program@@Command?
     9 - Hello@@SysOp Breaking in to Chat@@
    10 - Please Wait...
    11 - You have gone too long without input.  Goodbye!@
    12 - I'm Sorry, your time has expired for this call.@

<page-header>
SYSTEM UTILITIES                   NEW USER PARMS                      PRIME 2.2
<page-break>New User Parms


Fig. 13.0

1) New User Call Limit (CL) .... 1
2) New USer Class Code (CC) .... *
3) New User EXpert level (EX) .. 0
4) New User Time Limit (TL) .... 1
5) New User Telex (TX) ......... 0

6) New User Security level        
              1111111111          
    01234567890123456789          
    BAAAAAAAAAAAAAAAAAAA          

S)ave Changes  L)oad Parms   Q)uit


     This utility will allow you to set the default parameters you want to give to your new users.  These are the parameters that will be given to your users WHEN THEIR PASSWORD IS ISSUED.  The ONLY exception to this rule is the Byte Limit.  The Byte Limit is not in effect until the second call.

     Make sure you Save your changes before Quitting the utility.

<page-header>
SYSTEM UTILITIES                   "WHERE" FILE                        PRIME 2.2
<page-break>Update Where File


     The "Where" file is used by the system to keep track of various items.  It is IMPORTANT that you Update the "Where" file ANY TIME you change the name or location of a BOARD, or MENU.  It is a good idea to Update the "Where" file anytime you make ANY changes dealing with the disk location of a major system item.

     This is the ONLY method of making the change permanent.



LOG/BACK OUT


     This command will "back" you out of the BBS to the "waiting for call" screen without logging you off.  It is a fast way to terminate your activities in the system utility area.

<page-header>
SYSTEM UTILITIES                USER FILE MAINTENANCE                  PRIME 2.2
<page-break>User File Purge & AppleWorks Utility


Fig 14.0

                                [1] Print Appleworks Text File
                                [2] Purge Old Users
                                [Q] Quit To System Utility


     This utility will aid you in maintaining your User File.  There are currently options to do two things: Print a text file that is compatible with the Appleworks Database, and an option to Purge the users who haven't called your system recently.


     1) Print Appleworks Text File
          This option will cause the system to read your User File, and write it back into a Text File that will be compatible with the Appleworks Database.  The program will develop a text file with thirty (30) data fields.

          The fields in the compatible file are structured in the same order as they are in the regular User File.  You will need to structure your Appleworks Database in the same order.  The file created as a result of running this, USER.ATX, option can be found on directory number zero, the USERS directory.

     2) Purge Old Users
          This utility will ask for the Last Date you wish a user to have called by, in order for that user not to be purged.  The system will then search the User File for users who haven't called since the date you entered.  When such a user is found, you are asked if you wish to close that user's account.  If you answer yes, then that record is marked as deleted, and the system moves on to the next record.  If you should answer no, then the system will move to the next record without deleting the user.

<page-header>
MENU AND BOARD UTILITY                OVERVIEW                         PRIME 2.2
<page-break>Menu & Board Utilities


     The Board and Menu utilities operate in pretty much the same manner.  For this reason, the two sections will be examined together, with exceptions noted for commands that pertain only to one utility in particular.  The chapter dealing with Command Editing is rather long, and you may wish to skip over it until you are actually ready to edit or add a command.  Hopefully, by following the page headers, you will be able to navigate your way through this section of documentation, as due to the way the commands fall on the menu, this section is rather broken up.

     Both of these utilities are actually internal menu generators; the Board utility simply provides a few more options for storage allocation and special features.  The security scope of the menus generated with these utilities presents an extremely wide spectrum of options to the Sysop.  Whole series of menus and boards may be created, and the access restricted to just those callers that you desire to use them.  Other people who use your system will not even know these special sections and boards exist, as the Menu security system makes the access command totally invisible.  Even more options are provided in the Board utility for you to set up special security access so that you may authorize a "Remote" sysop to control that board.

     The internally-generated menus will conform to whatever width the user has set their display screen to be, automatically, while the caller is using the system.  This assures your users of an attractive, readable menu.  Menus are displayed in columns of 40.  A standard 80 column display device would therefore get 2 menu columns, repeated text would be 79 columns wide.

     Menu construction is based on a "level" type system.  Each menu may have up to nine separate levels, with each level actually being another completely different menu.  There are command routines within the system that may be assigned which will allow your users to "Flip" between these menu levels.  By using this "Leveling" feature, you can block entire menus from select users.  A common practice among sysops is to place all of the bulletin boards in a separate menu.  With PRIME, we have made your Main Menu Level 0, and your Boards Menu Level 1.  We have also made your General Files Menu Level 2.

     Menus are constructed using three elements.  They are: Action Commands, Borders, and Null Fields.  Action Commands are the options you want to present to your users.  Borders are displayed anywhere that you want them within a menu.  Null fields are used to separate the menu levels.

     It is also possible for you to use "External" menus with the PRIME system.  External menus are menus that are generated by an outside source, such as the Special Editor found on the [*] SysOps Menu on your system.  You may make menus with things like "text graphics" in them, you can also use command descriptions that are longer than 40 characters with the external menus.  If you make an external menu, it must be stored on the same prefix that its corresponding internal menu is stored on (normally prefix number 0), and must be named M.FIL.#.#, with # representing a number between 0 and 63.  Should you decide to use External menus, remember that they will be displayed EXACTLY as created.  Commands will not be blocked from those that do not have access, and the display will not conform to the remote user's screen if it is not the same width as the menu.

NOTE:  If you choose to use External menus, you must STILL make an Internal menu for the system.  The system will use the INTERNAL menu as its operating guide.  All Commands in the Internal menu MUST match those in the External menu.  All security provisions set in the Internal menu will apply to the External menu.

     In the coming chapters the options presented you in the Board & Menu utilities will be examined.  Differences will be noted as follows:

     *= Board Command Only
     #= Menu Command Only

     All other commands will apply to both utilities and will operate in the same manner in both places.

<page-header>
MENU & BOARD UTILITY                 MAINTENANCE                       PRIME 2.2
<page-break>Menu & Board Maintenance Options


Fig. 15.0

          [L]ist Existing Board / Menu        [E]dit a Board / Menu
          [C]reate a New Board / Menu         [D]elete a Board / Menu
          [M]anually Edit Board / Menu list   [Q]uit/rtn to Main Utility Menu 
        * [R]eset Msg Board Pointers


     You will be presented with these same five options (with the exception of the Reset Msg Board Pointers) when you choose either [B]oards or [M]enus from the Main System Utility menu.  The text on the menu will reflect your actual choice, either Boards or Menus.  Since the Edit option is fairly detailed, it will be skipped over, and documented last.

COMMANDS:

     [L]ist Existing Board / Menu
          After pressing this command, the appropriate list of Board or Menu numbers, names, and disk prefixes will be displayed.  This is an easy method for you to find out the name-number of a Board or Menu that you wish to edit.

     [C]reate a New Board / Menu
          These utilities will create new Boards or Menus.  These are the two basic types of menus the system uses: a Board Menu and a System Menu.  For example, your Main menu is a System Menu, while the options for your General board are found on a Board Menu.  Since each System Menu has nine levels, it is rarely necessary to Create a new System Menu.  You should use all available levels in a System Menu before creating a new System Menu.

          When you create a board or menu, the system will ask you for a number-name, and a disk prefix number for the prefix you desire to store either the Board or Menu on.  The system will then create the mold for your Board or Menu.  The system uses one of two files, depending on what type menu you are creating, these files are stored in the /UTILITY prefix, and are called MNU.33, and BRD.33.  It is recommended that you edit each of the these files first, so that you may set the global standards you want on your system.  If this is done, there is no need for you to re-edit these standards on each individual Board or Menu as you create it; you will only need to change the borders and the security provisions.

<page-break>     [D]elete a Board / Menu
          This utility option will delete a Board or Menu.  If you are deleting a Board, the utility will also remove all the message files from the disk.

          The system will prompt you for the number-name of the Board or Menu that you wish to delete.

     [M]anually edit Board / Menu list
          This option will allow you to edit the name or disk prefix of an item in the Board or Menu list.  You will be asked which item you wish to edit, you should respond with the number-name of the Board or Menu you wish to change.

          If you edit the name or prefix of any item in the Board or Menu list, make sure you Update the Where file to make your changes effective.  You must also transfer the files to the new prefix yourself, using Filer or some other utility.

     [Q]uit/rtn to Main Utility Menu
          This option will return you to the Main Utility menu.

     [R]eset Msg Brd Pointers
          This command will only operate in the Boards section.  It is designed to allow you to clean up a message board that may be experiencing errors.  It compares the actual messages stored in the B.X subdirectories to the information in the FIL.MSG.  If anything is in error, it automatically corrects the trouble and saves the FIL.MSG with the updated information.

          You are given the option to manually reset one message board or allow the program to check all boards automatically.

     The next items we will take a look at are the board and menu parameter editing utilities.  Using these utilities you can customize each of your boards to have the characteristics you desire.
<page-header>
MENU & BOARD EDIT                   EDIT OPTIONS                       PRIME 2.2
<page-break>Edit MENU / Board


Fig. 16.0

                          [C]ommands          [P]rompts
                          [T]ypes (Menus)     [S]ave File
                          [W]ho's Who         [Q]uit
                          [1] Print Menu    # [F]eedBack List
                        * [2] Globals

*= Board Edit Only
#= Menu Edit Only 

     These are the options presented you in the Board and Menu Edit utilities.  You may reach these utilities by selecting "E", from the Board or Menu Maintenance menu to Edit a Board or Menu. In order for you to make use of any of the Print options, your printer interface must be in slot number one.  The commands are listed beginning in the next chapter.

<page-header>
BOARDS & MENU EDIT                    COMMANDS                         PRIME 2.2
<page-break>Commands


Fig. 17.0

 Num Typ Level         Command

   4 Bdr Lvl:0  =                  
   5 Bdr        -<Your Board Name>-
   6 Bdr           Main Menu       
   7 Bdr         ^S=Pause  X=Abort 
   8 Bdr        -                  
  10 Cmd        [B]oards Menu      
  11 Cmd        [P]ost Office      
  12 Bdr        -
  13 Nul
  14 Bdr Lvl:1  =

[M]ove  [C]opy  [I]ndex   [N]ew Screen [S]wap  [Q]uit  [L]evel   [P]os To Lvl
[E]dit  [A]dd   [D]elete  [R]eplace


     As previously explained, commands are structured from one of three elements: Borders, Null Fields, and Commands.  All three of these are considered a menu command by the system.  Borders and Nulls are acted on internally, and Commands are acted on based upon the user's input.  You may place borders and commands throughout your menus, but Nulls are reserved for separating Menu Levels.  When you first insert a Command, it is of type Nul; you must then Edit that command, or your menu will end at that spot.  Note, if the Command display says [N]ull, this is not a Null level separator.  This is instead a Null Command, which simply has no function.  A Null separator is denoted by a Nul in the Type category.  Please don't confuse the two types of Nulls.

NOTE:  Movement through the commands is accomplished by using the following keys.

[.] The Period will move the cursor DOWN Five command elements.
[,] The Comma will move the cursor UP Five command elements.
[>] The Greater-Than symbol will move the cursor DOWN Ten command elements.
[<] The Less-Than symbol will move the cursor UP Ten command elements.

    Additionally, the UP and DOWN arrow keys will move the cursor up or down one element at a time.

OPTIONS:

[M]ove
     This option will move an element from one position in the menu to another.  You will be prompted for the element to move, and it's new location.

<page-break>[C]opy
     This option will duplicate another element, or make a copy of it.  You will be prompted as to which element you want to copy, and where you want the copy INSERTED into the menu.  Don't confuse this with the REPLACE option.

[I]ndex
     This option will allow you to set the Index Bit Lock required to access these elements without having to manually edit each one.  Simply select 0-19.

[N]ew Screen
     Since these options are "HOT" (interruptable), you may want to clear the screen.  This will cause the screen to clear and it will then redisplay the current elements.

[S]wap
     This option will allow you to swap two elements for one another.  You will be prompted for each element and they will then be swapped.

[Q]uit
     This option will return you to the Board / Menu Edit menu.

[L]evel
     This option will allow you to set the start of a Menu Level.  The system will ask for the level number that you wish to set, and then for element number where you want the level to be located.  The system will then place the level start marker in the designated spot.

     Note:  The command that precedes the level Start marker must be a Nul separator.  The Level Start Marker DOES NOT start your menu level, the Nul separator does!

     Remember, a menu level is actually another menu.  Each level is displayed independently.

[P]osition To Level
     This option sets up the top of the element display you see on the screen.  It sets you at the level (0-9) of the menu you specify.  Don't confuse this with the [L]evel option.

[E]dit
     This command presents you with some pretty extensive options. This makes it necessary for the command to be explained in its own chapter.  That chapter will follow this one.

<page-break>[A]dd
     This option will allow you to add new commands to the system.  When you add (or insert) a command, the system will ask you which menu element you would like to add.  A Null separator will be placed in the spot directly above the existing element.  All other elements will be shifted down one spot.

[D]elete
     This option will allow you to remove a command from the menu.  You will be asked which menu element you wish to remove.  The system will then remove that element, and shift all other elements up one spot.

[R]eplace
     This option lets you replace an existing element with another existing one.  Let's say you wanted element 102 to be exactly the same as element 4.  You select the replace option, specify 102 and 4.  The program then replaces the element with the one you specified.

     In the next chapter the Edit option that was skipped over is reviewed.  This option is very extensive so you may want to grab a cup of coffee.
<page-header>
MENU & BOARDS EDIT                 EDIT COMMANDS                       PRIME 2.2
<page-break>Edit Commands


Fig. 18.0

                                 ** Edit Command #4 **

                                 [T]ext    = -
                                 [P]rompt  = (Border)
                                 [V]iew    = A
                                 [A]ccess  = A
                                 [I]ndex   = 0
                                 [S]ysop   = Z

                                 [C]md Type   = 0:Repeated Text
                                 [L]vl of Cmd = 0:Invalid Cmd! 
                                 [N]ame    = 0
                                 [D]k Pfx  = 0:/BBS.MAIN


     After you have selected a command to edit from either the Board or Menu Commands menu, a menu similar to the one above will be displayed.  It is with this utility that you set all parameters that deal with a command.  There are three types of commands, with each type having several levels (or internal routines).  The following text will examine each of the above elements.

[T]ext
     The Text element should contain the exact text that you want displayed on the menu.  Your text MUST include the prompt character or no prompt  will be displayed as part of the menu.  Your Text element is limited to thirty-nine (39) characters in length.

[P]rompt
     The Prompt element should contain the same character that you assigned as the prompt in the Text element.  The prompt is the Key the user must press to access the command.

     Entering a SPACEBAR as the prompt will distinguish this command as a BORDER, and not an action command.  The Text element will be displayed as part of the menu, but the rest of the command elements will serve no function.

NOTE:Entering the "]" character in either the View or Access will make the command inactive, and invisible even to the sysop.

<page-break>[V]iew
     This View element works in conjunction with the Index Byte to provide command security.  This element holds the value that the user must have in the indicated Index Byte in order to see this command on the menu.

     Example:  Assume you are setting up a command to access a board for Apple computer users.  You set the Index Byte to 1.  Now, you set the View element to a value of "B".  This means that in order for a user to be able to see this command, that user must have at least a "B" in his Index Byte 1.

[A]ccess
     The Access element, like the View element, works in conjunction with the Index Byte.  This element is set in the same manner as the View element, and controls actual Access to the command function.  It is possible, then, for you to make a command visible, but still not allow the user to have access.

     Example: We have your special Apple users board again.  You have set the Index Byte to "1", and have set the View to "B".  Now, to make it so that a user with a "B" in their Index Byte #1 can't access this board, you set the Access Element to "C".  A user that has the default "A" in their #1 Index Byte will not know that this board exists at all, a user that has a "B" in their #1 Index Byte will be able to see the command, but will not be able to use it, and a user with a "C" in their #1 Index Byte will have Normal access.  However, you would normally set both View and Access to the same value.

[I]ndex
     The Index element should hold the number of the Index Byte you want to use for security control with a particular menu command.

     You should think of the Index as a pointer to one of the 20 individual security control elements.  Each of the elements can hold a value of "A-Z".  Every command option on the system is controlled by the settings of one of the security elements.  Since you are a Sysop, all of your control elements have a value of "Z".  Each user's security control settings are stored permanently in the user's record on the system.

     Using the INDEX setting of each command you can "point" the system toward the control element that you wish to use to regulate the command's operation.

     Later on in this manual you will find a chapter devoted to the System User Utility, which will tell you how to set the corresponding Index Byte in the user record of each user you want to be able to see or use the command.  You should place the same value in each user's record that you have placed in the View or Access elements of the command if you wish the user to be able to use the option.

     If you wish to set up a general command that everyone can View and Access, just set the Index Byte to 0, and put values no higher than "B" in the View and Access elements.

     On some types of Boards it is necessary, for one reason or another, to set security so a user with normal security settings can Read a board, but not Post on it.  This action is simple and easy with PRIME.  Just use the Board utility, and set the appropriate Index Values for View and Access on the Read and Post commands.

[S]ysop
     The Sysop element should hold the Security Value (A-Z) that a user should have in order to have Sysop Access to this command.

     Sysop Access is particularly useful in the Board area.  By setting the appropriate values in the Delete, Toggle Edit, Edit, Toggle Private, and Save Changes commands, you can set the system so that a "Remote" assistant sysop can take care of the board without any intervention on your part.

     Example: Again let's use the Apple board.  Remember, you have set the View to a value of "B", you have set the Access to a value of "C", and we will now set the Sysop element to a value of "E".  Also, you have set the Index element to a value of "1".  We will save this command, and go back to the Main System utility menu.  From there, choose the Board option, and then Edit the Apple board.  Once back in the Edit mode for the Board, set up the same security on all the board commands.  You should set the Index values for both View and Access to the same level as the Sysop element for the Toggle Private, Toggle Edit, Toggle Protect, and Save Changes commands, so only the "remote" can see them.  You have now set this board so a remote sysop may run it.  The remote will be able to delete, edit, and  toggle the special features for any message ONLY on this board.

[C]md Type
     There are two series of Command Types in the PRIME system.  The first series corresponds with a Border command, and the other series works with Action Commands. There are four command types within the Border series, and three different Command types within the Action series.  The two series of Command Types are listed next.

<page-break>NOTE:  Border mode is signified by entering the [SPACEBAR] as the Prompt Character.
Series    Type   Description
------    ----   ----------------------

Border      0    Repeated Text:  This text element will be repeated all the way across the user's screen.

Border      1    Centered Text:  This text will be centered on the user's screen when displayed.

Border      2    Literal Text:  This text will be displayed from the left margin of the user's screen, exactly as written.

Border      3    Null Text:  This will display a blank line in the menu.

Command Type 1   System Command:  There are eighteen System Command Levels that do such things as page the sysop, load a board, etc.  All commands that don't deal directly with a board are considered to be System Type commands.

Note:  When editing or creating System Menus, you may only use commands that are System Type.  System Type commands may, however, be used in Board Menus.  Level 2 Command Types may ONLY be used in BOARD Menus, they MAY NOT be used in System Menus.


Command Type 2   Main Board Command:  There are nine Levels of Board commands.  Main Board commands consist of such options as Post Msg and Delete Msg.

Command Type 3   Run System Programs:  There are eight levels of System Program commands in the PRIME system.  System Programs are things like the download program, Special Editor, and the remote system utilities.

     Now, think back to the Command Edit Utility, and let's examine the Command Level option.

[L]vl of Cmd
     Command Levels work in conjunction with the Command Types that were just examined.  For each Type of command, there are several Command Levels.  Command Levels are actually your way of accessing, or "calling", PRIME's internal routines.

     In the next few pages you will find the function of each Command Level, classified by Command Type.

<page-break>NOTE: Type 1 commands may be used in any type of menu, Board or System.


Type  Lvl    Desc.
----------------------

   1    1    Commands with this Type/ Level setup will cause the system to display the menu for the current section.  The NAME and DSK. PFX. elements have no effect on this command.

   1    2    Commands with this Type/ Level setup will cause the system to "Flip" to the menu level corresponding with the number in the "Name" element.  The DSK. PFX. element has no effect on this command.

             Using this command is the best method of moving through System Menu levels.  Remember, you MUST have the level number in the NAME element.

   1    3    A command with this Type/ Level setup will cause the system to execute the log off routine.  The NAME and DSK. PFX. elements have no effect on this command.

   1    4    A command with this Type/ Level setup will cause the system to execute the "Page Sysop" routine.  The NAME and DSK. PFX. elements have no effect on this command.

             Depending on how you have the Chat Status set, the system will either give a message that you are not in or it will ring the pager.  The pager will only ring once.  It makes no difference how many times the user presses the prompt key.

   1    5    Commands with this Type/ Level setup will cause the system to run an External program.  External programs must be compatible with the PRIME Amper system.  Also, External programs must be stored on the disk 
             with a file name of PRG.#, where # represents an Integer between 0 and 63.

             There are is one External program that came with your PRIME system; that program is examined in another section of this manual.

   1    6    Commands with this Type/ Level setup will cause the system to print a message that the described command is currently unavailable.  This is useful when you want to go ahead and add a command for a new board to the menu display, but maybe you haven't finished building the menus for the board yet.  This command will allow you to have the command to access your new board display on the menu, but when accessed, the user will get the described message.  The NAME and DSK. PFX. elements have no effect on this command.

   1    7    Commands with this Type/ Level setup will cause the system to read a "System" message file.  You must place the number of the message file you want read in the NAME element, and you must set the proper Disk Prefix so the system can find the file.

             Message files are created by using the Special Editor  utility to create a "System" message file.  You may also create Message files using a Text processor like Appleworks.  Also, all message files must be stored on the disk within a file named MSG.#, with # representing a number between 0 and 63.  If you are using Special Editor this is done automatically.

   1    8    Commands with this Type/ Level setup will cause the system to Load a Message Board.  You must also specify the number of the board you want to load with this command in the NAME element.  You must also specify the disk prefix where the board is located, in the appropriate element.

   1    9    Commands with this Type/ Level setup will cause PRIME to Flip to the last System Menu that was used.

             You should use this option to exit back to the main system from a bulletin board.  The user will be placed back in the same Menu Level he/she was in when they accessed the bulletin board.

             Example:  You have set up MNU.0 so that the second level contains all of your boards.  The user accesses BRD.1 from the level two menu.  If you set the "Quit" command to this type/level setup, the system will return the user to MNU.0, level two, when the user quits the board.

   1   10    Commands with this Type/ Level setup will cause the system to Load another System Menu, but unlike the previous command, the entry level will be set to 0.  Otherwise, this command operates exactly like the previously described command.  You must put the number of the menu you wish to call in the NAME element.  You must also place the proper prefix number in the appropriate element.

   1   11    Commands with this Type/ Level setup will cause the system to "Flip" back to the previous Menu Level.  The NAME and DSK. PFX. elements have no effect on this command.

             This command is rarely used in a System Menu, but rather by the Board Menus.  An example would be when a user goes back to the main Board menu from the SysOp toggles sub-menu.

<page-break>   1   12    Commands with this Type/ Level setup will cause the system to read a "System" message file.

             This command works much the same as Level 7.  The difference here is that you DO NOT need the disk prefix. The system will attempt to read the file on its current prefix.

   1   13    Commands with this Type/ Level setup will force the system to display the names you have placed in the "Who's Who" fields.  It will display a unique list for both board menus and system menus.

   1   14    Commands with this Type/ Level setup will cause the system to read a "Giant" file.  You must place the number of the file you want to read in the NAME element, and the proper prefix number in the DSK. PFX. element.

             "Giant" files may also be either Text files generated with an outside source, or they may be generated with PRIME's Special Editor.  Giant files must be stored in a file named G.FIL.#, with # representing an integer between 0 and 63.  You must set the number of the file in the Name Field, and the proper number in the Disk Prefix Field.

   1   15    Loads a board, but unlike Lvl: 8 this option will display the contents of a text file before entering the board.  This text file must be named MSG.0, and must be stored inside the BRD.# directory for the desired board.  An option has been added to the "Board Globals.1" option in the System Utility to allow you to set a level for this message.  Once you set the level, only users with a lesser value will have to read the message file.  The index byte that controls this action is the byte that allowed entrance to the board.  This would be the byte that was set in the command that accesses the board.

   1   16    This command will activate the new feedback options found in Prime.  You can edit the feedback list using the edit menu segment of the System Utility.  You can build a list of 10 remote sysops that are to receive feedback from the users.  When the user selects the command set to Type 1, Level 16, this list will be displayed and the user offered the chance to send feedback mail to one of the remotes.  Program control will then be turned over to the E-Mail editor and the user should post his/her message.  This message will contain the notice "Feedback from a User" in the subject line denoting to the recipient that it is user feedback.  Feedback is just a part of the special E-Mail section included with Prime.

             By the way, if you are using several MNU.# files for some reason, each list is independent with each menu.  This means you can have more than ten remotes that can receive feedback.

   1   17    This option will allow the user to toggle the Time Remaining display on and off.  The user's setting is always retained in their user record.  This is so the user  need not set the option with each call to the system.

   1   18    This option will allow you to run the New Message scan program.  It is designed to allow your users the ability to read new messages on your BBS with little interaction on their part.  Sort of an automation program.  See the documentation file found on the EXTRAS disk for more details.

<page-break>NOTE: The following Commands may ONLY be used in Board menus.  What actually happens to your computer's little electronic "mind" when an attempt is made to access one of these commands from within a System Menu is as of yet undetermined!  However, "Gone Fishing" would be an appropriate description of the reaction.

 Type  Lvl   Desc.
----------------------

   2    1    Commands with this setup will cause the system to go into the "Post" message mode.  The system will ask the user a couple of informational questions, and then enter the Message Editor.

   2    2    Commands with this setup will cause the system to Delete a message.  The user will first be asked for the message number of the file to delete.

   2    3    Commands with this setup will cause the system to go into the Edit mode.  The user will be asked which file to edit; they will then be placed in the Message Editor, with the appropriate file in memory.

   2    4    Commands with this setup will cause the system to enter the "Read Messages" mode.  This mode is a way for a user to read messages in a forward, reverse, or individual mode.  An option is also presented so that a user may read messages that are "New" since the user's last call to the system.

   2    5    Commands with this setup will cause the system to "Toggle" the status of the "Message Protect" for a message.  The result of the toggle will depend on the previous status setting.

   2    6    Commands with this setup will cause the system to toggle the "Private" status of a message.  The result of the toggle will depend on the previous status setting.

   2    7    Commands with this setting will cause the system to toggle the "Edit" flag.  Switching this flag will make a message editable by someone other than the person who posted it.  The result of the toggle will depend on the previous status setting.

   2    8    This command setup will cause the system to Save changes made with the previous three commands.  You MUST Save Changes to make them permanent.

   2    9    This option presents users with the opportunity to read messages that are new since the last call to the system.

<page-break>     Let's take a look now at the last Command Type available in the PRIME system.  For the most part you will find these commands exhibited on Menu Level 3, the SysOp's Menu.  All commands in Type 3 run a System Program of some nature.

Type  Lvl    Desc.
----------------------

  3    1     Commands with this Type/Level setup will cause the system to run the EMAIL.SYS system program.

  3    2     Commands with a Type/Level setup of T3, L2 will cause the system to run the RMT.SYSUTIL system program.  This option will allow remote sysops access to the Main System Utility.  A remote password, SET-SYSTEM, must be used to gain access to the utility.

  3    3     This setup will cause the system to run the SYSUSER.UTIL system program.  This program is the one that provides the SysOp with the options necessary to maintain the system user file.  This utility is quite powerful and is fully documented a little further along in this manual.

  3    4     Commands with this Type/Level setup will cause the system to run the RMT.VALIDATE system program.  This option provides remote sysops with a way to Validate new callers without actually having access to the full system user utility.

  3    5     This setup will cause the system to run the USER.UTILITY system program.  This program is the one that provides the users with the opportunity to change their alias, password, column width, and numerous other items.

  3    6     This command setup will cause the system to run the SYS.STATS system program.  This option will provide the user with some interesting statistics about your system by sorting the user file.

  3    7     This command Type/Level setup will cause the system to run the XFER.SYS system program.  This is the download section, and you will find it fully documented in Appendix C of this manual.

  3    8     Commands with this Type/ Level setup will cause the system to run an external GAME program.  Game programs must be compatible with the PRIME Amper system.  Also, Game programs must be stored on the disk with a file name of GAM.#, where # represents an Integer between 0 and 63.  Note: The numbers 0-25 are reserved for future use by SmokeSignal Software

This completes your examination of Command Levels.  Let's now return to the remaining two Command Edit options, Names and Prefixes.

[N]ame
     The Name element should hold the Integer representation of the name either you or the system has assigned to an outside function.  This is especially important for such things as running External programs, and displaying and moving around within Menu files.  For most functions, the "Name" will be an Integer between 1 and 63.  For Board Menus and System Menus, you will be asked to assign a "Name" to the Board or Menu before it is created.  All Menus have nine levels, the level number will also function as the "Name".  You may assign your own "Names" to External programs and functions you create yourself.  It would be a good idea, however, to use the pre-assigned names for all External items shipped with your original system.

     Also, it is possible to have two External functions with the same "Name" as long as they are stored on different disk prefixes.  So you are NOT limited to just 63 External programs or Menus.

[D]sk Pfx
     The Dsk. Pfx element should hold the number of the disk prefix where the desired External program or Message file resides.  This must be set to the proper prefix or the call to the external file will not be successful.  Please see the section of this manual about Prefixes to find out how the prefix numbers are assigned.

     We will now return to the Board / Menu edit menus, so we can look at the rest of the available utilities.

<page-header>
MENU & BOARDS EDIT                    PROMPTS                          PRIME 2.2
<page-break>Prompts


     This option will allow you to edit the command Prompts.  Within the PRIME system, prompts serve two functions.  First, the prompt is displayed to the user as part of the command line, to let him/her know what section of the system they are in. The second function of the prompts is to let the sysop know what section of the system is being used.  This is accomplished by displaying the current prompt in the center section of line one, in the System Information Window.

     There are nine levels of prompts in a System Menu, and four prompt levels in a Board Menu.  The prompts for a System Menu should correspond with the menu levels.  There is one prompt for each level.  Except for the prompt for the Main Menu, these prompts are left unassigned when the system is installed.  Board Menus are different, however, in the respect that the first four levels are assigned by the system automatically when a Board is Created.  I will explain which menus correspond with the Board prompts, and give an example of System prompts beginning next.


Fig. 19.0

                               Board Prompts


                        Level        Corresponding Menu

                          0          Board Main Menu
                          1          This prompt is unused
                          2          Board Scan Menu
                          3          Board Message Editor Menu


System Menu Prompt Example:

     Let's assume that you have set up MNU.0 so that it contains three levels.  The first level holds the main menu, with Chat, User Utilities, etc.  Level two contains a menu offering choices for several bulletin boards, and level three contains a menu offering choices of several General File sections.  The prompts would be set as in the following:


Fig. 19.1

                        Level        Corresponding Prompt

                          0          <Main Menu>
                          1          <Boards Menu>
                          2          <G-File Menu>

<page-break>     The user would then see a command prompt that looks similar to the following:

                                 cmds=:FEBUDO?
                                 <Main Menu>
                                 Command:

     When you Quit the Prompt editor, you will be returned to the main Board Edit, or Menu Edit menu.

<page-header>
MENU & BOARDS EDIT                 TYPES (MENUS)                       PRIME 2.2
<page-break>Types (menus)


     As stated previously, PRIME is capable of using External menus, as well as its own Internal Menus.  This utility is used to tell the system what type of menu to expect For Each Menu Level.

     External menus are actually ProDOS TEXT files that you have made using either your word processor, or the Special Editor provided with the PRIME system.  If you should choose to use an External menu, the menu must be stored on the same prefix as the corresponding Internal Menu. In other words, External Boards Menus must be stored in the same prefix as the board, and External System Menus must be stored on prefix Zero.  External menus MUST be stored in a file named M.FIL.#.#, where # represents an Integer between 0 and 63.  The first digit represents the Menu Number, and the second digit represents the Menu Level.

NOTE:  If you create an External Menu, you must also create an Internal Menu with the same functions.  You must use the same exact commands and prompts as those used in your External Menu.  All operation in PRIME is governed by the Internal Menu!  External Menus are used for display purposes only!

     If you would like to display an External Menu, then edit the proper level in this section to tell the system you want an External Menu used.
<page-header>
MENU & BOARDS EDIT                 MENU UTILITY                        PRIME 2.2
<page-break>Menu Utility
                                 [W]ho's Who
                                 [F]eedback List
                                 [1] Print Menu 

     The above options present some neat utilities for use with menus.  The options are examined below.

[W]ho's Who
     You may list the names of up to five sysops, or remotes in each section you setup.  This list will be displayed when the user presses the command with a Type/Level setup of T1/L13.

     Note: An empty element will abort the display.  This means that the names must be listed in sequence, with no blank elements between names.

[F]eedback List
     For each menu that you have you can have up to 9 SysOps listed in the Feedback list.  Users may easily send Feedback to any Sysop on the list by using the Feedback option on the board.  The Alias spelling must be EXACT!  Make sure you enter the correct box number when prompted.

[1] Print Menu
     This utility will print the menu file to your printer or screen, so you may easily examine the contents.  The menu is printed in a nice report type format.

<page-header>
MENU & BOARDS EDIT                 BOARD GLOBALS                       PRIME 2.2
<page-break>[2] Globals


     The Board Globals encompass such things as private messages, storage control, and various message addressing features.  These items are "Global" in the respect that their provisions affect every message on a board.  Some of these provisions may be overridden by the effects of some of the commands found in the Message Editor.  Let's take a look at what is found in the global section.


Fig. 20.0

          [A]uto Delete .........: On         [M]essage Protect .....: Off
          [P]rivate (all msgs) ..: Off        [T]otal max messages ..: 25 
          [S]how Privates .......: On         [N]ew Messages ........: Off
          [B]ack up from New ....: 0          [R]eload VAR file .....: ---
          [1] Auto-Sign .........: Off        [2] Private on Post ...: Off
          [3] From Visible ......: On         [4] Theme Msg Level ...: A 

          [5] Default Subject ...: Stuff
          [6] Default To ........: PROTREE SYSOPS
          [7] Global To .........: ALL


     The PRIME system uses two methods to control storage space.  In the first method, before a user is allowed to post a message, the system will check the appropriate storage device and determine if there is at least 4k of space available.  If there is not, the system will move to the top of the current board, and begin deleting Unprotected messages until there is at least 4k of free space.  Using the second method, when the number of messages on the board reaches the "Total Max Message" limit, the system will delete the first Unprotected message on the board, to allow the new message to be posted.

     Most of the options in this section deal in one way or another with message control and system limits.  Let's take a look at the available options.

[A]uto Delete
          The Auto Delete flag controls the action of the system when either the Message Limit is reached, or the storage device becomes full.  If Auto Delete is toggled ON, then the system will look for and delete the first Non-Protected message.  If no Non-Protected messages are found, the user will be informed that the board is full, and no more messages are allowed.

[M]essage Protect
          Setting this toggle ON will have the same effect as turning the Auto Delete off.  All messages will be "Delete Protected" by default.  The effect of this flag may be overridden by changing the toggle from within the message editor.

<page-break>[P]rivate
          Setting this toggle will result in all messages posted on the board being Private.  Private messages may be read by the author, the addressee, and anyone with Sysop level access for that board.

          A good example of a board where all messages are Private by default is the E-Mail System.

[T]otal Max Messages
          You may set a limit here for the number of messages a board will hold before it begins Auto Deleting.  The limit must be between 1 and 200.  A bulletin board is limited to holding a maximum of two hundred messages with the PRIME system.

[S]how Privates
          In the case of a user encountering a Private message while reading a board, the system has two possible ways to respond.  It will either give the user a line containing the message number and a report that the message is Private, or it will just skip the message altogether with no notice to the user.

          Setting this toggle ON will result in the system displaying the message number, and the report that the message encountered was Private.

[N]ew Messages
          Setting this toggle OFF will result in the system giving the user the report "No New Messages" when entering a board, if no new messages have been posted since the user's last call.  If the toggle is set ON, the system will give no report until the user attempts to use the "Read New" option.

[B]ack-up from New
          If you place a number in this element, the system will subtract that number from the number of the last message the user has read on this board, and display those messages again, as new, on the user's next call.

          Example:  If you set this number to ONE on a board, the user will be displayed the last message he read on this call, first, when he/she next calls the system.  PRIME will "Back-Up" from zero to nine messages on a board, depending upon the contents of this element.

[R]eload VAR file
          This command will force the variable file to be reloaded, thereby eliminating any changes you have just made.  It allows you to do eding to experiment and then, should you decide not to save the changes you just made, you can use this command to start over.

<page-break>[1] Auto-Sign
          Setting this toggle ON will cause the system to insert a user's Name and Box Number as the last line of any message they post on a board.  This feature is simply a convenience so that a user doesn't need to sign their name at the end of a message. The Auto-Sign also makes it easy for another user to find the author's Box Number, in order to reply to the message.

[2] Private on Post
          If you toggle the Global Private off, you may set this feature on, and the system will still ask the user who is posting the letter if the message is private.  If the user replies Yes, then the message will be coded Private.  This feature is handy for some types of boards, so that the users may leave Private messages to the remote sysop who is in charge.

[3] From Visible
          Setting this toggle on will cause the system to NOT display the author's name when a message is being read.  The author's name is stored in the Message Header by default.  This toggle will defeat the default setting.  If a user puts their name in the message itself, then it WILL be displayed.  This option ONLY blocks the name in the header.

[4] Theme Level
          You may set the security limit a user must have in order NOT to have to view the Theme message if you have used one.  The Index byte that is used is the same one that controlled the command that allowed the user access to the board you are editing.

[5] Def. Sub
          You may set a default message subject in this element.  The user need only touch the return key to take advantage of this feature.

[6] Def. To
          You may set a default addressee for messages in this element.  In most cases you would set this to the generic ALL USERS, or something of that nature.

[7] Gbl. To
          This element works a bit differently than the two previous elements.  This element protects the system from a user attempting to send global Private messages.  The system will NOT store any message as Private that had been addressed to the name in this element.  It is recommended that you put the same name here that is in the Global To element.

Note:     In your E-Mail area, it is recommended that you set the  Default TO to YOUR alias.  This makes it simple for your users to send you mail.

     This completes the examination of the Board and Menu edit utilities.  You should probably read through the previous few chapters at least once more, to make sure you have a thorough understanding of how menu commands work.
<page-header>
OTHER MENUS                         OPTIONS MENU                       PRIME 2.2
<page-break>Options Menu


     The Options Menu is found on the screen where the BBS is waiting for a call to come in.  By pressing 'O' from the Wait mode, you will be presented with the following choices:

Fig. 21.0

                                [U]ser Utilities
                                [P]hone Number List
                                [S]ystem Log Setting
                                [E]xit Program to Basic
                                [C]ontrol Settings
                                [Q]uit (Rtn.)

     The following chapters will explore each section in detail. You will return to this menu each time.  The sub-programs in this section deal with the user file, and the data used in controlling system access to new users.  The obvious items will be documented first, then the major utilities.

[U]   User Utilities
      The System User Utility is a complete sub-system which will allow you to edit the record of each user who accesses your system.  When you enter the System User Utility from the Option Menu, you should use the "Back Out" option to exit the utility.

[P]   Phone Number List  (Edit)
      It is from this section that the phone list is edited.  The explanation of this area will follow the New User Logons.

[S]   System Log Setting
      This area will allow you to track the callers to your BBS.  Here, you can Reset the printer top of form, toggle the LOG status, and view your caller log if it's on disk.

[E]   Exit Program
      This option is one of a few places the system will allow you to make a graceful exit to Basic.  You will be given the basic prompt, with the LOG program still in memory.

<page-break>[C]   Control Settings
      This command allows you access to the New User Logon defaults, access to update the System new file date, your chat status, BBS Name and the name of your main Sysop, usually you!

      [N]ew User Logons

      This utility allows you to control whether or not your system will allow new callers.  This option will be explained in the next chapter of this manual.

      [S]et System News Date

      System News is a file that you create for your system that every user is forced to read at least one time.  The file read is forced by comparing the last date the user was on the system, with the date that has been set for System News.  You should update the System News Date every time you change or update your System News.  You edit the System News file by using the Special Editor option that is found in the [*]SysOp Menu found on your system.

[Q]   Quit
      Quit will return you to the wait mode.

<page-header>
OTHER MENUS                       NEW USER LOGONS                      PRIME 2.2
<page-break>New User Logons

Fig. 22.0

                              [A]llow new user log-ons
                              [D]on't allow new user log-ons
                              [C]hange Side Door log-on
                              [S]tandard names only
                              [P]en names allowed
                              [Q]uit

     The New User Logon sub-menu may be found by pressing "O" from the Wait mode, then "C" from the Control Settings menu, and finally the "N" command.

     This section will provide you with options to control the accessibility of your system to new users, and whether or not you will allow Aliases (or Pen Names) to be used on your system.

Commands


[A]  Allow new user logons

     This will toggle your system so that it will issue passwords to new callers.  This feature is turned on by default.

[D]  Don't allow new user logons

     Turning this toggle on will force your system to give a message to all callers using the NEW command that your system is not accepting new users.  The system will then disconnect the caller.  The use of this option will effectively turn your board into a private system.

[C]  Change side door logon

     This is one of the most misunderstood features of PRIME.  The Sidedoor Logon is a secret password set by you, that when entered by a caller instead of the NEW command, will allow that caller to be issued a password when the "Don't allow new users" option has been set on.

     This is NOT a secret backdoor into your system installed by SmokeSignal Software!

[S]  Standard Names Only

     Pressing this toggle will set your system so it will not allow a new user to enter an alias.  The system will instead copy the user's real name into the alias field of the user record.

[P]  Pen Names Allowed

     Pen names are the same as aliases, and this will set your system to allow new users to enter an alias.

[Q]  Quit

     Press "Q" to return to the Control Settings Menu.
<page-header>
OTHER MENUS                    EDIT PHONE NUMBER LIST                  PRIME 2.2
<page-break>Edit Phone Number List

Fig. 23.0

                                 [P]hone Numbers
                                 [S]ave Changes
                                 [Q]uit/Return to Options

     The Edit Program Text section can be found by pressing "O" from the Wait Mode, and then entering a "P" from the Options Menu.

     This section will allow you to create a list of phone numbers that are not allowable on your system. This list can be handy for security purposes.

COMMANDS

[P]  Phone Numbers

     This is another powerful security feature of the PRIME system.  You may enter a list of phone numbers in this section, and if a caller tries to logon using one of these numbers, he will be disconnected immediately.

     There is no need for you to enter such numbers as 800-XXX-XXXX, or XXX-555-XXXX, as the system checks for these type number automatically.  The system will also check for obviously fraudulent entries by using the table below, with "X" representing any number:

          1XX-XXX-XXXX  0XX-XXX-XXXX
          XXX-1XX-XXXX  XXX-0XX-XXXX
          800-XXX-XXXX  900-XXX-XXXX
          XXX-555-XXXX

     It would be a good idea at this time for you to put your personal phone number, as well as your board's phone number in the list.  This command is NOT retroactive, if the number is already in the user file, the system will continue to accept it.

[S]  Save Changes

     All changes made to the phone numbers MUST be saved using this option.  Failure to do so will result in your changes being lost when you Quit this section.

[Q]  Quit

     Press "Q" to return to the Options Menu.

<page-header>
OTHER MENUS                   [CTRL]-C INTERRUPT MENU                  PRIME 2.2
<page-break>[CTRL]-C Interrupt Menu


     You may access the Main Interrupt Menu only from the LOCAL console.  You access this menu by holding down the "Control" key, and pressing "C" at the same time, while you are logged on to your board.  There is an interrupt menu available at most times on the system.  This chapter will examine the main interrupt menu, you will find most of the interrupt menus in the system have the same options available here.

     From the Main Interrupt Menu you have the following options:

     [Q]uit to Basic
          You may quit the program and enter Basic, with the BBS.1 program intact in memory.

     [U]ser Utilities
          This will put you into the Main System User utility.  This is an alternate way you may enter the User Utility while a user is on-line.  While you are in the utility, the user will see nothing on his/her screen.  Once there, you may validate the user, raise their security level, or whatever else you may have a need to do.  The user utility is examined in its own chapter later in this manual.

     [S]ystem Utility
          This is the Utility necessary to add commands to your menus, make new boards, and set most of the options that control your system.  This utility is quite extensive, and will be examined in the chapter of this manual following the Message Editor.

     [C]hat Status
          This option will allow you to set the SysOp In/Out status.  This is the response that your system will give a user when he/she has pressed the SysOp Pager.  The following values may be set.

          1)SysOp is Out     2)SysOp Might Be In     3)SysOp Is In

     [R]eturn to Program
          Pressing this option will return you to the main menu of the BBS.

<page-break>     There are a few more commands that may be entered only from the console, these commands are to allow you to immediately log a user off your system, toggle your printer on and off, and toggle upper/lower case on computers with a shift key mod.

     [CONTROL]-L  Repeatedly pressing CONTROL-L will toggle UPPER/lower case.  This option is useful if your computer is using a shift key modification.

     [CONTROL]-O  This will immediately log the caller off, without a message of any sort.  To the caller it will appear as if the carrier had been lost for some reason.

     [CONTROL]-P  This command will mask the user information found on the sysops console.  It will change the display of the users data to all "X"'s.  It may be toggled at any time without affecting the caller or the BBS operation.

     [CONTROL]-Y  This will log-off the current caller of your board, and give them a message that their time limit has expired.

     [CONTROL]-Z<Slot #>  This option will toggle the printer on and off.  Assuming your printer is in slot one, you could toggle the printer on with by holding down the CONTROL key, and pressing "Z" then "1".  You would then enter CONTROL-Z0 to toggle the printer off.


     By now you should be fairly familiar with the operation of the User Utility and the System Utility.  This brings you back to the Wait Screen.  We hope you are getting a grasp on your new software by this point.  PRIME is very powerful, and requires that you spend some time getting used to it.  You should go back through the previous chapters, and make sure you have a good feel for the system before you leave the system open for access by your organization or the public.

<page-header>
OTHER MENUS                          EXTERNAL PRGS.                    PRIME 2.2
<page-break>External Programs


     The external program function is one of PRIME's most powerful features.  It is possible to customize almost any Applesoft program so that it will operate in PRIME's environment.  Most existing programs require little modification for compatibility.  The exception to the rule, however, are programs with extensive screen formatting.  Screen formatting doesn't work well when trying to communicate in a "Generic" type environment.

     If you wish to use an external program, you should use the System Utility that was described in the earlier chapters of this manual, and create a command to access the External Program.  This would be a command with a Command Type of 1, and a Command Level of 5.  The name would be set to whatever number yo call it (i.e. PRG.1 so yo use a Name of 1), and the disk prefix would be set to 2, which is the External directory.

<page-header>
USER UTILITY                       USER UTILITY                        PRIME 2.2
<page-break>USER FILE UTILITIES

Fig. 6.0

                       [U]p Loads                [C]lass Code      
                       [W]idth                   [M]enu Width      
                       [R]ead Record             [V]alidate New Usr
                       [I]ndex Bit Codes         [D]aily Call Limit
                       [T]ime Limit              [1]-Telegram      
                       [2]Messages Posted        [3]Total Calls    
                       [N]ame                    [A]lias           
                       [P]hone Number            [X]Box Number     
                       [B]ack Out                [+]Log This User  
                       [?]This Menu              [Q]uit            

                       cmds=UCWMRVIDT!@#NAPB+?Q
                       SysUser Utility         
                       Command (?=Help):       

     Upon entry to the User Utility your display will be similar to Fig. 6.0.  Some of the explanations for these items may be a bit detailed, and some will be rather short.  Each item will be listed in the same order as it appears.  There are quite a few options here that are seldom used, but they were included in the software for your convenience.


COMMANDS

[U]p Loads
     The upload command will allow you to set the number of files a user may download (0-63) before he/she  is required to upload.  Resetting this counter to 0 will block the user from downloading files from your system.

[C]lass Codes
     The class code system is just what it sounds like:  A way for you, the sysop, to classify your users.  Say, for example, you want to have a special section of your BBS set aside for Apple computer users.  The class code system makes it easy for you to keep track of the users you have allowed access to that special section.  You just assign the users a unique character for a class code.  Then if you need to find all of your special section users, they will be pre-identified by the unique code.

     The system uses 9 characters to mark special users for itself.  Those codes and their meanings are below.

<page-break>   * = Nonvalidated User.  Users with this class code may not access your system.  This is the default class code for new users when the BBS is shipped.  It will not allow the user to get on the system until you verify his data and change the class code.

   # = Restricted User.  Users with this class code may access the system, but they may not post messages on the boards.  Most sysops change the new user default to this class code.

   ? = Questionable User.  A user with this class code is allowed access, but is given the message that his logon data was suspect.  Use this class code for those individuals with suspect real names and phone numbers.

   X = Suspended User.  When a user with a suspended class code attempts to logon to the system, he is denied access, and told that his privileges have been suspended.

   N = Normal User.  This is the standard class code for normal system access.  It has no special functions, and can be any other character except those mentioned in this section.

   D = Deleted User.  Assign this class code to a user when you want to delete his record.  This is the only method of deleting a user with PRIME.

   S = Sysop.  The only benefit to this class code is that it will cause the system to ask permission before deleting Electronic Mail after it has been read.

   ! = Restricted User 2.  Users with this class code may only post E-Mail and Feedback.

   % = NonValidated User2.  This user has the same access as a N)ormal user, but the user's name will show up when you validate new users.

[W]idth
     This option will allow you to reset the user's screen width.  It has no effect on the menu display, only on text input.

[M]enu Width
     By picking this command, you may set how many columns the menu will display in for the user. You set a value, 1-2.  The menus display in columns 40 characters wide.

[R]ead User Record
     Enter the box number of the user whose record you want to edit.  You MUST use this command BEFORE you use any of the other ones so that you have a record in memory to edit.

<page-break>[V]alidate New User
     This will search the user file for all users with class codes "#,!,% or *" and bring the user data up in the information window at the top of the screen.  You will be asked if you wish to validate that user.  Enter a 'Y' or a carriage return to validate the user.  Entering an 'N' or any other key will result in the system asking if you want that user's record marked as deleted.

     If you answer yes, you will be asked if you wish to edit the class code.  If you just wish the user to receive the standard class code of "N" for a normal user, then answer No.  If you wish to edit the code, then enter yes.  After the class code, you will be asked if you wish to edit the user's Index Bytes.  If you answer No, the system will proceed to the next new user.  If you answer Yes, you will be allowed the opportunity to edit that user's Index Bytes before proceeding on to the next new user.

[I]ndex Byte Code
     The Index Bytes are your security system with PRIME.  There are 20 separate Index Bytes, each pointing to a value, which can be  A to Z.  You should consider each Index to be a pointer to an individual security system.

     Most sysop functions are set to require that Index Byte 19 contains a value of 'Z'.  Also, a few of the optional special features require a value higher than the default 'A' to be in this Index Byte.

     Index Bytes are numbered 0 to 19, and hold Alphabetic values from A to Z, and the "]" character.

     The "]" character as the Index Value will result in that command being totally unaccessible.  Even the Sysop can't use the command.

[S]ave User Record
     Pressing 'S' will save the current user record to the disk.

[F]ind Class Codes
     This option will ask you for the class code you wish to find, and then bring up the user records containing that code, one by one, and display them in the user information window.  The system will then ask if you wish to alter the record, by editing the fields.

[D]aily Call Limit
     From this option you may set a limit to the number of times a user may access your system in a 24-hour period.  The default is set to 1.  If you don't have a clock card in your system, I recommend you set this to 9, which is no limit at all.  If you choose not to, remember to change the system date every day, or your users will quickly exceed their access limit.  Setting the count to 0 will effectively prevent a person from accessing your system, as they will have always exceeded their daily limit.

[T]ime Limit
     This is where you set the byte limit that a user may view before the system logs him off for time abuse.  You may set a value between 0 and 9, with 9 being almost unlimited access (1024 X 255 bytes or 255 minutes).  The individual time limits for each value are set in the time limit section of the System Utility.

     You don't have to own a clock to control access time with PRIME.  Just use the byte limits.

[1]Telegram
     Telegrams can be a great time saver.  A Telegram is a special message that you want a select group of people to be able to read.

     Using the Special Editor provided with your system, you can create and store 9 separate Telegrams on your system.

     Use the Telegram option here to set which telegram, 0 thru 9, that you want a particular user to receive, with zero meaning no telegram.  The Telegram will then be displayed immediately after the user logs on to your system the next time.

     Hint:  If you have previously used the class code option to classify select groups of users, sending Telegrams is simple using the "Find Class Code" option.

[2]Messages Posted
     This option will allow you to edit the ongoing count of the number of messages the user has posted on your system.  Some of the optional games distributed for the PRIME system may make use of this count in the making of player stats.

[3]Total Calls
     Like the Total Messages counter, this count may be used by optional game systems in setting player stats.

[N]ame
     You may edit the user's real name using this option.  WARNING:  No commas or colons!

[A]lias
     The use of an Alias has become very popular with BBS users.  If you have chosen to allow the use of an Alias on your system, this option will allow you to edit the user's entry.  WARNING:  No commas or colons!

[P]hone Number
     From this option you may edit the user's phone number.

<page-break>[X]Box Number
     This option permanently changes a user's account number, and should be used with extreme caution.

     The system will prompt you for the Box Number of an already existing DELETED account, and assign that Box Number to the user whose stats are appearing in the user window.

     It is recommended that you leave the user's old account active until he/she has logged on and retrieved all E-Mail.  Then delete the old account to complete the change.

[B]ack-Out
     This option will return you to the WAIT MODE.  You should only use this option if you have accessed the System User Utility by using the Option Menu.

[+]Relog This User
     This option should be used if you are updating a user while they are on-line.  This will log the user on who's record you have read into memory.  The user will be logged on with a full time limit, and the correct screen width.  If you change a user's record while they are on-line and do not use this option, the changes will be lost when the user terminates the call.

[Q]uit
     This option will return you to the Sysop Menu of your board.  Make sure you save the record, and use the relog option, "+" if you are updating a user while on-line, before you use this option.
