TC11 verify error when copy big files

[chris007]

Hi

I am trying to copy a directory with big files ( TC11.0 ) from one drive ( external USB SSD ) to another external USB Drive , ( normal hard drive ) with sizes around 17-20 Gigi Byte per file with verify on , The verification always fail
If I use 10.52 all works as it should

Regards

[chris007]

Forgot to say using Win10 Enterprise 19043.928

[ghisler(Author)]

I cannot reproduce that, verify works just fine also with files >10GB. The verify function was not changed except for the speed display in the progress bar.
Anyone else having this problem?

[white]

The verification always fail

Do you mean the verification fails while the copied files are the same?

[JOUBE]

from one drive ( external USB SSD ) to another external USB Drive

I have - a time ago - same problems. But this was with Version Tc10.52 and has nothing to do with the Tc itself but with the USB-Host-Controller of the Mainboard of that PC, as I found out later. This USB-Host-Controller was not able to handle USB<->USB copy for bigger files. So the verification of the Tc was right: The files are not the same because of the faulty USB-Host-Controller of the Mainboard. *) If I copy with Tc at first form USB to internal HDD/SSD and then in a second step from internal to target USB-Drive (and doing this with no other activities on that USB-Drive while copying) all works well. But all this is Tc independent. So, are you sure, that the problem comes with Tc11 first?

Joube

*) I even threw away a new 2.5" 4TB hard drive, thinking it was defective, which probably wasn't the case.

[ghisler(Author)]

Maybe he used different USB ports than before? On some PCs, there are multiple host controllers to handle the large amount of USB ports.

[chris007]

Hi All

Thank you for all the feedback
When I swap around the usb drives it sometime work , so possibly a usb/win10/xxx unknown hardware/software combination that is causing this

Regards
Chris

[JOUBE]

When I swap around the usb drives it sometime work , so possibly a usb/win10/xxx unknown hardware/software combination that is causing this

I think, this thread can be moved to the forum 'Total Commander (English)' (or to the forum: 'TC Behaviour which will not be changed'). In any case, this is not longer an open issue.

Joube

[ghisler(Author)]

Moderator message

Moved to the English forum

[Gerdd]

My 28 cent worth on this:

Even though I practically never copy files without TC involved any more I think I can confirm that this is a hardware issue rather than a TC issue:

A lot of my copying is video files (mostly MP4) between 0.5 and 10 GB usually. The majority of processes involves USB drives, often both as sources and as targets. I recall one Mobo I used that didn't have any USB3 ports and still only had old PCI slots (which were too slow to fully support USB3 adapters, which is why those adapters usually required PCI Express slots.) So, no PCI Ecpress slots, no USB3?

No, there still is that small village in Brittany that resist all attempts of Caesar ... Nonsense!

But it turned out that that mobo actually had one PCI Express slot - for an extra video card (ordinary SVGA was supported by an onboard interface, which was good enough for me.) The seven port USB3 adapter I fitted to this slot actually worked quite well - or so it seemed. Until I compared files and TC got into the habit of telling me that those two files were DIFFERENT! but not enough memory to show me HOW different they were. So I learned to add an entry to TC's Start menu, which invoked "cmd /K fc.exe /B >>__FileCompare.log" with the parameters "%P%S2 %T%R" and gave me a list of single byte differences between the two files - morethan what the 32 bit TC I was running at the time could give me.

Thus I learned that I had a lot of copies of video files that had a small number of single bit errors, which fortunately in most cases were not visible - at least the data structures of the files were only very rarely affected (and a single pixel colour error for a single frame would normally not be noticeable.)

So, even though TC was almost always involved, it was not to be blamed - and to corroborate that, I have never had problems like that on any other system.