slow down a batch file
\n<\/p>\n
\n“Gustav Medler” wrote in message
\n> Hello,
\n> is there a program anywhere which stopps executing of batch files for 1
\n> or 2 seconds without need to touch the keyboard? <\/p>\n
> PAUSE requires a keyboard stroke…. batch needs user’s attention…. <\/p>\n
There are four main options for delays in Batch scripts: <\/p>\n
1) Use the time-delay built into CHOICE command <\/p>\n
\nThis can be used for delays from 1-99 seconds. For example,
\nthis command line delays 10 seconds before resuming. Change
\nthe 10 to a number from 1-99 for other delay periods. <\/p>\n
\n:: Delay script execution for 10 seconds
\nREM | choice \/c:delay \/td,10>NUL <\/p>\n
\n2) Use the built-in delay mechanism of the PING command. <\/p>\n
\nAssuming you have Microsoft TCP\/IP installed, you can PING
\nthe LocalHost and obtain delays in this way. With PING, you
\nneed to specify a number equal to 1 second longer than you
\nwant the delay to be. Unlike CHOICE delays, PING delays are
\nnot limited to 99 seconds, however. <\/p>\n
\n:: Delay script execution for 10 (= 11-1) seconds
\nping -n 11 127.0.0.1>NUL <\/p>\n
\n3) The free Microsoft SLEEP.EXE command <\/p>\n
\nMicrosoft provide a free SLEEP utility as part of the free
\nWindows 98 Resource Kit Batch tools. With the SLEEP.EXE
\nexecutable placed in the system path, for example in the folder
\nC:\\WINDOWS\\COMMAND, the delay syntax is simple: <\/p>\n
\n:: Delay script execution for 10 seconds
\nsleep 10 <\/p>\n
\nDownload Microsoft SLEEP.EXE Batch tool free from:
\nftp:\/\/ftp.microsoft.com\/Services\/TechNet\/samples\/ps\/win98\/reskit\/scrp…
\nand click on the filename SLEEP.EXE <\/p>\n
\n4) Using the START command
\nSometimes, a delay is wanted merely to allow a GUI process to finish.
\nIn these cases the START command is useful. The command line: <\/p>\n
\nstart \/w “C:\\program files\\SomeProgram.exe” <\/p>\n
\nwill run the program SomeProgram.exe in a separate process and \/w=Wait
\nfor it to complete before continuing. Use “quotes” around any file
\nspecification that contains [Space]s. For brief help with START type:
\nstart \/? <\/p>\n
\n====== <\/p>\n
\nNotes:
\n(a) Although the CHOICE delay method is useful to know, CHOICE
\ndelays are very CPU intensive. Typically, CHOICE uses up all
\nthe spare CPU time available during the delay (although it isn’t
\nperforming any useful task). The PING version of the delay uses
\ntypically under 0.5% of CPU capacity, and will often record a
\nnegligible CPU usage on fast systems. So for other than trivial
\ndelays, PING is most definitely to be preferred. Delays using
\nthe SLEEP command use negligible CPU time. <\/p>\n
\n(b) To study CPU usage of tasks such as the CHOICE, PING,
\nor SLEEP delay techniques, you can use the free Microsoft
\nprocess viewer WinTop: <\/p>\n
\nTo install WinTop, get the free download from page:
\nhttp:\/\/www.microsoft.com\/windows95\/downloads\/default.asp
\nscroll down the page, and locate the item: Windows 95 Kernel Toys
\nClick on that and click the DownLoad Now button on the next
\npage. Run the packed executable: w95krnltoys.exe, in a temporary
\nfolder, and when it unpacks, right click on WinTop.inf, and click
\ninstall. After a few moments, you can remove the contents of the
\ntemporary folder. Place a link to C:\\Windows\\Wintop.exe on the
\ndesktop to run WinTop. To terminate a process with WinTop, right
\nclick on the process, click Properties, Priority tab, click
\nTerminate Process Now. WinTop has a small database of “essential”
\nOS components (they show with a small cog icon) which it won’t
\nterminate (for example mmtask). The Win95 Kernel Toys package is
\nsuitable for Win98 (and ME as far as I am aware). <\/p>\n
\n(c) Windows 95\/98\/ME START command features:
\nSTART is an external command: executable file START.EXE
\n(For brief help with START, type the command: start \/? ) <\/p>\n
\n(i) start \/w Program.EXE \/Any \/Switches
\nThis runs Program.EXE in a separate process thread, and Waits(\/w)
\nfor it to complete before continuing. If Program.EXE returns an
\ninformative ERRORLEVEL, START (with \/w) returns that ERRORLEVEL
\nto the parent Batch file. <\/p>\n
\n(ii) start Program.EXE
\nAs \/w, but doesn’t wait for Program.EXE to complete, nor does it
\nreturn an informative ERRORLEVEL from Program.EXE <\/p>\n
\nWindow control for the STARTed process is provided through the
\n\/m(=run in Minimized window) \/max(=run in MAXimised window) and
\n\/r(=run in Restored window). <\/p>\n
\n(iii) start DATAFILE.EXT
\nOpens DATAFILE.EXT in the application registered in the CLASSES_ROOT
\nsection of the Registry to handle files of that type. For example:
\n (a) start http:\/\/www.website.com\/index.htm
\n opens that page in your default Web browser.
\n (b) start textfile.txt
\n opens that file in your default Text editor (usually NotePad). <\/p>\n
\n(iv) Native ERRORLEVELs from START
\nstart \/?>NUL
\nThis command line returns ERRORLEVEL 255 if used in the Windows GUI
\n(protected mode), and ERRORLEVEL 1 if used in real-mode. <\/p>\n
\n(v) Separate START command line parameters with [Space]s
\nWhen using START, always use [Space]s to separate its command line
\nelements, so for example, although, without START:
\nchoice\/c:yn
\nis valid syntax, with START, you must insert a [Space] before \/c:
\nstart choice \/c:yn <\/p>\n
\nNote: Windows 2000
\nIn Windows 2000 and similar OSes, START is an internal command.
\nUse start \/? in Windows 2000 for details of the extensive extra
\nfeatures available (including process priority control). <\/p>\n
\n—
\n(pp) William Allen <\/p>\n
<\/p>\n","protected":false},"excerpt":{"rendered":"
slow down a batch file<\/p>\n","protected":false},"author":4,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-266","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"http:\/\/www.wildow.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/266","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.wildow.com\/blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.wildow.com\/blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.wildow.com\/blog\/index.php?rest_route=\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"http:\/\/www.wildow.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=266"}],"version-history":[{"count":0,"href":"http:\/\/www.wildow.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/266\/revisions"}],"wp:attachment":[{"href":"http:\/\/www.wildow.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=266"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.wildow.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=266"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.wildow.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=266"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}