Is anyone aware of a Bluetooth Mouse that will function in a Bootcamp Windows 7 partition? Cannot use the Magic Mouse or Magic Pad as the CAD program running in Windows does not respond to "swiping", etc. Need some type of functional wheel or roller ball.
Thanks. I'm currently using an old BT Mighty Mouse, but the roller balls eventually crap out, and Apple is no longer making them.
My Mircosoft InetlliMouse Explorer for Bluetooth worked fine for me under both Boot Camp and Mac OS-X when I was still using it. My much cheaper Logitech BT mouse also worked quite wekk, but it was a bit small for my hand. If my Microsoft mouse had an on/off switch so I wouldn't constantly run the batteries dead carrying it in my backpack, I might still be using it now, even though I find myself trying to use forward and back swipes on my PC mouse at work.
Bob:
Have a Logitech V470 that won't install properly in Windows 7 (in Bootcamp partition). It recognizes and installs, then disappears. Re-install yields a "recognition" issue, and ultimately it won't work. I will look into the Rocketfish mouse. I assume your Windows 7 installation is in Bootcamp (versus VMWare or Parallels). Can you confirm?
Thanks.
GeneonMAC wrote:
Bob:
Have a Logitech V470 that won't install properly in Windows 7 (in Bootcamp partition). It recognizes and installs, then disappears. Re-install yields a "recognition" issue, and ultimately it won't work. I will look into the Rocketfish mouse. I assume your Windows 7 installation is in Bootcamp (versus VMWare or Parallels). Can you confirm?
Thanks.
Yes my Windows 7 is installed in a Boot Camp partition.
Do you have the correct driver for your v470, for bluetooth? According to Logitech's site the V470 works with Windows 7. Here is the driver site.
Thanks, Bob.
Unfortunately, I have already installed SetPoint 32-bit. I'll try re-installing it again, and make sure that all other programs are closed when doing so. In discussions with Logitech (a US tech support agent, not overseas), they DO NOT support Bootcamp, which is an unfortunate message. I'm nursing along my Might Mice, to make them last as long as possible (using in Bootcamp only) to see if this gets resolved.
I do like the V470. It would be a lot nicer if going back & forth wasn't such a pain.
Appreciate your feedback. Any other ideas welcome.
I don't understand their statement "...they DO NOT support Bootcamp...". Running Windows 7 in a Boot Camp partition is the same as running Windows 7 on a PC. If Logitech's drivers support Windows 7 on a PC then they will/should support Windows 7 in a Bootcamp partition.
Are you doing the installation correctly? Do you need to install the driver before turning on the bluetooth mouse? Or does Windows 7 recognize the new hardware when you turn on bluetooth and the mouse? What shows up in Control Panel > System > Device Manager? Is the mouse listed with a warning? Is bluetooth listed with a warning? Does the mouse try to pair with Windows 7?
While Logitech is happy to support Windows 7, apparently there are some driver issues with Windows 7 installed in Bootcamp. The tech indicated that they do not support Bootcamp. Can't say I understand, either. Windows 7 recognizes the V470, with or without the new Logitech drivers/software installed. It will open in the Bluetooth Window, recognize as a Bluetooth Travel Mouse, and install the drivers. The little circle is there for a while, then disappears when the picture of the V470 acquires the correct description as a Logitech V470 Mouse. Then in 10 - 15 seconds, the error triangle shows up, then the picture disappears. An attempt at reinstalling brings up a "pairing error", even though the pairing information shows as correct, if I double click on the picture before it disappears- it brings up the connection details, which appear correct.
The other odd thing that happens on the MAC side, is that the Logitech software disables the "rename" function normally available in the bluetooth devices "gear" drop-down menu. "Update Device Name" shows, but not "rename". I have sent off a support request to Logitech requesting instructions on how to rename the mouse, but have not received any answers yet. I appreciate your feedback.
SUCCESS!
With another try at installation this morning, another trick pulled off a working installation.
Clicked on the Bluetooth icon on the toolbar, which opened the Bluetooth Device window. Then chose "add a device", discovered the Logitech V470 BT Mouse and let Windows 7 automatically install. As soon as the initial "Lazer Travel Mouse" icon appeared in the Bluetooth Device window, double click it (with either the touchpad or mighty mouse) to open the "Properties" window, which will stay open, even after the icon disappears in the Bluetooth Device window.
The Properties window has four (4) tabs - General; Hardware; Services; Bluetooth. Click on "Services" and see an unchecked box next to "Drivers for keyboard, mice, etc. (HID)".
I checked the box and ... the correct driver (re?)installed and the mouse immediately began to function properly. It continues to operate properly after several back and forth re-boots between MAC OS 10.6.6 and Windows 7.
Even a blind squirrel finds an acorn now and then.
Bob: See my post of today (2/16/11). I solved the probelm and now have the V470 working properly on BOTH sides of my MBP!
Really appreciate your responses anbd efforts.
Have a great day!
Salmon, Kings (Chinook) and Silvers (Coho). Sometimes Rainbow Trout when it is not Salmon season. I'm not much of a fly fisherman although I do own a fly rod.
I know this is a very old post but I just spent WAY to much time trying to download drivers, update my Windows 7, etc. in the hopes of getting my Microsoft Sculpt mouse to work and your simple method of "right click the device, go to properties, and check the driver box in the services tab" made me SOOOOO happy...and feel a bit like a dee dee dee.
I concur. My new Logitech M557 BT mouse was discovered by Win7 in Bootcamp install but would never fully connect - it timed out. I had pretty much given up hope to making the M557 work, having mainly played with perceived driver errors which could not be identified. The solution from GeneonMAC works perfectly, but you have to do the right click for properties immediately after the icon for the discovered mouse appears - it won't come up if the 'connecting to device' runs very long.
