...previous

COMMAND LINES

Every
section (except menu and options) sections consists of command lines and comment lines. Comments can be placed in the end of every string using special syntax. Whitespaces in the begin of any string is ignored. Strings, begins with semicolon ( ; ) interpreted as comments and ignored.
Every command line consists of four parts: optional one-time execution label, time field, executive command and optional in-line comment. Time field and command can be separated with whitespace(s) or have not separator. Label must be separated with whitespace or colon (":") from time field. In-line comment should be placed at the end of string and separated from other parts with key combination *!.
If command line is too long and can not be viewed without scrolling, it can be divided on several parts. At the end of every parts of divided command, except last of them, should be placed special key *+ . All whitespaces at the begin of continuations is ignored. In every partstring of command can be in-line comments. It should be placed after divide key.
Time field can contains also repeat interval for
cyclic commands. Executive field can contains command modifiers. Thus, common command format is following:

; comment
.label:time-time{interval -stop} window_modif start_modif command*!comment

Time can be defined with four ways:
  1. directly, as HH:MM (all digits is required, including zero), for example, 05:30. In place of one or several digits may be used "joker", - simbol "*". Charplace with "*" do not used in time checking (always YES). If command has time field like **:**, it will be executed every minute. If command has time field like **:*0, it will be executed on 0, 10, 20 minute of every hour. If command has time field like 1*:15, it will be executed on 10:15, 11:15, 12:15 ... to 19:15 including.
    Time field can be extended into time interval. Such commands will be executed on first enter into this interval: on first margin or on system load between interval margins and one time during session. To set interval add second time point, separated with hyphen ("-") from the first time point.
    Sample: 16:00-23:00 - command has such time field will be executed on 16:00 or on reloading of the schedule from 16:00 to 23:00.
  2. with delay from Runner loading, format: ^XXX, where еее - delay value in minutes. Sample: ^5 - in five minutes after the Runner was started, ^ - on start (as well as ^0).
  3. with delay from schedule loading, format: ~XXX (as previous). This commands will be executed on every schedule reload (including first load on start of the Runner, reload with re instruction, reload with menu and so on). It is usable to set interruptable cycles (all works cyclic commands are interrupted on reload of the schedule).
  4. with delay in seconds from execution of previous (higher) command. Format: +XXX, where XXX - delay value in seconds. XXX may absent. It is same as zero delay. It is not allowed to use cyclic commands. Whitespaces separating + and delay value is inadmissible. It is allowed to use any number of command in such group. Delay of every following commands starts from execution time of a previous. It is required first command has time set with other method in such group of commands. It is allowed to use empty command (only time field without executive part). First command may be cyclic. Such command groups can be used in user menu section too.
It is possible to execute commands on events. To define this command use "impossible" time field (hour value > 23d). It is recognized following values:
  1. 97:xx to execute command, when mouse cursor is stay in the one of screen corners during 0,4 second. Minutes ('xx') set controlled corner: 00 - for Left-Top, 01 - for Right-Top, 02 - for Left-Bottom, 03 - for Right-Bottom. It can be same commands for the one position.
    Sample: 97:01 "C:\Windows\System\Dangerous creatures.scr" /s to launch screen saver when cursor is stay in Left-Top corner of the screen.
  2. 98:xx to execute command on Windows shutdown;
  3. 99:xx to execute command on Runner finishing;
Using one-time execution label you can define commands to execute one time per day, independently from way to set execution time. Label must be placed at the begin of the command line before time field. Label consists of prefix, identifier and separator and has following format:

.identifier:

Prefix is a char point (".") or a colon (":"). They replace each other during work cycle. Separator can be whitespace or colon. Identifier can contains any symbols, except whitespaces and colons. Sample:

.This_is_a_one-time_execution_label:

It can be set cyclic commands. Time field defines first execution moment of the command. After that command will be executed one time per defined number of minutes. Cycle finish on Runner exit, on schedule reload, if on the next execution point Runner is sleeping (see built-in instruction sl) or on user-defined moment. To set cyclic execution, place interval in minutes after the time using following format: HH:MM {interval} command. Sample: ^0000{15} command - command will be executed on Runner's start and every 15 minutes after that.
To set end of cycle time point place it with cycle interval between "{}", leading with hyphen, as: {interval -EOC}
Sample:

08:00 {10 -17:00} >cm=>me=New message(s)!
This command will check for new e-mail messages from 8 to 17 o'clock every ten minutes.

If the command contains path name for the launched application, it will be set as current directory for this application, except applications, started with Windows shell (see modifier #).
Window state, starting method and logging may be set with special command modifiers, which placed before the executive field of the command line in the following order (any modifier can absent; only on modifier of one kind may be used):

  1. window state of launched application set with modifiers , (comma), ' (apostrophe) ш ? (question-mark). Comma sets minimized state of window, apostrophe - maximized, and question-mark - hidden (without visible window and button on the TaskBar). Use last modifier carefully. Before using it in automatic mode, check that it will not damage the system. Do not use it with interactive application or use instruction cw for closing such programs. Samples:
  2. kind of logging set with modifier % (percent-mark). If this modifier is absent, for this command will be used logging mode, set in the option section. If combination %0 is present, such command will not be logged in any case. If combination %1 is present, command execution will be logged always. Samples:
  3. kind of start of the application set modifier #. If it is absent, executive field interpreted as module pathname and command line for new process. Such command may be used only for applications, and get full control for the executed program. Samples: However, it may be launch applications, using Windows shortcuts, associated files types, etc. It is equal to double clicking on object icon in the Windows Explorer, or on the DeskTop. Use modifier # for this kind of command. In the right side of this modifier it may be placed pathnames for shortcuts, folders, files of registered types, URLs and so on. Action will be depend of the type of object (it will be default action, for example, for the "DOC" file will be executed MS Word, for the URLs will be started MS Internet Explorer or Netscape Navigator). Samples:

...next