New
#11
Interesting observation.
The keyboard input buffer in Windows is only something like 64 characters and the combination of hooks set by applications such as your fingerprint device and layers of software do indeed slow things down remarkably.
Part of the problem is the way windows handles user commands. These are rolled into an internal messaging loop that runs through all running software on the system. When you type a letter "A" Windows has to figure out which is the foreground window, which control in the window is selected, etc. Once this is done it sends a "message" to that window to display the letter A in the appropriate control. The control itself then has to figure out what to do with the A -- store it, process it as a command, reject it, etc.-- and then draw it on the screen.
The thing to understand is that this "message" is little more than a subroutine call that *does not return* until your input is processed. Get several of these hooked into the keyboard and it does indeed slow the whole system down... noticeably.
So, add this slowness to a fast typist and you're asking for keyboard buffer overruns... Literally you're typing faster than it can process the input data and characters get dropped.
I used to have the problem on win95/386 computers all the time and there's really nothing you're going to do about it... except slowing down (and yes as a touch typist I realize how difficult that is).