TightVNC v2.7.1 Client and Server have CAPSlock off
1234567890
abcdefghijklmnopqrstuvwxyz[]\/.,
Client turns on capslock
1234567890
ABCDEFGHIJKLMNOPQRSTUVWXYZ[]\/.,
Client turns off capslock, Server turns capslock on
1234567890
abcdefghijklmnopqrstuvwxyz[]\/.,
client turns capslock back on (server side just broke client side shift function)
1234567890
ABCDEFGHIJKLMNOPQRSTUVWXYZ[]\/.,
CLIENT SIDE AND SERVER SIDE TURN CAPSLOCK OFF
!@#$%^&*()
ABCDEFGHIJKLMNOPQRSTUVWXYZ{}|?><
The biggest issue I have with this is I can't really use \ anymore, it turns into | instead, but none the less this is should be re-create-able by hitting capslock on the client and serverside, I was able to do it on a few different machines.
Thanks!
I should probably add this is running the 64bit version on Windows 7 64bit Professional just in case it matters =)
Ok so I narrowed this down, I actually misunderstood the real problem at first, so let me explain a fast way to reproduce this 100%.
Server has capslock off, and client side has capslock off I connect, open notepad.
I type c:\
this shows up c:\
I type C:\ [Hold shift] C: [Release shift] \
this shows up C:\
I hit capslock on the server side
I type C:\ [Hold shift] C: [Release shift] \
this shows up c:| <-- yes the c is lowercase
I hit capslock on the server side again to turn it off
I type c:\ c [Hold shift] : [Release shift] \
this shows up C:|
It seems capslock is making something function improperly with shift
If change capslock on the client side, but leave the server side alone, I'm able to re-create the issue as well, with the same steps above
It also seems to fix if you close the application you are working in and re-open it, notepad in my case. However even if you close it and re-open it, you can still re-create the problem. Just adding more info to help pinpoint the real problem.
Last edit: Psych 2014-07-21
I'm having the same issue on Win7 Pro 64bit with version 2.7.10 64bit
Me too Win7 Pro 64bit with version 2.7.10 64bit
Any updates on this? Seems other people are having similar issues too. My current work around is just Cut and Paste anything Case Sensitive, or that has characters in it requiring the use of the SHIFT key.