LarsBlog

I have a beloved Logitech USB MouseMan Wheel, that I've had forever and never want to change.  I use this with the mouse buttons reversed, in order to reduce wear and tear on my tired achey left-click finger.  During a recent upgrade to Vista x64, I discovered that Logitech's current SetPoint driver doesn't support my mouse anymore!

Under XP, I used Logitech's old MouseWare driver, which let you configure all the buttons on your mouse.  The best thing about MouseWare was that your altered button configuration carried through to any VMs or Remote Desktop sessions, which is not true of the Windows Control Panel's "Switch primary and secondary buttons" feature.  This saved me no end of arguments with colleages by ensuring I never needed to reverse mouse buttons on any remote servers!

So after attempting a few hacks to try to get SetPoint to detect ny antiquated mouse, I stumbled across X-Mouse Button Control.  This gave me all the features I miss from MouseWare, and appears to work with any mouse!  And best of all, because these changes are performed by intercepting clicks, they carry downstream to any Remote Desktops sessions I'm running, without having to swap the mouse-buttons in Control Panel on the remote machine!  Unfortunately, the same does not hold true for virtual machines guests in VmWare 6.5, which must intercept mouse-button clicks before X-Mouse Button Control does.  The mouse changes only work properly in Unity mode.  But I guess that's better than nothing.