Lax wrote:
One way to avoid this issue is to just run it via the uplink instead of via the session.
...
If you just want to "launch 2 programs at once", put the other program in the "Launch without hooking executable" of your Game Profile?
[/quote]
Neither would work as intended... The idea is: I launch certain prog before EVE starts. It does its dirty work on EVE executable, then quits. Then my [crap] provider cuts the link while I sleep. EVE instances lose connections and restart. Then, for every new EVE instance another instance of wrapper prog should start again, do its work again and quit - without my (i.e. user, manual) interference. It just doesn't work using this "preload executable" trick, I've just tried... it launches wrapper once, when I launch certain EVE profile manually, yet it doesn't relaunch it on EVE disconnect. It HAS to be in the pre-startup I think!
Lax wrote:
I spent some time the other night working on OSExecute, and really I just need to replace this function with something similar but different.
Maybe you are right... you know the mechanics, after all, not me. This way or that, can you add this "something similar" anytime soon please? If I've got it right, OSExecute is intented to launch any OS command. Can you add something simplier for now, something like LaunchExecutable (with path and parameters, preferably)? Of course, it shouldn't wait until executable finishes, like batch file does (unless you add "start" prefix before the executable name) - it has to just launch the file and go on to load the main game executable.