Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

keyboard map problem


  • Please log in to reply
2 replies to this topic

#1 Herk

Herk

  • Members
  • 1,609 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:S.E. Idaho, USA
  • Local time:04:00 PM

Posted 28 March 2005 - 11:42 PM

I'm working on a computer with a strange problem. According to the user, the motherboard threw sparks and the machine was sent back to Compaq, who replaced the motherboard. Ever since, the numpad won't work. It doesn't matter if you change keyboards - whether multimedia or simple - the numpad still won't work. If you turn off numlock, some other functions of the keys work.

I've been assuming that this is a hardware problem, but it's possible that they did something weird when re-installing the motherboard, for instance, if they didn't re-install Windows XP, perhaps something didn't get associated with something else.

The only thing I've done about it was to go into the registry to set the numlock to be turned on by default, which it now is, but when using something like Calculator, nothing happens.

Anybody got any ideas, or know how to reset the keyboard mapping to default?

BC AdBot (Login to Remove)

 


#2 KoanYorel

KoanYorel

    Bleepin' Conundrum


  • Members
  • 19,461 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:65 miles due East of the "Logic Free Zone", in Md, USA
  • Local time:04:00 PM

Posted 28 March 2005 - 11:53 PM

If the MOB threw sparks then any number of other circuit are probably fried as well.
Entire system needs to go back/be replaced.
Not worth your time to even work on...

:thumbsup:
Koan
The only easy day was yesterday.

...some do, some don't; some will, some won't (WR)

#3 Herk

Herk
  • Topic Starter

  • Members
  • 1,609 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:S.E. Idaho, USA
  • Local time:04:00 PM

Posted 29 March 2005 - 01:00 AM

If the MOB threw sparks then any number of other circuit are probably fried as well.
Entire system needs to go back/be replaced.
Not worth your time to even work on...

Well, it seems to work fine, other than this problem. I was busy cleaning malware and updating Windows and so on. It's quite usable, except for having to use the numbers at the top of the keyboard. My opinion is that if it's still broken when they got it back, they should have sent it back again. But I don't even know how long ago the problem occurred.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users