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.

Hi mat,

Glad to be of help.  It's not something that you are doing wrong.  The script was capturing those keys and filtering them, but with the side-effect of Windows hotkey functionality being lost.  (I probably got over-zealous with the filtering of these special keys.) 

I have updated the script so that it no longer captures Alt and Win.  This should be a fairly transparent change... the only forseeable side effect would be that these two keys could possibly double-strike, but this is probably innocuous and a more rare event, since the users' fingering is usually more "careful" with these keys.

Please download the script and/or exe file again (same link above) and the normal funcitonality of the Alt and Win keys should now be restored.  Blessings...

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.

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!

LitwDell, no I did not know of that registry setting for FilterKeys. That is really a terrific find. I have read through the whole thread, and based on their findings, that solution should work similarly to what my utility can do. The advantage there is that it is a feature built right in to Windows (XP onward). The downside is that it requires editing of the Registry, which can be dangerous if safety steps are not taken (e.g. backup the Registry, set a System Restore point, etc.).  Also, that method does not eliminate the side-effect of slowing down the auto-repeat rate, it will unfortunately still be limited by the filtering time. It does, however, appear to provide finer control over the settings. The method of choice appears to be given in Post #6 of that thread, with the option in a subsequent post to not bother with turning on FilterKeys at the Control Panel level.

I haven't tried it, so I can't report (yet) on how well either option works. But it does looks like a nice, built-in alternative to the KeyBounceFilter AHK utility, albeit still being a workaround to fixing the real problem at the source: lowering the bounces at the HARDWARE level (hard for Dell to do), or increasing the keybounce-gating time at the DRIVER level (not nearly as hard for Dell to do... but they would need to write and support the new driver).

Did you just do the regedit / value change / reboot, or did you also check the boxes in the FilterKeys Control Panel?

Are these the values that you used:

My Computer\HKEY_CURRENT_USER\Control Panel\Accessibility\Keyboard Response
    AutoRepeatDelay = 500
    AutoRepeatRate = 50
    BounceTime = 35  (Reduce to a lower number like 25 or 15 if your intentional double strokes are filtered.)

If so then you could indeed try lowering BounceTime. My registry has another field "DelayBeforeAcceptance" (defaults to zero) which I cannot find any documentation on. (Just curious about that one.)

This is too funny.  I couldn't remember how I left the filter keys settings.  So after you posted, I went into the "Ease of Use" center and the "use filter keys" were enabled.  When I clicked on change settings, it actually had BOTH bullets highlighted - BOTH Turn On Bounce Keys and Turn On Repeat Keys.  It's a radio button, so this is supposed to be impossible.  LOL.  It must have something to do with having registry edits.  I canceled out of that screen and left "as is", just as the link instructed to do.

Oh oh... now you've done it! Two radio buttons enabled at once?  That spells the doom of the world as we know it. You were wise not to change the control panel settings when you saw that ominous sign... you might have been pulled into the Windows Vortex.

I remember when radios actually had mechanical buttons that physically moved the dial to a station that you had preselected (usually by pulling the button out and then pushing it back in). If that mechanism wasn't complicated enough, they also had an interlock that would only let you push one button in at a time. Some radios would have some "play" in the mechanism so if you did push in two buttons at once, the dial would move to somewhere in between the two stations that you selected. So I guess it's not totally impossible to have two radio buttons pushed in at once?   ;)