Index: openafs/doc/txt/winnotes/afs-changes-since-1.2.txt
diff -c openafs/doc/txt/winnotes/afs-changes-since-1.2.txt:1.13.2.15 openafs/doc/txt/winnotes/afs-changes-since-1.2.txt:1.13.2.19
*** openafs/doc/txt/winnotes/afs-changes-since-1.2.txt:1.13.2.15	Mon Dec 13 09:15:16 2004
--- openafs/doc/txt/winnotes/afs-changes-since-1.2.txt	Sun Jan 30 23:24:05 2005
***************
*** 1,3 ****
--- 1,79 ----
+ 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.
+ 
+   * 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.
+ 
+   * Default location of Cache file is now %TEMP%\AFSCache
+ 
+ Since 1.3.76:
+ 
+   * A bug affecting new installations of 1.3.75/76 would result in
+     the creating of incorrect mountpoints in the freelance root.afs 
+     volume for the default cell.
+ 
+     If "fs \\afs\all\<cellname>" lists a volume name of "root" instead
+     of "root.cell", you have been affected by the bug.  To correct the
+     problem, execute the following commands:
+ 
+           fs rmmount \\afs\all\<cellname>
+           fs rmmount \\afs\all\.<cellname>
+         
+           fs mkmount \\afs\all\<cellname> root.cell <cellname>
+           fs mkmount \\afs\all\.<cellname> root.cell <cellname> -rw
+ 
  Since 1.3.75:
  
    * A bug has been fixed in the auto-generation of Freelance root.afs
***************
*** 127,132 ****
--- 203,209 ----
  
    * 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.
  
Index: openafs/doc/txt/winnotes/afs-install-notes.txt
diff -c openafs/doc/txt/winnotes/afs-install-notes.txt:1.11.2.8 openafs/doc/txt/winnotes/afs-install-notes.txt:1.11.2.11
*** openafs/doc/txt/winnotes/afs-install-notes.txt:1.11.2.8	Tue Dec  7 07:48:57 2004
--- openafs/doc/txt/winnotes/afs-install-notes.txt	Sun Jan 30 23:24:05 2005
***************
*** 1,4 ****
! OpenAFS for Windows 1.3.74 Installation Notes
  ---------------------------------------------
  
  The OpenAFS for Windows product was very poorly maintained throughout the 
--- 1,4 ----
! OpenAFS for Windows 1.3.78 Installation Notes
  ---------------------------------------------
  
  The OpenAFS for Windows product was very poorly maintained throughout the 
***************
*** 56,61 ****
--- 56,76 ----
  
  When the MLA is installed, UNC paths of the form \\AFS\cellname\path may be used.
  
+ 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
+  * 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
+ 
  
  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
***************
*** 155,167 ****
       Kerberos KDC is inaccessible at logon time.
  
  
! 7. The AFS Systray tool (afscreds.exe) supports several new command line 
  options: 
  
      -A = autoinit 
      -M = renew drive maps 
      -N = ip address change detection 
      -Z = unmap drives
  
  autoinit will result in automated attempts to acquire AFS tokens when 
  afscreds.exe is started.  afscreds.exe will attempt to utilize tickets stored
--- 170,190 ----
       Kerberos KDC is inaccessible at logon time.
  
  
! 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
***************
*** 463,469 ****
  filenames using the ANSI Code Page instead of the OEM Code Page.  The ANSI
  Code Page is a compatible superset of Latin-1.  This setting is not the 
  default setting because making this change would prevent OpenAFS for Windows 
! from being able to access filenames containing the above characters.
  
  ------------------------------------------------------------------------
  
--- 486,504 ----
  filenames using the ANSI Code Page instead of the OEM Code Page.  The ANSI
  Code Page is a compatible superset of Latin-1.  This setting is not the 
  default setting because making this change would prevent OpenAFS for Windows 
! from being able to access filenames containing the above characters which
! were created without this setting.
! 
! 
! 30. There is a known issue with storing Windows Roaming Profiles when
! the profile contains either directories or files with names which cannot
! be represented in the local OEM character set.  In this case, attempts
! to write the profile back to AFS will fail.  OpenAFS for Windows does
! not currently support UNICODE.  To avoid this problem some sites run
! logoff scripts (assigned by group policy) which rename all files to use
! only the supported characters for the locale.
! 
! 
  
  ------------------------------------------------------------------------
  
***************
*** 477,482 ****
--- 512,540 ----
  %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:
