Keyboard is randomly inserting 2, 4, 6, and 8 when using the arrow keys!

[DodgerLD]

Hi,

I recently did an in-place hardware upgrade (new m/board, CPU, memory, and GFX) AMD -> Intel, using this procedure, and while it wasn't the smoothest process in the world (didn't expect it to be, as no one ever mentions this technique), it appears to have worked for the most part.

The only problem I'm having is with my keyboard (Genius SlimStar). When I use the arrow keys, usually when I hold them in and they repeat, the number 2, 4, 6, or 8 (depending on the key) is inserted at random times.

I've tried:

• Uninstalling and re-installing the driver

• Using another keyboard -- the keyboard was old and slow, but didn't seem to have the same problem

• Using the keyboard in another PC -- the problem didn't occur.

No luck unfortunately.

Any ideas?

I'm going to see if I can find a PS/2 to USB adapter, so that I can see if the problem occurs when using USB.

D.

 

[JaYp146]

Try pressing NumLock. Now try the arrow keys.

 

[DodgerLD]

Interesting, when Num Lock is *off*, the problem doesn't seem to occur.

Of course, that means I don't have a numeric keypad when it's off, but it's a step in the right direction, thanks.

D.

 

[corkyg]

Evidently you are tryimg to use the arrows in the numeric pad - they are 2.4.6.and 8 when NumLock is on. It has always been that way that I can remember.

Therefore, to leave NumLock on and avoid that, use the NORMAL arrow keys located between the numeric kepyad and the regular keyboard. They are directly below rhe insert, home, pg up, delet, end, and pg dn keys.

 

[DodgerLD]

@corkyg

The problem is with the normal arrow keys, I'm not trying to use the numeric keypad arrow keys.

D.

 

[corkyg]

If that is the case, there is a problem with your computer's ability to correctly interpret the keyboard scancodes. Something is causing the stand alone arrow keys to be "seen" as those in the numeric pad.

Is this a USB or PS/2 connected keyboard?

Try this - go into the BIOS and set the default to NUMLOCK OFF. Reboot and try your normal arrow keys. Then manually turn NUMLOCK ON for the keypad, and see if that corrupts the stand alone arrows.

 

[DodgerLD]

It's a PS/2 keyboard.

I've already tried turning num lock off in the BIOS. As soon as I turn it on manually, the problem continues.

Thanks,

D.

 

[corkyg]

OK - it could be the keyboard. You say an older slower one does not have the problem, and the Genius take the problem to another PC. Yes - try a PS/2 to USB adapter. If that doesn't work, you really should replace the keyboard.

 

[DodgerLD]

No, the problem *doesn't* occur on the other PC.

I don't have a PS/2 to USB converter, and I'm not sure it's worth buying one just to test. I think maybe that if the port was defective, the problem would be more severe.

I don't think it's the keyboard -- it would be a bit odd if it suddenly died just at the point at which I upgrade my system.

D.

 

[JeffreyLebowski]

Go to the control panel and look at Keyboard, and then Hardware and see what is there.
Make sure it shows 101/102 key.

You can also install specific keyboard drivers from here as well.

 

[mpilchfamily]

If that doesn't help try clearing the CMOS. Sometimes it fixes little PS2/USB problems.

 

[DodgerLD]

Originally posted by: JeffreyLebowski
Go to the control panel and look at Keyboard, and then Hardware and see what is there.
Make sure it shows 101/102 key.

You can also install specific keyboard drivers from here as well.

It shows 'MultiMedia Keyboard' -- which is the name of the Genius driver, IIRC.

D.

 

[DodgerLD]

Originally posted by: mpilchfamily
If that doesn't help try clearing the CMOS. Sometimes it fixes little PS2/USB problems.

No luck.

I'll probably have to re-install Windows.

 

[corkyg]

OK - before starting that huge undertaking, why not try booting with Windows out of the equation? IOW, but with a bootable CD, that carries its own OS and meyboard driver. That way you can just about weliminate Windows as the problem should the keyboard continue to malfunction.

A good boot test would use something like Acronis TrueImage Rescue CD or a similar CD by Symantec, or BART PE, etc.

If the problem persists, you can bet it is not Windows. It is either the BIOS itself or hardware. Then I would consider reflashing the BIOS.

 

[corkyg]

OK - before starting that huge undertaking, why not try booting with Windows out of the equation? IOW, but with a bootable CD, that carries its own OS and keyboard driver. That way you can just about eliminate Windows as the problem should the keyboard continue to malfunction. If it works OK, then that is a green light to reinstall Windows.

A good boot test would use something like Acronis TrueImage Rescue CD or a similar CD by Symantec, or BART PE, etc.

If the problem persists, you can bet it is not Windows. It is either the BIOS itself or hardware. Then I would consider reflashing the BIOS.

 

[DodgerLD]

Originally posted by: corkyg
OK - before starting that huge undertaking, why not try booting with Windows out of the equation? IOW, but with a bootable CD, that carries its own OS and keyboard driver. That way you can just about eliminate Windows as the problem should the keyboard continue to malfunction. If it works OK, then that is a green light to reinstall Windows.

A good boot test would use something like Acronis TrueImage Rescue CD or a similar CD by Symantec, or BART PE, etc.

If the problem persists, you can bet it is not Windows. It is either the BIOS itself or hardware. Then I would consider reflashing the BIOS.

Actually, now that I think of it, I have the same problem in Ubuntu (inside a virtual machine).

Do you think I should update the BIOS? I didn't see anything relevant in the changelog since the version I have (1306). The motherboard is an Asus P5Q.

If yes, what is the recommended method? Does Asus Update work well? Asus EZ Flash? Other?

I would post the BIOS changelog here, but the stupid POS Asus website is giving me 'Service Unavailable' (as usual).

Thoughts?

Thanks.

 

[vshah]

if ubuntu is inside a virtual machine it isn't accessing the hardware directly, it is doing so through windows. so you can't really tell from that if windows is the problem.

you could try installing generic msft drivers instead of the keyboard's drivers

 

[DodgerLD]

Originally posted by: vshah
if ubuntu is inside a virtual machine it isn't accessing the hardware directly, it is doing so through windows. so you can't really tell from that if windows is the problem.

you could try installing generic msft drivers instead of the keyboard's drivers

I just reproduced the problem in BartPE, so it looks like it's a hardware issue.

D.

 

[corkyg]

Have you tried a different keyboard, i.e., a USB one?

 

[DodgerLD]

Originally posted by: corkyg
Have you tried a different keyboard, i.e., a USB one?

I don't have a USB keyboard to test with, but I have tried two other keyboards and neither of them exhibit the same problem, while the problem keyboard works fine on two other systems.

I tried using a generic Microsoft driver and the problem still occurred -- which means the only other thing it could be is a hardware conflict.

The restart issue I'm also having (see here) seems to be getting a bit worse, so I'm more interested in getting that sorted out (I think it may be a PSU issue). After that, I guess I'll have to purchase a new keyboard.

Thanks,

D.

 

[corkyg]

Originally posted by: DodgerLD
... but I have tried two other keyboards and neither of them exhibit the same problem, while the problem keyboard works fine on two other systems.

Why not just swap keyboards with a system where they will each work AOK?

A new keyboard should solve the problem, however. Go USB.