Bug fixes
---------

See knwnbugs.xr5 for a complete list of bugs / problems in XR5. All bugs with
status 'F' should be fixed in this version.



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

CFS: Expanded NodeExtraDir.

  New syntax is

     NodeExtraDir address directory [Hold] [Notify]

  Hold makes BT-XE *not* send the files when calling (obvious, uh?).

  Notify makes BT-XE generate a message on the fly, notifying the remote of the
  files being sent. Usually helps the remote to keep his inbound clean, or at
  least without unknown files.


CFS: Stats

  The stats screen nows support going up and down in all lists, by using the
  arrow keys. This way you can see the complete lists instead of the top
  systems only. Also, left and right may be used to go to the previous/next
  screen.


CFS: Added random node information system.

  Three new keywords for this:

     RandomSysop       group,[group,...] Sysop name
     RandomSystem      group,[group,...] System name
     RandomMyLocation  group,[group,...] Location

  The group is an user selected tag that may contain a number of sysop,
  system and location definitions.

  BT-XE chooses a group randomly before each call. Then it chooses a
  sysop name, a system name and a location from that group.

  A example:

     RandomSysop     BEACH Carlos "hot" Fernandez
     RandomSystem    BEACH Enjoying the Spanish summer
     RandomSystem    BEACH Possibly swimming!
     RandomLocation  BEACH Somewhere with water
     RandomLocation  BEACH On vacation!

     RandomSysop     BT-XE Carlos "coder" Fernandez
     RandomSysop     BT-XE "C"arlos Fernandez
     RandomSystem    BT-XE A Binkley-XE Development Site...
     RandomSystem    BT-XE Can't stop coding BT-XE stuff

  If one string is ok for two groups, you may separate them with commas,
  for example

     RandomLocation  BEACH,BT-XE Madrid, Spain

  If something is not defined for a group, BT-XE will just pick the default
  string, defined by Sysop, MyLocation or System (so these keywords are
  still required).


CFS: Improved history screen

  Now it is almost complete or at least very close to what I wanted to do.


CFS: Added a new stats page.


CFS: Address

  Expanded Address with a new optional parameter, 'region'. For example

     Address 2:341/70 34

  Adds 2:341/70 to the address list (as always) and 2:34 to the region
  list. As of now it is only used in for the 8th page of the stats.


TJW: added DZA capability (DirectZap ZedZap variant)


TJW: new keyword "NoDirZap" to globally disable DirectZap


TJW: added keyword "DebugFlags <8 digit hex value>"

  This sets an internal variable of BT-XE used for debugging.
  To be used by BT-XE bug hunters together with BT-XE team.
  *** DO NOT USE IF YOU DON'T KNOW WHAT YOU ARE DOING! ***


TE:  new keyword "IPRepChar"

  I added this keyword in reflection of the test listing of IP nodes in
  the zone 2 nodelist. The problem with these nodes is that MakeNL can't
  cope with phone numbers with dots in it, so the IP nodes get listed
  with dashes instead of dots, e.g. 000-192-168-1-1. For existing
  fidonet configurations, it is no problem to remove the leading "000"
  (see the Dial keyword), but it is a problem to replace the dashes with
  points. For this purpose, you can use the keyword "IPRepChar". Simply
  add

    IPRepChar -

  to the configuration of your vmodem task, and every dash will be
  replaced by \. (which means a single point) when dialing out.

  Don't use this keyword on a "conventional" modem line!


CE: added keyword "CheckPath <Errorlevel> <Checktime in sec.>"

  checkroutines for not existing network drives. If inbound,
  outbound, flagdir or netdir isn't available in an waiting binkley,
  because fileserver is down, then binkley terminates immediately.
  - 'Errorlevel' is the errorlevel when binkley exit. Default is 253,
    allowed is 1 - 255.
  - 'Checktime' is the time in seconds between 2 checks. Default is 30,
    allowed is 1 - (2^15)-1 (short int).


AW: request via maxfiles.idx with internal request processor

  Files with full paths in compiled Maximus filebase will be found and sent, if
  files.dat+files.dmp are present. Previously only the files in the main
  filearea path could be found. One reason less to use a request processor ;-)


