<https://forum.eset.com/topic/1194-progress-bars/#comment-6770>
<http://schema.org/text>
"Hello, \n\nUnfortunately, as my colleague Marcos pointed out, it's kind of a chicken-and-egg situation: The only way to determine how long it would take to scan all the objects on the disk would be to recursively enumerate them, determine which files are archived, compressed, protected with a runtime packer, etc., apply some general estimates about resources required to scan these, and then generate a progress report based on that. Sadly, this operation would greatly increase the amount of time required to perform the scan, since there is a significant amount of overhead involved in preprocessing all that information. And, of course, it would still only be a \"guess.\" A more accurate one, perhaps, but still a guess. \n\nProbably the real solution here is to come up with a better way of displaying the information which doesn't rely on progress bars. They are good when the output being measured is consistent and, well, largely static across systems, but scanning objects for malware is a dynamic activity and does not map very well to a two dimensional line. \n\nRegards, \n\nAryeh Goretsky \n"
<https://forum.eset.com/topic/1194-progress-bars/>