Input for other applications works fine [so windows mobile gives or can give the correct value], thus I assume that Run.GPs makes it own translation. Disabling this internal mapping or an option to change this mapping used by Run.GPS should in principle solve the problem.
The problem is that this device has a very special keyboard with two letters per hardware key. Regarding key input, we can take only what we get from Windows Mobile. As it seems, this mapping of hardware keys works only with the Windows internal keyboard so far.
We don't have this device here yet, but when we get hold of it, we will check what can be done.
So far, please use the numerical keys to select the letter you want.
Sofar I see one bug, being that routes are not shown [based on the arrow pointing to the start of a route I assume the route is loaded correctly] Tracks are loaded and shown correctly. Instant trails are also shown.
Everything works fine exept the keyboard. The Voice Messenger has a querty keyboard layout and the hardware keys setup is completly different. Consequently it a terrible job to enter any text. If you disably the hardware key option nothing works anymore and you have to manual [outside the programme] configure the settings file in order to getting the programme working again. Selecting the alphanummeric option casus the keyboard to use only the nummeric keys what is exactly the opposite of what I would expect of such option.