Re: PB 4.2 error in keypad [Del.] key maping in RDP session by sergeir
sergeir
Mon Nov 22 02:34:19 CST 2004
Anyone from Microsoft, please help !!!
This is just another reason why we can't migrate from CE
4.1 to CE 4.2. This problem is critical to our customers
and they will not buy any platform from us, which has this
error, thus we can't sell any developed platform with CE
4.2 and stay on CE 4.1.
I don't know what is the new model and what was the old
model, but we do know that CE 4.1 does not have this error
in numeric keypad in terminal session.
Sincerely
Sergei
>-----Original Message-----
>The layout manager provides a mechanism to remap keys to
various locales
>without having to rebuild the keyboard driver. If you're
using the PS/2
>drivers that come with PB, those already use the new
model. I was thinking
>of custom keyboard drivers, where the driver is included
as part of the BSP
>and might have been ported from earlier versions of the
OS. As I said, if
>you weren't using the new model, you'd probably have more
problems than just
>this.
>
>I don't know where this problem is coming from, I haven't
done much with
>varying locales especially relating to RDP.
>
>--
>Dean Ramsier - eMVP
>
>
>"Sergeir" <anonymous@discussions.microsoft.com> wrote in
message
>news:70bf01c4cd3a$c216ae00$a601280a@phx.gbl...
>> Hi Dean,
>>
>> thank you very much for your reply.
>> What is the new layout manager model - I have no idea on
>> this. Is it coming by default with PB 4.2 ? I am only
>> including the following in my PB 4.2 test platform :
>>
>> /-><BSP name> Based x86->Device Drivers->Input Devices-
>> >8042 Keyboard/Mouse English
>> /->Windows Thin Client->International->National Language
>> Support
>> /->Windows Thin Client->Core OS Services->USB Host
Support-
>> >USB Human Input Device
>>
>> and I have not chnaged any C++ code in the area, which
is
>> related to keyboard. But we do have our own shell, etc.
>>
>> We do not use USB keyboard for this test, only PS/2
>> keyboard with standard 104 keys. Even though USB HID is
>> added - for USB mouse.
>>
>> What are these changes you are mentioning which can fix
>> the numeric keypad keys problem ? So this problem is
not a
>> new version RDP problem ?
>>
>> I have read PB Help but cannot find anything useful.
>>
>> Thanks again
>>
>> Sergei
>>
>> >-----Original Message-----
>> >Are you using the new layout manager model? If not,
>> there are some changes
>> >that have to be made to the keyboard driver to get some
>> of these keys to
>> >work properly. You may have already made them, because
>> if not you'd
>> >probably have more problems than you're seeing now.
I've
>> run into similar
>> >issues with USB keyboards, although the problems were
>> with general numeric
>> >key functionality and not just locale issues. I
haven't
>> done anything with
>> >PS2 recently.
>> >--
>> >Dean Ramsier - eMVP
>> >
>> >
>> >"Sergeir" <anonymous@discussions.microsoft.com> wrote
in
>> message
>> >news:751301c4cc79$422051e0$a301280a@phx.gbl...
>> >> Dear experts,
>> >>
>> >> We have found a strange behavior of some Windows CE
4.2
>> >> module, which is responsible for numeric keypad
support.
>> >> Maybe I am wrong and this is a problem originated in
RDP
>> >> of CE 4.2 ?
>> >>
>> >> Two test scenarios are compared.
>> >>
>> >> 1. Platform Builder 4.1 - works properly
>> >> 2. Platform Builder 4.2 - error in [Del] key handling
>> >>
>> >> Test scenario description :
>> >>
>> >> Build a simple enterprise web pad or a thin client
>> >> platform. We have used x86 processor on a simple
device
>> >> with a PS/2 standard keyboard connected to it, a CEPC
>> >> would work. Include English locale only in your
platform
>> >> Display Based Devices->International->Locale
Services-
>> >> >English(US) National Language Support Only.
>> >>
>> >> Build a platform and deploy it. When it is up and
ready,
>> >> connect to a terminal server using included RDP
feature.
>> >> You can use either Windows 2000 Server or Windows
2003
>> >> Server, the only requirement is that either server
>> should
>> >> have additional national language installed on it,
with
>> a
>> >> language selection indicator on a task bar. We have
>> tested
>> >> Russian.
>> >>
>> >> Then run some simple application, which can handle
>> >> keystrokes, for example a notepad.
>> >> Select Russian language in a task bar. Then press
>> NumLock
>> >> so it is toggled and it's led is lit. Now press [/]
key
>> on
>> >> a numeric keypad, and / appears well, then press the
>> >> [Ins] key on a numeric keypad, and 0 appears too.
Then
>> >> press [Del] key on a numeric keypad, but . will not
>> >> appear, instead a corresponding Russian symbol
appears
>> >> under Windows CE 4.2, but . appears properly under CE
>> 4.1 !
>> >>
>> >> Why it is so !? If, say under Windows CE 4.2
Microsoft
>> has
>> >> decided to map all numeric keypad keys to appropriate
>> >> national language keys, then it should be
>> >>
>> >> NumLock ON and [/] US -> respective national symbol
>> for /
>> >> NumLock ON and [Ins] US- > respective national symbol
>> for 0
>> >> NumLock ON and [Del] US -> respective national symbol
>> for .
>> >>
>> >> OR (like in CE 4.1 when national language in RDP
session
>> >> does not matter)
>> >>
>> >> NumLock ON and [/] is always /
>> >> NumLock ON and [Ins] is always 0
>> >> NumLock ON and [Del] is always .
>> >>
>> >> But not the mixture of the two !
>> >>
>> >> Please note : we do not include any locale into the
>> >> platform in either case. This is done intentionally
to
>> >> isolate the problem occurring in CE 4.2.
>> >>
>> >> Did anybody else encounter such problem ? Doesn't
have
>> to
>> >> be Russian language, maybe any other national
language
>> in
>> >> RDP session is not working properly with numeric
keypad
>> >> keys ?
>> >>
>> >> Can someone provide a clue whether this should be
>> searched
>> >> in RDP area or in CE numeric keypad driver area (if
>> that
>> >> is separate from a keyboard driver) ?
>> >>
>> >> Thanks
>> >>
>> >> Sergei
>> >>
>> >
>> >
>> >.
>> >
>
>
>.
>