input translation errors

[BSigworth]

I have 4 POS (point of sale) computers to our 2003 sp2 TS server. Each has
a (USB) Magtek Mini Wedge MSR reader connected to it for credit card
processing. The MSR readers emulate a keyboard as far as their input.
When I scan a credit card with Notepad open I can read the input on screen.
The problem is that in the Terminal Services environment I get translation
errors when reading a credit card. Examples are the case of some characters
are changed (upper case instead of lower case or vice versa) also ? and /
switch along with ^ and 6 (these mark beginning and end of data strings).

Thanks,
Bruce

 

[Vera Noest [MVP]]

I've read a couple of similar posts here the last year. This is
what I've saved from previous answers (haven't tested any of them
myself):

* The problem is a SHIFT problem. There may be a problem with a
"stuck" shift key. Try tapping the left and right ones a few times.

* some fixes in the Vista version of the client may help.

* it is a bug in TS, this only appears when the connection is in
full screen. When it is in smaller resolutions it works perfectly.

* Problem solved. When select "on the local computer" option in
RDP->options->Local resources->Keyboard everything works fine in
every mode.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?QlNpZ3dvcnRo?= <BSigworth@discussions.microsoft.com>
wrote on 08 aug 2007 in
microsoft.public.windows.terminal_services:

> I have 4 POS (point of sale) computers to our 2003 sp2 TS
> server. Each has a (USB) Magtek Mini Wedge MSR reader connected
> to it for credit card processing. The MSR readers emulate a
> keyboard as far as their input. When I scan a credit card with
> Notepad open I can read the input on screen. The problem is
> that in the Terminal Services environment I get translation
> errors when reading a credit card. Examples are the case of
> some characters are changed (upper case instead of lower case or
> vice versa) also ? and / switch along with ^ and 6 (these mark
> beginning and end of data strings).
>
> Thanks,
> Bruce

 

[BSigworth]

In my case the last two items proved to be true...

* it is a bug in TS, this only appears when the connection is in
full screen. When it is in smaller resolutions it works perfectly.

* Problem solved. When select "on the local computer" option in
RDP->options->Local resources->Keyboard everything works fine in
every mode.

Changing the settings in RDP fixed the problem.

Thanks,
Bruce


"Vera Noest [MVP]" wrote:

> I've read a couple of similar posts here the last year. This is
> what I've saved from previous answers (haven't tested any of them
> myself):
>
> * The problem is a SHIFT problem. There may be a problem with a
> "stuck" shift key. Try tapping the left and right ones a few times.
>
> * some fixes in the Vista version of the client may help.
>
> * it is a bug in TS, this only appears when the connection is in
> full screen. When it is in smaller resolutions it works perfectly.
>
> * Problem solved. When select "on the local computer" option in
> RDP->options->Local resources->Keyboard everything works fine in
> every mode.
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
> =?Utf-8?B?QlNpZ3dvcnRo?= <BSigworth@discussions.microsoft.com>
> wrote on 08 aug 2007 in
> microsoft.public.windows.terminal_services:
>
> > I have 4 POS (point of sale) computers to our 2003 sp2 TS
> > server. Each has a (USB) Magtek Mini Wedge MSR reader connected
> > to it for credit card processing. The MSR readers emulate a
> > keyboard as far as their input. When I scan a credit card with
> > Notepad open I can read the input on screen. The problem is
> > that in the Terminal Services environment I get translation
> > errors when reading a credit card. Examples are the case of
> > some characters are changed (upper case instead of lower case or
> > vice versa) also ? and / switch along with ^ and 6 (these mark
> > beginning and end of data strings).
> >
> > Thanks,
> > Bruce
>

 

[Vera Noest [MVP]]

Great, I'm glad that your problem is solved, and thanks for
reporting the solution back here!

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?QlNpZ3dvcnRo?= <BSigworth@discussions.microsoft.com>
wrote on 08 aug 2007 in
microsoft.public.windows.terminal_services:

> In my case the last two items proved to be true...
>
> * it is a bug in TS, this only appears when the connection is in
> full screen. When it is in smaller resolutions it works
> perfectly.
>
> * Problem solved. When select "on the local computer" option in
> RDP->options->Local resources->Keyboard everything works fine
> in every mode.
>
> Changing the settings in RDP fixed the problem.
>
> Thanks,
> Bruce
>
>
> "Vera Noest [MVP]" wrote:
>
>> I've read a couple of similar posts here the last year. This is
>> what I've saved from previous answers (haven't tested any of
>> them myself):
>>
>> * The problem is a SHIFT problem. There may be a problem with a
>> "stuck" shift key. Try tapping the left and right ones a few
>> times.
>>
>> * some fixes in the Vista version of the client may help.
>>
>> * it is a bug in TS, this only appears when the connection is
>> in full screen. When it is in smaller resolutions it works
>> perfectly.
>>
>> * Problem solved. When select "on the local computer" option in
>> RDP->options->Local resources->Keyboard everything works fine
>> in every mode.
>> _________________________________________________________
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> TS troubleshooting: http://ts.veranoest.net
>> ___ please respond in newsgroup, NOT by private email ___
>>
>> =?Utf-8?B?QlNpZ3dvcnRo?= <BSigworth@discussions.microsoft.com>
>> wrote on 08 aug 2007 in
>> microsoft.public.windows.terminal_services:
>>
>> > I have 4 POS (point of sale) computers to our 2003 sp2 TS
>> > server. Each has a (USB) Magtek Mini Wedge MSR reader
>> > connected to it for credit card processing. The MSR readers
>> > emulate a keyboard as far as their input. When I scan a
>> > credit card with Notepad open I can read the input on screen.
>> > The problem is that in the Terminal Services environment I
>> > get translation errors when reading a credit card. Examples
>> > are the case of some characters are changed (upper case
>> > instead of lower case or vice versa) also ? and / switch
>> > along with ^ and 6 (these mark beginning and end of data
>> > strings).
>> >
>> > Thanks,
>> > Bruce