Bug fixes
---------

???: Fixed cosmetical problem with Elapsed: xx:yy:zz

  A trailing blank overwrote the window frame


???: Fixed cosmetical problems with Zoomed Outbound view

  EE colours and headline


???: Fixed SRIF extension (wrong) .Txx to (correct) .xx (xx=TaskNo/Hex)


???: Fixed cursor position when shelling or entering terminal mode


???: Added Hydra key to "native_protocols".

  Until now, you were not able to select Hydra in terminal mode ...


???: Fixed "main outbound removal" bug when using "MakeDir".

  If there is an outbound without "." in its filename then just let it be -
  even if it's empty.


???: Fixed ShortCostLog $m


???: Fixed cursor positioning to end of screen


???: Fixed saving of recent activity window

  It is now saved on all exits, not only on Alt-X exit


TJW: fixed >2GB bug

  Changed free space limitation from 2GB to 128GB (please test this! ;-)


TE/TJW: Fixed % character

  Usage of % character in modem commands is now possible (see below).


???: OS/2 only: Priorities

  Assured that answering and in/outbound sessions run at MODEMPRIORITY With
  ZedZap, session were running at REGULARPRIORITY until yet. Now, session run
  at least with MODEMPRIORITY (or with JANUS/HYDRAPRIORITY).


???: Bugfixes to SRIF

  SRIF now (finally!?) correctly states which system is listed and which is
  protected.


???: Bugfixes to FreePoll


???: Fixes for dialtry's bug while using FreePoll


TJW: Fixed *.REQ bug

  If a session was aborted, *.Rxx files kept lying around and the next caller
  got all the stuff he did not want. Especially long distance links were quite
  unhappy with that, if the requested stuff was large.

  Now BT-XE deletes the <inbound>\<address>.R<task> request files for ALL your
  own addresses at the end of the session.


???: Removed additional "newline" in Binkley.Log after SPAWN and ext. protocols.

  Additional newline is only printed at start of BT. This was maybe only the
  case in some internal betas ...


???: Fixed bug that TimeSync was not executed if mail was received.

  Moved call for TimeSync direct to end of session. Mail exits etc. will be
  done *after* TimeSync now.


???: Fixed SRIF response file naming (correct e.g.: outbound.zzz\NNNNnnnn.QLO)

  Should work together with function request programs now.


???: Fixed SRIF session data in Yoohoo / FTSC sessions

  If you had a EMSI session and after that a Yoohoo session with a SRIF freq,
  wrong data was put in the response packet (Sysop name, site, mailer).


???: Fixed some bugs in ShortCostLog output routine