AW: Maximus 3.0x support with maxfiles.idx request

  With the new keyword:

    MaxPrm  <path+filename of max.prm>

  it is possible to specify a the max.prm of a Maximus 3.0x setup. Then
  the filearea data is taken from the Maximus setup. No need to generate
  the Max 2.x-compatible area.dat file any more!
  It is no problem to specify a Maximus 2.x max.prm with the keyword, it
  will be auto-detected by BT-XE which version it is.
  The MaxAreas keyword therefore is obsoleted with this.

  The request security has been enhanced accordingly:

    FileSec   class/flags
    KnownSec  class/flags
    ProtSec   class/flags

  class/flags could of course also be numeric_level/flags or only class or
  only numeric_level.

  With the new syntax you can specify a Class/Flags combination that is
  matched against the acs strings in the filearea file. The acs strings
  are fully interpreted by BT-XE like in Max 3.0x, that means things like:
  ACS Sysop/A|Twit/B!X|name=testy_tester
  are supported. The name= option of the acs strings are matched against
  the sysop name that is transferred in the handshake.
  If you changed the default classnames of Maximus 3.0x from Twit, Disgrace,
  and so on to your own classnames, it will work too, as BT-XE will read
  your Maximus 3.0x access.dat security database and interpret the new
  classnames and levels.

  For Maximus 2.x, a level<=>classname reference is now built-in, so you
  could use now "FileSec Worthy" instead of "FileSec 3", if you like.
  You can also specify a Maximus 2.x max.prm with "MaxPrm", the version
  will be auto-detected and the 2.x or 3.x mode chosen as necessary.


AW: Binkley now transmits offset to UTC in EMSI

  You should make sure your TZ variable is set correctly, see tz_ibm.doc or
  tz_watc.doc.

  In the EMSI handshake now the TZUTC addon like with FD 2.12 or FD 2.20c is
  sent, telling the offset from local time to UTC. The transaction number
  itself is local time and so are the timestamps in the history file and the
  timestamps of disk files.

  Now the UTC value of the transaction number can be calculated and the time
  difference to the local system clock is always around +-0 and not multiples
  of 3600 seconds because the remote time zone was previously unknown/unset.


MR/AW: NodeTimeZone <addr> <TZ string _without_ TZ=>

  Use this keyword to set the time zone of a node.

  If the remote system doesn't send a TZUTC value, the time zone and therefore
  his time offset to UTC is unknown. With NodeTimeZone you can set the TZ
  string for this node and you will get correct time difference values for
  timesync operation.
  Remember: set your TZ variable correctly to get correct time values.

  - for systems that transmit only its local time in tranx and that are
    in the same time zone as your system, you don't need to set NodeTimeZone.
    Logfile example:

     : 10 Feb 15:45:03.14 BINK RemTim: Tue, 10 Feb 1998 18:45:01 +0100
     : 10 Feb 15:45:03.14 BINK LocTim: Tue, 10 Feb 1998 18:45:02 +0100
     : 10 Feb 15:45:03.14 BINK UTCdif: -1

  - for systems that transmit its local time in tranx and the TZUTC EMSI Addon,
    you don't need to set NodeTimeZone. This is the case, if the reported
    time offsets in logfile are different from one another. Also the time diff
    is not multiples of 3600 but a small number near +-0.
    Logfile exampe:
                                                                 vvvvv
     : 10 Feb 15:45:03.14 BINK RemTim: Tue, 10 Feb 1998 18:45:01 +0100
     : 10 Feb 15:45:03.14 BINK LocTim: Tue, 10 Feb 1998 12:45:02 -0500
     : 10 Feb 15:45:03.14 BINK UTCdif: -1

  - for systems that transmit only its local time in tranx and that are
    NOT in the same time zone as your system, set a correct NodeTimeZone for
    this node.
    Logfile example:

     : 10 Feb 15:45:03.14 BINK RemTim: Tue, 10 Feb 1998 18:45:01 +0100
     : 10 Feb 15:45:03.14 BINK LocTim: Tue, 10 Feb 1998 12:45:02 +0100
     : 10 Feb 15:45:03.14 BINK UTCdif: +21599

    If your timezone is TZ=CET-1CDT, set "NodeTimeZone <node> EST5EDT"

  - for systems that transmit its local time in tranx and a false value in the
    TZUTC EMSI Addon, set a correct NodeTimeZone for this node. That will
    override the false value from the handshake.

  - for systems that falsely transmit UTC time in tranx (instead of his local
    time), set "NodeTimeZone <node> UTC0" for this node.


TJW: merged history importer utilities into BTUTIL

  They are invoked now by: BTUTIL GETHIST ...


TJW: some new alias keywords

  Inbound               - same as NetFile
  Outbound              - same as Hold
  OutboundRescanPeriod  - same as ReadHoldTime
  OutboundCache         - same as CacheHold

  Please use the new keywords because it's likely that we remove the old ones
  in a future release.


CE: added keyword "AKAMatching".

  AKAMatching shows an incomming EMSI caller only your AKA's, if the zone is
  identical. If the zone is differend, the caller will not see your AKA. This
  feature is importent for big systems with many AKA's, because you can reduce
  the number of AKA's for smaller systems with know only 10 or 20 AKA's


AW: changed the history file (callhist.all) format for the DOS version

  If you upgrade from the XR5 DOS version, you must convert the history
  file (callhist.all) before you upgrade to XR6. Use the program
  xr5toxr6.exe. Use it only if you upgrade from the XR5 DOS version,
  not from any other version, and use it only once.

  Due to a small error in the history file definition the format for the
  XR5 DOS version was slightly different from the OS/2 or Win32 version. The
  XR6 format is now equal among all three OS versions.


MR: Enhanced [expression] (partial config inclusion / exclusion).

  You can now use:
   - [exp1] & [exp2] - means exp1 AND exp2 must evaluate to TRUE.
   - [exp1] | [exp2] - means exp1 OR  exp2 must evaluate to TRUE.

  You can connect as many [exp] with & or | as you like. The evaluation is done
  from left to right.

  Examples:
   [%task%==1]                              ;only task 1 (as usual)
   [%task%==1] & [%OS%==OS2]                ;only task 1 under OS/2
   [%task%==1] | [%task%==3]                ;only task 1 or 3
   [%task%==1] | [%task%==3] & [%OS%==OS2]  ;only task 1 or 3 under OS/2
   [%OS%==OS2] & [%task%==1] | [%task%==3]  ;only task 1 under OS/2 or task 3


CE: added Keyword "NodeInboundDir <AKA> <Directory>"

  NodeInboundDir allowes you to specify an extra inbound directory for an
  node, to handel his mail as special mail. The directory entry ignores the
  original inbound entrys (unknown, known and protected) for this node.
  - AKA is the nodenumber
  - Directory is the new inbound directory.


CE: change "StartBlkSize" from max. 2048 to max. 8192 (8k ZModem block at
    begin)


CE: added keyword "NoModem"

  with NoModem you don't need a COM port for Binkley. It is nessesary if you
  need a schedula without a modem. At the time this keyword is for OS/2 only.


CE: added "SyncHydraSessions <AKA>"

  with SyncHydraSessions you will only SEND data while RECEIVEing data in an
  Hydra session. This is only active in outbound calls.


CE: added size calculation of NodeExtraDir for #MOH and freepoll


HJK: Removed keyword "WinFossil"

  The use of the WinFossil for the Windows version routines now depends on
  which version is used, the NTCOMM version (for NT) or the WinFossil (for 95).


CE: added flag-file BTENDSES.%TASK%

  BTENDSES.xx terminates an active session when sending files to the downlink.
  It will not kill the session on incomming files!


HJK: "AfterMail" new style with WIN32

  AfterMail should also work in the new style now under Win32. Please refer for
  the syntax to the OS/2 implementation section by RH.


HJK: "Shell" keyword new style both OS/2 and WIN32

  Shell keyword now works same as the AfterMail keyword:
   Old Style: "Shell <any string>"
   New Style: "Shell [#]<any string>"

  I changed this to start a detached session of "shell" program. The session is
  in VIO-mode, independent and gets the starting binkleys environment. It will
  be started minimized and invisible.

  To enable detached sessions you have to:
   1) add the "#" char (this signals your intentions)
   2) change the command this way: Shell #<program-path>\program.exe

  Example: Shell #c:\bink\squish\squish.exe

  If you don't change your config, nothing changes. The char "#" is removed
  if you don't run OS/2 or WIN32.


HJK: "WindowTitleFmt" and "SharePort"

  Those keywords can now also be used in Windows version, "SharePort" works
  only in the NTCOMM version. With almost the same beheaviour as in the OS/2
  version.


SMS: added support for "ExtrnMail <errlv> RING"

  You may also use ExtrnMail for "RING" now. This is intended for use with a
  voicebox, e.g. ANSW.EXE.
  The "RING" is just "RING" and NOT the response from your modem. Even if your
  modem says "RINGING" on incoming calls you have to use "RING".


SMS: added CallerID to EXTMAIL.CMD / SPAWNBBS.CMD

  The CallerID now is passed as %7 to EXTMAIL.CMD and %6 to SPAWNBBS.CMD.
  You may use the following commands to distinguish CallerID and the extended
  connect string in the batch:

    SET CALLERID=%6
    SET CONNECT=
    IF NOT %7.==. SET CALLERID=%7
    IF NOT %7.==. SET CONNECT=%6
    ECHO CallerID: %CALLERID%, Connect: %CONNECT%


AW: removed "HoldAfterBadConnect"