Hello everyone. I’m a new DOpus owner. I have created an MD5 button like this.
GetSizes NODESELECT MD5
Clipboard COPYNAMES=hash2
Now I want that it also create a file named check.md5 in the current directory and place the info in the file. Please put me in the right direction. How can I do this?
I do have QuickSFV but its 64 bit version is slower than the DOpus built-in MD5 generator. Surprisingly I have found out that the QuickSFV 32bit is faster than its 64bit version but of course it doesn’t integrate into the context menu.
(See the FAQ on how to use button examples if you don't know what to do with the XML. You don't have to edit any XML; you can just copy it to the clipboard, then right-click on the toolbar and select Paste.)
Yeah, something weird going on with the DOS echo command there, I think. I found a way to fix that but then realised it still won't work with more than one file so it's a bit useless really. (That's because the clipboard data has multiple lines and there's no easy way to write them to a file.)
I'd recommending finding an MD5 util that has a command-line interface. From a quick search this one looks good and has a free command-line version:
If you just run fsum.exe /T:E then it'll create a .MD5 file with the hash (in the same format as Opus's "hash2" for each file, one .MD5 per file.
If you run it with fsum.exe /T:R then it'll creat one .MD5 file for the whole directory.
It's also got options for recursive scanning and for verifying the checksum files.
[quote]I have also one other question. If I use this:
GetSizes NODESELECT MD5
Clipboard COPYNAMES=hash2
in a button, does it calculate the MD5 for the selected file twice?[/quote]
Looks like it's only calculated once. I just checked using Process Monitor and the files only get read one time. Also, the Clipboard command finishes instantly if you run it when the hashes are already shown in the lister.
The Clipboard COPYNAMES=hash2 command will cause the hashes to be generated if they haven't already so putting both commands on the button is somewhat redundant.
Well I want to copy to clipboard the hash and also need to know visually if the hash is ready so that I can paste it, hence the 2 commands. I don't think its redundant. Please correct me if I'm wrong.
If you just use the second command, how do you know it's ready?
With two or more files you get a progress dialog. With only one there's no indication except CPU usage, which could be improved. I've filed a feature request.