Mice - Hardware

[SyntaxError]

I did. Nothing has changed. Until you people fix SetPoint, nothing will change, but given Logitech's track record with software, I don't see this happening anytime within the next 20 years.

Look around on this forum. Your customers are not happy with your products. The problem 99% of the time is not the pc your products are used with. It's your products themselves. Your software is horrible, always has been.

While your hardware used to be excellent, it has gone downhill over the years, at least the mice and keyboards have. I don't know about the rest of your products. Although I admit I've had my eye on some of your speaker sets, but given my recent experience with your products, I'll never spend another penny on anything with the Logitech name on it.

Nevertheless, I am hesistant to return my MX400 for a refund. I really do like this mouse, but without properly working software to go with it, it might as well be a brick.

Logitech should probably clean house in the programming department, because there's too many people there who don't seem to know what they are doing. I strongly suggest cleaning house in your quality control department as well. I've heard countless reports from users that their Logitech hardware was faulty right out of the box.

Message Edited by SyntaxError on 04-09-200711:44 PM

[SyntaxError]

Out of desperation, I've installed SetPoint 2.60 with UberOptions and much to my surprise, it freakin' works. XP recognizes the MX400 just fine, SetPoint installed fine and showed the correct mouse image without having to manually install it, and because SetPoint 2.60 works, so does UberOptions. I now have working application specific settings.

I can't say that I'm completely happy since I never should have had to go through all the BS I've experienced in the last couple weeks, and my position on never buying another Logitech product still stands.

There's still one minor feature missing. I would really like the ability to program a keystroke that acts exactly like the same keystroke would on the keyboard. It other words, if I assign "x" to a mouse button, and I push and hold that button, the keystroke should repeat just like the keyboard would until I let go of the button.

This really isn't alot to ask. If the mousehooks in SetPoint had been written correctly to begin with, it would work. Logitech should seriously take a software lesson from Microsoft and Razor. They got it right long ago without alienating their customers.

I've tried adding the appropriate code to the user.xml file where needed, but when I load SetPoint after editing, it removes my changes. Oh well, just a minor inconvenience.

Since I can now program my mouse to my liking (with the above exception), I have decided not to return it to the store for a refund, but it is the last Logitech product I will ever buy, until sweeping improvements are made.

[Mona]

I am glad that you managed to get your mouse working. I will forward your feedback to our software development team in regards to this.

[Chidawg66]

Hi,

I'm having the same problem right now. I've tried 3.3, the most current version, and 2.6 and none of them work. I'm thinking about throwing this thing away and buying another mouse.

[Chidawg66]

So about 1 month back, my mouse would just randomly stop working. I had to plug and unplug my mouse again and again. Now it just freezes every couple of seconds and stop working then work and sometimes it would just stop completely as before.

so frustrating...

[rlowens]

Sounds like the mouse itself is faulty. Try it on another PC to make sure it is the mouse that is the problem (not your PC). If the problem is the same on the other PC, get the mouse replaced.

Less than 30 days since purchase, you need to exchange it where you got it.
After 30 days, you would be covered under the 3 or 5 year warranty from Logitech.
See here for RMA info.

[Chidawg66]

Here's the thing though... most RMA's you have to ship back your mouse. During that time in which your RMA is processed basically I'll have no mouse. It's only 50 bucks... might as well buy a Microsoft mouse or another kind of mouse instead of going through the whole RMA process.

[rlowens]

They often don't need the broken mouse back. Give them a call and see.

[Quixotic]

I am also having this exact same problems, on two different computers, one with XP and a brand new computer with Vista. The 3.3 drivers nor the 4.6 drivers provided a fix. Every so often it freezes up, then occasionally it will make the sound it makes when you connect a USB device for the first time and fix it self after 3-5 seconds. Sometimes you need to unplug and plug it back in for it to work. The drivers also recognize it as a Logitech MX320 Laser Mouse instead of the MX400.

[APrather]

I have similar problems with MX320... Its obviously a BAD BAD software/driver

I wonder what Logitech-- techs got to say? will they help resolve or make us forget ?