Update on Cascading Windows VM

Well I noted that this problem can depend to the fact that in Windows TightVNC Server runs with desktop sharing and this can provoke problems like windows cascading. (The viewer from VM see my Win 10 desktop with the VM opened that see my desktop with the VM opened.. and then til the infinite)


Instead on Linux, when I connect from Win 10, the server creates my own space and not share the actual desktop so no problems at all.


I ask if anyone of you knows a way to run the TightVNC Server for Windows in exact the same way it runs on Linux (I don't know where a configuration file is located in Windows)  so that what I see in my viewer is not the shared actual desktop, but a different one avoiding so cascading problems.


Bye all

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

___________________________________________________________
TightVNC mailing list, [email protected]
To change your subscription or to UNSUBSCRIBE, please visit
https://lists.sourceforge.net/lists/listinfo/vnc-tight-list