butterscotch Posted April 20, 2007 Share Posted April 20, 2007 windows xp. my problem is with the numpad on my keyboard. it stopped working after my brother loaded linux on the same hard drive and removed it. whenever i press the numlock key it gives a beep. i have tried a known good keyboard. same problem. i just cant type numbers with the numpad section of the keyboard. i have tried uninstalling and reinstalling the keyboard driver but no go. now i bought a brand new keyboard which i tested for numpad functionality especially in the shop before bringing it home but when i plugged it into my system the same problem persists. please help me somebody, anybody... i am going crazy! PLEEEEEEEEEEEEEEEEZ HELP ME Hi everybody... thank you sooooooooo much especially metrogirl ... you know what stupid me i must have someday turned sticky keys on ... ticked the option under mouse tab 'use mouse keys' in accessibility options. once i unchecked that everything just came back to normal.... i feel like such a dork ... newayz loooooove you all Link to comment Share on other sites More sharing options...
LinkFreak Posted April 21, 2007 Share Posted April 21, 2007 Heres the easy way... Back up everything and reinstall.. Or it could be something in your BIOS. Link to comment Share on other sites More sharing options...
Ictinike Posted April 22, 2007 Share Posted April 22, 2007 Try your Bios, then phone whomever you purchased the computer from. (Dell etc) Link to comment Share on other sites More sharing options...
Metrogirl Posted April 22, 2007 Share Posted April 22, 2007 A good way to check if Windows is seeing the right keycodes is to install KEYTWEAK which allows you to see what codes a key sends (if it's sending anything at all) and also to remap the keyboard. I always install it in a new system so I can turn off those pesky Windows and Menu keys near the spacebar which p*** me off because I catch them when I'm typing fast. Keytweak didn't fix Butterscotch's problem - we discussed this in a PM - but it showed that his keyboard and BIOS settings were working properly because the right keycodes were getting sent. Which I think means that something in XP is stealing the input before the applications can see it. It could be something which gets loaded at startup, or a virus or maybe a game controller. Link to comment Share on other sites More sharing options...
Metrogirl Posted April 27, 2007 Share Posted April 27, 2007 Hey, Butterscotch - thanks the the PMs and it's good to hear that the problem is fixed. Link to comment Share on other sites More sharing options...
Recommended Posts