Hi List,
is there any particular reason why x2goclient.exe will save session settings to the registry and will only use a "sessions" file when called with "--portable"? Using the "sessions" file is the default for Linux and AFAIK also for Mac OS X, so why the variation in x2goclient.exe?
IMO, using the sessions file by default simplifies handling across client operating systems (especially as there is no import/export option between the "sessions" file on Windows and the registry). That's why saving to the registry should be dropped if nobody uses it, or made optional ("--save-to-registry" or somehing like that) if there are a few users that need it.
So, to the Windows client users out there: Can anyone of you think of a reason that speaks against saving the settings in a file?
Until we have a decision on that, my workaround is a link with the following destination: X:\x2goclient.exe --portable --home=%USERPROFILE% (where X: is a read-only network drive, and %USERPROFILE% is a reserved variable on Windows that contains the path to the user's home directory) BTW, Alex will soon implement a change so that the sessions file can be stored on the read-only network drive as well.
-Stefan