Re: Keyboard problem Win8 ctrl caps lock etc SOLVED

[Bill Troop billtroop@xxxxxxxx]

Hi Kari, I will try those programs. I don't see how they can be
that different in their effects, given that they are only (so I
understand) performing simple, well-understood registry alterations. But
this last experience has shaken me! My best guess is that there was some
interaction with the touchpad's palm-rejection algorithms. One of these
days when there is nothing better to do, I will try to replicate the
'bad' situation.


Kbdedit looks particularly interesting, with its (apparently unique)
complex remapping of 'dead' keys. This could be a solution, on my laptop,
for the lack of any numeric keypad functionality, for the times
when I am not using the IBM M keyboard kindly given to me by Paul.


At 07/02/2014 07:54, you wrote:

> In fact there may be several
> solutions. Keyboard reprogramming is a complex matter. However, there are
> plenty of capable programs out there. You could check some of the
> following:
> 1)
> http://www.klm32.com/KbdEdit.html; eudora="autourl">
> http://www.klm32.com/KbdEdit.html - a relatively easy to use Keyboard
> Editor
> 2)
> http://atnsoft.com/keyremapper/; eudora="autourl">
> http://atnsoft.com/keyremapper/ - a sophisticated Key Remapper
> 3)
> http://www.kbdedit.com/; eudora="autourl">
> http://www.kbdedit.com/ - a professional Keyboard Layout Editor
> 4) or a reprogrammable (EEPROM-based) keyboard like the Avant
>
> I am running kbdedit (number 3) on top of a reprogrammed Avant. A
> reprogrammable keyboard has the advantage of being operating system
> independent.
>
> Best regards,
>
> Kari Eveli
> LEXITEC Book Publishing (Finland)
> lexitec@xxxxxxxx
>
> *** Lexitec Online ***
> Lexitec in English:
> http://www.lexitec.fi/english.html; eudora="autourl">
> http://www.lexitec.fi/english.html
> Home page in Finnish:
> http://www.lexitec.fi/; eudora="autourl">
> http://www.lexitec.fi/
>
>
> 7.2.2014 3:05, Bill Troop wrote:
> > The moral is things aren't
> > always what they seem and yes, there is usually a solution. Something was
> > obviously very wrong. What it could be, I have no idea, but I suspect it
> > may have had something to do with the touch pad and its driver. Who
> > knows? It's gone!