Page 1 of 1

Keyboard and trackpoint inoperative when Windows loads

Posted: Fri Jul 12, 2013 3:19 pm
by Nigellus
Since my desktop stopped working, I spend a lot of time with my T-60 plugged into my docking station. Sometimes when I boot to windows, though the keyboard works on the password-prompt, it won't work once Windows loads, and I have to reboot.

Well, I've started to notice that it isn't just the external keyboard plugged into the docking station. When I am working in ordinary laptop mode, the same thing happens. My T-60's keyboard and trackpoint work fine on the log-in screen, but once Windows XP loads, they don't work at all. Actually, this is worse than when it's in the docking station because the mouse plugged into the docking station still works.

Any ideas what's going on?

Re: Keyboard and trackpoint inoperative when Windows loads

Posted: Fri Jul 12, 2013 3:41 pm
by Neil
I had a ThinkPad once that did sort of like that. Mine had a fault in the touchpad, such that whenever it was connected to the motherboard, the keyboard would not work. When I physically disconnected the touchpad the keyboard and trackpoint worked fine.

You've got nothing to loose by trying it. It might not work for you, but then again it just might.

Re: Keyboard and trackpoint inoperative when Windows loads

Posted: Fri Jul 12, 2013 4:10 pm
by Nigellus
I tend to think it's software related because it always works in safe mode.

Re: Keyboard and trackpoint inoperative when Windows loads

Posted: Fri Jul 12, 2013 4:26 pm
by Neil
Yeah...probably so. Might try removing the drivers for the trackpoint /keyboard and ultranav...reboot and let Windows reinstall them. Might work...stranger things have happened.

Re: Keyboard and trackpoint inoperative when Windows loads

Posted: Tue Jul 16, 2013 5:42 pm
by TuuS
I've seen issues where the windows drivers behave this way, but installing the lenovo drivers always fixed it. It was only with WinXP and I've only seen it happen on laptops build before 2008, identical models built in 2008 never showed these symptioms so perhaps there was a firmware change in some of the hardware.