I've run into this problem more than once. Because of it, I ended up getting a separate radio controler for the mouse, and another for the keyboard. With one comtroller, either the mouse would lock up and refuse to synchronize (eventually the same thing happened to the keyboard), or the channels would start switching randomly for no good reason.
Right now, to avoid problems, I'm running the 9.27 Mouseware in Win98SE, and using the default Microsoft PS/2 drivers in Win2k. That seems to do the trick. I finally gave up trying to use any Logitech software in Win2k, and the latest version for the second service pack on the website is horrible beyond belief.
Logitech is supposed to release a WinXP-compatible mouse driver around the 17th, but I doubt that I'll try it.
And yes, I'm also using the Logitech Cordless Mouseman Optical, as well as the Cordless iTouch keyboard.
Basically, in my previous situation, I think I had a bad radio controller that was having increasing difficulty running the whole desktop (mouse and keyboard) ... AND I was fighting bugs in the latest Logitech software.
The finishing touch was to change the PS/2 rate for the mouse to 200. And to avoid using the USB ports, regardless of the OS. I could get a higher refresh rate for the mouse using the PS/2 port, anyway. USB is 125Hz ... but that's shared between the two ports on the hub. And USB takes up CPU cycles that I can use for other things. Plus, an Optical Mouse is a high-powered device, which really means that it is all that a USB port can handle without errors. So if you do it this way, nothing else should go into the other port.
All my problems are now completely gone ... so this method <i>does</i> work.
There's a pretty good warranty on these devices ... so RMA-ing a bad controller should not be out-of-the-question.
Hope this helps!
Toejam31
<font color=purple>My Rig:</font color=purple> <A HREF="http://www.anandtech.com/mysystemrig.html?rigid=6847" target="_new">http://www.anandtech.com/mysystemrig.html?rigid=6847</A>