diff --git a/doc/xml/ReleaseNotesWindows/relnotes.xml b/doc/xml/ReleaseNotesWindows/relnotes.xml
index ab5f1c3934..9b4211c79f 100644
--- a/doc/xml/ReleaseNotesWindows/relnotes.xml
+++ b/doc/xml/ReleaseNotesWindows/relnotes.xml
@@ -840,8 +840,9 @@
http://www.jpsoft.com.
Microsoft PowerShell 1.0, 2.0 and 3.0 also support UNC paths as the current directory.
- The Cygwin environment also supports UNC paths as the current directory. Enter AFS
- paths with two leading forward slashes: //afs/grand.central.org/software/openafs/.
+ The Cygwin environment also supports UNC paths as the current directory. Enter AFS paths
+ with two leading forward slashes: //afs/grand.central.org/software/openafs/. As of Cygwin
+ 1.7.18-1, AFS Symbolic Links are supported natively by the Cygwin environment.
3.10. aklog.exe
@@ -1835,40 +1836,50 @@ network paths are inaccessible when Protected Mode is on.
The Windows Volume Shadow Copy Service is not implemented. As a result, AFS backup volumes are not accessible via the Explorer Shell.
-
- There is no support for storing DOS attributes such as Hidden, System, or Archive.
-
+ There is no support for storing DOS attributes such as Hidden, System, or Archive.
-
- There is no support for Alternate Data Streams as required by Windows User Account Control to store Zone Identity data.
-
+ There is no support for Alternate Data Streams as required by Windows User Account
+ Control to store Zone Identity data.
-
- There is no support for Extended Attributes.
-
+ There is no support for Extended Attributes.
-
- There is no support for Access Based Enumeration.
-
+ There is no support for Access Based Enumeration.
-
- There is no support for Windows Management Instrumentation
-
+ There is no support for Windows Management Instrumentation
+
-
- There is no support for Distributed Link Tracking and Object Identifiers
-
+ There is no support for Distributed
+ Link Tracking and Object Identifiers
+
-
- There is no support for storing Windows Access Control Lists. Only the AFS ACLs are enforced.
-
-
+ There is no support for storing Windows Access Control
+ Lists. Only the AFS ACLs are enforced.
+
+
+ There is a bug in the Explorer Shell which can result in the Shell responding to a
+ Ctrl-V (Paste) operation with an out of space error. The bug is that the Shell
+ queries the root directory of the UNC Path or Drive Letter for free space instead of
+ the path in which the Paste is being performed. To work around the bug, select a
+ directory in another volume under the same root and then return to the target
+ directory before initiating the Paste. Performing the Paste using the Context Menu
+ instead of Ctrl-V will avoid triggering the bug.
+
+
+ Windows file systems support a maximum of 31 reparse points (mount points or
+ symbolic links) within a path.
+
@@ -4332,8 +4343,8 @@ Default: 0
Regkey: [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters]
Type: DWORD {0, 1}
-
- Default: 0 on Windows 8 and Server 2012, 1 otherwise
+ Default: 0 on Windows 7, Windows 8, Server 2008 R2 and Server 2012, 1
+ otherwise
Determines whether or not the AFS Cache Manager will generate 8.3 compatible shortnames for all objects stored in AFS. Short names are disabled by default on Windows 8 and Server 2012. All prior operating systems enable short names by default.
0: do not generate 8.3 compatible short names.
1: generate 8.3 compatible short names.
@@ -4382,6 +4393,36 @@ Default: 0
0: prevent setting the FILE_READ_ONLY_VOLUME flag. (default on Win7 and below).
1: permit setting the FILE_READ_ONLY_VOLUME flag. (default on Win8 and above)
+
+ Value: ReparsePointPolicy
+
+ ReparsePointPolicy
+
+ Regkey: [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters]
+ Type: DWORD {0, 1}
+
+
+ Default: 0
+ Windows file systems use reparse points to represent special file system objects such as NTFS
+ Junctions, Symbolic Links and AFS Mount Points. Windows applications must be designed
+ to work with Symbolic Links because several standard file system functions behave differently when the provided
+ path specifies a reparse point. Although there is not a significant impact for Symbolic
+ Links to Directories and Mount Points to volume root directories, Symbolic Links to
+ Files can result in applications misinterpreting the file size and attributes.
+ The ReparsePointPolicy value permits alternate behaviors for reparse point objects
+ on a global basis. In this version, there is only one policy option which permits
+ Symbolic Links to Files to be represented with the target file's size and attributes in
+ the output of FindFirstFile, GetFileAttributes, and GetFileAttributesEx
+ operations.
+ 0: All Reparse Points are treated as reparse points.
+ 1: Reparse Points to Files treated as the target File.
+