cyberkahuna
asked on
Number pad not working
The right hand number pad on my keyboard does not work. I am currently running WinXP professional which I upgraded from WInXP home to try to resolve this issue, without success. I don't believe it is a motherboard issue because it does not matter if I use the regular keyboard port or a usb keyboard. I have also tried the suggestions given to "nitin hfci" for the same issue on 6/26/02 regtarding the registry and tried the accepted answer regarding Win Bulletin Q315468 given by crash2100 - no luck there either. The num lock key itself appears to be working because it beeps high and low when you press it and the arrow direction keys (2=down,4=left,6=right,8=u
YarnoSG
Have you tried different hardware (maybe your keyboard is going bad, they do y'know)?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for your suggestions, but I have already tried several different keyboards (Both standard & usb) to no avail. Unfortunately the suggestion for reinstalling the driver did not solve the problem either. Is there a way I can physically delete the driver from a folder somewhere on the computer (a cab file perhaps?) I think even after uninstalling the keyboard driver and allowing it to reboot the system just reinstalls the same corrupt one. If I put in the windows cd I just get a message that says that there are no drivers better than the one windows automatically installed. Anyway thanks for the suggestions, any further ideas of things I might try?...
have you tried 'sfc /scannow' ? this will fix any corrupt system files
Start -> Run -> sfc /scannow {enter}
Start -> Run -> sfc /scannow {enter}
ASKER
Thanks Anthony E for your suggestion. I gave it a try, but still no go.
maybe in C:\WINDOWS\inf you can have a look see what you can work out from there, maybe copying new inf file from another downloaded driver or whatever see if that does anything.
If that dont work, has the numpad on the right ever worked? have you tried using the rollback driver?
If that dont work, has the numpad on the right ever worked? have you tried using the rollback driver?
Below is the location of the driver for the PS2 keyboard port on my machine. This is the port driver, not the keyboard driver. I have a generic keyboard on a PS2 connection. You never did say what you have so if you could put that down it would really help alot. If you run sfc it should have replaced the driver if it was bad but it might have overlooked it. SFC, like everything else in windows, is subject to error.
Please tell us your Keyboard mfg and model and we can do more-if it's anything but ps2, then the driver below won't apply.
Driver c:\windows\system32\driver
Please tell us your Keyboard mfg and model and we can do more-if it's anything but ps2, then the driver below won't apply.
Driver c:\windows\system32\driver
ASKER
Thanks for your suggestions but I don't think it is a port issue since I have the same problem whether I use a ps/2 connected board or a USB connected one. I also assumed (incorrectly it appears) that when I installed WindowsXP Professional over the existing WIndowsXP Home it should have corrected any driver issues as well. However it appears I am back to square one. Since I have tried several different style/ types of keyboards and upgraded the operating system (I don't want to have to do a clean install unless absolutely necessary) My gut tells me it is some kind of regestry or inf file issue, but I can't seem to find or fix it. I'm still open to suggestions :-) Thanks
ASKER
My Thanks to timothyfrier for putting me on the right path. The problem appears to have been in one of the windows applets. When I uninstalled and re-installed the mouse driver, the keyboard driver and the accessibility options, the problem has corrected itself. Many Thanks to all for your input..
ASKER
Also note for future reference that I had to be in "safe mode" to effectively undo & redo the drivers for the keyboard & mouse
Glad you got it fixed. Your fix probably ranks in top 10 of "Seemingly Unrelated Solutions" that keeps everyone using Windows babbling to themselves. Good Luck.