Ú¿ ÚÂÄ¿ ¿ ÚÄÂÂÄ¿ ÚÂÄÄ¿ Ú¿ ÚÂÄÄ¿ ÚÂÄÄ¿ ô ô ³ ³ ô ÃÅÄ Ã´ ÃÅÄ Ã´ ÀÙ ÀÙ ÀÄÙ ÀÙ ÀÁÄÄÙ ÀÁÄÄÙ ÀÁÄÄÙ ÀÁÄÄÙ ÚÂÄÄ¿ ÚÂÄÄ¿ ÚÂÄÄ¿ ÚÄÂÂÄ¿ Ú¿ ¿ ÚÂÄ¿ ÚÂÄ¿ ÚÂÄÄ¿ ÀÁÄ¿ ô ³ ÃÅÄ Ã´ ô ¿ ³ ÚÅÁÄÁ¿ ÃÅÄÁ¿ ÃÅÄ ÀÄÄÁÙ ÀÁÄÄÙ ÀÙ ÀÙ ÀÁÄÁÄÙ ÀÙ Ù ÀÙ Ù ÀÁÄÄÙ I n t e l e c S o f t w a r e ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿ ³ TimeZone ³ ÚÁÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿³ ³TimeZone is a "time slot" assignments utility! It limits when users or when³³ ³a group of users can access your BBS! Now you can adjust time based on when³³ ³in their slot the user calls! This program is ideal for all netmail hubs who³³ ³can't control when their nodes are calling them. There are *two* methods of³³ ³operation in TimeZone, (A) the standard way I have seen time slot utilities³³ ³operate is that you assign a user a window. If they call in any time during³³ ³that window they are granted access with their full amount of allotted time!³³ ³Problem here is that if a user has 30 minutes allotted and calls at the very³³ ³"end" of his or her window there's the possibility of this user running into³³ ³the next users "window". So we came up with a (B) option! When using this B³³ ³method of operation you can prevent the above scenario from happening. If a³³ ³caller calls with 5 minutes left in his or her window, TimeZone grants this³³ ³caller just those 5 minutes! Of course, you can still use the (A) method if³³ ³that's your preference. TimeZone also suports exemptions either by security³³ ³level or by "EXEMPT" in the user notes record for that user. If a user calls³³ ³when TimeZone is enabled and they DO have a timeslot, if they called when it³³ ³was their proper time they will be shown a screen showing that TimeZone has³³ ³let them "pass". But if they called outside their assigned time slot, they³³ ³will be displayed the current time, and what their time slot IS, and then itÃÙ ³logs them off. ³ ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿ ³ Installation TimeZone ³ ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ The installation of TimeZone is fairly simple. TimeZone should be in- stalled into logon script questionnaire (my setup is shown below). Run PCBSetup, go to File Locations and then to the Questionnaires section as shown below. Now in my setup, the file defined below as "LOGON" is not actually a script questionnaire, but it's really a text file, also shown below. Substitute file names and paths that apply to your setup. You must also enable the "Notes PSA" in the user records. See PCB doc. ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ» º File Locations º º NewUser/Logon/Logoff Questionnaires º º º º Name/Loc of New Reg Questionnaire : E:\PCB\MAIN\LOGONNEW º º Name/Loc of Answers to New Reg. : º º º º Name/Loc of Logon Script Quest. : E:\PCB\MAIN\LOGON º º Name/Loc of Logon Script Answers : º º º º Name/Loc of Logoff Script Quest. : E:\PCB\MENU\BYE º º Name/Loc of Logoff Script Answers : º º º º Press F2 to edit the NEWASK file or F3 to edit the NEWASKG file º ÈÍ hh:mm ÍÍ mm-dd-yy ÍÍ F1 Í help ÍÍÍ caps: OFF num: OFF ins: OFF ͼ My "LOGON" script questionnaire really only consists of two lines, the first one is the only applicable one for the installation of TimeZone. Change the path to fit your setup though. here's my LOGON script file: !E:\PPE\TIMEZONE\TIMEZONE.PPE !E:\PPE\UAI\UAI.PPE Please note that the ! in the above paths needs to be in column one! This is all that is needed to be done to call TimeZone whenever users call into your system. That's the installation, now to configure it... The configuration file must be located in the same directory as the TIMEZONE.PPE and must be called TIMEZONE.CNF. Config File Details ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿ ³ Not Used ³ -> The first 3 lines are no longer used but ³ Not Used ³ -> must exist. ³ Not Used ³ -> ³ A or B ³ -> See notes on A/B switch (You will love this) ³ 60 ³ -> The "exempt" security level (blank if none) ³ 22:30 ³ -> The time when TimeZone is to be "activated". ³ 06:30 ³ -> The time when TimeZone is to be de-activated ³ 1 ³ -> Which note line to write time slot or EXEMPT ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ to in user's record. Enter time slot as (ex) 02:30-03:30 in the 1st 11 spaces in the note field. Don't put anything else in this field! See note below on the EXEMPT flag in the user record notes. ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿ ³ TimeZone PCBoard 15.2 PPE Time Slot Manager! ³ ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ The A/B Switch! There are now two methods of operation in TimeZone now! A, the standard way I've seen any time slot utility operate, is that you assign a user a "minutes window". If they call in any time during that window then they are granted access with their full amount of allotted time. Problem here is that if a user has 30 minutes allotted and calls at the very "end" of his or her window, there's the possibility of this user running into the next users "window". Scenario: John Smith has a time slot of 06:30-07:00 and Jim White has a window of 07:00-07:30. They both have 30 minutes per day allotted to them. If John Smith calls at 06:59 he can tie up the BBS until 07:29. Now, Jim White has only 1 minute in which to make his time window. Thus the B Switch! When using this B method of operation you can prevent the above scenario from happening. If John Smith calls at 06:45, instead of having his full 30 mins, now he only has 15 mins, preventing him from interfering with Jim White's time slot. I do this by adjusting the "time left" info in the user record, *not* the time used info. This way if they call back when TimeZone is not enabled they have their full allotment of unused time. But there are the traditionalists who will prefer to run this the "standard" way, and if so, just use the A Switch. Exempt Flag Options There are two ways of exempting users from being effected by TimeZone's operation. One is exempting all user with xx security level or higher by entering this desired security level on line 5 of the config file. (Ex:) If you want to exempt level 60 users and higher from being "cut off" by TimeZone, place a 60 in line 4 of the config file. If there's a user who has a securoty level below 60 and you want to exempt this user as well, then place EXEMPT in the first 6 spaces of the notes field. This method totally exempts the user from any type of time adjustments that TimeZone would normally attempt to make on the user regardless of who's time slot this user may infringe upon. This should not be used too frequently but has been included to make TimeZone the most effective and flexible way to manage time slots on your system. What It Does To Who If a user calls you when TimeZone is enabled, and they do not have a slot, they will be displayed the time, the time frame that TimeZone is enabled, and then logged off. If a user calls you when TimeZone is enabled, and they DO have a time- slot, if they called when it was their proper time they will be shown a screen showing that TimeZone has let them pass. But if they called outside of their assigned time slot, they'll be displayed the current time, and what their time slot IS, and then it logs them off. Also, if you want to run TimeZone on one node only (or specific nodes) then on this (or these) nodes you'll need to update that nodes' PCBOARD.DAT to reflect a "different" logon script that contains TimeZone in it only.