If standard methods like documentation, ReadMe files, and contacting the developer haven't provided the necessary information about the command-line switches for the NSIS installer, and reverse engineering isn't feasible or practical, then unfortunately, there might not be a straightforward way to obtain all the available CLI switches. In such cases, trial and error might be your best option. You can try experimenting with different command-line switches to see if they have any effect on the installer's behavior. However, be cautious when using undocumented switches, as they may not be officially supported and could potentially cause unintended issues. Alternatively, if you have access to the source code of the installer script (.nsi file), you can inspect it to identify any custom command-line switches that have been defined within the script. Ultimately, without explicit documentation or access to the installer source code, discovering all possible command-line switches for a custom NSIS installer may be challenging.
I understand your situation. Sadly, there are no built-in tools or commands in NSIS that would conveniently list all command-line switches for a particular installer. Indeed, the nature of NSIS allows developers to create custom switches, but it doesn't obligate them to provide a mechanism to list or introspect them.
Ultimately, the switches are defined and processed within the installer's source code itself (.nsi files or potentially script files included by them), which unfortunately cannot be automatically extracted from the compiled executable.
Without access to the source code, or specific knowledge and documentation about the implemented switches, it's very hard to discover them. Decompiling the installer would essentially be reverse engineering, which is usually illegal and often discouraged.
Therefore, your options are limited to:
1. Trial and Error: You mentioned the /op=n switch, which is evidently a custom switch. You can try different switches in a similar format and see if they achieve the desired results. This method is risky, as unintended switches might cause the installer to behave unpredictably.
2. Documentation and Support: Even if the documentation doesn't detail the custom switches, you could try contacting the developers or customer support teams. Explain the situation and the need for automation; they might provide assistance or further documentation.
3. Reversing: With extreme caution (and purely for academic or your own personal use), you could attempt to reverse engineer the process. This route is not recommended and could potentially be against the license agreement.
Please, keep in mind that if command-line switches are not documented, there might be a good reason for it, e.g., they might not be considered stable or supported interfaces and could change in future versions without notice. Always respect the developer's choices, their copyright, and intellectual property rights.
