Urm, no not really... /notportable just tells XMBC it has been launched by the entry setup by the installer, and not to run in portable mode (so save settings etc. into the same folder as the executable, rather than %appdata%\Highresolution Enterprises\XMouseButtonControl or whereever chosen during install.
I repeat again, the setup window *should* only show at startup if XMBC is already running. So if the setup window is showing, that would suggest that XMBC is being run more than once. The log file should indicate this, and say something along the lines of:
Code: Select all
05-06-2023 08:23:03.509> MultInstance: Sending command line '/notportable' to an existing instance of X-Mouse Button Control
05-06-2023 08:23:03.510> MultInstance: Successfully finished communicating with the first instance of X-Mouse Button Control.
05-06-2023 08:23:03.510> Received 2048 bytes on the IPC named pipe.
05-06-2023 08:23:03.510> Received message with data 0x80000204 from another instance of X-Mouse Button Control.
05-06-2023 08:23:03.510> RemoveMouseHook(true)
05-06-2023 08:23:03.515> EndHookThread called with no hook or timer thread initialised!
05-06-2023 08:23:03.571> Exiting Hotkey Thread MessageLoop...
05-06-2023 08:23:03.572> CMyMessageWnd::OnSetup - Opening setup dialog.
This (opening the setup window the second time you run XMBC) is by design, so one can get to the setup window if running XMBC completely hidden (no icon in the tray which you are not doing). After telling the first instance to open the setup window, the second instance will terminate, thus leaving only one copy of XMBC running. So the only way to see that two instances have been started, would be to look in the log I guess (you should never see more than one instance of XMBC in task manager except very briefly during startup where the above communication between instances and log is generated)