Team... I have a customer using the MK4000 in a time-clock application being driven by wavelink telnet. They are reporting that in small batches, this works fine... but if we have a large number of people clocking on or off at one time - say the start of the shift - the device slows right up to the point of almost not working. They are comparing this to a TN client running on a PC, so we are trying to eliminate the server as the cause of the bottleneck. My suspicion is that blockbuster is working TOO well, and it is capturing and sending multiple scans of the same code, causing system delays. Is there some way we can de-tune the scanner to work more slowly in this application? Can we insert a delay of 1 sec after a successful decode before the MK opens the scanner again? Any feedback would be appreciated. Thanks and regards, -JP