I have been trying to fix this problem for the past few days and couldn't
find much on the WWW that could help - so I'm resorting to posting a question
online as it seems that the problem is unique.
Few days ago, I decided to clean my laptop's keyboard by disinfecting them.
I basically used an antibacterial wipe tissue, but because I was rubbing each
key one by one, it must have caused the system to go haywire.
Now, everytime I press 'm', the number '0' comes up. Likewise:
u = 4
i = 5
o = 6
I don't know what to do - is there someone who could help me?
On the other hand however, assuming that is *ALL* you were doing to cause
the problem - i.e. working on the keyboard *only* - then it is highly likely
that you've damaged your keyboard beyond economical repair and it just isn't
worth any further attempts to repair it (especially as you felt the need to
disinfect it!).
A brand new replacement keyboard can be bought for as little as a few $ from
most PC retailers (and even some supermarkets). At least there should be no
need to disinfect a brand new one!
Mart
"HY" <H...@discussions.microsoft.com> wrote in message
news:98414E3E-4783-4172...@microsoft.com...
This is typical for a laptop. Just turn off the NumLock.
At least a System Restore would have fixed it too <g>
Mart
"Ogg" <no-spam...@at.all> wrote in message
news:OT1AzZnx...@TK2MSFTNGP05.phx.gbl...
HY
The orignial poster's problem was probably that Num Lock was enabled
on his keyboard.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)
Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.
Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com
> Now, everytime I press 'm', the number '0' comes up. Likewise:
> u = 4
> i = 5
> o = 6
If so, and as you are some three months down the line from the original
post - and the replies!! - did you see the suggestion from Steve Winograd to
check that the 'Num-Lock' wasn't enabled.
Mart
"crackershell" <cracke...@discussions.microsoft.com> wrote in message
news:B8544EB0-F94D-4C61...@microsoft.com...