Code
cmd.exe /C start "" /affinity 0x?? "C:\Program Files (x86)\Windower4\Windower.exe" -c profilename.ini
to launch POL directly using a specific profile. However, Windower4 no longer uses individual files for profiles. I've tried:
Code
cmd.exe /C start "" /affinity 0x?? "C:\Program Files (x86)\Windower4\Windower.exe" -c Oversample
which will launch POL directly. However, it's pulling the default profile, not my profile named Oversample. When using just:
Code
cmd.exe /C start "" /affinity 0x?? "C:\Program Files (x86)\Windower4\Windower.exe"
windower will launch, but show default settings as if it's failing to get it's settings.xml.
From this, I've concluded that the method in which I'm launching it is causing a failure to load the settings file. So, my questions are:
Is there documentation on command line arguments anywhere? If not, am I using -c properly or is it just a leftover from 3.4 that isn't functional?
and
What should I change to be able to load settings and launch from command line? Even if -C isn't supported, I'd like to be able to launch from C# so I can have a one-click overwrite user file(I have more than 4 logins, trying to finally ditch XI-Util after I saw the sandboxing plugin in a thread yesterday).
Apologies for the long-winded post, wanted to include as much detail as possible. Thank you very much for any responses.