Why don’t I just shut up and buy a new one that works with W7? Because the button spacing on the newer trackballs is different enough from the old one to make it an issue for me. Is it really that tough to create a quick driver so we can use perfectly good albeit 12-year old mice? The entire mouse works! All electrical impulses are making it to and being interpreted by the OS. I’m looking at the basic mouse control panel with W7 (64bit) and it has a heck of a lot of functionality that is very close to Mouseware capability but for one issue – it’s evidently capable of recognizing the 3-button mouse as a 2-button mouse only. Why can’t Logitech and Microsoft get together and devise a backwards-compatible driver that allows this to work right? How difficult can this be? Do you really need to build a special driver to map “Double Click” to the middle button? That’s really a toughy? Really? I just don’t get it. ![]() I’m not looking for super-configurability here. However, you can not map the middle button to anything. It actually DOES function as the Left, Right, Scroll Wheel and trackball all work in all versions of Windows in “basic mouse” mode. ![]() Now I am no hardware driver author nor am I a computer science major but it totally baffles me that a mouse can not function when the only things it has to do are provide electrical impulses for three buttons, one scroll wheel, and one trackball. ![]() ![]() SetPoint does not work with it nor does Vista or W7, apparently. Unfortunately, the best mouse you ever made, the *old* MouseMan Wheel (T-BB13), is and has not been supported since Mouseware 9.x. I love Logitech products and have several.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |