Bug in Total Commander ?!
Moderators: Hacker, petermad, Stefan2, white
Bug in Total Commander ?!
When I try to use Total commander to copy mp3 files to Creative MuVo2 FM mp3 player which features a 5GB Seagate ST1 microdrive, the speed is slower than 400KB/S. But when I copy the same files using windows explorer, it costs less than 25 seconds for 80MB files.
I tried windows commder v4.03 v4.54 v5.11, the results are same. Is it a bug of Total Commander?
I tried windows commder v4.03 v4.54 v5.11, the results are same. Is it a bug of Total Commander?
Settings
2Maxis
Hello !
Welcome on board !
- You could try to change the copying-mode :
Menu Configuration >>> Options >> Tick the radio-button : “Also use big files copy-mode”.
- If that doesn't the trick, try then the last option below :
“Use copy+paste via Explorer…”
Kind regards,
Claude
Clo

Welcome on board !
- You could try to change the copying-mode :
Menu Configuration >>> Options >> Tick the radio-button : “Also use big files copy-mode”.
- If that doesn't the trick, try then the last option below :
“Use copy+paste via Explorer…”

Claude
Clo
#31505 Traducteur Français de T•C French translator Aide en Français Tutoriels Français English Tutorials
- pdavit
- Power Member
- Posts: 1529
- Joined: 2003-02-05, 21:41 UTC
- Location: Kavala -> Greece -> Europe -> Earth -> Solar System -> Milky Way -> Space
- Contact:
Re: Bug in Total Commander ?!
OT: By the way, where did you find those old versions?Maxis wrote:I tried windows commder v4.03 v4.54 v5.11, the results are same. Is it a bug of Total Commander?
"My only reason for still using M$ Window$ as an OS is the existence of Total Commander!"
Christian Ghisler Rules!!!
Christian Ghisler Rules!!!
2Pdavit:
I have these releases (but i don't remember exactly where i got it)
WINDOWS COMMANDER V1.12
WINDOWS COMMANDER V1.13
WINDOWS COMMANDER V1.30
WINDOWS COMMANDER V1.50
WINDOWS COMMANDER V2.00
WINDOWS COMMANDER V2.01
WINDOWS COMMANDER V2.11
WINDOWS COMMANDER V3.03
WINDOWS COMMANDER V3.53
WINDOWS COMMANDER V4.03
WINDOWS COMMANDER V4.54
WINDOWS COMMANDER V5.11
If you're interested i can send it to you.
- franck8244
- Power Member
- Posts: 704
- Joined: 2003-03-06, 17:37 UTC
- Location: Geneva...
- pdavit
- Power Member
- Posts: 1529
- Joined: 2003-02-05, 21:41 UTC
- Location: Kavala -> Greece -> Europe -> Earth -> Solar System -> Milky Way -> Space
- Contact:
I would really appreciate that! Thank you!sas2000 wrote:If you're interested i can send it to you.
pdavit @ hotmail . com
Just remember the size limitations of hotmail. You will probably need to create three zips.
Please, exclude v4.54 and v5.11 I already have them. Thanks again!
"My only reason for still using M$ Window$ as an OS is the existence of Total Commander!"
Christian Ghisler Rules!!!
Christian Ghisler Rules!!!
TC uses proprietary copy/move routines. This is sometimes very useful since you can adjust e.g. the blocksize for those operations or define wich partitions are on different Harddsiks to optimize copying. In addition you prevent using the caching mechnism of Windows wich is often not optimal.Maxis wrote:BUt I am curious about the reason.
But in some cases these copy routines do not work as expected. So you can define that TC uses Explorer -method to copy files. E.g using USB-stick needs the Explorer method to get full speed.
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
For me, big files mode seemed to be much slower.
Hi there,
I had a defective CD and tried to save the file, so tried the different copy modes on the single 700MB .mpg the CD contained.
"reliable, but slow" produced ~1-3M/s and went fine up to 98%.
"also use big files" produced ~400-700k/s and failed after 90%.
Is there an explanation? e.g. "DON'T USE IT FOR OPTICAL DRIVES" or such?
I had a defective CD and tried to save the file, so tried the different copy modes on the single 700MB .mpg the CD contained.
"reliable, but slow" produced ~1-3M/s and went fine up to 98%.
"also use big files" produced ~400-700k/s and failed after 90%.
Is there an explanation? e.g. "DON'T USE IT FOR OPTICAL DRIVES" or such?
Re: For me, big files mode seemed to be much slower.
On CD there are always Blocks from 2048 byte.Surranó wrote:"reliable, but slow" produced ~1-3M/s and went fine up to 98%.
"also use big files" produced ~400-700k/s and failed after 90%.
Is there an explanation? e.g. "DON'T USE IT FOR OPTICAL DRIVES" or such?
If the buffersize is 1024k you will need 512 Sectors to fill the buffer.
If the buffersize is 10240k you'll need 5120 Sectors to fill the buffer.
I think that the probability of read errors is increasing with a bigger buffer (while you have no read error to expect on HDs). Tus it will take longer to fill this buffer. Additional you get a temparture problem: reading continous a time will warm up the CD - that makes it harder to read it.
And I guess that if there occurs a read error the whole buffer is dismissed. Thus you will loose 5119 Sectors (in the worst case) instead of 511. That would explain the difference - I think.
After all I would advise against the 'big file copy mode' for CDs.
And for retrieving data from known damaged CDs I would search for special tools instead of using TC.
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
Re: For me, big files mode seemed to be much slower.
Thanks for the explanation, I'm enlightenedSheepdog wrote: After all I would advise against the 'big file copy mode' for CDs.


Actually, we tried quite a few things, including dd. I just tried if my drives fared better than the four drives we tried on my workplace. No big deal.[/quote]And for retrieving data from known damaged CDs I would search for special tools instead of using TC.
Re: For me, big files mode seemed to be much slower.
[/quote]Surranó wrote:Actually, we tried quite a few things, including dd. I just tried if my drives fared better than the four drives we tried on my workplace. No big deal.
What about BlindRead/BlindWrite? It'sgot a quite good read engine. I know there were some other, I will search in my HD.
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