View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0005479||SUMo||Bug||public||2019-05-11 19:18||2019-05-12 09:51|
|Priority||normal||Severity||minor||Reproducibility||have not tried|
|Target Version||Short term|
|Summary||0005479: command line mode with standard help switch doesn't work as expected|
|Description||SUMo command line mode of SUMo doesn't work as expected.|
When I enter a folder with SUMo installed in the standard Windows 10 console, I start SUMo in command line mode with the standard help switch (/?). I expect a standard output or standard error response in that console window with reporting available and implemented switches i.e. for scanning or reporting, eventually extended by version info before returning to the console prompt.
What I observe instead is no output of the SUMo application at all in that console window and an immediate return of the console prompt. It additionally either started a new instance of SUMo window or switched focus to return to an already existing one, probably depending on file path and state of eventually running instance.
When start trying the command line mode, I had an instance of SUMo Pro v22.214.171.1241 already running and initially started via Windows start menu. For the command line, I changed directory of the Windows console to the location where I installed the PortableApps framework with its components SUMo Portable and SUMo (needed by SUMo Portable). In the folder of this SUMo component, I entered the full name with full absolute path and the standard help switch. This version of SUMo is 126.96.36.1999. It's the first time I used that file and that path and the command line for this file. It started this new instance into its GUI reporting also its version.
|Additional Information||When I use the GUI of PortableApps to start SUMo Portable, I couldn't start it because it detected that other instances of SUMo are already running and asking in a popup window to close the other instances before restarting SUMo Portable in the PortableApps framework again.|
When I took a closer look of the instance of SUMo started via command line, I was wondering several other aspects:
* It didn't show the button to acquire the Pro edition although I never entered a license key for that old version nor that path of SUMo.
* When looking into its about section, it reported it as registered with the registration information of the already running instance of the installed SUMo Pro version of different path, drive and location although I never entered a license key for that old version nor that path of SUMo.
* When looking into its configuration, I expected its default configuration as I never started SUMo of that file location before, neither via command line nor via PortableApps GUI. What I saw cannot be the default configuration. Instead it reused the configuration of the installed and running instance of SUMo Pro. Why?
I did not yet check if this happens also on the older device with older operating system.
|Tags||No tags attached.|
|related to||0000565||acknowledged||Kyle_Katarn||Command line support|
|related to||0001508||acknowledged||Kyle_Katarn||Command line option CHECK|
|related to||0005481||acknowledged||Kyle_Katarn||multiple instances of SUMo running leads to loss of registration|
|related to||0005480||acknowledged||Kyle_Katarn||Please extent the command line mode with the reporting and the scanning feature distinguished by different switches|
|2019-05-11 19:18||wolf||New Issue|
|2019-05-11 20:23||wolf||Issue cloned: 0005481|
|2019-05-11 20:23||wolf||Relationship added||related to 0005481|
|2019-05-11 22:43||wolf||File Added: sumo.cli.hlp.20190511.png|
|2019-05-11 22:43||wolf||Note Added: 0003274|
|2019-05-12 09:45||Kyle_Katarn||Relationship deleted||related to 0005481|
|2019-05-12 09:46||Kyle_Katarn||Relationship added||related to 0005481|
|2019-05-12 09:48||Kyle_Katarn||Status||new => acknowledged|
|2019-05-12 09:48||Kyle_Katarn||Target Version||=> Short term|
|2019-05-12 09:48||Kyle_Katarn||Relationship added||related to 0000565|
|2019-05-12 09:48||Kyle_Katarn||Relationship added||related to 0001508|
|2019-05-12 09:51||Kyle_Katarn||Relationship added||related to 0005480|