Hi Paul,

 > Does anyone have or know of a decent file that will describe
 > the Binkley.evt file and what order events should go in?


=== Cut ===

;              BINKLEY.EVT - Event File Info for BinkleyTerm
;              Just add to the end of your BINKLEY.EVT file
;
; Extracted from 2.30, 2.40, 2.50 documentation
;
; Event scheduling options are covered in the Reference Guide section titled
; "Scheduling Events." File BT-REF
;
;REM ***       EST in the fall         4 - 5, TZ=EST05
;REM ***       EDT in the spring       5 - 6, TZ=EDT04
;
;Event   [] []

;
;      
;      All . . . . Every day of the week
;      Week  . . . Weekdays, Monday through Friday only
;      WkEnd . . . Weekends, Saturday and Sunday only
;
;      Sun or Mon or Tue or Wed or Thu or Fri or Sat ... that day only
;
;      
;      hh:mm,month,day
;      hh:mm,month
;
;      indicate that the event is to take place on all months
;      hh:mm,0,day
;      i.e. Fri 23:00,0,14 23:00 F E1=131
;
;      In you wanted something to happen every leap year, create an event
;      like this:  All 23:15,2,29 23:15 F E1=132
;
;      []
;      hh:mm   Optional. Not needed except in 'F' flag.
;
;      []
;      This parameter is OPTIONAL.  If used,  designates a
;      string of characters to be added to the command line of the
;      configuration file parameters 'Packer,' 'AfterMail' and
;      'CleanUp.'  The string should be enclosed in quotation marks.
;      Event All 00:00 01:00 "-sA -c"
;
;      Up to 32 extra characters can be added with the 
;      parameter.
;
;  
;
;    A=     This allows you to control the amount of time that
;           BinkleyTerm will sit idle between attempting an outgoing
;           call.  The format is "A=x" where x is the number of
;           seconds desired, which can be a number between 0 and 1800
;           (1800 seconds = 30 minutes).
;           i.e.,   A=60 would yield a wait time in the range of
;                   30 to 90 seconds, 60 being the average.
;                   If no A= set, then default is 120.
;    B      This flag tells BinkleyTerm that BBS operation is allowed
;    C      Only mail marked as Continuous Mail will go out
;    D      This flag tells BinkleyTerm that the event is dynamic.
;           Dynamic events continue until there is no longer any mail
;           of the specified type to be sent.
;           Note that dynamic events must be started before or at the
;           same time as non-dynamic events, if the dynamic event is
;           to overlap a non-dynamic one.
;    F      Event 'forced' and will occur at the first possible moment.
;           If you do use this option, use it only on zero-length events
;    E1=    The 'E1=' option tells BinkleyTerm what errorlevel to
;           exit with at the beginning of the event.
;    E2=    The 'E2=' option tells BinkleyTerm what errorlevel to
;           exit with after mail is received.  The E2= exit is only
;           executed if the incoming mail does not meet the criteria
;           for an E3= exit, or if an E3= exit does not exist.
;    E3=    The 'E3=' option tells BinkleyTerm what errorlevel to
;           exit with after compressed mail is received.  If mail is
;           received during the event, and compressed mail is not a
;           part of the mail received, then an E2= exit is performed.
;           If compressed mail was received (even in conjunction with
;           other mail or files) then the E3= exit is performed.
;
;     Event exits E4-E9 can now be followed by a three character
;     string.  If that string is matched in the file extension of
;     a received file, then the designated errorlevel exit will be
;     taken.  For example:
;
;    E4=100,TIC     (Received .TIC Files Cause Exit 100)
;    E5=100,FLE     (Received .FLE Files Cause Exit 100)
;    E6=110,REQ     (Received .REQ Files Cause Exit 110)
;    E7=120,MO?     (Received .MO? Files Cause Exit 120)
;
;     The order of exit precedence is as follows:
;
;    E3
;    E4-E9
;    E2
;    AfterMail
;
;     When more than one E4-E9 exit applies, the first one is the
;     one taken.
;
;    H      "High-Priority Crash" - Binkley will send Crash flavored
;           mail IMMEDIATELY, no matter what the cost.  All other
;           mail flavors are sent according to cost or other
;           constraints imposed by the current event.  This behavior
;           mirrors that of Crashmail under Opus 1.1x+ with one
;           exception - Crashmail call(s) are made at normal intervals
;           during an H event, rather than forcing a repetitive poll
;           as with Alt-M.
;    K      No send to any nodes marked in the nodelist as #CM
;           Note that this option is only valid when an Opus Version
;           6, QuickBBS or TBBS nodelist is in use.
;    L=     The 'L=' flag is the 'less than or equal to cost' flag.
;    L<     The 'L<' flag is the 'less than cost'
;    L>     The 'L>' flag is the 'greater than cost'
;    M      NOTE!  This flag should ONLY be used when the
;           'NewNodelist,' 'QuickNodelist' or 'TBBSList'
;           configuration file options are used!  The 'M' flag
;           indicates that the event is a 'mail' event, and that it
;           is okay to send mail to anyone in the nodelist,
;           regardless of their #CM designation.  This flag is
;           normally used during local mail schedules, and during
;           National Mail Hour.
;    N      Not to accept inbound file requests during this event.
;    Q=nnn  Inhibits Bink from calling out with less than nnn bytes
;           of data for a node (?LO + ?UT sizes). You should probably
;           have at least one event with Q=0 (the default if none is
;           specified) in order to get the mail out.  (Henry Clark
;           gets credit for this idea)
;    R      Event is 'Receive Only.' Send mail only if polled for it.
;    S      Event which is "send only" meaning that BinkleyTerm will
;           continue to send normally, but will not answer the phone
;           (or if the modem is in auto-answer mode, BinkleyTerm will
;           not respond).
;    T=     This option allows you to control the maximum number of
;           call attempts and failed connects that will be acceptable
;           to BinkleyTerm.  The T= option accepts two parameters,
;           and is used in the format "T=x,y" where x is the maximum
;           number of failed connects (carrier established, session
;           fails - a chargeable call in toll situations), and y is
;           the maximum number of call attempts (no answer, no
;           session - generally NOT chargeable toll situations).
;           The default x parameter is 3, the default y parameter has
;           not been explicitly specified, but is quite high.
;    X      By default, BinkleyTerm will treat outgoing file requests
;           (.REQ files) in the same manner as Normal packets and
;           attaches.  This would include forcing a dial attempt
;           during events that would allow Normal mail to be sent.
;           Sometimes this is undesirable operation, such as during
;           National Mail Hour when destination systems typically do
;           not accept file requests. Using the 'X' flag for an
;           event tells BinkleyTerm not to force a call for a file
;           request.
;
=== Cut ===

        Kevin

--- GoldED 2.50+