Well, shucks. I was hoping for a mouse I'd dealt with, or at least one that I had some specifics on.
The mouse queue parameters are set in a key located in this section of the registry:
HKLM\CurrentControlSet\Services
We're looking for a REG_DWORD value called MouseDataQueueSize. A standard PS/2 mouse uses the location HKLM\CurrentControlSet\Services\i8042prt\Parameters, and the Intellipoint mouse uses the location HKLM\CurrentControlSet\Services\msi8042prt\Parameters.
The Logitech mouse may keep its parameters folder in the same location as the standard PS/2 mouse, or it may not. Sorry, I'm not familiar with it. But, when you locate it, you can adjust the MouseDataQueueSize as follows. (If you don't see a folder name that's obviously related to your mouse, just use the search function to find the MouseDataQueueSize value.) Double-click on the MouseDataQueueSize value. It's default setting is 0x64 hex (100 decimal). The theory is to keep doubling (and rebooting) until the problem goes away.
Now for the interesting point. The MouseDataQueueSize value had to be set to decimal 16000 to get the desired result on the two Intellimouse systems I "fixed". (That's NOT a typo.) That would be a lot of reboots. I suggest trying 8000 right off the bat, then 16000. If that doesn't do the trick, then this technique probably isn't going to fix your issue. (Remember, this was all deduced under W2K, and with a different type of mouse than yours. And device drivers under W2K may have quite different characteristics from those in Win9X.)
If you are also seeing keyboard lockups when the Zip drive is polled, then under the HKLM\CurrentControlSet\Services\i8042prt\Parameters folder you can locate the values PollingIteration, PollingIterationsMaximum and ResendIterations. The first two default to 12000 decimal, and might be doubled to 24000 for effect. ResendIterations has a default value of 3 decimal (or hex, for that matter) which could be set to 8. These are the settings I used on the two systems with Intellipoint software.
If you're going to do this, do yourself a big favor. Back up your registry first. And write down the steps you try and the perceived effect on the system, to help you optimize.
To be frank, I don't hold out much hope for this to work under Win9X, though it might provide some relief. If you do try it, please let me know how it turns out. If it's worthless (or worse) I want to be sure not to suggest it to another Win9X user. If it works, it might be useful to others. (I think this issue is more common on W2K systems than on Win9X systems.)
Regards,
Jim