Mouse jumps back to primary computer after 1 to 2 seconds

Multiplicity has connected two Windows 7 embedded computers for ~5 years and worked perfectly for all that time, but yesterday it suddenly started behaving oddly.  When trying to move the mouse to the secondary computer it jumps back to the primary computer after about 1 to 2 seconds.

The primary computer has two ELO touchscreen monitors working in MIRROR mode.  The secondary computer has just one ELO touchscreen monitor.  Nothing has changed in the hardware setup at all.

I can connect perfectly to the secondary computer in KVM mode (complete secondary screen appears and is usable on the primary computer screen) but trying to move the mouse to the secondary computer is not possible even though the connection is established.

I did notice that there appears to have been an auto-update to the Multiplicity version on the primary computer because when checking the versions it was different to the version on the secondary computer.  Primary today is V3.57 00103.kvm.  The secondary computer was V3.43 00082.  How can I tell when this updated happened thus whether it might be the cause of the problem?  Anyhow, I updated the secondary to match the primary and restarted it.  Secondary now reports V3.57 00103 but the problem persists.

It is almost as if something is forcing the mouse back to the primary computer.  I did disconnect both touchscreens on the primary computer but that also did not change the symptoms.

Have you seen a problem like this before?

 

6,204 views 3 replies
Reply #1 Top

Hello,

I have forwarded your report to the Stardock support team for their review and recommendations.

Please keep an eye on this thread for any updates.

We really do appreciate your feedback, thanks.

Reply #2 Top

Hello,

Sorry to hear you are having trouble.

Try the purge, reinstall on each PC, please:

https://forums.stardock.com/486104/multiplicity-support-faq#reinstalling

Sean Drohan
Stardock Product Lifecycle Manager

Reply #3 Top

It appears that the auto-update that happened on the primary computer broke something.  To fix the problem I did a complete uninstall (as recommended by Sean Drohan) on the primary computer then reinstalled the original version of Multiplicity (V3.43) that had been in use for several years prior to the auto-update.  That made everything functional again.  I probably could have installed the latest version after the full uninstall but I decided it best to go with the known version that had worked for a  long time.

Lesson here is to not allow auto-updates!!!!!!!!!!!!!  Stick with what you know works unless there is a compelling reason to jump to the latest version.