Solo Startup Flags

From Eigenvector Research Documentation Wiki
Jump to navigation Jump to search

Stand-alone applications like Solo, Solo+MIA, Solo+Model_Exporter and Solo_Predictor support several command-line flags to customize the start-up behavior. The flags listed below can be used by either (A) calling the application from a DOS window/Linux command line, (B) creating a shortcut to the Solo application and editing the shortcut to include the flag(s) desired, or (C) calling Solo from another program which permits inclusion of flags in the command line.


Clear Settings Start up "clean" without any user-stored settings (including license codes, user preferences, start-up folders, window locations, squelched tips, and other user-defined settings). Useful when Solo is having trouble starting because of some user-defined settings, or when used with the -loadsettings flag to get a specific start-up state. This flag is automatically and always used with Solo_Predictor (user-defined settings are never stored).

-loadsettings "filename"

Load Settings Load user settings from the specified XML file specified by the fully-qualified string "filename". A settings XML file can be created by using the "Save" option from the Preferences Expert or using the settings file format description. Often used with -clearsettings so that only the settings in the specified file are used.

If a file named default.xml is present in the application folder or the top-level installation folder (usually C:/Program Files/EVRI/Solo or similar on Windows), this file will always be read before reading the file specified by the -loadsettings flag.

-licensecode "newcode"

License Code Use the supplied license code "newcode" in place of any previously-stored license code. Often used with -clearsettings although the clearsettings flag is not necessary to install a new code.

-load "filename"

Load Load the contents of the specified file into the base workspace after starting up.


Automation Server Opens Solo with no graphical user interfaces and opens a communications socket for control by a 3rd party application. See Socket Interfaces in Solo_Predictor for information about connecting to Solo via sockets and scripting.


Automation Server with No Socket Same as -automation except no socket will be opened. Generally only used internally by DLL-connection calls because Solo will be otherwise unreachable in this mode.

NOTE: When referring to a file name as input it may require escaped quotes. For example:
$Solo_Predictor.exe "-debug -loadsettings ""C:\Program Files\EVRI\Solo_Predictor_41\application\default.xml"""