There is no reliable way of getting the command line parameters out of an executable. At least as long as the author or the executable does not want to provide the information.
Therefore my answer is also generally valid for any executable:
You can try the SysInternals Strings utility to dump all human readable content and maybe you find something.
Usually the output is quite long, so you want to dump it into a text file and later analyze the textfile with a text editor
strings -n 3 -q myapplication.exe > params.txt
For your first try you can use Strings on itself:
strings -q strings.exe > strings.txt
You should find the undocumented
/accepteula switch. The other switches are hard to find, because they are single character switches.
Check in advance if the executable is packed by something like UPX. If so, unpack it before running Strings on it. If the executable is UPX packed you should get some output similar to this at the beginning:
!This program cannot be run in DOS mode.
But even if you don't find anything, there might still be command line parameters, but they are just not available in a human readable format (but maybe encrypted).
And of course, also consider that one option is that the executable does not take any command line parameter.