Multiplicity and Virtual PC (VPC)

from Stardock Forums
Here is the problem that I have. I am runnign the last pro version. On my left (primary monitor) I am running virtual PC in full screen mode and on my Right (Slave machine) I am doing work. After some time of switching back and forth I can no longer use my mouse. The keyboard continue to work fine. I will click something and it has no effect. I then have to use the keyboard and shut down the VPC. Any body use this with VPC and have the same problem.
multiplicity
4,345 views 5 replies
Reply #1 from Stardock Forums Top

I am experiancing the same, i use Microsoft Virtual PC 2004 as my primary development platform, running on my host PC, i also have 2 more computers connected and linked either side via multplicity.


the VPC works fine for about 10 minuites, then when i move the mouse to one of the other PC's to test the application, i can no longer use the mouse in the Virtual PC on return...


this seems to be a constant problem, which i am hoping will be resolved ASAP. this is an amaizing app that is 100% more stable than Synergy. Can Someone from stardock please shed some light on this.

Reply #2 from WinCustomize Forums Top
Do you regain control in VirtualPC if you unload MP from the local machine?
Galactic Civilizations IV
Reply #3 from WinCustomize Forums Top
I've noticed similar behavior using VMWare Workstation on my secondary PC. I don't think the mouse will come back unless you reboot the primary system
Reply #4 from Stardock Forums Top
I am also having this problem (Virtual PC 2007). I am not able to regain control of the Virtual PC mouse functions after unloading Multiplicity. If I use Windows Remote Desktop to shutdown the virtual machine, then restart Virtual PC, I am usually able to regain control. Otherwise, I have to reboot the host machine.

I tried using Remote Desktop from another machine to access the host machine but was still unable to control the Virtual PC application with the mouse.

It seems as though the Win32 mouse event messages for Virtual PC are not being forwarded back to the host system after being intercepted by the Multiplicity server.
Reply #5 from Stardock Forums Top
I have a very similar problem with VPC 2007 & Multiplicity. I use VPC on the primary machine. What happens that after some random interval (e.g., 10 minutes) it becomes totally unresponsive (will not accept input, and the top level VPC menus don't work either). I usually end up having to kill the entire VPC process and start anew. I do not get this when I shut down Multiplicity first.