From: Anes L. <ane...@we...> - 2007-09-18 15:00:39
|
Hi One of my associates told me that under Linux + RDP 1.5 the Numlock Key isn't working properly, cause he was using some VT Emulation sofwtare insied his RDP Session. So we checked what scancode a Windows RDP Client would send when pressing Numlock. It sended c0145, while the Linux RDP 1.5 Client was sending c045. Any idea how I would get the Linux Client to send the same scancode like the Windows Client ? Thanks in advance and best regards. Anes |
From: <as...@ce...> - 2007-09-19 07:38:19
|
On Tue, 18 Sep 2007, Anes Lihovac wrote: > One of my associates told me that under Linux + RDP 1.5 the Numlock Key= =20 > isn't working properly, cause he was using some VT Emulation sofwtare=20 > insied his RDP Session. First of all, are you using the -N option?=20 > So we checked what scancode a Windows RDP Client would send when >=20 > pressing Numlock. How were you checking this? > It sended c0145, while the Linux RDP 1.5 Client was sending c045. >=20 > Any idea how I would get the Linux Client to send the same scancode like = the=20 > Windows Client ? It was a while I wrote the code, but if I remember it correctly, NumLock=20 changes are not sent with normal scancodes, but rather using the special=20 RDP_INPUT_SYNCHRONIZE flag. I would be surprised if this isn't enough.=20 0xc045 also looks strange. According to the keyboard scan code=20 specification, NumLock sends 0x45 on press and 0xc5 on release.=20 Regards,=20 --- Peter =C3=85strand=09=09ThinLinc Chief Developer Cendio AB=09=09http://www.cendio.se Wallenbergs gata 4 583 30 Link=C3=B6ping=09Phone: +46-13-21 46 00 |
From: <as...@ce...> - 2007-10-08 12:10:24
|
On Wed, 19 Sep 2007, Peter =C3=85strand wrote: > > It sended c0145, while the Linux RDP 1.5 Client was sending c045. > >=20 > > Any idea how I would get the Linux Client to send the same scancode lik= e the=20 > > Windows Client ? >=20 > It was a while I wrote the code, but if I remember it correctly, NumLock= =20 > changes are not sent with normal scancodes, but rather using the special= =20 > RDP_INPUT_SYNCHRONIZE flag. I would be surprised if this isn't enough.=20 >=20 > 0xc045 also looks strange. According to the keyboard scan code=20 > specification, NumLock sends 0x45 on press and 0xc5 on release.=20 I've tried GETKEY.EXE now and I can confirm that there's indeed a=20 difference between mstsc.exe and rdesktop. I'm not sure I fully trust=20 GETKEY.EXE, though. It displays 0x45 keypresses as PAUSE, which seems very= =20 wrong to me. Perhaps it doesn't handle the special case sequence that=20 Pause generates.=20 I've discovered another very strange thing: When using Excel 2000 or XP,=20 the numeric minus behaves just like F8, which activates the "extend=20 region" mode! This only happens with rdesktop, not with mstsc.exe. Even=20 more strange is that GETKEY.EXE does not display any differences between=20 these clients.=20 Perhaps there's some "new" way of generating keyboard input in RDP that we= =20 are not aware about. Or, this might simply be a Excel bug. The scancode=20 for NUM SUB is 0x4a, while the scancode for F8 is 0x42. The bitpatterns=20 are 1001010 versus 1000010.=20 Regards,=20 --- Peter =C3=85strand=09=09ThinLinc Chief Developer Cendio AB=09=09http://www.cendio.se Wallenbergs gata 4 583 30 Link=C3=B6ping=09Phone: +46-13-21 46 00 |
From: Anes L. <ane...@we...> - 2007-09-19 07:53:59
|
On Wednesday 19 September 2007 09:38:01 Peter =C3=85strand wrote: > On Tue, 18 Sep 2007, Anes Lihovac wrote: > > One of my associates told me that under Linux + RDP 1.5 the Numlock Key > > isn't working properly, cause he was using some VT Emulation sofwtare > > insied his RDP Session. > > First of all, are you using the -N option? Yes, without the option -N Numlock wouldn't send anything. > > > So we checked what scancode a Windows RDP Client would send when > > > pressing Numlock. > > How were you checking this? We found an old Porgramm called GetKey.exe which prints all the scancodes. If you want, I can send it to you. > > > It sended c0145, while the Linux RDP 1.5 Client was sending c045. > > > > Any idea how I would get the Linux Client to send the same scancode like > > the Windows Client ? > > It was a while I wrote the code, but if I remember it correctly, NumLock > changes are not sent with normal scancodes, but rather using the special > RDP_INPUT_SYNCHRONIZE flag. I would be surprised if this isn't enough. > > 0xc045 also looks strange. According to the keyboard scan code > specification, NumLock sends 0x45 on press and 0xc5 on release. > Well the Output of the GetKey.exe program shows me 0045 for Down and c045 f= or=20 Key Up. Thanks and best regards Anes |
From: <as...@ce...> - 2007-09-19 07:59:23
|
On Wed, 19 Sep 2007, Anes Lihovac wrote: > > > So we checked what scancode a Windows RDP Client would send when > > > > pressing Numlock. > > > > How were you checking this? >=20 > We found an old Porgramm called GetKey.exe which prints all the scancode= s. >=20 > If you want, I can send it to you. Yes, please do.=20 Regards,=20 --- Peter =C3=85strand=09=09ThinLinc Chief Developer Cendio AB=09=09http://www.cendio.se Wallenbergs gata 4 583 30 Link=C3=B6ping=09Phone: +46-13-21 46 00 |