I now have your exe on my Inspiron 1521 which has given me double rr since new.  Talking to Dell gave no solutions.  Your exe seems to have solved the problem - hurray!!! Thank you!!!  One small thing; the backspace is now slow.  Can that key be rmoved from a key list?

Thanks again!!!

Hey, I'm delighted to know that this little utility has helped someone besides just myself!  (I was starting to wonder if everybody's double-keystrikes had somehow magically all disappeared!)

Before firing off suggestions, I should ask... by "slow", do you mean that the auto-repeat on the Backspace is slow?  I ask this because that's the usual way people use the Backspace key, me included.  (For the uninitiated reader, the "auto-repeat" is what happens when you hold the key down.  It fires-off the key like a machine gun, saving you from having to strike the key over and over.)  If this is the case, then please read through my top post where I talk about adjusting the auto-repeat rate down (around the third paragraph from the bottom).  This is important, because auto-repeat affects all keys, not just Backspace.  (Think how often you auto-repeat the Space bar, or dashes, or the cursor/arrow keys!)

Otherwise, you have a couple of options.  You could shorten the gating time to less than 40 by modifying the shortcut like I describe in the last two paragraphs of my top post.  Finally, you can modify the script (AHK) file to remove the Backspace (or other special keys).  If you really need it, I can tell you which lines to remove.  But you will want to install AHK so that you can run the modified script.  (I hope you understand... I'd rather not get into the business of creating custom scripts... that could turn into a full-time activity!!)

Hope that helps!

Haha, thanks for the kudos.  The real fix for this problem would be at the driver/controller level, to tweak the debounce routine and nix the bounces at the source. Doing that would side-step the side effect of having a hard ceiling on the auto-repeat rate. Fortunately, for me at least, the bounces are all sub-50 msec so that the auto-repeat rate ceiling is not too low for me. (Yup, I had to up my gate time to 50 to squelch some rougue bouncers).

Typing in Caps... Did you mean the cAPSLOCK key? If so, then my apologies, I have that key permanently remapped to LeftShift!  I have no use for that key (actually, I have nothing but utter disdain for that key), and hence I did not test it.  If you absolutely must have it, there probably is a way to make it work by editing the script.  FWIW, I DO GET ALL CAPS WITH THE SCRIPT RUNNING ON MY INSPIRON 1470 BY HOLDING DOWN EITHER LSHIFT OR RSHIFT (OR OF COURSE, CAPSLOCK) AS I TYPE.  It works for me in Notepad, Windows Explorer, OpenOffice, and web browsers like this forum page (obviously).

On the subject of cAPSLOCK, for any of you out there are interested in relegating that vile vestigial hang-over from the typewriter age to be a nice, kind LShift key, you can do it by un-commenting line 24 of the current version of the script KeybounceFilter.ahk:

Capslock::LShift 

i.e. remove the semicolon (;) at the start of the line.  That's the AutoHotkey language for creating a hotkey-map.  You can also use the Keymaps that are built into windows, but since you're running the script anyway, there's not really much overhead involved. And this way, you don't need to edit the Registry.

Sorry to see you have had such a rough time with this, aleki.  I must say that this experience has tried my patience as well.  Dell did what they could, but in the end, the problem was not fixed.  So, I am happy to provide this option to those who are stuck waiting for when (or if) the driver or controller can be corrected.

I am mystified why your Shift function is not working with this script.  However, now that I am clearer on what it is, let me walk you through the process of modifying the AHK script.  First, download the AHK script (not the EXE).  Open it in Notepad (or if you are a developer, your favorite code editor).  Now go to line 47, which looks like this:

Hotkey, +%k_char%, k_KeyPress

Now comment this line out by adding a semicolon.  It should then look like this:

; Hotkey, +%k_char%, k_KeyPress

This is the line that captures all shifted keys for filtering.  By "removing" this line from the script, it will no longer filter shifted keys.  Let's see if this at least brings them back for you, even though they will not be filtered.  Save the modified script, say, as something like  "KeybounceFilter_NoShift.AHK".  Then go to the Download page of the AutoHotkey site and download and install the latest build of the AHK Installer.  Once installed (and maybe after a Restart), you will be able to run the script that you just modified directly in its AHK form (just double-click the script).  Also, make sure the old version of the script isn't still running when you are running the new one.  If it works, just make a shortcut to the new one like you would have done for the old one, in the Startup folder.

I've tried installing your script & it seems to be doing a great job of eliminating the problem of duplicate letters appearing. Since installing AHK though, various other common key combinations seem to have stopped working, such as alt+tab & windowskey+e (to open explorer). Can you confirm whether this is a side effect of the script, or am I doing something wrong?

Many thanks for your efforts to solve this problem.

Great.

Thanks for such a quick response.

I'm trying the updated version of the script now & it seems to be working ok so far. Will let you know if I come across any other issues.

Script updated again today. Corrected side-effect where "+" and "^" were not coming through the filter.

Script has been updated to correct improper trapping of the "}" key.

Thanks for kkeeping this utility updated kingdoseeker. I am still having issues even in my brand new replacement.

No problem aleki... It's good to know that the utility is helping.

Actually, another Dell user pointed out the bug to me. I fixed it right away because I need that key too! (I was surprised that I hadn't noticed it before.) So, I'm in there with all of you, at least until Dell can devote a little time to tweaking the debounce portion of their keyboard driver. As much as I like helping out, it would be better if their driver development team could fix the problem at the source.

Hi Oliver,

I also tried that FilterKeys approach, but I was disappointed that the minimum filtering time offered by Windows was 0.5 seconds (500 milliseconds).  That was way too slow for my typing... I couldn't wait that long to type words with double letters, like "school", which would come out as "schol". It became as much a problem as the original problem. My utility should allow you to set the filtering time down to well below 50 milliseconds, which will still allow for pretty decent typing speed, as long as your keyboard bounce is not too severe.

On that topic... I have noticed recently that the bouncing on my Dell Inspiron 1470 keyboard has gotten worse. I had to up the filtering time to 70 msec to keep the output clean. Oh well, at least I can still type with the thing!

Hi,

thanks for providing a solution to this issue. While searching for more information, I came across a Microsoft tutorial dealing with duplicate characters in the Ease of Access Center: http://www.microsoft.com/enable/training/windowsvista/bouncekeys.aspx

On my e6410, this seemed to reduce the problem pretty similarly to the KeybounceFilter, although from time to time the problem still occurs.

Oliver.

I just received my system two weeks ago, and I have the exact same problem.  I've read threads going back to early 2009 with reports of this problem.  I'm running in circles with Dell support.  I may try the scripts provided above (thanks to the author for posting it), but as mentioned - this really doesn't feel like a permanent fix.  This keyboard double-hit is driving me crazy.

Hi Oliver, I also tried that FilterKeys approach, but I was disappointed that the minimum filtering time offered by Windows was 0.5 seconds (500 milliseconds).  That was way too slow for my typing... I couldn't wait that long to type words with double letters, like "school", which would come out as "schol". It became as much a problem as the original problem. My utility should allow you to set the filtering time down to well below 50 milliseconds, which will still allow for pretty decent typing speed, as long as your keyboard bounce is not too severe. On that topic... I have noticed recently that the bouncing on my Dell Inspiron 1470 keyboard has gotten worse. I had to up the filtering time to 70 msec to keep the output clean. Oh well, at least I can still type with the thing!

KingdomSeeker288 - Have you seen this proposed solution to double-hits?  (found this on a 2008 thread).  I thought you might have some feedback on this approach - did you know this registry setting existed (was modifiable)?

http://forum.eeeuser.com/viewtopic.php?pid=364796#p364796