Welcome!

Now - everyone join in and say: "No!" \:\)

You can use the Shell command to invoke external commands that Kix will wait for, or Run to invoke a command that runs independent of your script.

One of the best ways to accomplish this (and the easiest to debug) is to create a variable that holds the command, then display it, and finally run it. When it is working fine, you can remove the "display it" step. Something like:
 Code:
$Cmd = 'iexplore.exe'        ; base command
$Cmd = $Cmd + ' http://url'  ; define the URL part
; repeat the above to add any additional parameters or arguments
; Pay attention to the leading space in each command component

'About to run: ' $Cmd ?      ; show the command (for debugging)
Run $Cmd                     ; run the command string

This may seem more complicated, but it allows you to pay close attention to each argument/parameter, getting the quotes right, etc. Speaking of quotes, we tend to use single quotes in Kix (especially in this case)because DOS comands usually require double quotes - it's easier to embed the double quotes this way.

Glenn

PS - if you have several consecutive shell commands to run, a BAT file might be the way to go - you can even create it with Kix as you need it. For single commands, use Shell or Run.
_________________________
Actually I am a Rocket Scientist! \:D