TJW: fixed "NoPickup" bug

  If you had NoPickup in your config and called a remote system using Bink 2.60
  (XE or original, doesn't matter) to send some stuff, the remote Binkley
  terminated the session immediately without even receiving your stuff.



New features
------------

???: Enhanced CPS log entries (with lower .. upper CPS rate for each xfer)


???: Debug messages for creating / removing outbound directories


???: Added "Rescanning" status msg while outbound rescans


???: Source code: replaced all TABs by SPACEs for easier DIFF/RCS/CVS handling


???: Changed hydra crc table allocations from dynamic to STATIC


???: Wrong config verbs

  Added delay if wrong config verbs are read, also added filename and line
  number to error message.


???: SRIF

  The SRIF file now also contains a "Password SECRET" (if SECRET is the actual
  PW in protected sessions) line. This line is only present on PW protected
  sessions.


???: Log files

  The logs are closed when spawning to allow other programs to include their
  logs in the main log.


TE: Support for a PROBOARD fileindex

  Rather than scanning your whole hard disk for each file request, information
  can now be taken directly from your Proboard configuration, so that a) you
  don't have to set up a huge OKFile and b) file request is accelerated
  considerably, allowing for filerequest from CDROM. Perform the following
  steps to set up Proboard support (this works much like the configuration of a
  Maximus fileindex):

  Add the following lines to your Binkley.Cfg:

    PBAreas <Proboard Fileareaconfig>

      The Proboard Filearea configuration file is usually named "FILECFG.PRO"
      and located in your Proboard system directory.

      Example: PBAreas e:\mailer\pb\filecfg.pro

    FileSec <level>
    KnownSec <level>
    ProtSec <level>

      In Proboard, you use "levels" (numbers from 1 to 255) to set up which
      users are allowed to access which files. In BinkleyTerm, calling systems
      area classified as unknown (->FileSec), listed in your Nodelists
      (->Knownsec), and those with a session password (->ProtSec). Here you can
      set up the correspondence between the two security mechanisms. If you,
      e.g., enter KnownSec 30, then every system which is listed in your
      nodelist may freq from file areas with a security level of 30 or below.
      You should always have a FileSec statement, while the two others are
      optional.

    OKFile <okfile>

      You normally already have this statement, where <okfile> is the path and
      name of a text file containing your magics and filearea paths.

  Now edit your OK-File. Leave the magics there, but remove all normal
  pathnames. Instead, enter the following line:

    *<Proboard Fileindex>

      The Proboard file index is usually named FILESIDX.PB and located in your
      Proboard system directory.

    Example for a OK-File with PB-support:

      @FILES    e:\mailer\filebase\filelist\ALLFILES.ZIP
      @UNISCHED e:\mailer\filebase\fidosoft\UNISWB05.LZH
      @NODELIST e:\mailer\nodelist\nodelist.lzh
      *e:\mailer\pb\filesidx.pb

  Please note that you must not use MaxAreas and PBAreas at the same time! Only
  one of these keywords should occur in your Binkey.Cfg. - Also note that you
  should run PBUTIL FI at least once a day in order to keep your fileindex up
  to date.

  As the Proboard fileindex is not fully documented, this feature is
  experimental. I have tested this with PB 2.12 and PB 2.15. If you have
  problems with future Proboard releases, please contact me via netmail.


TJW: Loglevels

  Negative LogLevels do the same as positive ones, but only log to disk if
  Carrier detect is true.


TE/TJW: Changed config file parser (; and % character treatment)

  '%' has a VERY ambiguous semantics:

    - It can prefix a "rest of line"-comment (if it is at 1st non-white-space
      column position in the config line).
    - It can designate the start/end of an environment variable reference.
    - It can be used simply as "%" character.

    We resolve this the following way:

    1. If first non-white-space char, it is a comment.
       e.g.: "%comment" or "     %comment"

    2. If there are some characters between 2 percent signs try to evaluate an
       environment variable of this name.
       e.g.: "%TASK%" or "%task%" or "%What_Ever!%%What_Else?"

       If there are no characters between two "%" ( = "%%"), use it as a single
       "%" character.
       e.g.: "Init AT%%B%%C %%D" -> "Init AT%B%C %D"

       If the environment variable is not defined, just copy the name of it.
       e.g.: there is not variable "NOTDEF" defined. "%NOTDEF%" -> "NOTDEF"

    4. If there is only a single "%" in the whole line, also use it as a single
       "%" character.
       e.g.: "Init AT %B" (no other % in this line) -> "Init AT %B"

    BTW: %WHATEVER%%TASK% - this is valid and interpreted correctly
         1        2A    B               (two environment variables).

         This is no problem with the %% at pos 2 and pos A - because first
         %WHATEVER% is evaluated (and consumes both % at pos 1 and pos 2).
         Afterwards, %TASK% is evaluated ...

  ';' is a bit WEIRD, too:

    It can be a "rest-of-line"-comment or a literal character.

    We resolve this the following way:

    1. If first non-white-space char, it is a comment.
       e.g.: ";comment" or "    ;comment"

    2. If there is a sequence "<white space>;;", then don't begin a comment,
       but just read it as "<white space>;".
       e.g.: "AT ;;XY" -> "AT ;XY"

    3. If there is a sequence "<white space>;" (and no ";" following), it is a
       comment.
       e.g.: "Init ATZ|      ; init the modem"

    4. In any other case, just read it as ";" - no comment.
       e.g.: "AT;XY" -> "AT;XY"


