This is a known issue in RDC 2.0b, as was pointed out to me it is even
mentioned in the ReadMe.
This does not negate the fact that it is utterly appalling that something as
simple as keyboard mapping is still wrong in programs like RDC after
_YEARS_.
Not only does RDC 2.0b have this problem (as did RDC 1.0.x), but so did
VirtualPC, so does Netopia's Timbuktu (I reported it to them EIGHT YEARS
AGO, and despite multiple upgrades to both the Mac and Windows versions it
is still not fixed), so did Parallels (not sure if the more recent versions
still suffer this), and so on.
Boot Camp originally suffered this, but Apple FIXED it.
VNC has never suffered this, and this is because unlike all the rest, it was
originally written in Cambridge England, and not by Americans who it appears
fail to recognise that there is life outside the USA (intelligent life as
well since we are Mac users after all).
Note: because Apple Remote Desktop is based on VNC, when it controls a PC it
also works properly.
Unfortunately, while Microsoft are aware of this problem, nothing gives me
any confidence that they will fix it, after all they have already had years
to do so and it does not affect Americans so why should they give a s**t
about the rest of the world, I mean we only pay MORE for Windows etc. than
Americans so obviously we are totally unimportant.
I also note that Microsoft are definitely not going to address the aspects
of RDC that break established Mac behaviour for programs, for example when
you close the last/only session in RDC 2.0b it quits the program (that might
be the Windows way, it is not the Mac way).
On 10/9/07 11:08, in article
1189418904.313187.222910.DeleteThis@r34g2000hsd.googlegroups.com,
"john.batty@gmail.com" <john.batty.DeleteThis@gmail.com> wrote:
> I have a UK keyboard and am connecting to Windows Terminal Server
> running UK locale.
> This is therefore completely standard for anyone running in the UK.
>
> Some of the keyboard keys do not map correctly - in particular there
> appears to be no way to enter a backslash. Which is incredibly
> annoying when you want to type a file path.
>
> I presume this is also a problem for anyone else with non-US
> keyboards.
>
> There are posts going back several years complaining about this, and I
> presumed it would be fixed in the next release. However, after
> waiting 2 years for 2.0 beta I find that it has not been fixed.
>
> This really makes it a pain to use Remote Desktop outside the US.
> Please please address this problem - it can't be hard to fix!
> >> Stay informed about: Key mappings on non-US keyboards - backslash in particular