;
;	EVENTS.INI: Fido/FidoNet events definition file
;	For: Fido/Fidonet version 12
;	Copyright T. Jennings 
;
;This file defines all of the events that Fido/FidoNet can execute. 
;After making any changes to this file, please be sure to run SET-FIDO 
;to make the changes take effect.
;
; - EVENT EXECUTION: -
;
; Fido/FidoNet searches the event list from top to bottom, and executes the
;first one found that is runnable (current time is within the window) and
;has not been run yet. You can have events that overlap, such as one that
;runs every day, with single-day exceptions before it.
;
;Instructions follow these sample events.
;
;DAY	TIME	WINDOW	EVENT TYPE	DESCRIPTION
;
;	all	9:00	480	Page		;enable the Page command (9a - 5p)
;	all	9:00	180	Page		;enable Page, (9a - noon)
;	all	13:00	240	Page		;enable Page, (1p - 5p)

;	all	2:00	60	FidoNet A	;normal, default FidoNet event (PST)
;cont	all	0:00	1440	FidoNet A	;continuous FidoNet mail
;----------------------------------------------------------------
;
;You do not need to have any events defined at all in order to 
;use Fido; you may want to set an event to allow callers to use the
;P)age-Operator command however. The example supplied does this.
;
;If you want to use FidoNet, the electronic mail program, then you
;need to add one or more events to cause FidoNet to run at a predetermined
;time. Please refer to the manual for details on installing FidoNet.
;
;Each event definition must fit on one line, and the various components
;of the event line must be in the order below; you can use tabs, spaces,
;etc to make it more readable. There is room for 100 events.
;
; - EVENT DEFINITIONS -
;
; You can have any number of the same type events. 
; 
; The DAY is the day of the week the even should run; days are named
;MON, TUE, WED, THU, FRI, SAT, SUN and ALL. ALL means every day; it 
;saves you the trouble of entering seven nearly identical events when you
;want the same thing to happen every day.
;
; The TIME is the time of day the event should start. This is given as
;hours and minutes, in 24 hour format: 00:00 is midnight, 12:00 is noon,
;and 23:59 is one minute before midnight (11:59 PM).
;
; WINDOW is the number of minutes that the event should be run for; if 
;you want an event to run from 9 AM until 11:30 AM, you'd use a TIME of
;11:30, and a window of 150. (2 hrs 30 minutes; 2 * 60 plus 30).
;
;The EVENT type can be any one of the following. Please refer
;to the manual for what the various event types are.
;
; PAGE
;	This is the "event" that tells Fido when to honor caller
;	P)age-Operator commands or not. It is not truly an event. During the
;	time the "event" is active, the P)age-Operator command will try to
;	get the attention of the Sysop, who can talk to the caller
;	via the local keyboard. This example enables the P)age-Operator
;	command from 9:00AM until 5:00PM:
;
; ALL 9:00 480 Page        ;480 minutes is 8 hrs
;
;
; FIDONET (tag letter A - W)
;	This causes FidoNet to run during the specified time. In
;	many cases you will use only "FidoNet A".
;
; ALL 2:00 60 FidoNet A    ;typical IFNA National Mail Hour
;
;
; ERRORLEVEL (number 3 - 255)
;	This causes Fido to terminate to DOS with the specified
;	ERRORLEVEL, which can be tested for within a .BAT batch file.
;	Refer to the manual and to your DOS documentation.
;
;	Note that the "WINDOW" here is somewhat misleading. Fido/FidoNet
;	will run the event only once, regardless of how long it is
;	set to run. What the time does do is allow a wide "window" for
;	the event to run; for instance, a FidoNet event as in the example
;	above won't actually end at 3:00; it does post-processing that
;	takes a few minutes. To compensate for this, set the ERRORLEVEL
;	event wide to make sure it catches it.
;
; Mon 4:00 20 ERRORLEVEL 17 ;exit to DOS at 4:00AM or thereabouts
;
;
; IDLE
;	The IDLE event causes Fido/FidoNet to do nothing at all
;	for the entire event; it will not answer the phone either.
;
; Sat 9:00 480 IDLE        ;be IDLE during business hours
;
;
;
; SPECIAL OPTIONS:
;
; There are special options that can be applied to events. 
;
;OPT:
;Normally, Fido will limit callers time limits so that they do
;not interfere with upcoming events; for example, if there is an
;event scheduled for 9:00 AM, and the caller logs in at 8:45 and 
;has a 60 minute limit, the caller could potentially stay connected
;throughout the entire event, causing Fido/FidoNet to miss it.
;
;To prevent this, Fido will shorten a callers time limit to ensure
;the system will be free to execute the event. (The caller gets
;appropriate warnings, etc as to the shortened limit.)
;
;There are times however when it is acceptable for callers to 
;preempt scheduled events; for example, if you merely need to run
;a program via an ERRORLEVEL event sometime during the day, but not
;necessarily at some specific time, the event modifier "OPTIONAL"
;can be used. This tells Fido/FidoNet not to cut a callers limit short;
;the caller can stay on during all or part of an events time window,
;causing the event to be missed entirely or its start time delayed.
;
; Here are two examples:
;
;OPT	ALL	8:00	240	errorlevel 8	;execute when no user is on
;OPT	ALL	8:00	10	errorlevel 8	;coudl be missed entirely
;
; Assume that the caller has a 60 minute maximum time limit. In the first
;example, if the caller logs in at 7:59 and stays on 55 minutes, the event
;will start at 8:54. No matter what time a caller logs in, the event will
;be run.
;
; In the second example, if a caller logs in before the event and stays 
;connected betwwen 8:00 and 8:20, the event will be missed entirely. This
;is another way of deferring events. Keep in mind that there may be up to
;100 events.
;
;
;RUSH
;RUSH mail is way to make Fido/FidoNet send messages out as soon
;as a caller logs off the system. It does this by modifying
;FidoNet events so that it gets run after each caller logs off,
;and stops the event when there is no mail to send, or no more
;tries left. 
;
;For example, you could define a daytime event such as "FidoNet L"
;to handle only the few system you send to regularly, such as the
;one below:
;
;RUSH All 9:00 360 FidoNet L    ;special FidoNet event
;
;(in ROUTE.L)
;Send-To 999/1 990/23 777/34             ;only these systems
;Send-Only                               ;send rapid fire
;dial-tries 2                            ;try only twice
;
;After any caller disconnects, Fido will invoke FidoNet, and if it
;is between the hours defied (here, 9:00AM until 3:00PM) FidoNet
;will run schedule L. If there is no mail for the systems in the
;send-to line, the event terminates instantly, and Fido will
;accept calls. If there is mail however, FidoNet will attempt to
;send it in the normal manner, in this case as send-only, maximum
;two tries per system. When either the mail is sent, or it has
;tried twice for each system, FidoNet returns to Fido.
;
;There are no restrictions on FidoNet events, schedule tags,
;routing controls or scheduling of RUSH events. You can also
;define RUSH ERRORLEVEL events.
;
;CONT
;CONTinuous FidoNet events allow Fido/FidoNet to handle both human
;callers and incoming and outgoing FidoNet mail at once. New FidoNet
;messages are put into packets, which FidoNet can hold for pickup or
;deliver as necessary, under the control of the usual routing controls.
;(See the manual for routing language details.)
;
;CONT FidoNet events make packets as a normal FidoNet event. But instead
;of the event running til completion, it will (if so enabled) make one pass
;of phone calls, and then return to Fido, where it will accept human callers
;or incoming FidoNet calls. Since the packets aare ready, they can be
;picked up as in a regular event.
;
;Coupled with the mail-errorlevel and file-errorlevel options, you can have
;near-realtime FidoNet and EchoMail processing with very little effort.