final pre-1.3.71 build available for testing

I have uploaded what I expect to be the final pre-1.3.71 build
of OpenAFS for Windows.  The reason for the delay is the problem
with 1.3.70 on AIX.  (see openafs-info discussion).

Daily builds can be found at:

   /afs/athena.mit.edu/user/j/a/jaltman/Public/OpenAFS/
   \\afs\athena.mit.edu\user\j\a\jaltman\Public\OpenAFS\
   http://web.mit.edu/~jaltman/Public/OpenAFS/

Since 1.3.70:
   * A new Windows authorization group "AFS Client Admins" is now
     created and populated with the members of the "Administrators"
     group.  The group is used to determine which accounts on the
     machine may be used to modify the AFS Client Configuration via
     the UI and command line tools.  afs_config.exe, fs.exe,

   * Modify the WinLogon Logoff Event Handler to query NT4 domain
     controllers for the remote profile path if Active Directory
     services are not available.

   * Fix aklog.exe to not add the AFS ID to the username

   * PTS registration of new users to foreign cells has been added to
      afscreds.exe

   * The cm_Daemon thread is used to perform checks for
     down servers, up servers, volumes, callback expirations,
     lock maintenance and token expiration.  Due to a gaff in
     larger integer division the thread never performed any
     work.  Instead the current time computation would always
     be less then the trigger times.  This had an adverse affect
     on the client's ability to maintain communication with servers,
     keep volumes up to date, and flush user tokens and acls
     when they have expired. This was broken when the 1.3 branch
     was modified to support VC7 which no longer included
     largeint.lib

   * An initialization problem with the Freelance code was
     detected while fixing the callbackRequest.  The cm_rootSCachep
     object is obtained during afsd_InitDaemons() but the callback
     information is incomplete.  The callback information will not
     be obtained until cm_MergeStatus is called from within
     cm_GetCallback.  Unfortunately, cm_SyncOp did not properly
     test for the conditions under which the callback information
     must be obtained.

   * Reports have been filed indicating that callbacks were
     being lost.  An examination of the code indicated that the
     cm_server_t objects were not being properly reference
     counted by the cm_scache_t and cm_callbackRequest_t objects.
     In particular, the cm_server_t objects may have been freed
     from beneath the cm_conn_t objects.

     All of the reference counting is now done via the functions:
         cm_GetServer
         cm_GetServerNoLock
         cm_PutServer
         cm_PutServerNoLock
     this improves the ability to track the referrals.

     Each cm_BeginCallbackGranting Call now allocates a reference
     to the cm_server_t.  The cm_EndCallbackGrantingCall either
     frees the reference or transfers it to the cm_scache_t
     cbServerp field.  These are then appropriately tracked
     through the cm_Analyze call.

   * Ensure that the dnlc hash table is the same size as the
     dir name hash table (as per original author's note).
     Increase the dnlc CM_AFSNCNAMESIZE to a multiple of 8
     for compatibility with 64-bit systems.

   * fix smb_ApplyV3DirListPatches to properly apply the hidden
      attribute to dotfiles when the infoLevel < 0x101 and
      cm_SyncOp has failed.

   * Fix the Freelance registry initialization code.  There
     was a possibility that some systems could end up with
     garbage in the registry during a clean install.

Please test these builds.

Thanks.

Jeffrey Altman