From 023693693a451571c87d51b67b9c30a0176ffc89 Mon Sep 17 00:00:00 2001 From: Ted Smith Date: Fri, 1 Jul 2016 17:27:58 +0100 Subject: [PATCH] v2.6.9 Final --- DiskModule/diskmoduleunit1.lfm | 2 +- README.txt | 14 +++ project1.lpi | 179 ++++++++++++++++----------------- unit2.lfm | 4 +- 4 files changed, 103 insertions(+), 96 deletions(-) diff --git a/DiskModule/diskmoduleunit1.lfm b/DiskModule/diskmoduleunit1.lfm index 1855542..b8e6b95 100755 --- a/DiskModule/diskmoduleunit1.lfm +++ b/DiskModule/diskmoduleunit1.lfm @@ -3,7 +3,7 @@ object frmDiskHashingModule: TfrmDiskHashingModule Height = 600 Top = 155 Width = 691 - Caption = 'QuickHash 2.6.8 (2011 - 2015) (c) Ted Smith - Disk Hashing Module' + Caption = 'QuickHash 2.6.9 (2011 - 2015) (c) Ted Smith - Disk Hashing Module' ClientHeight = 600 ClientWidth = 691 Position = poScreenCenter diff --git a/README.txt b/README.txt index 03e1361..65567e0 100755 --- a/README.txt +++ b/README.txt @@ -1,3 +1,17 @@ + +V2.6.9 – July 2016 + +The UNC and long path name fixes still had not entirely worked as hoped when tested on big data sets. Further fixes implemented to ensure the filename and path to an existing file in a very long path is detected, and likewise re-created when copied. + +Improvements made to the way QH reports errors. Errors are generally quite rare except when dealing with very large volumes of network data in a dynamic environment. Prior to v2.6.9, a message window would appear which was not very useful if there were over a few dozen errors because the list was too big for the screen and the automatic saving of that data seemed to go wrong and generate save errors. That was fixed to a simple warning that errors were found and the user is now prompted to save a text file in a place of their choosing. + +If QuickHash fails to initiate a handle to a file at the time of hashing, not only will the user be told that there was an error initiating a handle (as it did before) but it will now tell you which file is causing the problem. + +If the user pastes the path of a mounted drive as a UNC path (e.g. M:\MyServer\MyDataShare\MyFolder) as either source or destination, the user will now be told to fix it to a true UNC path rather than simply crashing out! + +Status bar in the bottom of the Copy tab (the part that shows the user what file is currently being hashed) was being truncated if the path length was particularly long, and was still truncated even if maximised to the full screen size on a 40” monitor! That has been improved. + + V2.6.8 – June 2016 In the 'Copy' tab, users can now select multiple source folders so that multiple folder content can be hashed, copied to a single destination folder, and then hashed again. Note that an experimental limit exists – if the list of files in memory exceeds 2Gb, Quickhash will likely crash. Please report such instances. If they are too many, I will implement another technique. diff --git a/project1.lpi b/project1.lpi index f729988..27a434c 100755 --- a/project1.lpi +++ b/project1.lpi @@ -19,7 +19,7 @@ - + @@ -50,7 +50,7 @@ - + @@ -90,8 +90,8 @@ - - + + @@ -100,67 +100,67 @@ - + - + - + - + - + - + - + - + - + - + - + @@ -169,7 +169,7 @@ - + @@ -249,7 +249,7 @@ - + @@ -261,7 +261,7 @@ - + @@ -312,7 +312,7 @@ - + @@ -323,13 +323,13 @@ - + - - - + + + @@ -411,10 +411,10 @@ - + - + @@ -539,142 +539,136 @@ - - + + - - - + + - - + - + - + - - + + - - + + - - + + - - + + - - + + - - + + - - + + - - + + - - + + - - + + - - + + - - + + - - + + - - + + - - + + - - + + - - + + - - + + - - + + - - + + - - + + - - + + - - + + - - + + - - + + - - + + - - - - - - + + @@ -692,7 +686,6 @@ - diff --git a/unit2.lfm b/unit2.lfm index 5bdd878..6fdd0be 100755 --- a/unit2.lfm +++ b/unit2.lfm @@ -1,7 +1,7 @@ object MainForm: TMainForm - Left = 421 + Left = 306 Height = 689 - Top = 110 + Top = 98 Width = 1018 AllowDropFiles = True Caption = 'Quick Hash v2.6.9 (c) 2011-2016 - The easy and convenient way to hash data in both Linux, Apple Mac and Windows'