12
3
I use TightVNC Viewer version 1.4.0 and want to save 75% scale and Full-screen mode settings. When I set them, close connection and then open it again, settings are default again.
How to save it permanently? Is it possible to save a password?
12
3
I use TightVNC Viewer version 1.4.0 and want to save 75% scale and Full-screen mode settings. When I set them, close connection and then open it again, settings are default again.
How to save it permanently? Is it possible to save a password?
9
For Windows XP:
For Windows 7 (Right clicking in the Task Manager doesn't display the correct menu):
fullscreen=0
to fullscreen=1
.
1
If you are using TightVNC 2.x, on Windows it is not straight forward like you would expect. You should save connection info to .vnc file, and you cannot just Open with... tvnviewer.exe
The full procedure is that you should Copy shortcut of your existing VNC Viewer, rename it to your connection name and right click it, click Properties and inside Target editbox put parameter called optionsfile
. The final Target should look like this:
"C:\Program Files\TightVNC\tvnviewer.exe" -optionsfile="C:\fullpath\savedconnection.vnc"
0
I am a TightVnc newbie but am 'familiar' with 'programming' techniques (well, just about keeping my head above the waterline). This question is a bit old but it had me stumped for a while. Here's what I did to get a copy of the TnvViewer 'OptionsFile':
- Open/Load TightVnc Viewer on my Windows 10 PC; ie connect to the other PC.
- On the toolbar of the TightVnc viewer window > click the 'save' icon ("Save session to .vnc file".
- This opens a Windows Explorer 'save' window to my Windows PC; navigate to my chosen folder, create a filename, and click 'Save'.
- I now have a 'standard/basic' options file to play with.
Apologies, as I cannot confirm what all the options do; I was just pleased to get the file. As long as the Windows Explorer 'Open With' link connects the options file with TnvViewer, double clicking the options file puts me straight into TnvViewer on my nominated PC. Hope this helps other Newbies.
0
In my version of TightVNC 1.2.9, the target must look like this (/config
instead of -optionsfile=
in Arunas' answer):
"C:\Program Files (x86)\VNC\vncviewer_T129.exe" /config "C:\Users\...\vnc\mysettings.vnc"
Please [edit] this so it makes sense by itself. It’s OK to copy part of Arunas Bartisius’s answer as long as you give credit. Also, please identify your version of TightVNC.
– Scott – 2019-03-20T15:24:46.963I did not copy anything from somebody elses answer. – mjavu – 2019-03-21T16:12:00.940
I didn’t say that you did copy anybody’s answer. My point is that, all by itself, your answer doesn’t make much sense. I suggested that you improve it to say something like, “As Arunas Bartisius says, the procedure is to make a copy of your VNC Viewer shortcut, open Properties, and change the Target field. But, for TightVNC 1.2.9, the target must look like this: "C:\Program Files (x86)\VNC\vncviewer_T129.exe" /config "C:\Users\...\vnc\mysettings.vnc"
(using /config
instead of -optionsfile=
in Arunas' answer).”
0
"C:\Program Files\TightVNC\tvnviewer.exe" -optionsfile=FILENAME.vnc
But this means that you have your vnc
file already saved which is what OP is actually asking about. – Dawid Ferenczy Rogožan – 2018-02-12T17:16:59.773
2What do you do with this? – Jon – 2014-03-08T04:33:24.367
Thanks for this information. When click this .VNC file an error occurs:
My .VNC file begins like this:
[connection] host=192.168.1.103 port=5900
IP address is correct. What can be wrong here? – JohnM2 – 2010-03-08T18:22:43.610
But loading this config file when app is opened works good, so it is already very good. – JohnM2 – 2010-03-08T18:25:10.860
Are [connection], host=192.168.1.103, and port=5900 all on different lines? (Okay, so probably the superuser comments just don't allow putting them on different lines). Did you edit the file in Notepad or some simple text editor? I don't know how TightVNC behaves if there are weird line endings. Also, is version 1.4.0 a beta? All I see on their site is 1.3.10 (stable) and 2.0 Beta. Maybe 1.4.0 has a bug. – Ben – 2010-03-08T22:47:09.430