Verifying files while they copy
Moderators: Hacker, petermad, Stefan2, white
Verifying files while they copy
Is it possible to have Total Commander verify files that you copy, WHILE they are bing copied, to ensure that everything was copied 100% error-free? Alternatively, is there an option to do this automatically right after the files finished copying?
It is a bit of a hassle to have to go into the synchronize dirs tool and then do so manually...
Another thing that I was wondering about:
Running Total Commander from a CD makes changes to the settings impossible because new settings must first be saved to the config file before OK is accepted - could you perhaps check for read-only media and then still allow changing the settings, but only keep them in memory? This particularly applies when used with a BartPE CD...
How about a linux version of TC in the near future?
Is there a way to SAVE a file list to a text file instead of just being able to print it to a printer?
It is a bit of a hassle to have to go into the synchronize dirs tool and then do so manually...
Another thing that I was wondering about:
Running Total Commander from a CD makes changes to the settings impossible because new settings must first be saved to the config file before OK is accepted - could you perhaps check for read-only media and then still allow changing the settings, but only keep them in memory? This particularly applies when used with a BartPE CD...
How about a linux version of TC in the near future?
Is there a way to SAVE a file list to a text file instead of just being able to print it to a printer?
Re: Verifying files while they copy
You may create a CRC-Checksum of those files (if they are in subdirectories just use Branchview [Ctrl]+) and test the checksum after the copy. Otherwise, to ensure the copy was 100% correct there is no other way than a bit by bit compare - which is done by the Synchronise Dir Tool. But then you may use it for the copy as well:nblom wrote:Is it possible to have Total Commander verify files that you copy, WHILE they are bing copied, to ensure that everything was copied 100% error-free? Alternatively, is there an option to do this automatically right after the files finished copying?
Compare both directories, synchronize and wait until it's compared again.
Another thing that I was wondering about:
Running Total Commander from a CD makes changes to the settings impossible because new settings must first be saved to the config file before OK is accepted - could you perhaps check for read-only media and then still allow changing the settings, but only keep them in memory? This particularly applies when used with a BartPE CD...
You can start TC with Command Line Parameter and set this way the ini-file to a writable directory e.g. %temp%.
How about a linux version of TC in the near future?
No chance. For details please use the Forums search.
Is there a way to SAVE a file list to a text file instead of just being able to print it to a printer?
Just install a new printer and select manually the port to 'redirect to file' (Instead LPT1 or anything) and choose as type "Standard->Generic/Text only".
sheepdog
"A common mistake that people make when trying to design something
completely foolproof is to underestimate the ingenuity of complete fools."
Douglas Adams
completely foolproof is to underestimate the ingenuity of complete fools."
Douglas Adams
Vielen Dank, Sheepdog.
I'm not totally sure how to use that CRC-Checksum method, so I will stick with the Synchronize dirs for now.
Thanks again.
It would be nice though, if there was a way to save a filelist directly to text file instead of that "workaround", which I have been using as a matter of fact
N.
I'm not totally sure how to use that CRC-Checksum method, so I will stick with the Synchronize dirs for now.
Thanks again.
It would be nice though, if there was a way to save a filelist directly to text file instead of that "workaround", which I have been using as a matter of fact

N.
Last edited by nblom on 2006-12-11, 06:26 UTC, edited 1 time in total.
To use those CRC-Checksum is rather simple.
CRC does a certain calculation with every single byte of a file wich results in a checksum that is nearly unique. So if there is one singly byte different you get a complete different checksum.
So if you want to create a checksumfile for the files to copy you simply have to
1a. if you want to copy subdirs activate first the branchview (with Ctrl+b)
1b. mark the files you want to copy
2. Select from Mainmenu "Files->Create Checksums (SFV-Format)...
Now a file with checksums of all selected files is created.
3a. Deactivate the branch view if necessary (Ctrl+b again)
3b. copy the files
3c. copy the checksum-file
4. switch to the target dir
5. doubleclick at the checksum-file
Now TC automatically verifies all checksums and reports any error.
This is faster than the byte by byte compare but it is not as secure (because it is possible to alter a file while keeping the CRC-Checksum- although this would not happen by coincidence). The advantage of the Checksum-method is that you can perform this check at any time to make sure the files are not corrupted. And for normal copy processes it should be secure enough.
sheepdog
CRC does a certain calculation with every single byte of a file wich results in a checksum that is nearly unique. So if there is one singly byte different you get a complete different checksum.
So if you want to create a checksumfile for the files to copy you simply have to
1a. if you want to copy subdirs activate first the branchview (with Ctrl+b)
1b. mark the files you want to copy
2. Select from Mainmenu "Files->Create Checksums (SFV-Format)...
Now a file with checksums of all selected files is created.
3a. Deactivate the branch view if necessary (Ctrl+b again)
3b. copy the files
3c. copy the checksum-file
4. switch to the target dir
5. doubleclick at the checksum-file
Now TC automatically verifies all checksums and reports any error.
This is faster than the byte by byte compare but it is not as secure (because it is possible to alter a file while keeping the CRC-Checksum- although this would not happen by coincidence). The advantage of the Checksum-method is that you can perform this check at any time to make sure the files are not corrupted. And for normal copy processes it should be secure enough.
sheepdog
"A common mistake that people make when trying to design something
completely foolproof is to underestimate the ingenuity of complete fools."
Douglas Adams
completely foolproof is to underestimate the ingenuity of complete fools."
Douglas Adams
Hi nblom,nblom wrote:Thanks for the help
How do I configure Tc to use Killcopy instead of its normal built-in routine?
you can edit (or create) an 'userCMD.ini' in your TC folder.
Add there an section like
Code: Select all
[em_CopyWithKillcopy]
cmd=%Commander_Path%\MyTools\KillCopy\KILLCOPY.EXE
Param=/%L/%T/ -vt
* go to "Configuration | Options... | Misc" > Redefine hotkeys
* choose 'F5'
* press on 'magnifying glass'
* select your em_xyz command
Or in german|> http://www.ghisler.ch/board/viewtopic.php?p=107679#107679
HTH?
rid
2nblom
RID500 solution is ok if you're using Tc7ß, but if you're using a previous version of Tc you must look in your wincmd.ini for [user] section (if you can't find it you must create it ) and add these 3 lines inside it :
Obviously you must change "menu6 cmd6 param6" to adequate number, if you don't have any previous [user] entries then it should be "menu1 cmd1 param1".[user]
menu6=KILLCOPY
cmd6=C:\WINDOWS\SYSTEM32\KILLCOPY.EXE
param6=/%L/%T/ -vt
Then
* go to "Configuration | Options... | Misc" > Redefine hotkeys
* choose "SHIFT+F5" or any other keys combination.
* press on "command".
* select "cm_UserMenu6".
Bye.