Sample of Runner's command line,
schedule placed into file c:\schedule files\runner.rsc
"c:\Program Files\Runner\runner.exe" c:\schedule files\runner.rsc
If you launch second instance of the Runner, it will be shown message "Runner
already loaded" and second instance will finish. If first instance of the
Runner is hidden, it will be shown.
To disable test of existing instance(s), use command line key /b
as a first symbols of pathname of the schedule if it is in command line, or
only this key, if schedule name is RCOMM.TXT. If schedule pathname contains
whitespaces, conclude key and filename in inverted commas.
Examples:
So far as command execution point consists of two parts (day and
time), schedule file also hase double structure, as well as "INI" files.
All schedule separates with sections. Headers of sections
(
section name
) defines day to execute a command, and
command lines
define time and command to execute.
Thus, general view of the schedule is following:
; comment
[section 1]
command 1
command 2
........
command N
; comment
[section 2]
command N+1
command N+2
........
command N+M
........
First (or unique) schedule section may not have a header. In this case commands of such sections will be executed every time as well as commands of the ev section. It facilitates using Runner as command interpreter.
Note: it is recommended set as the last command of the schedule
used as command file built-in instruction
ex, in other case Runner will not finished after execution of the
schedule. Example of such command file (filename is RCOMM.TXT):
Runner can be loaded manual, however it is recommended to place shortcut to Runner into the Startup folder of the Main Menu, or to use included in the package program SETUP.EXE to install Runner into the system registry.