I suspect that this will be a case of won't work due to unsupported FileAssociation launch for UltraVNC. You may want to reference the following article for more information:
Having said that, it doesn't seem to do anything on my Windows Vista box and I cannot see how I would configure a permanent association that worked in the way it wants.
Vnc viewer authentication failed install#
It supposedly works with windows file association launch because it has an option (-register) that is meant to install the association mapping for Windows. In my opinion this is a fault in the design of vncviewer (UltraVNC). Unfortunately, UltraVNC requires the insertion of "-config" or "\config". vnc file (in this case) as the first command line parameter. When a windows application is associated with a filetype, and a file of that type is launched, the standard behavior is for Windows to launch the associated application using the. The problem, therefore, is the Windows File Association behavior of UltraVNC. If you save it, and then manually open it from inside UltraVNC then everything works. I have verified that UltraVNC does understand these files. Provided you click on the RUN option when downloading the file, you should get auto-connected. vnc file that is understood by most VNC clients. Unfortunately, you just can't do this from inside a browser (too much of a security risk - browser does not allow it).
Ideally, we'd directly launch your VNC client for you.
This is a tricky issue, and I think that the fault is with the design of the UltraVNC client.
0 kommentar(er)
