Time remaining counter

Posted By: Greater Monster | Feb 5th, 2005 @ 2:55 AM
page 1 of 1
Comments: 5 | Views: 9513
#Feb 5th, 2005 @ 2:55 AM
Greater Monster
Greater Monster
Deconstruct! (Jacques Derrida 1930-2004)
Can anyone tell me how the 'time remaining' counter while copying files in Windows works?
That counter goes up and down, especially when the filesize differs greatly. That I can understand, each file has overhead and a lot of small files up the copy time.
What I'd like to know is what the counter is exactly based on: the last copied files, data transferred in the last, say, 10 seconds, or maybe the last 10 files.
#Feb 5th, 2005 @ 4:34 AM
Rossj
Rossj
Greater Monster wrote:
Can anyone tell me how the 'time remaining' counter while copying files in Windows works?
That counter goes up and down, especially when the filesize differs greatly. That I can understand, each file has overhead and a lot of small files up the copy time.
What I'd like to know is what the counter is exactly based on: the last copied files, data transferred in the last, say, 10 seconds, or maybe the last 10 files.


Raymond Chen has some info on why it gives such bad estimates.  Unfortunately not sure it really answers you question Sad
#Feb 5th, 2005 @ 5:03 AM
Greater Monster
Greater Monster
Deconstruct! (Jacques Derrida 1930-2004)

I can understand why it is impossible to give a exact time. Besides file sizes ect (which can be seen in advance) you also have a load of other factors the change during copying. If you copy and during the copy you start a program, there goes your estimate. Strictly speaking a change in outside temperature can influence the computers speed and thus the copy-speed.

But somewhere someone decided that, although it would be an estimate, some calculation will be made.
And what that calculation is, that is what I'd love to know.

I think it is based on the copy-speed of the last completed file, based on the behavior of the estimate. But I am only halfway sure.

#Feb 8th, 2005 @ 8:37 PM
NeoTOM
NeoTOM
OMG WTF REDESIGN
Judging by how often it updates, it's either by the last  second's speed or by how long it took the last 100k (or so) to copy. I'm guessing the former. I'd like someone "in the know" to clear this up, though, as my curiousity has now been spiked.
#Feb 9th, 2005 @ 2:42 AM
Greater Monster
Greater Monster
Deconstruct! (Jacques Derrida 1930-2004)
I think your theory is better because the time can change during the copying of a file (as opposed the right or shortly after it). You see that even better when copying a single large file of the internet (assuming that uses that same calculation).

A website filled with Microsoft developers, please answer, please Wink
#Apr 1st, 2005 @ 10:45 AM
Greater Monster
Greater Monster
Deconstruct! (Jacques Derrida 1930-2004)
Yesterday I was at the Microsoft Technet/MSDN sessions in Rotterdam (The Netherlands) talking on this subject with two Dutch Microsoft developers and although they offered a few possibilities, they didn't have the answer anymore than non-Microsoft developers.
Well, I give up (no, I don't, knowing myself). What caculation is used? Moving average? Data left to copy divided by the speed at that moment?
Will I ever find the programmer that developed that routine. Stay tuned Wink
page 1 of 1
Comments: 5 | Views: 9513
Microsoft Communities