windows-doc-updates-20050728

updates for 1.3.8600

doc/txt/winnotes/afs-changes-since-1.2.txt

@@ -1,9 +1,22 @@
 Since 1.3.85:
+ * Optimize calls to cm_CheckServer from cm_Analyze.  Only check
+   down servers for the current cell not all cells.
+
+ * If the scache LRU list becomes corrupted, the AFS Client Service
+   might enter an infinite loop at startup.   Detect the corruption
+   and discard the cache contents in this case.
+
+ * Fixed the Explorer Shell's remove mountpoint functionality.
+
  * Fixed a deadlock caused by the holder of cm_aclLock attempting to 
    obtain a mutex lock on a cm_scache_t object whose lock is held by
    a thread attempting to obtain the cm_aclLock.
 
 Since 1.3.84:
+ * Really fixed DNS AFSDB queries to ensure that "csail" cannot be
+   misinterpretted as "csail.mit.edu" when the resolver 
+   is configured to append ".mit.edu" to failed DNS queries.
+
  * Added a new registry key, "LogoffPreserveTokens" (see registry.txt),
    that can be used to force the preservation of user tokens upon logout.
 

doc/txt/winnotes/afs-install-notes.txt

@@ -1,19 +1,30 @@
-OpenAFS for Windows 1.3.8500 Installation Notes
+OpenAFS for Windows 1.3.8600 Installation Notes
 -----------------------------------------------
 
-The OpenAFS for Windows product was very poorly maintained throughout the 
-1.2.x release cycle.  While the Unix version was being enhanced and its 
-quality was improving the Windows version stagnated.  The IBM AFS 3.6 product 
-was not designed for the Windows 2000/XP/2003 operating system nor was it 
-architected with highly disconnected environments in mind.
+OpenAFS for Windows 1.3.8600 is the best client available for 
+Microsoft Windows operating systems.  It can be installed either as
+a new installation or an upgrade from previous versions of OpenAFS
+for Windows or IBM AFS for Windows.  Installers are provided in two
+forms:
 
-The 1.3.x series of releases not only fixes a large number of bugs in the 1.2 
-series but also attempts to enhance the functionality of the product to better 
-fit the usage model of today's users.  Several items standout.  
+  * an executable (.exe) that is based upon the Nullsoft Scriptable
+    Installation System, or
 
-0. The default AFSCache file is approximately 100MB.  This space is required 
-in addition to the space allocated to OpenAFS binaries.
+  * a Windows Installer package (.msi) that is built using WiX and
+    can be customized for organizations via the use of MSI Transforms
+    (see msi-deployment-guide.txt)
 
+System Requirements:
+
+Operating System: Windows 2000, 2000 Server, XP Home, XP Pro, 2003 Server
+64-bit versions of Windows are not supported in this release.
+
+Disk Space: up to 60mb required for the OpenAFS binaries plus 100MB 
+for the default AFSCache file.   (The size of the AFSCache file may
+be adjusted via the Registry after installation.)
+
+Additional Softare:  MIT Kerberos for Windows 2.6.x if Kerberos 5 
+authentication support is desired.
 
 1. The Kerberos 4 infrastructure on which the 1.2 series is reliant is no 
 longer secure.  Cross-realm Kerberos is very important in the AFS context and 

doc/txt/winnotes/afs-issues.txt

@@ -1,4 +1,4 @@
-This file is a rough list of known issues with the 1.3.84 release of OpenAFS
+This file is a rough list of known issues with the 1.3.85 release of OpenAFS
 on Windows.  This list is not complete.  There are probably other issues 
 which can be found in the RT database or on the mailing list.
 
@@ -105,7 +105,7 @@ in smb_Listener() thread.
      or by the new AFS Client Service Administration tool when executed 
      by an authorized user.
 
-(27) No support for byte range locking.
+(27) No support for byte range locking (or locking at all)  
 
 -------------------------------------------------------------------------
 List of unfunded projects: