I find Robocopy better for those purposes? It just worked for windows 10 running with a USB recovery disk. Kent Boogaart Kent Boogaart k 34 34 gold badges silver badges bronze badges. Close, but not available on XP y deafult. Though I will consider it. How to overwrite existing files in destination? Do I have to delete it manually? Esentutl cannot overwrite files so you'll have to add line if exist destination RWM 7. Iconiu Iconiu 2 2 silver badges 4 4 bronze badges.
Gulzar Nazim Gulzar Nazim 51k 24 24 gold badges silver badges bronze badges. If you want to copy files and see a "progress" I suggest the script below in Batch that I used from another script as a base I used a progress bar and a percentage while the script copies the game files Nuclear throne: echo off title NTU Installer setlocal EnableDelayedExpansion echo Iniciando instalacao Compo Josef Josef 7, 3 3 gold badges 30 30 silver badges 33 33 bronze badges.
Yes, I know I could write such a thing. The idea is to reuse any available resources and to simplify sharing of the script. To be fair Gulzar, Josef was offering to send you one, and to send you his available resource to you for reuse.
I suspect you stopped reading after 9 words. Any Josef, you could share those to the rest of the community : — Fernando Barrocal. When I get home I'll dig them up and post a link here. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password.
Post as a guest Name. Email Required, but never shown. Don't steal input focus to show a progress update or completion.
Users often switch to other programs while waiting and don't want to be interrupted. Background tasks must stay in the background. Don't worry about technical support. Because the feedback provided by progress bars isn't necessarily accurate and is fleeting, progress bars aren't a good mechanism for providing information for technical support.
Consequently, if the operation can fail as with a setup program , don't provide additional progress information that is only useful to technical support. Instead, provide an alternative mechanism such as a log file to record technical support information. Don't put the percentage complete or any other text on a progress bar.
Such text isn't accessible and isn't compatible with using themes. Don't combine a progress bar with a busy pointer. Use one or the other, but not both at the same time. Don't use vertical progress bars. Horizontal progress bars have a more natural mapping and better flow.
Clearly indicate the progress phase. The progress bar must be able to indicate if the operation is in the beginning, middle, or end of an operation. For example, progress bars that immediately shoot to 99 percent completion, then stay there for a long time are particularly uninformative and annoying.
In these cases, the progress bar should be set initially to at most 33 percent to indicate that the operation is still in the beginning phase. Clearly indicate completion. Don't let a progress bar go to percent unless the operation has completed. Provide a time remaining estimate if you can do so accurately. Time remaining estimates that are accurate are useful, but estimates that are way off the mark or bounce around significantly aren't helpful.
You may need to perform some processing before you can give accurate estimates. If so, don't display potentially inaccurate estimates during this initial period. Don't restart progress. A progress bar loses its value if it restarts perhaps because a step in the operation completes because users have no way of knowing when the operation will complete. Instead, have all the steps in the operation share a portion of the progress and have the progress bar go to completion once.
In this example, the operation moved to the step of copying files and reset the progress bar for that step. Now users have no idea how much progress has been made or how much time is left. Don't back up progress. As with a restart, a progress bar loses its value if it backs up. Always increase progress monotonically. However, you can have a time remaining estimate that increases as well as decreases because the rate of progress may vary. Use indeterminate progress bars only for operations whose overall progress cannot be determined.
Use indeterminate progress bars for operations that require an unbounded amount of time or that access an unknown number of objects. Use timeouts to give bounds to time-based operations. Convert to a determinate progress bar once the overall progress can be determined. For example, if it takes significantly longer than two seconds to determine the number of objects, you can use an indeterminate progress bar while the objects are counted, and then convert to a determinate progress bar.
Don't combine indeterminate progress bars with percent complete or time remaining estimates. If you can provide this information, use a determinate progress bar instead. Don't combine indeterminate progress bars with animations. An indeterminate progress bar is effectively a generic animation, so you should use one or the other but never both. If users can do something productive while the operation is in progress, provide modeless feedback. You might need to disable a subset of functionality that requires the operation to complete.
If the window has an address bar, display the modeless progress in the address bar. Otherwise, if the window has a status bar, display the modeless progress in the status bar.
Put any corresponding text to its left in the status bar. Place modal progress bars on progress pages or progress dialog boxes.
Provide a command button to halt the operation if it takes more than a few seconds to complete, or has the potential never to complete. Label the button Cancel if canceling returns the environment to its previous state leaving no side effects , otherwise label the button Stop to indicate that it leaves the partially completed operation intact. You can change the button label from Cancel to Stop in the middle of the operation if at some point it isn't possible to return the environment to its previous state.
Center the command button vertically with the progress bar instead of aligning their tops. In this example, halting the copy leaves any copied files, so the command button is labeled Stop. In this example, halting the search leaves no side effect, so the command button should be labeled Cancel. Use the following time formats. Start with the first of the following formats where the largest time unit isn't zero, and then change to the next format once the largest time unit becomes zero.
This compact format shows the most important information first so that it isn't truncated on the taskbar. Make estimates accurate, but don't give false precision. If largest unit is hours, give minutes if meaningful but not seconds.
Keep the estimate up-to-date. Update time remaining estimates at least every 5 seconds. Focus on the time remaining because that is the information users care about most.
Give total elapsed time only when there are scenarios where elapsed time is helpful such as when the task is likely to be repeated.
If the time remaining estimate is associated with a progress bar, don't have percent complete text because that information is conveyed by the progress bar itself. Use a concise label with a static text control to indicate what the operation is doing. I do not care if the progress indicator is in a terminal or a GUI window. Robocopy functionally replaces Xcopy , with more options.
The command is robocopy …. The command is available on every windows machine but the y option is presented in windows vista. As it works only with single files does not look very useful for a small ones. Other limitation is that the command cannot overwrite files. Some interesting timings regarding all these methods.
0コメント