I looked briefly into each of the dlls and the executable for another topic and nothing in particular popped out at me. I'll have another look some other time, but if it's anywhere I'm going to wager its in the executable which will take a while to search through and even longer to disassemble, rewrite the command, and reassemble. I could just replace the string constants if they exist in the binary, but I would like to have a RUNPROG tag that responds but without hal tagging on extra topic related stuff, and a version where hal doesn't say anything at all.
EDIT: Thanks for that jasondude. I may end up trying to rewrite all the scripts so that everything is run like that and the hidden RUNPROG tag is never used. At least that way I will have all the control I could possibly want, though I would expect that RUNPROG may have some additional security and exception handling beyond what the script might provide. When I've got time between work projects and I'm in the mood I'll have a go at seeing if I can use the script to reference the shortcut.dat file the same way RUNPROG does as I don't want to write a rule for every program on my computer. I must be crazy though, I'm working two projects, one of which is writing a fuzzy inference system and the other doing research on some fast methods of transparency rendering in a deferred shading engine, and then with all my free time I'm working on hal
