Keyboard blues

First off, someone will want to move this to hardware, but I think that is wrong.

XP Pro, SP3, current updates, Comodo firewall, A^2 AV, Lenovo T60p Dual CPU - 2.1 ghz, 15.6" screen, 3 Gb computer memory, 3 cent operator memory

Months ago I had a mess with Lotus Symphony (now removed), the default office with XPPro. My keyboard immediately started going dead on boot - intermittently. A local geek agrees with me that it's a software issue.

The proof - to me - came when I had to boot to an external, USB drive back up of my system that was many months out of date and on which Symphony is still working. Never once in weeks, when I was using that system drive did the keyboard fail to come up; on the internal drive system it's a gamble at every boot.

By the way, if the keyboard does come up on the internal system it never goes dead until the next boot. Another thing that makes me sure it isn't hardware.

I'd like to update my backup, but one of several things I don't want on it is the keyboard problem. I'm open to any suggestions about how software could be the issue and what to do about it.

 

When the keyboard does not work, is there anything in Event Viewer that lists a problem.

Edit: Scratch the HID service. I was thinking of something else.

 

I found nothing related to this issue, only some errors about starting services for deleted programs (which I disabled and would rather delete if I knew how).

There was one Warning that I have no clue about:

"Windows cannot open DllName registry entry for [a whole mess of alphanumeric characters] and it will not be loaded."

I did see something in Applications that may or may not be relevant.

Event Type: Warning
Event Source: Userenv
Event Category: None
Event ID: 1517
Date: 12/1/2011
Time: 1:12:35 AM
User: NT AUTHORITY\SYSTEM
Computer: LAPTOP2
Description:
Windows saved user LAPTOP2\User registry while an application or service was still using the registry during log off. The memory used by the user's registry has not been freed. The registry will be unloaded when it is no longer in use.

This is often caused by services running as a user account, try configuring the services to run in either the LocalService or NetworkService account."

 

Here is link to Event ID: 1517.

http://www.eventid.net/display.asp?eventid=1517&eventno=1206&source=Userenv&phase=1

You can do a search in the registry for that alphanumeric string and see what application it relates to.