>Edit: I took a look at your source, and I'm unsure about the >reasons you're doing things the way you are. First, shell >scripts should have their first line set to ``#!/bin/sh'' (or >whatever shell you want to use), and should be set as >executable.
I took out the #!/bin/sh for testing since I couldn't get it to work, the script was marked executable.

> Second, it seems like a waste of resources to start bash >via execve() in order for it to just execute other commands, >unless you want to be able to execute commands like >``cd /drive0/var/emptris && ./emptris'', which would, in all >honesty, probably solve your problem here.

This is quite true I'm sure, I thought about executing the files directly, but then I ran into this problem with a program needing a working directory. And now I just realized my mistake with the startemptriv script I didn't run ./emptriv I just ran emptriv (doh!).

Ok the next version of Starter will run programs directly. If you need to run scripts (like in this case) you can just put /bin/sh -c /myscript in the program config file. I'll also have to look into a way of killing a program after it's started.

On a side note to the killing a program idea.. does anyone know how to Unbind a menu item in hijack?? This is what I need so starter could start a program, unbind it's menu item and then bind a new menu item called "Stop EmpegVNC" or whatever