STABLE14-winnotes-update-20050126

add dr watson info to install notes.

update changes list


(cherry picked from commit e41837e876f7dc947e8718b6dc972b803023eae5)

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

@@ -1,4 +1,29 @@
 Since 1.3.77:
+  * The list of ACL entries was becoming corrupted because the function
+    which obtained a free entry was doing so without the appropriate lock
+    being held.
+
+  * Changed the default @sys name list to "x86_win32 i386_w2k i386_nt40"
+    for 32-bit x86 systems.  The default for itanium will be "ia64_win64"
+    and "amd64_win64" for amd 64-bit processors.
+
+  * When executing executables, Windows provides a mechanisms by which
+    the normal search for DLLs can be bypassed.  If a file foo.exe is
+    being executed and there exists a file or directory "foo.exe.local" 
+    (the contents are ignored if a file), then Windows will search for
+    DLLs first in the "foo.exe.local" directory and second in the 
+    directory in which the "foo.exe" file is located.  
+
+    Previous releases of OAFW would improperly return 
+    STATUS_NOT_A_DIRECTORY instead of the expected 
+    STATUS_OBJECT_PATH_NOT_FOUND.  This would cause the Windows SMB client
+    to terminate the search for the DLL causing the execution of the 
+    application to fail.                                                                           
+
+  * Re-work the reference counting of smb_vc_t objects.  The references
+    stored in the waiting locks were not counted.  This could result in
+    an assertion if the reference count drops below 0.
+
   * Correct deadlock condition in cm_EndCallbackGrantingCall which can
     be triggered if the volume referenced by the cm_scache_t object is
     offline.

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

@@ -1,4 +1,4 @@
-OpenAFS for Windows 1.3.74 Installation Notes
+OpenAFS for Windows 1.3.78 Installation Notes
 ---------------------------------------------
 
 The OpenAFS for Windows product was very poorly maintained throughout the 
@@ -56,16 +56,18 @@ 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:
+The MLA is installed with a binding to "Client for Microsoft Networks" but not 
+to "File and Printer Sharing for Microsoft Networks".  If you fail to bind 
+"Client Microsoft Networks" you will not be able to access the AFS Client 
+Service when the machine is disconnect from the network.  If you bind "File 
+and Printer Sharing ..." there will be a conflict between the name "AFS" and 
+the name of the machine on the published IP Address.  This will 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
+ * bind the "Client for Microsoft Networks" to the MLA
+ * unbind "File and Printer Sharing for Microsoft Networks" from the MLA
  * Disable and then Enable the MLA
  * start the AFS Client Service
 
@@ -168,13 +170,21 @@ What Integrated Logon does not do:
      Kerberos KDC is inaccessible at logon time.
 
 
-7. The AFS Systray tool (afscreds.exe) supports several new command line 
+7. The AFS Systray tool (afscreds.exe) supports several command line 
 options: 
 
     -A = autoinit 
+    -E = force existing afscreds to exit
+    -I = install startup shortcut
     -M = renew drive maps 
     -N = ip address change detection 
+    -Q = quiet mode.  do not display start service dialog
+             if afsd_service is not already running
+    -S = show tokens dialog on startup
+    -U = uninstall startup shortcut
+    -X = test and do map share
     -Z = unmap drives
+    -: = magic parameter for high security mode 
 
 autoinit will result in automated attempts to acquire AFS tokens when 
 afscreds.exe is started.  afscreds.exe will attempt to utilize tickets stored
@@ -502,6 +512,29 @@ file  %WINDIR%\TEMP\afsd.log.  The AFS Client startup log is
 %WINDIR%\TEMP\afsd_init.log.  Send the last continuous block of log 
 information from this file.
 
+Configuring DrWatson to generate dump files for crashes:
+
+ * Run drwtsn32.exe to configure or to identify where the log and the crash dump 
+   files are created: 
+   - click Start > Run...  
+   - type drwtsn32 <enter>. 
+   - Select either a Crash Dump Type: Mini or Full. 
+   - Clear Dump Symbol Table
+   - Clear Append to Existing Log file. 
+   - Check Dump All Thread Contexts.
+   - Check Create Crash Dump File
+ * Next run the monitoring module of Dr. Watson: 
+   - click Start > Run...
+   - type drwatson <enter>. 
+   - Once a crash happens, Dr. Watson generates a dump file and a report in the 
+     log file, including the address of the crash and the stack dump.
+
+Once you have the Dr. Watson's logfile and minidump, zip them and send them as
+attachments with your e-mail to openafs-bugs@openafs.org.
+
+When reporting a error, please be sure to include the version of OpenAFS.
+
+
 ------------------------------------------------------------------------
 
 How to Contribute to the Development of OpenAFS for Windows: