06-01-2009 07:26 AM
First off, I want to impress upon the Logitech company that I do love this mouse. It's an amazingly slick and fun-to-use tool for every PC action I perform and makes my computing well worth the time.
As far as my concern, well, I'm pretty certain it's with SetPoint, so let me just start with some basis information here:
I recently reinstalled Windows XP: Pro. I have 2 gigs of ram on my laptop and when installing the mouse, I had a clean slate with everything, having installed it with the original manufacturer's drivers that came with the mouse. After having the mouse for awhile, however, I began to notice some peculiarities.
Issue 1: When I would try to highlight text, the actual "highlight drag" would highlight some text, but then sporatically stop or else, highlight text that I never intended on highlighting to begin with. This often occurs with drag-selection on the desktop, as well.
Issue 2: Attempting to single-click on something sometimes sporatically turns into a double-click. This mostly happens after spending some time in an open window, after which I then try to click onto a different open window. What often happens is that after doing something in either Firefox or Internet Explorer, I will then click on an icon on my desktop to only highlight it, but with this issue, the mouse seems to inconsistenly and sporatically double-click it, instead.
Has anyone here had similar issues and if so, could you please help me out here? This is really taxing on my nerves since I've downloaded and installed various different versions of the drivers Logitech has issues to it's customer base. Am I going to be required to purchase a new mouse by a different company just to get this fixed!? This is so frustrating.
06-01-2009 08:24 PM
Please try adjusting the double click speed in Control Panel. That sometimes helps with this issue. If the problem persists, please try using the mouse with a different computer to verify if this is due to worn out/defective micro-switches (a more common cause for this problem).
06-01-2009 09:08 PM - edited 06-01-2009 09:09 PM
I have the VX Revolution and I just upgraded to Setpoint 4.72.40 from 4.60 and I'm experiencing some strange things too, similar to you but different. For example, if I place my cursor over buttons (such as the red "X" button to exit a window) it will highlight like always, but sometimes when I click it does nothing at all. I can click 5 or 6 times in a row before getting the action to happen.
At first I thought it was my batteries, so I put new ones in. No difference. Then I thought maybe it was a signal issue, so I set my mousepad right next to the receiver/transmitter.
I've finally come to the realization after futzing with this for two days that it's the Setpoint 4.72.40 software and when I have time to mess with it more I'm going to rollback to 4.60 to confirm it. Unfortunately I don't have the time to experiment anymore, work to get done. Just wanted to let you know that it IS possible that it's SETPOINT causing your issue.
XP Pro SP3
Core 2 Duo E7400 2.8Ghz
06-02-2009 08:27 PM
06-02-2009 09:33 PM
To check if SetPoint is the culprit, plase try using the mouse with SetPoint uninstalled.
Thanks for the idea CJChew.
I uninstalled SetPoint, and yes so far the odd behavior has stopped. I no longer have to click several times on an "X" to get a Window to close or two open tabs in my taskbar, etc...
I know this isn't what Logitech wants to hear, but there appears to be some bugs / problems with the current SetPoint version.
06-03-2009 08:23 PM
06-03-2009 08:55 PM
If you really need SetPoint's function, you could try using version 4.0 of Setpoint. That version is usually quite reliable.
Please don't take what I'm about to say personally. What I'm about to write is going to be very candid, with no intention of being rude, but simply as a user/consumer of Logitech products for over 10 years now. I've owned several varieties of key/mouse combos, webcams, and other Logitech products over the past decade and I often recommend your products to my friends, family, and customers.
However, this needs to be posted:
"IF I REALLY NEED SETPOINT'S FUNCTION"??? Are you kidding me? Well let's see - the whole reason I own an MX3000 keyboard or a VX Revolution etc... is to have use of the multimedia functions and programmable keys and other special functions that your product labels promise, and those features of course do not work without SetPoint! If I wanted to just stare at all these multimedia buttons and have them do nothing, then I could just use the keyboard that came with my computer. I spent the money on a multimedia Logitech product to have these features, so OF COURSE I NEED SETPOINT.
Do you have any idea what it's like to hear Logitech say (to paraphrase / translate your post) "well, some of are drivers are pretty reliable. Forget the ones that we're recommending to use with your product and grab some older version that might be more stable, but maybe not". I mean seriously, that's what you sound like to me as the consumer. I would think that for the premium that I pay for my Logitech products that the latest "stable" drivers should actually WORK with a tried & true O/S such as XP Pro SP3.
I'm sorry if this post comes across as rude, but let's keep it real for a minute here - Logitech has all but admitted that the SetPoint drivers are buggy at best, no matter which version we choose to use. How about getting at least ONE version of SetPoint to actually WORK and WORK SMOOTHLY with the operating systems that it advertises compatibility with, as well as the pricey products that we're paying for to have the functionality that your advertising promises.
To be blunt - the situation is ridiculous and Logitech is faltering. I can't believe I'm actually surfing online retail sites tonight looking at other brands of keyboards and mice after all these years of being a Logitech patron. This may sound far-fetched to some people, but Logitech OWES it to us customers to provide a stable SetPoint version that is stable and current, so that we can actually USE the functions of the products we've purchased from you.
Again, please don't take this post personally, but do take it sincerely. After 10 years of owning dozens of Logitech products I'm actually looking at Microsoft input devices now, and that's just sad.
04-06-2010 07:02 AM
Had the same issue (now resolved).
Have had setpoint 2.7.odd installed since machine was purchased in Nov 2007. XP Pro. And haven't had an issue until March 2010. Naturally assumed it was a virus, but after using task manager to kill every process one by one. You guessed it, setpoint.exe was the culprit. Start it up and the problem would come back (not immediately, but after 10 minutes or so and usually after using IE).
The solution was to download the latest version (6 at time of this posting). Every now works well again.
If I had to guess what the real problem was I would have to think an unrelated update (probably to IE or an extension) has rendered the old version of setpoint incompatible.
04-11-2010 06:25 AM
I'm having the same issue as of about 2 weeks ago, perhaps it is indeed related to an MS update? Anyone find anything out? it's driving me crazy! disapplying accelleration in SetPoint seems to have helped slightly by slowing things down?!
04-16-2010 12:48 AM
Having the same problem, issue seems to be resolved by uninstalling SetPoint but I do agree its ridiculous for this to not be fixed, the above posts are nearly a year old, so still an issue after so long?