I make these utilities as entertainment, it is my "game".
This is an important information because it tells a lot about the aim of your utilities. Until now my asumption was that your goal is to develop tools which are helpful to gather information for a user. In this case you should write it from the perspective of the user. As to what I understand now is that you rather try to explore the opportunities of Batch scripting and test your skills. And obviously that's the reason for your "installation" of the scripts, even though they would work without. And that's the reason why you try to simulate a progress bar, even though you're completely reversing the sense of a progress bar. (Calling it a lie sounds harsh, however you know it's the truth.)
Speaking of progress bars:
- Notice the user if and only if there is a risk that the user thinks the script might be frozen. That is, a task takes noticeable longer than 5 seconds.
- In such cases it should be good enough to just print a message like "Please be patient, this might take a while." before you start the time consuming task.
- If you still want to animate something, do it in parallel while the task is running. That's the expection of the users. Once they recognize that you waste their time, they will not use your tool anymore.
- Don't use a progress bar unless you can divide the task into logical subtasks, and you can advance the bar once a subtask is finalized. A progress bar should indicate the current progress of the task. If this is not possible you could still animate something else. Like a spinner:
viewtopic.php?p=59838#p59838
But still only do it if the task takes longer than 5s and definitely only do it at the same time the task is running.
Steffen