windows-notes-20050104

updates

diff --git a/doc/txt/winnotes/afs-changes-since-1.2.txt b/doc/txt/winnotes/afs-changes-since-1.2.txt
index 800abd9..d83a51c 100644 (file)
--- a/doc/txt/winnotes/afs-changes-since-1.2.txt
+++ b/doc/txt/winnotes/afs-changes-since-1.2.txt
@@ -1,14 +1,37 @@
 Since 1.3.77:
+  * Correct deadlock condition in cm_EndCallbackGrantingCall which can
+    be triggered if the volume referenced by the cm_scache_t object is
+    offline.
+
+  * The AFS Service needs to respond to SERVICE_ACCEPT_SHUTDOWN messages
+    in addition to SERVICE_ACCEPT_STOP.
+
+  * Move RPC shutdown until after the SMB and RX shutdown procedures 
+    complete.  Block until RPC shutdown is complete.
+
+  * Modify afslogon.dll (integrated logon) to wait for service if its
+    state is START_PENDING.  If the timeout period occurs, reset to 
+    the retry interval and not the sleep interval.
+
+  * When renewing the server list for a cell obtained via DNS AFSDB
+    records, the cm_cell_t entry must be removed from the list of all 
+    cells.  Otherwise, the list of cells will be corrupted.
+ 
+  * In the dcache and scache modules, use the cm_scache_t dataVersion
+    instead of the cm_fakeDirVersion.  
+
+  * Synchronize fs.c with the unix version.
+
   * The variable used to determine whether a file or virtual memory
     mapped cache is used was not properly initialized to a default
     value. If the registry setting "NonPersistentCaching" was not
     set, the choice would be random.   Properly initialized to be
     "file".
 
- * The memory mapped view was never unmapped before closing the file
-   at service shutdown.  This is now properly cleaned up.
+  * The memory mapped view was never unmapped before closing the file
+    at service shutdown.  This is now properly cleaned up.
 
- * Default location of Cache file is now %TEMP%\AFSCache
+  * Default location of Cache file is now %TEMP%\AFSCache
 
 Since 1.3.76:
 
@@ -155,6 +178,7 @@ Since 1.3.72/73:
 
   * Fix AFS Client Configuration Control Panel to support new SysName
     protocol.
+
   * Fix a bug in afsd_service.exe which could result in the SysName
     not being read from the registry.
 

diff --git a/doc/txt/winnotes/afs-install-notes.txt b/doc/txt/winnotes/afs-install-notes.txt
index bcce7bf..6cd6840 100644 (file)
--- a/doc/txt/winnotes/afs-install-notes.txt
+++ b/doc/txt/winnotes/afs-install-notes.txt
@@ -56,6 +56,19 @@ is in use, the NETBIOS name associated with the AFS Client Service is simply
 
 When the MLA is installed, UNC paths of the form \\AFS\cellname\path may be used.
 
+The MLA is installed without binding the "Client for Microsoft Networks" or 
+"File and Printer Sharing for Microsoft Networks".  If you bind these options
+to the MLA there will be a conflict between the name "AFS" and the name of 
+the machine on the published IP Address.  This may result in a failure to be
+able to access files in AFS.  The "NET VIEW" command will return a "System 
+Error 52" message when this conflict exists.  To correct the problem:
+
+ * stop the AFS Client Service
+ * unbind the "Client for Microsoft Networks" and "File and Printer Sharing
+   for Microsoft Networks" from the MLA
+ * Disable and then Enable the MLA
+ * start the AFS Client Service
+
 
 3. Traditionally, when the AFS Client Service starts it must be able to 
 access the "root.afs" volume of the default cell.  The "root.afs" volume
@@ -476,6 +489,7 @@ logoff scripts (assigned by group policy) which rename all files to use
 only the supported characters for the locale.
 
 
+
 ------------------------------------------------------------------------
 
 Reporting Bugs: