OpenAFS for Windows 1.5.0 Development Release (17 Feb 2006)

Release 1.5.0 of OpenAFS for Windows is the first in a series
of unstable development builds leading up to the 1.6 stable 
release series.  

1.5.0 includes the following new functionality that is subject 
to change:

(1) Native Support for AMD 64-bit Windows platforms
MSI installers for 64-bit Windows platforms are now available.
NSIS has not yet been ported to 64-bit Windows.  The MSI provides
a native 64-bit AFS Client Service and set of tools.  At the 
present time there is not an installer for the subset of the
32-bit tools required to interface with 32-bit versions of MIT
Kerberos for Windows.  

(2) Build system changes
The build system has been modified to include the "sys_name" 
in the destination and object file paths in order to allow
multiple builds to take place in the same tree.

(3) Above and beyond the SMB Server re-write in 1.4.1, there 
are further optimizations in 1.5.0

(4) Code has been added to prevent the client from Pinging
a server simultaneously from multiple threads.  This will
reduce the work load of the server and reduce the time it
takes to establish new connections.

(5) Registry entries allowing the daemon thread's check 
intervals to be set.  These registry values are stored in
HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters
with type DWORD.  The units are in seconds.  In general the
default values should not be altered.  To deal with a broken
NAT the Up interval can be set to 30 seconds.

   daemonCheckDownInterval
   daemonCheckUpInterval
   daemonCheckVolInterval
   daemonCheckCBInterval
   daemonCheckLockInterval
   daemonCheckTokenInterval

(6) Windows Event Log Message Text resources are now provided.

(7) New Event Log messages are added for "Crypt" state transitions.

(8) Faster implementation of "fcrypt" algorithms improves throughput.

(9) The RX library can now be debugged by capturing DebugOutputString 
messages.

(10) 1.4.1 added a byte range lock allocation engine to the SMB Server
but without any backing by AFS File Locks.  1.5.0 turns on the use of
AFS File Locks.  However, it is important to note that the use of AFS
File Locks is controvertial for some organizations.  There are currently
discussions of extensions to the AFS3 Protocols to allow the use of 
AFS File Locks to be influenced by administrator policy.  As such, the
behavior of locking in each subsequent 1.5.x release may change.