Keyboard typing trash on PC2, when booting /loggin in, and often in operational use.

Multiplicity v3.43 Build 00082  /  Windows 10 Creator   /  2 PC’s

PROBLEM
Keyboard typing trash on PC2, when booting / loggin in, and often in operational use.

Problem exists trying  3 different keyboards. Often occurs when booting PC 2, types trash when trying to log in. Frequently have to use on-screen keyboard during startup.

If I return to PC 1 display and make several  clicks on desktop, keyboard will  then type properly on PC2, however, inconsistantly.

Solution? Thanks for your help - IM

11,791 views 5 replies
Reply #1 Top

When you are trying to type on PC2's keyboard during log in does PC1 have mouse focus on PC2?

Does this happen if PC1 is turned off?

 

Reply #2 Top

1) I log in to PC 2 by  moving the cursor from PC1 to PC2 and typing password.

2) PC2 does not have a keyboard unless you mean the on screen keyboard.

3) I don't know what 'mouse focus' is?

4) I never use PC2 with PC1 turned off.

5) I'm using a brand new Logitech K800 keyboard this morning, and the problem persists.

Reply #3 Top

Hmmm, I think I'll give Synergy a try!

Reply #4 Top

I have the same problem with Creators update of win 10 and monitor 2. I can fix it tho by opening the Multiplicity control panel, clicking on the Gear Icon for the secondary PC, choosing Configure Computer, then clicking on the Gear icon with the green check in it to the Right of the SAVE button. It seems to reconnect properly.  happens at least 5 times a day.  It's frustrating. But at least I don't have to re-boot.

Reply #5 Top

Quoting tslynch3, reply 4

I have the same problem with Creators update of win 10 and monitor 2. I can fix it tho by opening the Multiplicity control panel, clicking on the Gear Icon for the secondary PC, choosing Configure Computer, then clicking on the Gear icon with the green check in it to the Right of the SAVE button. It seems to reconnect properly.  happens at least 5 times a day.  It's frustrating. But at least I don't have to re-boot.
End of tslynch3's quote

Please contact support