Well, I don't have a soldatserver.exe, it's up to you to check the individual parts.

EDIT: To run some tests, you'll have to remove the three "-l" in front of the alias names, in the code above.
That is: change "alias -l sendkeys { ..." to "alias sendkeys { ..."; do the same with "alias appactivate" and "alias isrun".


1) does the $isrun-check work for you?
I tested with cmd.exe and some other apps.
while soldatserver.exe is running, type in any mIRC window:
Code:
//echo -a $isrun(soldatserver.exe)
It should return $true if it's running, $false if it aint running. In addition, try "soldatserver" instead of "soldatserver.exe". Test other applications, like:
Code:
//echo -a $isrun(cmd.exe) | run cmd.exe | echo -a $isrun(cmd.exe)


2) does /appactivate work for you?
Type in any mIRC window:
Code:
/appactivate soldatserver.exe
Is soldatserver.exe now the active app? If not, try "soldatserver" instead of "soldatserver.exe" (For example with Firefox, it's working for "appactivate firefox", but not for "appactivate firefox.exe".)


3) does /sendkeys work for you?
the command is "typing" keystrokes to the active app. Thus, while in mIRC:
Code:
/sendkeys /echo -a test{enter}
Should result in the word "test" echoed to your mIRC window.
You can play arround with these commands, e.g. sending keystrokes for testing purposes to apps, like:
Code:
//appactivate cmd.exe | sendkeys ipconfig{enter}
(if cmd.exe is already running, should trigger the ipconfig output there)

Something I forgot in the original post: to reset focus "back" to mIRC, you can use appactivate again, or the in-build command "showmirc -s".

Last edited by Horstl; 10/11/08 11:17 PM.