File Comparator Residual Thread Left Open?
Posted: 04 Dec 2009, 04:11
File Comparator Residual Thread Left Open? At least for a period of time?
Not sure if this is a Salamander issue or not (& I'm running PB 38).
After a File Compare might some sort of thread be left open, locking (at least part of) one of the files in the comparison?
Ran comparison on a number of larger files (>125 MB < 660 MB).
After doing so, after either comparing completely or hitting the 32K difference limit, I ran the same two files through (a Send To shortcut to) Hasher 1.00. In most instances hash computation of one of the two files would at some point stop. If I hit the Pause key in Hasher, a Hasher error comes up "Thread Error: Access is denied (5)". (Doing the same <without extensive testing> using HashMyFiles completed successfully.)
OpenedFilesView did not show the files in question. Did not check using an Sysinternals utilities.
Not sure if this is a Salamander issue or not (& I'm running PB 38).
After a File Compare might some sort of thread be left open, locking (at least part of) one of the files in the comparison?
Ran comparison on a number of larger files (>125 MB < 660 MB).
After doing so, after either comparing completely or hitting the 32K difference limit, I ran the same two files through (a Send To shortcut to) Hasher 1.00. In most instances hash computation of one of the two files would at some point stop. If I hit the Pause key in Hasher, a Hasher error comes up "Thread Error: Access is denied (5)". (Doing the same <without extensive testing> using HashMyFiles completed successfully.)
OpenedFilesView did not show the files in question. Did not check using an Sysinternals utilities.