@CLS@@X0B
     TimeZone is a "time slot" assignments PPE! It limits when users or when
     a group of users can access your system!  Now you can adjust time based
     on when in their slot the user calls! This program is ideal for all net
     mail hubs who can't control when their nodes are calling them...

     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 <g> 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. Note: If you
     are using the "B method" of TimeZone,  this "exemption method" won't let
     them have more time than what would  exceed  TimeZone's "starting time".
     The other way of exempting users on an individual basis  is to place the
     string EXEMPT in the designated user record note field. This method WILL
     totally exempt 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.

