The PATH
passed to a do shell script
command in AppleScript, or a do shell script
command in a Run AppleScript action in an Automator workflow, or a Run Shell Script action in an Automator workflow is /usr/bin:/bin:/usr/sbin:/sbin
, and any executable called that is not within that PATH
, then the fully qualified pathname needs to be used.
In AppleScript use the do shell script
command, e.g.,:
do shell script "open -a 'Parallels Desktop'; /path/to/prlctl start 'Windows 10'"
In Automator you can use a Run AppleScript action with the same do shell script
command as above.
Or use a Run Shell Script action with, e.g.,:
open -a 'Parallels Desktop'
/path/to/prlctl start 'Windows 10'
If you need a delay between the commands add, e.g., sleep n
when n
is the number of seconds to delay, e.g.,:
In the do shell script
command, e.g.,:
do shell script "open -a 'Parallels Desktop'; sleep n; /path/to/prlctl start 'Windows 10'"
Or in the Run Shell Script action, e.g.,:
open -a 'Parallels Desktop'
sleep n
/path/to/prlctl start 'Windows 10'
prlctl
command line utility. I would think that shouldn't be necessary, as it not for thevmrun
command line utility in VMware Fusion.