Use execution directives to process the script file. Again, the @THREAD
and @PROCESS directives are mutually exclusive.
The following table lists the supported execution directives.
Note: Timing out on the @WAIT_EVENT and @WAIT_NOTIFY directives
is not considered a failure.
@THREAD x
Specifies that the script lines following this
directive belong to thread number x until the next @THREAD directive
is encountered.
@PROCESS x
Specifies that the script lines following this
directive belong to process number x until the next @PROCESS directive
is encountered.
@SET_EVENT name 0|1
@WAIT_EVENT name [to]
Waits until the event name is set to 1.
@WAIT_EVENT does not cause a change of the event state. If you need a reusable
event, use this directive.
The timeout (to) is specified in milliseconds. If omitted, it defaults
to 3 minutes.
@WAIT_NOTIFY x [to]
Waits for a specific number (x) from an
expected MM_MCINOTIFY notification message. This number must match the index
used in the MM_MCINOTIFY reference line. The @WAIT_NOTIFY events are not
reusable because there are no events that logically reset it.
The timeout (to) is specified in milliseconds. If omitted, it defaults
to 3 minutes.
If the associated mciSendString function fails, the event is posted to prevent
delays for notifications that are never going to be sent.
@WAIT_PASSDEVICE alias [to]
Waits until the device instance with an alias of
alias gains use. This assumes that the alias names used within a
script file are unique. The maximum alias name length is 20 characters.
Note: Use a unique alias for every OPEN command.
The timeout (to) is specified in milliseconds. If omitted, it defaults
to 3 minutes.
The tool assumes that a unique alias is specified on each OPEN string command.
If unique aliases are not used, errors conditions might occur.
@REM comment
Echoes the comment to the screen and the
output log file. All other script comment lines (those starting with ;
or #) are neither transferred nor displayed.
@PAUSE to
Pauses processing of the current thread or process
in the input script file for the specified time. It does not stop the processing
of the notifications or window functions. Other threads or processes are
not affected by this directive.
@BREAK [message]
Causes a message box to appear with message
text. Script processing is halted until the user responds with the correct
action. For example:
@BREAK [replace the CD]
@CHECK [message]
Grades the success of the previous command based
on the user's response. A pop-up window displays the message and
prompts the user with Yes or No push buttons. The status is passed if the
user selects Yes, or failed if No is selected. For example:
@BREAK The music will play for 5 secs. Ready to time it?
play cdaudio notify
@PAUSE 5000
@CHECK Did it play?
[Back]
[Next]