essjae

After installing Start8 on my AMD Athlon II X4 system with 8GB I was no longer able to run any combination of VMs with Hyper-V that used over 3GB. A single 4GB VM would not start until the memory was lowered down to around 3300MB. Task Manager shows more than enough available RAM, for example. 3GB VM running, TM shows 4GB+free, attempting to start a 2GB VM fails. Similarly, with nothing running but system tasks, a 4GB Vm will fail to start with the same lack of memory error.

I had MP Pro set up on separate NICs, now on my primary machine it's switched over to my main LAN NIC and won't connect to my secondary's...it's on the wrong subnet. How can I force MP to go back to the dedicated NIC?

I had the same problem...I have a much older thread until I installed the latest beta 1.20j[rc]. https://forums.stardock.com/?forumid=267&aid=161468 Now I can't get MP to select my 2nd NIC, it only attaches to the primary NIC, unless I change my 2nd nic to the primary, run the MP config, reboot, then change my other NIC back to primary. It's held for a reboot, so this may work... spoke too soon. the latest beta still doesn't fix the left-click problem (:(

Just to update, the 1.21 update of MP Pro didn't solve the problem...I still need to keep my secondary mouse handy and left-click to get my primary mouse working.

You could take a look at Synergy, it's open source and works with *nix, Win, and Mac.

I've been seeing this problem more freqeuently lately. When I move the mouse from the primary, Vista x64, to the secondary, XPSP2, the left-mouse does not work...it either does nothing or acts as a right-click. Moving back to the primary the mouse continues to function correctly. Using the mouse on the secondary and left-clicking restores proper functionality. I have added the app to the Windows firewalls on both computers. Multiplicity is on a secondary subnet with static IPs.

I've had this happen a couple times, but I've been able to use the hotkeys to get the mouse back to the primary machine.

I have VMWare Workstation and Player installed on both my primary and secondary machine and have connectivity most of the time...I think something else is causing your issue.