Where does VNC Viewer save it's default settings

[redndahead]

I looked in the registry and they don't show up there so where can I find VNC viewer's default settings?

Also can these settings be used in the registry?

Adam

[Rudi De Vos]

file in %temp%
options.vnc

[redndahead]

can those settings be set in the registry to be the default settings?

[Rudi De Vos]

Only the server use registry settings
The viewer don't use the registry, but can read .vnc files.

The %temp%options.vnc is used to auto save the last settings (option: auto save) or you can use it as default (option: don't auto save)

[JITR]

Could the config file be saved somewhere else, please? I'd prefer `%USERPROFILE%\Application Data' (or deeper in a subdirectory under this path). Temprary directory is for temporary rubbish that may get deleted, I don't think it's clever to store configuration files there...

Or use `My Documents' as M$ Remote Desktop client does with the similar file of its own.

Well, now I see a reason why every user should have their own temporary directory... ;-) / :-(

[Rudi De Vos]

It depend how you see it.

When we first added the option.vnc file it was intend for temp save the settings, so that in case you miss the password you don't have to retype all. This is still the case if you check (save last settings)

But then people asked to use it as option (set once and reuse)
As you see, two uses for the same function....

The %temp% was a good choose for temp saving, but perhpas not if you
use it as presets.

[JITR]

It depend how you see it.

When we first added the option.vnc file it was intend for temp save the settings, so that in case you miss the password you don't have to retype all. This is still the case if you check (save last settings)

But then people asked to use it as option (set once and reuse)
As you see, two uses for the same function....

The %temp% was a good choose for temp saving, but perhpas not if you
use it as presets.

Ah, I see... Didn't realize such "evolution" took place. That, of course, explains everything. So I created my own `defaults.vnc' file stored in my home directory and pass it with `/config <path>\defaults.vnc' command line arguments. This `defaults.vnc' file has the `host' entry in the `connection' section set to empty value, so UltraVNC doesn't connect to any particular host but shows it's usual dialog instead. And of course with the default config loaded from my `defaults.vnc' file. :-) I guess this is the most proper implementation of the "second function" (as you described them) without relying on a "temporary" file.

And I'm refraining from using shared temporary directory for multiple users. This apparently won't do any good in Windows. The default out-of-box Micro$oft's setup uses `%USERPROFILE%\Local Settings\Temp' which is a separate directory for each user and it can be expected many application will count with this, so using shared directory for multiple users is just asking for trouble. Contrary to Unix environments, where applications are written completely different way and can happily share `/tmp'. Please don't take this personally, I'm not trying to say anything against UltraVNC. This is, unfortunately, the way how *many* applications behave according to strange Micro$oft's default setup. (Well, I have the feeling there were no per-user temporary directory settings in Windows NT 4.0. How could that work?)

And yes, UltraVNC is great program. I have quite heavily tested both UltraVNC and RealVNC (both server and client (ie. viewer)) and UltraVNC beats RealVNC in both cases. The ability to quickly enable and disable sending of special keys to the remote host is very useful feature. Plus the enhanced configurability of the server. And more. I could only hope for the ability to configure some of the hotkeys, but the default setup is quite good. So, keep up the good work and thanks for UltraVNC! And for your answer, too. :-D