I'm trying to run InnerSpace and ISBoxer from a Task, using Windows Task Scheduler. I don't plan on actually scheduling the task, just running it manually. As some surely know, by doing this you can avoid the automatic UAC confirmation on launch.
When I run this from a command line, it works with no problems:
C:\path\InnerSpace.exe run isboxer -launch charSetName
However, as a task, it only runs InnerSpace, and does not accept the arguments. The Task Scheduler API requires quotes around path and arguments, so I'm using:
Run: "C:\path\InnerSpace.exe"
Arguments: "run isboxer -launch charSetName"
Basically, this is identical to the command-line entry.
I've tried fiddling with the quotes, removing those around the arguments, escape-quoting the charSetName (though it has no embedded spaces), all to no avail.
Any idea why this won't work?
Incidentally, I know some people don't like UAC, but please refrain from suggesting I simply disable it. Personally, I think it's a good security precaution, particularly when you can circumvent the confirmation with Tasks. I just wish I could get it working with IS.
As to why I'm bothering to automate this process at all, There are sooo many steps to launching my game - run CH Control Manager, open a keymap, download it, click ok in dialog, run Ventrillo, connect to Vent server, run PlayClaw, run IS, run charSet - that I'd really just like to single-click the whole thing with a script.
Command line arguments
Moderators: Lavish Software Team, Moderators
I should have thought of this before: check the console. Sure enough it indicated a problem with the quotes:
Unknown command ' "run'
Apparently the one thing I didn't try was putting quotes only around charSetName, regardless of its lack of embedded spaces.
Thus altered, the Task works perfectly. Odd that the quotes were not required for the command-line version.
Unknown command ' "run'
Apparently the one thing I didn't try was putting quotes only around charSetName, regardless of its lack of embedded spaces.
Thus altered, the Task works perfectly. Odd that the quotes were not required for the command-line version.