View Full Version : Mx700

10-26-02, 09:14 AM
I received my Logitech MX700 cordless optical through FedEx yesterday (like I was telling a few of you in IRC). So here's my input, along with the only critique I have of it:

First off, the mouse is extremely comfortable in my hand. That's not surprising to me though. Logitech has always made mice that I found to be that way. Despite the difference in shape from my Dual Optical, both feel equally comfortable for use. Button placement is okay, with the thumb buttons being perfectly placed, and the others (in front of / behind the scrollwheel) being a bit less ideally located. The others are still easily usable, and thanks to the quality of the buttons, they aren't so sensitive that using the wheel with my fingers / palm over them causes them to be hit by accident. The buttons have also are very good in the sense that it's easy to use them and to tell when you've clicked one. The scrollwheel itself moves smoothly, with just enough feedback to let you know how far you've turned it (the 'click' isn't overdone on this mouse, and the wheel isn't stiff).

As for performance- it works mostly as advertised. I mean, it doesn't lag at all. The tracking and response feels just as good as my Logitech Dual Optical (and a bit better than the MS Intellimouse Opticals that both of these have replaced). I was pleasantly surprised. Also, the buttons are all reassignable, though I would have liked it if they'd allow more than just the F keys and other special keys (iow, you can't assign a letter or a number to the buttons). That's okay too, since my games nearly all allow associating commands with the same buttons the mouse supports.

The only issue I have with this mouse is the scrollwheel, and specifically in UT2003. The wheel works perfectly without any changes everywhere but in the game. The weird part is that, unlike the other Logitech mice I've used lately, the wheel IS being traced in the game without changing any settings. The problem is that it only works after the mouse has been held motionless for a second or two. Move the mouse, and the scrollwheel input stops. Simple as that. The fact that it works properly elsewhere tells me Logitech needs to get on the ball with the drivers a bit more. Somehow whatever the game (UT2003) is reading for the wheel is being hidden by the movement messages. Thankfully, with a full 8 buttons available for reassignment, I just assigned the forward / back buttons in the thumb area to be backspace and delete, and assigned the alternate next weapon / previous weapon binds in UT2003 to those buttons, so I don't lose any functionality at all. Still, I'd rather have the wheel work right, so I could use it for those functions, and assign specific weapons to the others.

All in all, it's a keeper. No more cord getting tangled / wrapped up around my keyboard tray, and no cleaning of dirty mouseballs.

10-27-02, 12:56 AM
Originally posted by SnakeEyes
The fact that it works properly elsewhere tells me Logitech needs to get on the ball with the drivers a bit more.

I see some things (still) haven't changed. :rolleyes:

Logitech's drivers (or lack thereof), not you. ;)

10-31-02, 08:24 AM
I just read the review of the MX700 (linked today from the nvnews main page), and the author mentions that the scrollwheel issues don't occur when not using the Mouseware software. A bit further along in the review, he mentions that the application-switching button is the only one that won't function without the Mouseware software. I haven't yet tried this, but it means I have to ask a question-

Has anyone else here used a Logitech mouse (4 button or more) without mouseware, and still had use of other than the three standard buttons and scrollwheel? It seems to me that when I last tried that, the 4th button (thumb button) on my Logitech Dual Optical stopped working, and the MS drivers saw it as only a 3 button scroll mouse.

Do I need to load some special software?

(I never use the app button anyway, but it'd be nice to be able to assign the other buttons in my games and still use the scrollwheel in the normal way..)

10-31-02, 08:31 AM
warp2search news page has word that using microsoft intellimouse explorer 3.0 driver solves problems.

11-01-02, 09:15 AM
Any idea where I can download that revision? I downloaded the MS Intellimouse 4.1 drivers (the ones on MS' site), but after installation, they detect that it's not an MS mouse and simply unload themselves from memory.

BTW, I am using the standard WinXP drivers MS provides, which (ironically) according to the hardware device listing, is actually a Logitech provided driver, and the scrollwheel functions wonderfully. Unfortunately, while the statement that the app-switching button doesn't work when doing this is true, the two thumb buttons are also not working. Even more ironic than that is that the two buttons for scrolling a page (the ones immediately to the front and rear of the wheel) work fine, but aren't programmable. I was able to scroll pages using them, which seems to suggest that by default they emulate the scrollwheel up / down movement, but at some predetermined fixed rate.

If I can find a driver that works as the standard XP version does, but with support (including programmability, I hope) for the two thumb buttons, this mouse will receive the Snake-Eyes 'Perfect Gaming Mouse' award. As it stands now, it's just got the Recommended for Gamers title. ;)

11-01-02, 10:03 AM
First, thanks for the warp2search tip, thcdru2k. I went there, and then read the reply posts on that news item.

From the reading, it appears that some users have had the MS Intellipoint drivers work fine, while others (like me) had no luck. After thinking about it for a few minutes, I had a brainstorm (well, a braindrizzle anyway :D). It's possible the people for which the MS software is working are using the PS2 port to connect their mice.

Right now my mouse is connected on the USB port. One thing I know for sure about the USB port is that devices connected to it identify themselves to the OS / USB driver. This explains why the Intellipoint software unloads itself when I try to use it- it sees that there are no MS mice present, and just quits.

My idea (which I plan to test tonight) is that the PS2 port DOES NOT identify the hardware connected to it, unlike the USB port. So if I load the MS software after connecting my mouse to the PS2, then tell Intellipoint that my mouse is an Explorer v3.0, it just loads and starts working for the 'Explorer 3.0' on the PS2 port. If this actually works, I'll leave my mouse on the PS2 port for the time being, and just bump up the PS2 rate to at least 125Hz (the rate the MX700 supposedly reports at is 120, but I've seen 125 mentioned in reviews, with values as high as ~148 reported with the rate checker software. I may even set mine to 150 to be safe).

Anyhow, thanks again. I'll report back here with my results, for anyone that's interested. (BTW, I don't know for sure that this is the reason the buttons aren't working yet, it's just a hunch. The reason I'm not certain is that the people over on Warp2search that have theirs working claim to be using MX500 [corded version of the MX700] mice).

11-02-02, 06:54 PM
Okay, final update.

First, the Intellimouse Explorer 3.0 is USB only. So PS2 doesn't work.

Second, using just standard XP drivers, and not the Explorer stuff, I get all buttons but the app-switch, only none of them are reprogrammable. (Basically, the two thumb buttons function as forward-back in web browsers, and that's all. I only discovered it as I was putzin around without either Intellimouse or Mouseware installed).

Last, I sent an e-mail to Logitech's tech support. It appears that the issue I have with Mouseware and the scrollwheel is a known issue and also that they plan to have the fix in the next set of drivers. (If it IS, W00T! I'd really like that, because other than the scrollwheel quirkiness in UT2003, this mouse is still the best I've used yet, by a long shot. :))

ad hoc
11-02-02, 07:47 PM
I'm not sure if this will fix your problems, but it did for me...

Try clicking the "Use MS Office Compabile Scroll Only" and "Scroll in Active Window Only" checkboxes unter the "Buttons" tab in the logitech software. See if that doesn't help.

11-03-02, 09:35 AM
This time around (I'll explain better in a second..) I don't have to worry about those settings- my mouse wheel is detected no matter whether I have it set or not, because, trust me, I've played with those. The wheel works if the mouse hasn't been moved for at least 3 - 4 seconds, and immediately stops when the mouse is moved.

The reason I said this time around is that in the past whether the wheel worked or not seemed to be random depending on the time of day, color of sky, amount of air, and local humidity. Changing those settings usually worked to resolve it, but not necessarily enabling them. What setting I needed to fix the problem was just plain random.

So these drivers are a small step forward from those (hey, at least the wheel seems to be detected for me all the time now..), if only movement of the mouse itself didn't make the wheel seem to stop. ;)

11-07-02, 08:51 AM
I own the MX300...

I am experiencing the same problem, the scroll wheel just doesn't work in games.

I do have a workaround... It is a pain but it does work. Before starting a game, go into the mouse properties and select "none" for the number of lines in the scroll wheel option. This kills the scroll for Windows apps, but for whatever reason the scroll works as it should in games. Just have to remember to set it back to your preferred setting (3 lines, etc.) when you are finished playing.

Here is hoping Logitech addresses this issue, as I love the mouse otherwise.

11-07-02, 09:12 AM
Originally posted by kuzujanakis
I do have a workaround... It is a pain but it does work. Before starting a game, go into the mouse properties and select "none" for the number of lines in the scroll wheel option. This kills the scroll for Windows apps, but for whatever reason the scroll works as it should in games. Just have to remember to set it back to your preferred setting (3 lines, etc.) when you are finished playing.

This is exactly how I used to "fix" issues with my old Logitech MouseMan+ (circa 1998). So it's been 4 years now and they still haven't solved this problem? :rolleyes:

11-07-02, 09:57 AM
I'll have to try that 'fix'. Anyway, we'll see how they actually address the problem in the next drivers (since I finally got a reply from someone in their support department, unlike in the past with similar issues, and that reply says it's known about, and is being fixed. :p)