Re: server -sharedisplay doesn't work?
"Tim Godfrey" <[email protected]> Fri, 18 Feb 2022 22:27:52 +0000
| Newsgroups | gmane.network.tight-vnc.general |
|---|---|
| Message-ID | <[email protected]> |
Hi All, I had a similar problem as @Ben with 2.8.59 running on a Windows 10 system. The options -shareprimary and -sharedisplay 1 failed to work. The remote session always included all monitors. I upgraded to 2.8.63. It has fixed the issue with -shareprimary, but introduced a a couple of new issues. After the install the auto-run registry key (Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run) was set to: "C:\Program Files\TightVNC\tvnserver.exe" -controlservice -slave This did not even load. Rather than loading, tvnserver displayed a dialog with the allowable options. I manually edited the registry key to my prior options, and rebooted: "C:\Program Files\TightVNC\tvnserver.exe" -controlservice -shareprimary This option allows the server to load and operate. The remote session contains the primary monitor only as desired. The only issue is that TightVNC no longer appears in the notifications area of the taskbar. I have no idea where the -slave option came from. It is not documented, but somehow was added by the installer performing the upgrade. I wanted to see a reference on commandline options. A search on keywords "tightvnc commandline options" leads to this document <https://www.tightvnc.com/doc/win/TightVNC_2.7_for_Windows_Server_Command-Line_Options.pdf> which is informative, but unfortunately from 2013. ___________________________________________________________ TightVNC mailing list, [email protected] To change your subscription or to UNSUBSCRIBE, please visit https://lists.sourceforge.net/lists/listinfo/vnc-tight-list