17-Jan-2004, 07:43 PM
I'm using BC to copy large files over ftp, and I keep on getting read timeouts on large files.
For example, I've copied an entire folder of large files (from the ftp site to local drive) and all 3 of the largest failed with "Read timeout" errors. These files are 76Mb, 86Mb, and 170Mb respectively. All other files (ranging from 161 bytes up to 61Mb in size) worked fine.
Is this a known bug, or maybe I'm just unlucky, and it was just coincedence that the 3 largest files all failed? I tried one of them a second time, and it failed again. I was able to successfully transfer the files fine using a different ftp client.
On a related note, an idea for improvement - how about a better progress report which could include current throughput and estimated time. Something like the internet explorer file download window?
Current file: mylargefile.dat
Size: 50,420,925 bytes
Current transfer rate: 35.4kb/s
Estimated time left: 14 min 32 sec
Its just useful to know whether its going to take 2 minutes or 2 hours, I don't expect great accuracy :-)
Thanks,
Paul.
For example, I've copied an entire folder of large files (from the ftp site to local drive) and all 3 of the largest failed with "Read timeout" errors. These files are 76Mb, 86Mb, and 170Mb respectively. All other files (ranging from 161 bytes up to 61Mb in size) worked fine.
Is this a known bug, or maybe I'm just unlucky, and it was just coincedence that the 3 largest files all failed? I tried one of them a second time, and it failed again. I was able to successfully transfer the files fine using a different ftp client.
On a related note, an idea for improvement - how about a better progress report which could include current throughput and estimated time. Something like the internet explorer file download window?
Current file: mylargefile.dat
Size: 50,420,925 bytes
Current transfer rate: 35.4kb/s
Estimated time left: 14 min 32 sec
Its just useful to know whether its going to take 2 minutes or 2 hours, I don't expect great accuracy :-)
Thanks,
Paul.