Page 1 of 1

Custom Copy Verification questions

Posted: 15 Jul 2011 19:45
by xyusr
I'm curious how verification works. I'm assuming a hash (md5, for example) is generated as a file is copied, then the copied file is read back, hashed, and compared to the original. Is this correct? Isn't the OS just giving back the memory cached copied file and not reread from disk? How about a network share?

Thanks for any help.

Re: Custom Copy Verification questions

Posted: 15 Jul 2011 19:54
by zer0
xyusr wrote:I'm curious how verification works. I'm assuming a hash (md5, for example) is generated as a file is copied, then the copied file is read back, hashed, and compared to the original. Is this correct? Isn't the OS just giving back the memory cached copied file and not reread from disk? How about a network share?

Thanks for any help.
A hash is generated once a file is copied, not while the file is copied. It's in the help file ;)

Re: Custom Copy Verification questions

Posted: 15 Jul 2011 20:16
by admin
Yes, XY ensures that the cache is flushed and the target is really read from disk, not from cache.

Re: Custom Copy Verification questions

Posted: 16 Jul 2011 18:50
by xyusr
admin wrote:Yes, XY ensures that the cache is flushed and the target is really read from disk, not from cache.
How about a network share? Thanks.

Re: Custom Copy Verification questions

Posted: 16 Jul 2011 20:19
by admin
xyusr wrote:
admin wrote:Yes, XY ensures that the cache is flushed and the target is really read from disk, not from cache.
How about a network share? Thanks.
Same. Why should it be different?

Re: Custom Copy Verification questions

Posted: 18 Jul 2011 05:40
by xyusr
My network share is from a server running Debian Linux and Samba. So, there is a way to have a PC client running Xyplorer clear the disk cache on this server so copy verification works correctly?

Re: Custom Copy Verification questions

Posted: 18 Jul 2011 09:18
by admin
xyusr wrote:My network share is from a server running Debian Linux and Samba. So, there is a way to have a PC client running Xyplorer clear the disk cache on this server so copy verification works correctly?
Hm, I don't know. I just tell Windows to clear the disk write buffer, and I assume it does (it's notable, too, because the operation takes much longer compared to no clearing the cache). Not sure whether this extends to the other machine's cache.

Re: Custom Copy Verification questions

Posted: 20 Jul 2011 14:28
by alps
Which is the most reliable and fast,verification ?

Re: Custom Copy Verification questions

Posted: 20 Jul 2011 15:41
by nas8e9
alps wrote:Which is the most reliable and fast,verification ?
From the help file:
Verification: Verify the correctness of each copy operation on the fly (file by file). If a verification fails you are prompted to continue or abort the operation. You additionally get the option to continue without further such messages. You can choose among several verification methods:

· None (no verification).

· Byte-to-byte: Most secure, but slower on huge files.

· MD5: Fastest if the hashing algorithms offered here.

· SHA-1: More secure than MD5 but slightly lower. Faster than Byte-to-byte on huge files.

· SHA-256: Available only from Vista/Win7.

· SHA-512: Available only from Vista/Win7.
Based on the above, I'd say SHA-1 offers the best compromise. For greatest security, byte-to-byte is the way to go.

Re: Custom Copy Verification questions

Posted: 21 Jul 2011 11:55
by alps
I know the above one,but what's the definition of huge here,greater than how much size?
"· SHA-1: More secure than MD5 but slightly lower",it's slower,right !

and what does this mean --MD5: Fastest if the hashing algorithms offered here.

Re: Custom Copy Verification questions

Posted: 21 Jul 2011 13:30
by admin
alps wrote:I know the above one,but what's the definition of huge here,greater than how much size?
"· SHA-1: More secure than MD5 but slightly lower",it's slower,right !

and what does this mean --MD5: Fastest if the hashing algorithms offered here.
There are 2 typos, sorry.
It should have been:
- slightly slower
- Fastest of the

definition of huge: try it, I think it also depends on the system (RAM etc.).