Re: [rdesktop-devel] Scancodes for Numlock

[Anes L. <ane...@we...>]

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