VMware

How does TightVNC connects to Windows VM built-in virtual display? [C++ / system]

I’m reading through the TightVNC code, trying to understand how it connects to the built-in virtual display of my VMware Windows Server VM. It calls a bunch of functions like OpenDesktop in /win-system folder and also has a file called x11region.c in /Region, which makes think it “creates” a desktop imitating an X11 server on Linux.

Anyone played around with code that connects to the built-in virtual display of a VM could point me in the right direction here? The codebase ([http://tightvnc.net/download.php](http://tightvnc.net/download.php)) is quite extensive and I am a bit lost, help appreciated.

Phil


View Reddit by philippemnoelView Source

Related Articles

3 Comments

  1. My guess would be it’s not specific to what you are calling the “built-in virtual display” it would be connecting to Console 0, which is the default user desktop. like if you rdp into a windows server, the sessions would normally be console 1 and console 2.

    console 0 is general what you would see if you where sat in front of the machine.At least it used to be years ago when I admin’ed windows boxes.

    not sure if that helps at all.

  2. VNC is a service that lives in the guest and has nothing at all to do with VMware. I’d also hazard to guess that the x11 code isn’t doing anything in Windows. Remember that VNC is cross platform and x11 is the graphical environment on every non-Windows platform that can run VNC.

Leave a Reply

Your email address will not be published. Required fields are marked *

Close