The byte range locking support in these installers utilizes AFS' advisory
locks to simulate Microsoft Windows mandatory locks.   When an application
opens a file, a lock will be placed in AFS indicating that the file is in
use.  If the lock is a write lock, the use of the file will be restricted 
to other applications running on the same machine as the first application
to apply the lock.   Applications running on other machines will see the 
full lock and will be unable to access the file.

Most Windows applications and Windows itself opens files in shared read mode.
When this is done, a read lock is applied to the file.   This does not prevent
shared read access across multiple machines but is used to ensure that no one
writes to the file while it is in use.

As locks are checked and applied during the file open operation, it is 
crucial that users have the locking 'k' privilege in all directories in 
which the user might read a file or execute an application unless the directory
exists on a read only volume.  A failure to assign the 'k' privilege will result 
in "Access Denied" errors during file open.

Please send feedback on the byte range locking support to 

	openafs-win32-devel@openafs.org

Thank you.

Jeffrey Altman