9

I have Synergy server on a Windows 7 box, and a Mac client connected to it. Most keys work fine, except for the Shift key on the right side. The left Shift key works just fine but not the one on the right side.

Does anybody have the same issue, and what is the resolution?

studiohack
  • 13,468
  • 19
  • 88
  • 118
Haoest
  • 235
  • 2
  • 9

5 Answers5

5

I was struggling with the issue at work until my good friend Paul Udruscu pointed out that I can use KeyTweek on Windows, to remap the right shift key to the left one and alleviate the issue altogether.

tomlogic
  • 185
  • 1
  • 7
Ash
  • 151
  • 1
  • 2
3

I can confirm that downgrading a windows 7 server to 1.3.4 fixes the problem. On the Windows 7 server I tried every server up through 1.4.2 beta and none of them fixed the problem. On OSX 10.6 client I tried everything up through the 1.4.2 beta and none of the newer versions solved the problem.

Trav
  • 46
  • 2
3

This is logged in the synergy bug list here: http://synergy-foss.org/pm/issues/2842 so yes, lots of people have the same issue.

They don't seem to come closer to fixing this however.

Legolas
  • 479
  • 5
  • 12
2

Going off the workaround above by Ash, this can also be accomplished by adding a registry value to Keyboard Layout. It remaps the left shift key to the right shift key.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Keyboard Layout
New binary value
Name: Scancode Map
Value: 00 00 00 00 00 00 00 00 02 00 00 00 2a 00 36 00 00 00 00 00

Reference: modified this example; worked on Windows 7 with Synergy 1.4.8.

Indrek
  • 24,204
  • 14
  • 90
  • 93
Audrey
  • 21
  • 1
0

Are you running 1.3.6 by any chance? I just ran into the same problem between a Windows 7 server and Mac OS 10.6 client, exactly as you describe.

I installed the 1.3.7 nightly build (902 specifically) from http://synergy-foss.org/packages/ on both ends, and the problem appears to be fixed.

Edit: scratch that, the problem is back. Going to try a few more things...

Lem
  • 3
  • 1
  • I downgraded my server back to 1.3.4 and that solved the problem. Client on Mac is fine as 1.3.6. – Haoest Feb 02 '11 at 19:56
  • Yup, taking the server back to 1.3.4 fixed it. I tried going all the way forward to 1.5 nightly, but no dice. Thanks! – Lem Feb 02 '11 at 20:07