Adam Albright said:
Again the old fanboy trick... make up some goofy fallacy and pretend
the other guy subscribes to it so you can try to prove him wrong.
I never said time remaining indicators are or need to be absolute,
what I DID say is copying/moving files in Windows through Explorer
never has come close and they've always been all over the map
typically going up and down as the job nears completion.
Adam, when you notice this behavior are you running some other program that
may also be accessing the hard drive?
I've noticed that if I simply leave the computer to do the copy(s) the time
remaining estimate will be pretty close to accurate, but if I'm running
something else (like if I'm watching TV using MMC) the estimate will
fluctuate, going up and down every time it refreshes the time remaining.
Even if disk-indexing kicks in, though it is a low priority, this will also
throw the estimate off.
Windows uses the size and current disk throughput to estimate the time to
copy the files, but if the disk throughput changes due to some other disk
activity then the current estimate is invalid and at the next refresh of the
estimate it will change. Going up when the disk is being used by some other
process, and of course, down when the only process is the copy itself.
I noticed one instance when I was recording two shows and watching a
pre-recorded show at the same time, a download of a CD image (it was
Ubuntu), after the download was finished and Explorer was copying the file
to the Download folder from the temp folder started with an estimate of 9
HOURS. It took a much shorter time than that and during the copy the
estimate went down rather quickly, but I'm assuming at the moment it made
the first estimate the disk was being thrashed so thoroughly by MMC with the
playback and recordings going on, Explorer must have seen the available disk
throughput at something insanely low.
Bug or not, I'm stunned that this seems to be such an issue for some people.
Do we not remember the days when what today would be considered a very tiny
file took quite some time to copy, and we had no real indicator of how long
it was going to take other than our previous experience with other files?
Remember copying files using a command-line?
"copy /home/mickey/download/somestuf.txt
/home/mickey/documents/somestuf.txt"
Didn't get a time estimate with that . . .
And when we finally did get one, it was never very accurate, often not even
close.
Mic