PeerLock, Version 3.0.0
To upgrade, double-click on the installation file (plk30.exe) in the Explorer window, or choose "Run" from the Start Menu and then select the application.
If you are upgrading the current version of PeerLock (2.0.3 to 3.0.0) simply install the application over your existing PeerLock and the previous version will be backed up in a sub-folder called 'BACKUP' (if the option to keep a backup is selected during the installation).
If you are evaluating a new version of PeerLock 3.0 and you already have an existing copy of PeerLock 2.0 or older, please select a new directory during the installation.
Note: For more information on the latest features and how to implement specific scenarios please go to: http://www.peersoftware.com/support/peerutilities.aspx
|
New Features
|
ID
|
DESCRIPTION
|
345
|
NEW! Added full Unicode support to allow the locking of files that contain Unicode characters in their name or path (for example files using Chinese character sets).
|
728
|
NEW! Added a new Include/Exclude Users option to allow the exclusion of files opened/locked by specific users. For example, you may choose to exclude files that are opened by the Administrator since activity generated under this account is typically non user related and does not need to be reacted on. Doing so will increase performance in PeerLock by filtering out unnecessary activity. For optimal performance we recommend you exclude the user account under which PeerLock and/or PeerSync are running.
.png)
|
732
|
NEW! Added a new Performance slider to adjust the PeerLock application priority. To achieve faster PeerLock response rate move the slider to the right. To achieve lower CPU usage move the slider to the left.
Each slider position represents the following values:
|
Sleep Frequency
|
Sleep Value
|
Slider Position 1
|
10
|
100
|
Slider Position 2
|
25
|
50
|
Slider Position 3
|
50
|
25
|
Slider Position 4
|
100
|
10
|
|
732
|
NEW! Added Event Thread Settings to specify the number of threads used to detect and lock opened files. This feature improves the detection and locking of opened files and overall responsiveness of PeerLock. Increase this value if you want PeerLock to have more threads available for locking files. The Timeout setting is used to determine for how long to leave inactive threads running for.
|
1090
|
The PeerLock service will now be able to start and run even when there are no valid connections at initialization. Failed Jobs will be added to the retry cycle and will be retried until the connection is re-established.
|
|
|
Performance
|
ID
|
DESCRIPTION
|
607
|
NEW! Improved performance by optimizing the detection logic for opened files that need to be excluded.
|
866
|
Resolved an issue where error handling and error reporting/messaging caused performance to be greatly degraded. Previously errors seemed to hold up the locking/release threads causing other file events to be delayed.
|
|
|
New Defaults
|
ID
|
DESCRIPTION
|
617
|
By default PeerLock will run using Server Mode Detection and will no longer require the PSLockMon.Sys driver. Local Mode Detection is no longer supported and cannot be selected.
|
|
|
Reporting
|
ID
|
DESCRIPTION
|
672
|
NEW! Added Cache Management reporting. If the option to Clear Cache at Start is enabled or the Clear Cache button is hit, a log entry will be made for each PSLock or Stub file that is deleted. The following entries may now be logged:
Deleted PSLock File (At Start) ...
Deleted Source PSLock File (At Start) ...
Delete Stub File (At Start) ...
|
|
|
User Interface
|
ID
|
DESCRIPTION
|
1040
|
Resolved an issue where clearing the Released Files list did not reset the Released Files list counter.
|
|
|
Miscellaneous
|
ID
|
DESCRIPTION
|
1084
|
Resolved an issue where event oscillation may occur. PeerLock on the Target could potentially be triggered when files are being released by PeerLock on the Source.
|
1085
|
Fixed an issue with long file paths. PeerLock would continuously lock and release a file if the parent folder path was under the windows 255 character limit (but exceed this limit on the target). The file would be ignored if the parent folder was past this threshold.
|
|
|
Related Links:
The manufacturer of PeerSync makes no warranties, implied or otherwise, for use of this product. User assumes all responsibility for any data loss or damage.
Copyright © 2003-2009 Peer Software, Inc. All Rights Reserved. Privacy Policy
PeerSync is a registered trademarks of Peer Software, Inc.
Embedded Open File Manager is a registered trademark of EVault.
Reproduction in whole or in part without permission is strictly prohibited.
Last Updated on Wednesday, June 17, 2009