============================================================================ $VER: CNet Amiga Pager, v5.00 (27-Sep-96) by Dotoran of Frontiers! ============================================================================ What Is It? ~~~~~~~~~~~ A NEW Chat command written specifically for CNet Amiga, v4.22. It will perform the same function as CNet's built-in chat function, however also gives the SysOp MANY, MANY more functions they can perform! Version 5.00 allows for Multiple SysOps, so after the Pager has been set up, the user will be asked WHICH SysOp they wish to Page. After the reason has been entered, a requestor will pop up on the FRONT MOST screen shortly after the specified SOUND file has been played, and the specified SPEECH has been orated. This requestor tells you which port requested the chat, the date and time the chat request was made, any SysOp Comment on file, the handle and real name of the user, and the reason why they wish to chat. There is also the option to have CNet use the CC command to send a "Chat Request OLM" if a SysOp happens to be somewhere online, instead of being disturbed by an annoying requestor. This will ONLY be done if the requesting user has ACCESS to use the CC command. If they do NOT have access to use CC, then a regular page will be attempted. If you are NOT available, Pager will display your custom "SysOp OUT" reason for that HOUR of that DAY. All 24 hours of all 7 days can receive a unique "SysOp OUT" reason. (Using MCI Commands, you could even have the reason display a TEXT file if you feel a more lengthy reason is needed at times.) On the Chat Page Requestor are eight buttons, described below: "Chat" - [ Uses "C" as an alternative to the mouse! ] ~~~~ - Will alert the user you are coming to chat with them by sending them a "System OLM Message". (These messages interrupt into whatever the user is currently doing, provided their current activity isn't set to block these OLM's). System OLM Messages can NOT be responded to. "OLM" - [ Uses "O" as an alternative to the mouse! ] ~~~ - Allows you to send a customized System OLM to the user, instead of actually having to chat with them. After selecting this button, you'll be given another requestor with three buttons: (Use the RAMIGA key in conjunction with the alternative key to activate these buttons). "Send" - [ Use RAMIGA - S as an alternative to the mouse! ] ~~~~ - The text entered in the string gadget will be sent to the user as a System OLM Message. Normally, you'd simply press RETURN to send the text, but you CAN press SEND instead. - Pressing RETURN with NO text in the string gadget will activate the IGNORE button, which functions the EXACT same way as the main IGNORE button, described below. "Cancel" - [ Use RAMIGA - C as an alternative to the mouse! ] ~~~~~~ - This will abort the sending of the OLM Message, and return you to the main Pager Requestor, allowing you to make a different choice on what you'd like to do for/to the user. "Ignore" - [ Uses RAMIGA - I as an alternative to the mouse! ] ~~~~~~ - Acts the same as the IGNORE button described below. - This button will also be activated if you press RETURN with NO text in the string gadget! - While you're sitting in the String Gadget, you can activate any of the buttons by pressing RAMIGA-Hot Key, as defined above. "FSend" - [Uses "F" as an alternative to the mouse! ] ~~~~~ - Will give you a file requestor you can use to ADD files to the user's Select Buffer. - Use the MOUSE to select multiple files by holding down the SHIFT key, then selecting those files you wish to add. - Use the Up and Down arrows with RETURN if you'll only be adding ONE file, as an alternative to using the mouse. - Click the "Done" button(or press RAMIGA-D) to complete the procedure. - As many of the files will be added to the user's Select Buffer as are possible. This means if you have it set in your CNET CONFIG that users can only select 10 files at a time, and you specify you wish to add 20 files to the user's Select Buffer, only the first 10 files would be added(provided the user's Select Buffer was EMPTY to start with). If this should ever occur, the OLM that is sent to the user will let them know what has occurred. - The user will be charged for the download, based on your setting in the Pager CONFIG file. Certain config settings may also provide you with additional requestors allowing you to select specific costs for each individual file. - The file will be killed after the download, also based on your setting in the Pager CONFIG file. Again, additional requestors MAY be provided for you to select specific kill settings for each file IF you have it set that way in the config file. "Terminate" - [ Uses "T" as an alternative to the mouse! ] ~~~~~~~~~ - Will immediately drop that user's time remaining to 0, then drop carrier. (For those users who continually hound you to Chat!) - This will happen for ANY user, INCLUDING those with INFINITE time, and INCLUDING those with "System Operator" status! - A System OLM message will be sent to the user, with a slight pause after sending it, so that the user will be sure to SEE it before the program terminates their connection. "Gone In 5" - [ Uses "G" as an alternative to the mouse! ] ~~~~~~~~~ - Similar to the above, but will allow the user 5 minutes to finish up anything they may have been doing(Posting, Responding, etc.) - This will happen for ANY user, INCLUDING those with INFINITE time, and INCLUDING those with "System Operator" status! "Unavailable" - [ Uses "U" as an alternative to the mouse! ] ~~~~~~~~~~~ - Will inform the user you are no longer available to chat, and will additionally disable the "Sysop is in" checkmark for that port. More information on this below. "Busy" - [ Uses "B" as an alternative to the mouse! ] ~~~~ - Similar to the above, but will simply tell the user you are too BUSY to chat, while still maintaining your "Sysop is in" status. "Ignore" - [ Uses RETURN as an alternative to the mouse! ] ~~~~~~ - Will deactivate the requestor, WITHOUT alerting the user you are doing so. (If you simply do NOT want to be bothered). Whenever any of the above buttons has been pressed, the requestor will be removed from the screen, and the appropriate action(s) will be performed, as well as the "Reason" for chatting being removed from CNet memory, which means it should stop flashing in the Control Panel window. The user is "told" of the action you've taken in the form of a colorized System OLM that will be sent. When the "Ignore" option is used, NO OLM's are sent to the user. When the "OLM" button is used, the default bbstext colors will be used when sending the olm message. How Do I Install It? ~~~~~~~~~~~~~~~~~~~~ 1: An intuition-script language is used to close requestors created by Pager. This program is called ScripIt. There are two versions included in this package: ScripIt and Xit. You can opt to use EITHER one, but I'd suggest starting with the Xit program, as this will give you a 20K savings. Choose one of these files and copy it to your C: directory. NOTE: ScripIt is a scipting language that allows you to create scripts to mimic intuitionized events, like opening windows, pressing buttons, selecting items from menus, etc. You can find v1.20 on both Fred Fish Disk # 288, and on Disk A, Set I of the 4 CD-Rom AmiNet Set, if you'd like to take a look at it. Although written for WB 1.3, provided you don't get too fancy with your scripts, it will also work under WB 2.x and WB 3.x as well! 2: Copy both the "reqtools.library" and the "rexxreqtools.library" into your LIBS: directory. NOTE1: The complete "rexxreqtools.library" package can be found in the AmiNet Collection for anyone interested in obtaining it for your own use. 3: Copy the "Pager/" directory anywhere you wish. DOORS: is a recommended storage location, but the choice is yours. 4: In your BBSMENU file, in Menu # 2, the Available Everywhere Menu, locate the "Chat" command and place a "2" in front of the word, so it will look like this: 2Chat. Then, to the end of Menu # 2, add this line: Chat `1- | {#0doors:Pager/PagerChat} | | ~\|/~~~~~~~~ | | | | | `--> This path should MATCH the path you stored | | the "Pager/" directory in Step # 3 above... | | | `-----> A Control-Q character. | `---------> This states Access Groups 1 thru 31 can use the Chat command. (Change this to suit your needs) NOTE: The built-in CNet CHAT command will still work, but the user will need to type "2C", instead of "C" to use it. Also, although the Pager is written to play the same Chat Sound as CNet uses, your BBSTEXT Line 61 is NOT what loads and plays the sound. use the Pager CONFIG to modify the Sound that IS played. 5: Also add the following command to your Menu # 2 (Available Everywhere). This command is used to enter the CONFIG, edit the SysOp-Out Reasons, as well as allowing you to change your Availability Status for ANY Port. SYSop `31 | {#0doors:Pager/PagerMaint} | | ~\|/~~~~~~~~ | | | | | `--> This path should MATCH the path you stored | | the "Pager/" directory in # 3 above... | | | `-----> A Control-Q character. | `---------> This specifies it's a "SysOp Only" command. NOTE: We've added this command to Menu # 2, instead of Menu # 1, so that you can choose to give access to this command to other users, maybe Co-SysOps or something, simply by editing the `31 above... 6: Load your BBSTEXT file and go to line number 920: \n1\c7**** System Message\n1\a1\@1 In order for the colored OLM Messages to work correctly, you need to REMOVE the \@1 at the END of this line, so that the MCI Commands may be interpreted correctly. If you DON'T remove this command, all OLM's sent will look like the line above(with all MCI commands shown). I haven't seen/had any adverse effects by doing this, so it shouldn't pose any problems with other System Messages sent by CNet. You may also wish to take a second to "spruce up" the look of this line, perhaps by giving it some new colors, or changing the wording, etc. The user's will see this line displayed on their screens whenever you click one of the buttons on the Pager's requestor(except the IGNORE button). 7: While BBSTEXT is still loaded, go to line number 99: @ Logoff complete\n1 To the END of this line, add the following MCI command: {#0doors:Pager/PagerCleanUp} ^ ~~~~~^~~~~~~ | `--> This path should MATCH the one used in Step # 3 above. | `--> A Control-Q character. NOTE: There may be other MCI load commands added to this line for other programs, so you'll want to make sure the above command comes BEFORE any other MCI commands. NOTE: This is the script used to launch the Xit program that closes the requestor if the user should log off before you answer the page. If you opt to use the "Scripit" program, INSTEAD of the "Xit" program, you'll need to modify this program. You should change the filename from "Xit" to "ScripIt", as well as changing the extension of the ScripIt script from ".scx" to ".sc". 8: Save your BBSTEXT and BBSMENU files, then use the RAMIGA-T key combo to reload your BBSTEXT and BBSMENU files into CNet Memory, then... 9: Load your CNet CRON program and create the following NEW event: Name: PagerAMnt Event Type: RunARexx Port(s): 0 Execute Date: with an hour ENDING in :00. Invoke: Immediate-NoDump Repeat Days: 0 Repeat Hours: 1 Repeat Mins: 0 Valid Time: 00:59 /* In case another event is also running. */ Status: Ready Unloaded Port: Ignore Check Days: Check ALL SEVEN Command: doors:Pager/PagerAMaint ~~~~~^~~~~~~ `--> Use same path specified in Step # 3 above. NOTE: The AMaint file will run EVERY HOUR of EVERY DAY. It's quite small and will actually do NOTHING unless it HAS to. The file is used to toggle the global "Sysop is in" checkmark in your Control Panel's "ALL ports" menu. The settings DO work, but may not APPEAR in the menu, unless you first view one of the specific port's menus, THEN view the "ALL ports" menu. (Keep this in mind before reporting it as a bug. This is a problem with CNET, not with Pager). :-) 10: Logon to your bbs, then type the following at a command prompt: SYS CONFIG The "CNet Pager Config" file should then be loaded. Edit the fields to hold the info you will be using, then press ESC to SAVE the info. The CONFIG file will be explained FULLY below. 11: Next, type this command at a command prompt: SYS AVAIL The "CNet Pager Sysop-Out/Availability Editor" will be loaded. Use this file to create your "Sysop-Out" reasons, as well as your global "Sysop is in" hours. (The ones used by the AMAINT file above). More specific information is located below the detail given for the CONFIG file. 12: Also included in the archive are programs you can use to play sounds and produce speech which can be used by CNet Amiga Pager. Do the following with the included files: SOUND ~~~~~ I've only included the file "Sound" to be used for playing any sound data files you may wish to use. If you'd like to use this program to play sound on YOUR system, copy it to your C: dir. If you have another program you'd like to use instead of SOUND, make sure it's located somewhere in your PATH assignment, and that you type the appropriate launch line in the CONFIG program. Use the TEST SOUND command to make sure you have the arguments and paths set correctly. SPEECH ~~~~~~ I've included two ways to create speech on your computer. You can opt to use either one: If you'd like to use "SAY", then copy it to your C: directory, then load the CONFIG program and go down to "Speech Options" and press your ENTER key. Delete whatever may currently be in that field, then type the word "say" and press ENTER. You'll be presented with the built-in default format for use with the "Say" program. Try the TEST SPEECH command to see how it sounds. Play with the values given after the -f, -s, and -p arguments to change how the speech will be orated. If you'd like to use the SPEAK: handler instead, you should do the following: - Copy the "narrator.device" to your DEVS: directory. - Copy the "translator.library" to your LIBS: directory. - Copy the "speak-handler" to your L: directory. - If using WB 2.04, then add the SPEAK: entry to the file "mountlist", located in your DEVS: directory. - If using WB 2.1 or later, copy the "SPEAK" file into the DEVS:DOSDrivers/ directory. - You should now REBOOT your system (cold, not warm). After rebooting, logon to the bbs and enter the Pager Config by typing "SYS CONFIG" from any command prompt and go down to the "Speech Options" item. Type "speak" and press ENTER to use the built-in defaults for use with the SPEAK: handler. From what I have been able to discern, there is no way to modify the way the speech sounds using this version of the SPEAK: handler, which is why I prefer using the older "SAY" program, however use the TEST SPEECH command and see how the speech sounds when using SPEAK: and decide for yourself which you'd like to use. 13: That's It! (Wow! Wouldn't have been good luck to have 13 steps anyways!) How to Use Pager's Config: ~~~~~~~~~~~~~~~~~~~~~~~~~~ As mentioned in step # 10 above, typing "SYS CONFIG" will load the CNet Pager Config file, which has numerous options. When editing values in any of the string gadgets in the config program, remember that you can also use these commands to help: CTRL-B - go to Beginning of text. CTRL-N - go to eNd of text. CTRL-X - eXpell, or erase all text. CTRL-K - Kill from cursor to end of line. BACKSPACE - Delete a character and move cursor left. DELETE - Pull character to right of cursor INTO cursor. And now, the full descriptions for all Config options available: Graphics ~~~~~~~~ "Yes" ~~~ * With graphics enabled, users with 80 Columns and IBM-Ansi term emulation will be shown a picture similar to the Requestor that will be displayed on your screen. "No" ~~ * Users with less than 80 columns, or if you choose NOT to use the extended graphics will be shown text: "Paging SysOp...", etc. Pass to CC? ~~~~~~~~~~~ "Yes" ~~~ * When a user wishes to PAGE a particular SysOp, the "SysOp Port(s)" defined below will be checked for their ID Number. If the SysOp is found to be online on one of those ports, the user's "C" command will be converted into the appropriate "CC" command instead, PROVIDED that the user has ACCESS to USE the "CC" command. If they do NOT have access to the "CC" command, then a regular PAGE will be attempted. "No" ~~ * The "CC" command will NOT be used, and a regular PAGE will be attempted ALL of the time. Allow ChatBacks ~~~~~~~~~~~~~~~ "No" ~~ * Set to NO and the user will ONLY be allowed to use the Pager ONCE per call. They'll be told they've reached the maximum number of times they may use the Pager if they attempt a second page. "Yes, ?" ~~~~~~ * Where "?" is a 1, 2, or 3, which will allow the user to use the Pager ? additional times OVER their initial page, so a setting of "1" will allow the user to use the Pager TWICE(their first page, PLUS 1 additional page), etc. before being told they've reached the maximum amount. ChatBack Access's ~~~~~~~~~~~~~~~~~ * The Access Groups that can SKIP the above ChatBack restrictictions. In other words, users of these access groups may use the Pager ANY NUMBER OF TIMES! Use 12 Hr ~~~~~~~~~ * Set to YES, and all references to TIMES will be made in 12 Hour format when using the "PagerSysAvail" editor. Set to NO, and you'll be shown times in 24 Hour format. (You'll also be allowed to switch between 12/24 hour mode from within the editor too!) LogName ~~~~~~~ * This is the FILENAME to be used to store the PAGER LOG entries when- ever a user pages you. The format of the log entry is as follows: Handle Page Date Reason For Paging Paged? * The "Paged?" column can be one of the following three: "N" - You weren't available for chatting. "Y" - Available for chatting, and the requestor WAS displayed. "M" - Not available for chatting, BUT user sent MAIL instead. * If multiple SysOps are specified, then this name will be used as the STEM of the filename, where the SysOp's ID Number will complete the full filename. For instance, ID # 225 would have "LogName225" as the name of their chat log, etc. Ask After Log View ~~~~~~~~~~~~~~~~~~ "Query w/ Yes" ~~~~~~~~~~~~ * After log is displayed, you'll be ASKED if you want the log to be deleted. The DEFAULT answer(one used when you press RETURN) will be YES. "Query w/ No" ~~~~~~~~~~~ * Same as above, but default answer will be NO. "Answer w/ Yes" ~~~~~~~~~~~~~ * The log will be displayed and then AUTOMATICALLY deleted! "Answer w/ No" ~~~~~~~~~~~~ * The log will be displayed and left INTACT on the drive! NOTE: Use the "SYS D" command to DELETE a log file when using this setting. File Send Path ~~~~~~~~~~~~~~ * This field stores the path that will be initially scanned when you choose the "FSend" button, although you can choose to modify this path from the requestor as well. Added as a hopeful means of speeding up finding a needed file, if you anticipate requests for files that are more often found in one particular path, etc. Note that the file requestor will ALSO be shown on the FRONT-MOST screen now! Cost Percentage ~~~~~~~~~~~~~~~ * Allows you to specify the File Credit cost the user will be charged when they download the file(s) you send. Options for 1, 2, and 3 times the file credits are included. For example, if set to "2 X", then the file is charged as if TWO files were downloaded, etc. * The ALWAYS settings affect ALL files selected by you, and will NOT present additional requestors, however if you choose one of those options NOT using the ALWAYS keyword, the selection will be used as the DEFAULT button of a requestor that will be presented to you as the Pager works through the list of files. The requestor will allow you to specify unique costs for each file sent to a user's Select List. Pressing ENTER at this requestor will activate the default setting you chose here. File Kill Type ~~~~~~~~~~~~~~ * This option allows you to specify the DEFAULT setting for what happens to the file(s) the user downloads. There are four settings: "Don't Kill Download" ~~~~~~~~~~~~~~~~~~~ * File(s) will NOT be deleted after it has been downloaded. "Kill After Download" ~~~~~~~~~~~~~~~~~~~ * The file(s) will be DELETED after they have been removed from the user's Select List(after being successfully downloaded). "After DL or UnSelect" ~~~~~~~~~~~~~~~~~~~~ * This option means to DELETE the file, either AFTER it has been downloaded, OR after it has been UNSELECTED! "Kill After Unselected" ~~~~~~~~~~~~~~~~~~~~~ * The file(s) will be DELETED when the user unselects them from their Select Buffer, EVEN IF THEY DON'T DOWNLOAD THEM! * The ALWAYS settings affect ALL files selected by you, and will NOT present additional requestors, however if you choose one of those options NOT using the ALWAYS keyword, the selection will be used as the DEFAULT button of a requestor that will be presented to you as the Pager works through the list of files. The requestor will allow you to specify unique kill settings for each file sent to a user's Select List. Pressing ENTER at this requestor will activate the default setting you chose here. * Be VERY, VERY careful with this setting. If you choose one of the automatic settings(one NOT using the ALWAYS keyword), and a user requests a copy of your BBSTEXT file(or another IMPORTANT file), for example, then that file will be DELETED when the user finishes downloading it. Put mildly, this will come as an UNPLEASANT surprise the next time the system goes to use that file! Font (Size) ~~~~~~~~~~~ * You'll be presented with a font requestor where you can choose the font and size you'd like to use in the display of Pager's requestor. * After choosing the font/size, the TEST FONT gadget will automatically be launched, so you can be SURE the font will look appropriate on the screen, or if further modification will be necessary. TEST1 ~~~~~ * When you select this button(or press your "1" key), a requestor will pop up on your screen using the chosen font. This way, you can see how the chosen font looks in a requestor, before making a final decision. Speech Options ~~~~~~~~~~~~~~ * This line should contain the exact settings you would use if you were to launch this command from a CLI shell. * When you get to the point where the TEXT TO BE STATED should go, replace it with "" (minus the quotes). The Pager will then use the supplied text on the next screen in place of the "" given here. * Two built-in defaults are also present, and can be activated by simply typing one word, as shown below: Typing "say" and pressing ENTER will use: say -f -s180 -p170 Typing "speak" and pressing ENTER will use: echo "" >speak: * You can use an alternate program in the creation of speech, but it will be up to YOU to figure out the correct syntax to use here. * If you wish NOT to use SPEECH, then empty out the string gadget(either by deleting with backspace or CTRL-X), then pressing your ENTER key. You should see the text: which will tell you if you've successfully disabled the speech or not. TEST2 ~~~~~ * Selecting this button(or pressing your "2" key) will allow you to test the SPEECH operations of the Pager. This way, you will know if your options still need a bit of tweaking before it sounds satisfactory. Sound Player ~~~~~~~~~~~~ * This line should contain the exact command line of the program you will be using to play the SOUNDS specified below. * If you wish NOT to use SOUND, then empty out the string gadget(either by deleting with backspace or CTRL-X), then pressing your ENTER key. You should see the text: which will tell you if you've successfully disabled the sound or not. TEST3 ~~~~~ * Selecting this button(or pressing your "3" key) will allow you to test the SOUND operations of the Pager. You'll then be able to change the settings if you find a problem. SAVE ~~~~ * Selecting this button(or pressing "S") will simply SAVE the currently displayed settings to the config file, WITHOUT exiting the config. QUIT ~~~~ * Selecting this button(or pressing "Q") will check to see if changes were made(and ask if you'd like them saved), then will exit the Config file. Goto "SysOps" Screen ~~~~~~~~~~~~~~~~~~~~ * Selecting this button(or pressing "G" or "P") will take you to the second screen of the Config Program that deals with the SysOps Info. More on this second screen described further below. TEST PAGER ~~~~~~~~~~ * Selecting this button(or pressing "T") will test your current Pager setup. The following will occur in this order: - The SOUND will be played(if defined). - The SPEECH will be orated(if defined). - The REQUESTOR will be displayed. * Note that the requestor is a "mock" requestor, and although you'll be able to click ANY of the buttons, NONE of them will work, but will simply result in ENDING the test. Again, it's used solely to make sure your settings look and work well for you and your system setup. ESC ~~~ * Pressing your ESCape key will attempt to EXIT the config file. If changes were made, you'll first be asked if you wish to SAVE them, before you actually leave the program. On The "SysOps" Screen: ======================= Group ?: SysOp(s): ~~~~~~~~~~~~~~~~~~~~ * These settings are used to create groupings of SysOps that can possibly be paged by your users. An example will probably be the easiest way to describe what these settings do. Let's take the following 6 SysOps: SysOp # 1: Joe Jones (System SysOp) SysOp # 2: Joe Smith (Message Bases) sysOp # 3: Joe Brown (UD/File Bases) SysOp # 4: Joe Schmoe (Door Executables) SysOp # 5: Joe Mamma (Paid Subscribers) SysOp # 6: Joe Belle (Computer Club) In this example, you can see that there are a few SysOps whom you don't wish certain users to be able to page. For instance, users who are NOT subscribers shouldn't be allowed to Page SysOp # 5, non-club members shouldn't be allowed SysOp # 6, new users shouldn't be allowed 2 thru 6, etc. This is where the GROUPINGS come in. For "Groups", you specify which Access Groups should be allowed to Page SysOps stated in "SysOp(s)". You might do something like this: Group 1: 0 SysOp(s): 1 Group 2: 1-10 SysOp(s): 1-4 Group 3: 11-20 SysOp(s): 1-5 Group 4: 21- SysOp(s): 1- These settings would then mean: Users of Access Group 0 could only Page SysOp # 1, while users of Groups 1 thru 10 could Page SysOps 1 thru 4. Users in Groups 11 thru 20 could Page SysOps 1 thru 5, and users with Groups 21 or higher could Page ANY of the SysOps. Make sure to NOT include the SAME access group in MORE than one group, as the access group found FIRST will be the one used. (For instance, if Group 1 above was "0,21", then access group 21 would then ONLY be able to Page SysOp # 1, even though in Group 4 you stated they could page anyone.) If you create a group that has access to page only ONE SysOp, then the menu of SysOps will NOT be shown to the user. In other words, the user will not even KNOW other SysOps exist! You don't have to use all four groupings if you don't want to. If you wish not to use any groupings at all, then use these values: Group 1: 0- SysOp(s): 1- Even if you will NOT be using multiple SysOps, you should still make sure the above is stated. SysOp # ?: ~~~~~~~~~~ * Enter the ID Number, Handle or Real Name for this SysOp. The info will be checked for validity and the user's HANDLE will be displayed in this area. Sound to Play ~~~~~~~~~~~~~ * This should contain the path and filename of the SOUND you wish played whenever this SysOp is paged. * Clear this field out(delete, backspace, ctrl-x) if you wish to NOT have a sound played for this SysOp. You'll see "" displayed if the sound was turned off for this SysOp. * You'll see "DISABLED" displayed here if you TOTALLY disabled sound for ANY of the SysOps on the first screen of the config, and you will NOT be allowed to edit this area until you RE-ENABLE Sound on the first screen. Mail ID's ~~~~~~~~~ * If a user tries to Page a SysOp, and the "Sysop is in" menu item is NOT checkmarked, then the user will be asked if they wish to send the SysOp MAIL instead. This setting allows you to specify ALTERNATE mailboxes or FURTHER mailboxes if you wish the mail sent to another (or more than one) ID Number. * For example, using the SysOps from the previous example: SysOp # 1: Joe Jones (System SysOp) SysOp # 2: Joe Smith (Message Bases) SysOp # 3: Joe Brown (UD/File Bases) SysOp # 4: Joe Schmoe (Door Executables) SysOp # 5: Joe Mamma (Paid subscribers) SysOp # 6: Joe Belle (Computer Club) If a user chose to Page "Joe Mamma", but he was unavailable, if the user then chose to leave mail instead, you might want this mail message to be sent to BOTH "Joe Mamma" and "Joe Jones", etc. * Note that these are USER ID numbers and NOT the SysOp number defined in the config program. Port(s) Online ~~~~~~~~~~~~~~ * These are the PORTS that this user will MOST LIKELY be calling in on. The Pager looks at these ports when a user tries to Page them in case the probability for using the "CC" command exists. KILL SYSOP ~~~~~~~~~~ * Selecting this button(or pressing "K" or "S", depending on which of the two SysOp entries you're dealing with), will allow you to "mark" this SysOp for deletion from the Pager. * The "SysOp # ?" value will change to "" to show you of the upcoming action. To "undelete" the SysOp, simply go back to the "SysOp # ?" field and reenter that info. All other settings will not be affected. * To "officially" delete the SysOp, you will need to EXIT the config program. Note, however, that when a SysOp is deleted, you will LOSE any GROUP settings you may have previously had setup, as this data would no longer be valid, and would have to be recreated by you. Speech ~~~~~~ * This is the textual string that will replace the "" tag given in the "Speech options" on the first screen. Clear this value out if you wish to NOT have speech enabled for this SysOp. You'll see the text "" displayed instead. * You'll see "DISABLED" displayed here if you TOTALLY disabled speech for ANY of the SysOps on the first screen of the config, and you will NOT be allowed to edit this area until you RE-ENABLE Speech on the first screen. TEST SYSOP ? ~~~~~~~~~~~~ * The above info, as well as the current date and time and the HANDLE and REAL NAME of the user using the Config will be used to display a test Pager Screen. The following events will occur in this order: - The SOUND will be played(if defined). - The SPEECH will be stated(if defined). - The REQUESTOR will be shown. * Note that the requestor is a "mock" requestor, and although you'll be able to click ANY of the buttons, NONE of them will work, but will simply result in ENDING the test. Again, it's used solely to make sure your settings look and work well for you and your system setup. Forward Two SysOps ~~~~~~~~~~~~~~~~~~ * Selecting this button(or pressing any of these: F . > + = ) will display the next two SysOps. * Blank entries will be shown for SysOps who do not exist presently. To add additional SysOps, simply supply the needed "SysOp # ?" info, then change any of the other settings to suit. Backwards Two SysOps ~~~~~~~~~~~~~~~~~~~~ * Selecting this button(or pressing any of these: B , < - ) will display the previous two SysOps, if they exist. Previous Screen ~~~~~~~~~~~~~~~ * Selecting this button(or pressing "P" or "G") will take you back to the first config screen. ReDraw Screen ~~~~~~~~~~~~~ * Selecting this button(or pressing "R") will redraw the config screen. * This may come in handy in two instances: - You experience line noise when using the Config from Remote. - You enter a Handle or Real Name that was not found in your user data file(in which case, you'd be presented with the "Choose User" listing request, which will thoroughly destroy the look of your config screen). * The "R" command is also available from the first config screen, in case you experience line noise on that screen as well. ESC ~~~ * Pressing your ESCape key will attempt to EXIT the config file. If changes were made, you'll first be asked if you wish to SAVE them, before you actually leave the program. How to Use Pager's SysOp-Out/Availability Editor: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Something NEW to v5.00 CNet Pager is the SysOp-Out/Availability Editor. This makes creating the reasons you may not be available for chatting, as well as setting the times you ARE available for chatting incredibly easy. After typing "SYS AVAIL" (or "SYS A") from a command prompt, you'll see the main editing screen used for this editor. Here is some further info as to how to use this editor: If the "Sysop is in" item, located in the "port" menu of your Control Panel screen, is NOT checkmarked and a user attempts to page you, they'll be told you are not around, and additionally, Pager can supply a REASON why you aren't around. This editors main purpose is in defining those reasons. You'll see that all 24 hours of all seven days are visible on this one screen. You can use the cursor arrow keys to move the > cursor to any hour of any day. Pressing your ENTER key will SELECT that hour, and additionally will advance the > cursor to the NEXT hour in the day. Pressing ENTER numerous times will select RANGES of hours. Let's take an example to show you how this editor is used. Let's say that normally, between the hours of midnight and 6:00 AM you are sleeping, and that between 8:00 AM and 4:00 PM you are working, here's what you'd do: - Start by positioning the > cursor on "12a" (or "000") under the "SUN" column. - Press your ENTER key seven(7) times. You'll notice that the hours between 12a and 6a have become highlighted in purple. - Now use the arrows again to position the > cursor at 12a on MON, and again, press ENTER seven(7) times. - Repeat this process for the other five days. When you've completed this operation, all your "sleeping" hours should now be highlighted in purple. - Now press your SPACEBAR. In the edit rectangle at the bottom of the editor window, you'll be able to edit the reason. (Chances are you'll see the current "default" reason listed). Press your BACKSPACE key to DELETE this reason and type "sleeping right now.". (Leave off the personal pronoun, as that will be supplied by Pager itself). - Press your ENTER key, then press "S" to tell the editor you wish to apply the "sleeping right now." reason to all the SELECTED hours. In a second or two, the editor will redraw the screen, your selected hours will be unselected, and you may notice the COLOR of the hours has changed from CYAN to YELLOW. - Now if you move your > cursor around the screen, you'll see that when you are positioned on any hour between 12a and 6a on any day, you'll see "He's sleeping right now." (or "She's sleeping right now."). - To create your WORK hours, position the > cursor next to an "8a" and start pressing ENTER until you've highlighted all hours between 8a and 4p. Do this for any additional days you work as well. - Press your SPACEBAR to define the reason, delete the one that's there and replace with text like "working to pay off the house!", etc. - Press ENTER, followed by "S" to copy the reason into your SELECTED hours again. - The other two options you'll see in there are CURRENT hour and DEFAULT hour. The CURRENT hour is the hour the > cursor is presently sitting next to. This is helpful if you only have ONE hour you'd like to make a reason for, but don't wish to SELECT the hour in the process. - As mentioned above, after defining reasons, the COLOR of the hours changes from CYAN to YELLOW. Hours left in CYAN will use a supplied default reason if a user should ever page you during one of these hours. Press SPACEBAR, create a reason and press ENTER, then press "D" to replace the default reason with one of your OWN reasons. That's all there is to creating the REASONS why you might be unavailable to chat with a user. Use the above techniques to create as many additional reasons as you wish. You can select hours that already have created reasons and overwrite those hours with NEW reasons if you find the need to. The main POWER of the Pager is in the displaying of a custom REQUESTOR on the SysOps frontmost screen, however in order for this requestor to show up, you must make sure to place a checkmark next to the "Sysop is in" item in the "port" menu of the Control Panel screen. Remembering to set this checkmark in place, as well as removing this checkmark when you LEAVE the area can be a royal pain in the backside, so starting with this version of the Pager, you can opt to use the included AMAINT module to toggle the setting of this checkmark GLOBALLY(meaning that it affects ALL ports). This editor is also used to specify WHEN you'd like this checkmark to appear in the port menu. Let's take another example to see how this is accomplished: From our example above, we can see that we might possibly be available for chatting AFTER 4PM, so lets say we "want" to be available for chatting between the hours of 5PM and 8PM Sunday through Thursday, and between 5PM and Midnight on Friday and Saturday: - Move your > cursor to 5p (or "050") on SUN. - Press your "A" key four(4) times. You'll notice the hours between 5p and 8p ("050" thru "080") become highlighted in RED this time. - Repeat the above process for Monday through Thursday. - For Friday, start at 5p, but press "A" eight(8) times this time. Note that the hours between 5p and 12a become highlighted in RED. Also note how the day "wraps" over to Saturday to pick up the correct midnight. - Repeat this starting at 5p on Saturday. That's all you have to do. When you move your > cursor around the screen this time, you'll notice a little checkmark graphic appear on the right side of the reason box(lower right corner) whenever you're pointing at a time you have highlighted in RED. This is helpful in reminding you that it is the RED highlighted hours that affect the CHECKMARK status of CNet Amiga Pager. Once you've completed entering all your reasons, as well as defining the hours you'll be available, press your "Q" or "ESC" keys to SAVE and EXIT the editor. While IN the editor, you can also press the slash(/) key to toggle the display between 12 hour and 24 hour format. This editor creates and maintains numerous text files located in your Pager/ directory: Out.Sun, Out.Mon, Out.Tue, Out.Wed, Out.Thu, Out.Fri, and Out.Sat ~~~~~~~ ~~~~~~~ ~~~~~~~ ~~~~~~~ ~~~~~~~ ~~~~~~~ ~~~~~~~ - These seven files hold the REASONS you're not available for each day of the week. Each file has 24 lines, where the first line of each file represents 12:00 AM ("000" hours) Midnight, while the last line holds data for 11:00 PM ("2300" hours). - If a line appears BLANK in any of these files, this means a reason has NOT been created for that hour, in which case the DEFAULT will be used instead. Out.Def ~~~~~~~ - This file holds just one line defining the DEFAULT reason you're not available for chatting. It is also possible that this file could be BLANK as well. In this event, a hard-coded default of "not available for chatting right now." will be used instead. Availabilities ~~~~~~~~~~~~~~ - This is the file used by the AMAINT module to determine whether or not the "Sysop is in" item should contain a checkmark or not. There are seven lines in this file, which represent the seven days of the week(starting with SUNDAY, ending with SATURDAY). Each line contains a string of 24 1's and 0's, representing the 24 hours of the day, starting at 12:00 AM ("000" hours) MidNight on the left and moving rightward to 11:00 PM ("2300" hours) on the extreme right. A "1" means the checkmark SHOULD be used, while a "0" means the checkmark should be REMOVED. How Does This File Work? ~~~~~~~~~~~~~~~~~~~~~~~~ Please READ the following paragraphs for more IMPORTANT information! There is a Priviledge Flag in each user's EA screen that is called: "May page the sysop" It's located near the bottom of the third column when you enter the "Priviledge flags >>" screen. This priviledge flag has three settings: No - User is ALWAYS told you are NOT available for chatting. Yes - User is ALWAYS told that you ARE available for chatting. Def - User is ONLY told you are available for chatting IF the "SysOp Is In" setting from the Control Panel's Port Menu has a checkmark in it. (Note that individual ports can use different settings, so for example, you could state that you are IN on ports 1-3, but OUT on ports 4-12, etc) This program was written to look at the setting of this priviledge flag, and proceed accordingly. Use the command "SYS" to change the settings for any of the Port Menus you wish. You may also wish to define a function key in your CNet CONFIG that you can use to easily toggle your status settings for ALL Ports. Here's how that key might look: "SYS * " (minus the quotes, but remember the SPACE after the * symbol). To use the function ket to toggle your availability status manually, simply press the key(in which case, you should see the SYS * appear on the command line, then additionally type: N and press ENTER if you are NOT available, or... Y and press ENTER if you ARE available for chatting. So, the completed commands(before pressing ENTER) would look like the following: CNet: SYS * n CNet: SYS * y Using the SYS Command: ~~~~~~~~~~~~~~~~~~~~~~ From a command prompt, type "SYS ?" (minus the quotes). You'll be shown the help screen for the SYS command. Here's what it looks like in black and white: CNet Amiga Pager Maint, v5.00 by Dotoran of Frontiers! Format: [required] /= SYS - List Status for ALL Ports. SYS <[Port(s)]> - List Specified Port Status. SYS <[Port(s)]> <[S]wap/[T]oggle/[F]lip> - Swap Availability Status. SYS <[Port(s)]> <[Y]es/[I]n/[A]vailable> - Enable Availability Status. SYS <[Port(s)]> <[N]o/[O]ut/[U]navailable> - Disable Availability Status. SYS <[A]vail> - List Pager SysAvail Editor. SYS <[C]onfig> - Load Pager Config File. SYS <[L]og/[V]iew> - Display Pager Log File. SYS <[D]elete> - Delete Pager Log File. SYS <[H]elp/[?]/[/]> - Show This Help Menu Again. As you can see, there are MANY different arguments that can be used with the new SYS command. A brief description of each form follows. The first five forms of the command deal with the "Sysop is in" item, which is located on the port's "Port X" menu of Control Panel: SYS ~~~ Typing the command with NO arguments will show you a listing of ALL your "SysOp Is In" statuses for all loaded ports, starting with the GLOBAL setting. If the global setting is enabled(Available), statuses for all ports will display as: [Available] (inside squared brackets), as it does not matter what a specific port is set to if the GLOBAL setting is set to ENABLED mode. You MAY see an "Unavailable" while the global setting states "Available". This occurs if you REMOVE a checkmark from a port AFTER globally placing the checkmark. Remember, though, that this kind of editing will NOT work correctly if you are also using the AMAINT module. SYS <[Port(s)]> ~~~~~~~~~~~~~~~ You can optionally specify one or more port numbers if you only wish to check the status of specific ports. Use standard CNet Ranging techniques if multiple ports will be selected, like this: SYS 0-2,12 (List status of ports 0, 1, 2, and 12 only!) The three forms dealing with changing the states of the "Sysop is in" item should ONLY be used if you opt NOT to use the included AMAINT file, as the AMAINT file will affect whatever settings you choose for specific ports, and may cause for confusion at a later date. SYS <[Port(s)]> <[S]wap/[T]oggle/[F]lip> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ By specifying one or more ports as the first argument, followed by the letter S (or T or F), you can invert the availability setting for these ports, as shown in this example: SYS 0-2 S Status Before Command Status After Command ===================== ==================== Port 0: UnAvailable Port 0: Available Port 1: Available Port 1: UnAvailable Port 2: Available Port 2: UnAvailable You can type as much of the keyword as you wish, but only the first letter is required to activate the command. You may also specify a * to signify ALL LOADED PORTS, instead of 0-. SYS <[Port(s)]> <[Y]es/[I]n/[A]vailable> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ By specifying one or more ports as the first argument, followed by the letter Y (or I or A), you can ENABLE the availability setting for these ports, REGARDLESS of the port's present setting. This means that ports that do NOT have the "Sysop is in" option checkmarked WILL, and those that DO have it are left untouched. You can type as much of the keyword as you wish, but only the first letter is required to activate the command. You may also specify a * to signify ALL LOADED PORTS, instead of 0-. SYS <[Port(s)]> <[N]o/[O]ut/[U]navailable> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ By specifying one or more ports as the first argument, followed by the letter N (or O or U), you can DISABLE the availability setting for these ports, REGARDLESS of the port's present setting. This means that ports that HAVE the "Sysop is in" option checkmarked will have it's checkmark REMOVED, while those that DO NOT have it are left untouched. You can type as much of the keyword as you wish, but only the first letter is required to activate the command. You may also specify a * to signify ALL LOADED PORTS, instead of 0-. SYS <[A]vail> ~~~~~~~~~~~~~ Specifying an "A" for the argument will launch the Pager SysOp-Out & Availability Editor discussed fully earlier in this document. SYS <[C]onfig> ~~~~~~~~~~~~~~ This one you already know about, but I'll mention here that you really only need to specify the "C" of CONFIG to enter the Pager Config file. SYS <[L]og/[V]iew> ~~~~~~~~~~~~~~~~~~ Typing "L" (or V) as the first parameter will show you the current PAGER log, provided there IS one. How you'll be asked to DELETE the log is configurable through the CONFIG file. If Multiple SysOps have been defined, and User ID # 1 uses this command, a listing of SysOps will be displayed. This SysOp can then view ANY of the defined Chat Logs. SYS <[D]elete> ~~~~~~~~~~~~~~ Typing "D" as the first parameter will ask if you'd like to DELETE the current PAGER log. This argument was added in the event you chose the "Answer w/ No" option for the "Ask After Log View" item in the config. If Multiple SysOps have been defined, and User ID # 1 uses this command, a listing of SysOps will be displayed. This SysOp can then delete ANY of the defined Chat Logs. SYS <[H]elp/[?]/[/]> ~~~~~~~~~~~~~~~~~~~~ Another one you already know about, but now you'll know you can also use "H" or "/" (the unshifted question mark) to get help too! Also, any UNKNOWN argument entered should ALSO result in the HELP screen being displayed to the user. What Does "ScripIt" Do? ~~~~~~~~~~~~~~~~~~~~~~~ This was the method I decided to go with for TERMINATING the Requestor without a SysOp's intervention. The "PagerKILL.sc" file in the "Pager/" directory is the script used to CLOSE the requestor. The ScripIt script language was written for ADOS 1.3, however this script works perfectly fine under ADOS 2.xx and 3.xx. The ScripIt command file is only used when I need to CLOSE the requestor. It is NOT being loaded and stored in memory, so should not add any more overhead to your system. I've included the "Xit" file and another script, "PagerKILL.scx" with the 5.00 version of Pager. The Xit program is a special version of the ScripIt program used to run COMPILED ScripIt scripts, which is what the ".scx" file is. You may wish to use THIS file instead of the ScripIt file for a 20K savings. There are two times a requestor will be closed by ScripIt: - If the user who created the Page logs off your bbs BEFORE the SysOp had a chance to click one of the buttons. - If the requestor was displayed on the screen for LONGER than 5 minutes and either the same user or another user requests to Page the SysOp. There should now NEVER be a time when MORE THAN ONE requestor is ever displayed on your screen. If you ever see MORE THAN ONE requestor on the screen at once, please contact me and tell me how you did it! Closing Info & Acknowledgments! ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Once again, this file was written for CNet Amiga, v4.22, and will NOT function on EARLIER versions of CNet. If running an earlier CNet version, then I suggest you upgrade to the latest version, which is FREE for those of you who REGISTERED your copy of CNet. Those SysOps using v4.00 through v4.21 will NOT be able to use this version of Pager. Those SysOps still using CNet 3.05c should continue using my CNet Amiga Pager, v4.1. David Prothero originally wrote a program of this type, back in the CNet 2.3+ days(before the new MCI system). His program acted as the frame- work for this file. His requestor had three buttons, and did not include a way to inform the user of the SysOp's choice, so I think OVER ALL, this file is even BETTER than a simple CONVERSION. Thanks Dave, for giving me the routines to look at in order to make use of the "apig.library". Even though I am no longer using the "apig.library", I still owe Dave thanks for giving me the gumption to figure out ANY of these external libraries! I'd like to also thank "Spaceman Spiff", aka Donald Knott, the SysOp who uploaded Dave's original Pager program, asking if I could take a look at it. He wanted to use it on his system, and as I was finishing it up, I liked it so much, I decided to put it up on MY system. Alas, I've found that if a program is something I like to use on MY system, there's BOUND to be someone who'd also like it for THEIR system, so ENJOY! Thanks also go out to PMK (Peter M. Klein) for his insights as to how to access the Port Menus of CNet, as well as giving me the SELFILE() routine, which is how we can CHARGE and KILL the files we send to users using the new FSEND button. (As a sidenote, programmers may want to rip the routines used in this program dealing with the Select Buffer, Control Menus, and OLM's, as all three of these areas have CHANGED their getuser values, so look at mine to find the NEW values. At least until I finish the new getuser listing!) Thanks to The Brazilian (Bob Maple) for writing a file called "TISNIUM", (The Intelligent SysOp Not In User Message), which was the file that gave me the idea to create the separate, individual "SysOp OUT" messages. His file was written for the CNet, v2.3? version, so I thought we should ressurrect this feature as well. Thanks to Stig Joergensen of SCALA BBS for his help in figuring out how to access the FRONT-MOST screen through intuition using ARexx. (Programmers, that's what the "GF" routine does. It gives you the ADDRESS to use with the "rt_screen" tag used in the "rexxreqtools.library"...) And lastly, for v4.0, Thanks to Aunt Bea (Henry Priebe) for telling me about the "ScripIt" language, which is how we can finally get rid of the Pager Requestor if the user should log off(or after 5 minutes). He also let me know the correct usage of the SPEAK handler, after numerous failed attempts on my part using COPY and LIST, instead of ECHO. Dih! Enjoy this file, and if you find any bugs, or wish it had something it presently does NOT have, then feel free to drop me some feedback! - Dotoran! In the Future: ~~~~~~~~~~~~~ I'd also like to make the ability, so that if you select the "CHAT" button from the requestor, it will open that user's screen(if not already open), bring that screen to the front, and then immediately enter CHAT mode for you! I'd still like to do this, however we've discovered a bug in the OPENDISPLAY ARexx command in CNet, so until this command is fixed, this addition will be put on hold. This bug still exists in CNet, v4.22, so until Ray can track this one down, again we wait... :-( - Dotoran! ============================================================================ Frontiers BBS (716)/823-9892! ============================================================================