TE: Workaround a problem when scrolling the Recent Activity window

  The appropriate keystroke combinations Ctrl+UpArrow, Ctrl+DownArrow are
  nonstandard and do not work in some DOS environments. You may now
  alternatively use Ctrl+RightArrow and Ctrl+LeftArrow (which should work
  everywhere).

  Note:  If Scrolling continues refusing to work, increase the size of the
  -----  backscroll buffer by using "RecentActivityLines 300". This should
         only be a problem in the DOS version.


TJW: Priorities

  Lowered default JANUSPRIORITY and HYDRAPRIORITY values to F31 (was T31 yet)
  and default MODEMPRIORITY to F15 (was F31 yet). Added possibility to set Idle
  priority (be careful with setting prio to low).

  You may influence priorities using these environment variables:

  This is the default:                 This is as without priority control:
    SET REGULARPRIORITY=R31              SET REGULARPRIORITY=R0
    SET MODEMPRIORITY=F15                SET MODEMPRIORITY=R0
    SET JANUSPRIORITY=F31                SET JANUSPRIORITY=R0
    SET HYDRAPRIORITY=F31                SET HYDRAPRIORITY=R0

  Syntax: ...PRIORITY=<class>[delta]
    class:
      I = Idle (1)
      R = Regular (2)
      F = Foregroundserver (4)
      T = TimeCritical (3)
    delta:
      0 = normal
     ..
     31 = high (default, if not specified)


???: Changed M_BYTE_SUMMARY to show KB size instead of Byte size


???: Changed update_status()

  Changed janus/hydra update_status() to show min:sec instead of minutes for
  time remaining until completion of file transfer (ETA).


???: Cleaned up STATIC variables and made some dynamic - saves DOS memory ...


CE: "ChangeMailTo <flavour>"

  This is used for changing mail flavour to CRASH, DIRECT, NORMAL or HOLD after
  an rejected outbound call. The default is the change to Normal flavour.


TJW: Implemented xHydra / RH1 hydra

  This modified Hydra (which identifies in EMSI with RH1 flag) does file
  requests ONLY in the 1st transfer "batch". Mail packets and all flow file
  attaches are sent in the 2nd batch - while you already get the requested
  files from the other system!

  Until now, this was only possible with Janus - now you can do this with
  Hydra, too! So just send your filelist along with your filerequests if the
  other system supports RH1 / xHydra, too.

  Until now I know of these xHydra mailers: BT-XE ;-), Xenia and Maindoor If
  xHydra is used, this is shown via "Session method: xHydra".


???: Modified output of AKAs

  Until now there were 3 AKAs per line. Now the AKA: lines are "filled up" with
  AKAs as it fits on the screen (assuming 80 chars width).


???: Added message

  Added message "Rejecting human caller" if BBS caller tries while a MO event.


???: Added message for FreePoll / ConditionalPoll

  "Accepting <nodenr>. First call. ..." to avoid user confusion if a link calls
  the very first time using Freepoll (no TRX file present in outbound).


???: Removed warnings from BTLNG


HR: Enhanced user dialogue with Alt-G (get file[s]).

  BT-XE will now show destination address and system name after you entered
  dest address. You can now enter up to 3 filenames password flavour before the
  question "More Yes/No/Other" is asked.


HR: Enhanced user dialogue with Alt-S (send file[s]).

  BT-XE will now show destination address and system name after you entered
  dest address.


HR: ShowAlive

  The file I_ALIVE.xx is now generated also at transfer via Hydra, XModem,
  ZModem, Janus and Fax-Receive.


???: Changed freepoll volume compare to use "reject if size <= MinSize*1024"

  This means if you configure MinSize=0 only calls with really NOTHING on hold
  will be rejected. Until now, configuring 0 made no sense (size < 0 ?).