THE SCHEDULED EVENT EDITOR
                          ____________________________


     Upon entering the event editor, a screen as follows appears.
     ________________________________________________________________________

     NN:Description                   :Typ:Bsy:Time :Len:Days   :Execinfo
     ==:==============================:===:===:=====:===:=======:============
     +1  Pack Messages                  Pak 0   00:00 292 SMTWTFS pack

     Event editor (?=help) :
     ________________________________________________________________________

           <CR>Redisplay menu
           (D)elete   (I)nsert
           (M)odify   (P)osition
           (Q)uit

          <CR>Redisplay menu -- Redisplays the listing of events.

          (D)elete -- This will allow you to delete an unwanted event.

          (I)nsert -- This will insert another event into the list.

          (M)odify -- This will allow you to modify an existing event.

          (P)osition -- This will move an event from one position to another.

          (Q)uit -- Exits the Event Editor.

     When you select the (M)odify command, you are asked to select the
     event that you would like to modify.  After choosing, the event data
     is displayed.
     ______________________________________________________________________

        Event #1 of 8

        !. Active       : Yes
        1. Description  : Pack Messages
        2. Sched. type  : Pack msgs
        3. Event data   : pack
        4. Off hook time: None.
        5. Exec. time   : 00:00
        6. Busy during  : Yes
        7. Soft event   : Yes
        8. Run if missed: Yes
        9. Last day exec: Today
        A. Days active  : SMTWTFS
        B. Node number  : 0

        Edit menu (?=help) :
     ______________________________________________________________________

          !    This determines whether or not the event is active.

          1    This field describes the event.  (Up to 80 characters)

          2    This is the type of event that will be executed.  There are
               six choices:

                    ACS -- Enables only certain callers who have the correct
                         security settings to access the BBS at a certain time
                         of the day.

                    Chat -- Not implemented yet.

                    DOS -- Shells to the DOS level and executes files defined
                           in the Event Data.

                    External -- This requires a batch file for execution, which
                         is used to detect an ERRORLEVEL value.

                    Pack -- This event packs the message bases by removing
                         all deleted messages and adjusting the number of
                         messages in each base to conform to the maximum
                         limit set in the message base editor.

                    Sort -- This event sorts the file bases by scanning the
                         directories and sorting by name.

          3    This field will vary with the type of event being executed.

                    DOS -- The name of the program to be run.

                    External -- The ERRORLEVEL value to be used when the BBS
                         quits to DOS.

                    ACS -- The ACS setting that users must have.

                    All others -- Not used; the event data field will be
                         ignored.

          4    This is the time before an event that the BBS will become busy.
               If a user is online, their online time is adjusted for the
               event.


          5    This is the time of day that the particular scheduled event
               will occur.  It is defined in the 24-hour format.

          6    This field determines whether or not the modem will be made
               busy during the scheduled event.

          7    This tells if the event is "Hard" or "Soft".  Hard events
               will make Renegade shorten a user's time online if it will
               keep them on longer then when the event will run.  Soft events
               wait for the user to logoff before the event is run.

          8    This field determines if the BBS should run the event if it
               missed it the last time it was supposed to be run.

          9    This field sets the number of days since the event was last
               run.

          A    These are the days of either the regular week, or the month,
               that the scheduled event will occur.

                    Weekly -- Event will occur at least once every week.  A
                    bar with the current days active will be displayed as
                    follows:

                              Current: SMTWTFS
                                      [       ]

                    Modify by entering "X"'s under the days the event is to be
                    active.

                    Monthly -- This will occur only one day in the month, and
                            is modified by entering the day it is to be run.

          B    This field determines which node will run the event.  0 means
               the first free node will run it.

          [    This will jump back one entry in the list of events.

          ]    This will move forward one entry in the list of events.

          F    This will move to the first entry in the list of events.

          L    This will move to the last entry in the list of events.

          J    This will jump to a specified entry in the list of events.

          Q    Saves all entries in the list of events and returns to the
               main editor screen.

*-----------------------------------------------------------------------------*