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):
- 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:
- 09:30 ,path\program.exe - in the minimized state
- 09:30 'path\program.exe - in the maximized state
- 09:30 ?path\program.exe - in the hidden state
- 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:
- 09:30 %0path\program.exe - without logging
- 09:30 %1path\program.exe - always logging
- 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:
- ; next command launch application AnyProga
; and put to it command line "any_keys"
08:00 c:\program files\AnyProga\AnyProga.exe any_keys
- ; next command create new directory "NewDir"
; (using DOS command shell of Windows 95)
15:00 command /c MD NewDir
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:
- ; alarm-clock
06:00 #c:\sounds\alarm.wav
- ; DOS-session with automatic
;console closing on end of session
;using PIF-file
20:00 #c:\dos\dosprog.pif
- ; check for new Runner versions
^0000 #http://home.comset.net/panoff/runner
...next