Hi everyone.
I recently updated from Windows 7 beta to the latest Windows 7 release candidate (both are 64 bit versions).
I've encountered one major problem with the release candidate. For some reason, my Logitech MX Revolution wireless mouse (which works fine in Windows XP MCE 2005) will randomly be dropped by Windows 7. I have to go and unplug the USB signal receiver, then plug it back in for the mouse to work. I have to do this frequently and at random intervals (though I've noticed navigating the pipboy 3000 menu in Fallout 3 seems to have the mouse hang more consistently than in other parts of the game.)
The Logitech mouse does broadcast in the 2.4 GHz frequency band (like wireless routers), but after I moved my wireless router to another room, it seemed to resolve the signal conflict and allow smooth operation in Windows XP. In Windows 7, it works fine until it drops out. I've given it over 30 seconds to become responsive, but it never does until I unplug then plug the receiver back in (generally to another USB port).
I've not been able to find a Windows 7 driver for my specific product, so not sure what other approaches I can take.
This is a major pain in the ass, and I've been unable to find current documentation on this issue or someone with a similar problem.
Additionally, it looks like most of the sound glitches have been fixed in the latest release, though I am noticing that music plays back on only two of my speakers (the fronts), even though other sounds play properly through my 5.1 speaker set up. Haven't found a solution for that yet. I'm using the (now old) Audigy 2 ZS Platinum Pro.
Here's a copy of a post I did on another forum where a similar problem was mentioned by another user (though no fix had been found):
I have a similar problem.
Windows 7 64-bit. Latest release client (I downloaded it from Microsoft three days ago).
I too downloaded and installed the latest version of setpoint, though it did NOT solve the problem.
For my MX revolution, the mouse won't just drop out for a few seconds, once Windows 7 decides to ignore it, it ignores it until I unplug and plug the USB reciever back in to a different USB port.
I have to repeat this frequently. It's a total pain in the ass. Since it sounds like the symptomology varies a bit, I'll list my system specs. Let's see if we can solve this or isolate the factors causing this (and maybe someone will offer a fix in the meantime).
If I plug in my wired old MS mouse, the MS mouse works fine.
Windows 7 Ultimate 64-bit - Release Candidate. Build 7100.
5.0 score on the Windows Experience Index
AMD Athlon 64 x2 Dual Core Processor 4400+ 2.20 GHz
4 x 1 GB Corsair XMS DDR 400 RAM
ASUS A8N32-SLI Deluxe (BIOS memory hole enabled for Windows 7, so I can use my 4 GB of RAM)
dual XFX 7950 GT extremes in SLI mode (via latest Windows 7 NVIDIA driver)
Sound Blaster Audigy 2 ZS Platinum Pro
Western Digital Caviar Black 1 TB HD (currently dual partitioned with Windows XP and Windows 7. Used to also have linux distros for triboot via the GRUB launcher).
Dell 2405 FPW 24" widescreen LCD (I usually connect my mouse's USB reciever to the powered USB hub on the monitor. The mouse will still be dropped by Windows 7 if I use a "direct" USB port on the computer itself).
I tend to run BOINC and Valve Steam in the background. There are currently two "unknown devices" listed in the device manager... I THINK one of them is the "creative game port", though not certain. Not sure what the other is.
The only other possible factor I can think of is possibly Windows 7 confusing the 2.4 GHz wireless router signals with the mouse's 2.4 GHz wireless signal and perhaps shutting it off as a security measure (a guess)? I know when I had my wireless router 2 feet from my mouse, the MX didn't play nice with Windows XP. After moving the router to another room, my mouse has operated just fine in Windows XP.
In Windows 7, I get the mouse drop outs and it won't work until I unplug and replug the USB reciever back in, with or without Logitech setpoint installed.
I recently updated from Windows 7 beta to the latest Windows 7 release candidate (both are 64 bit versions).
I've encountered one major problem with the release candidate. For some reason, my Logitech MX Revolution wireless mouse (which works fine in Windows XP MCE 2005) will randomly be dropped by Windows 7. I have to go and unplug the USB signal receiver, then plug it back in for the mouse to work. I have to do this frequently and at random intervals (though I've noticed navigating the pipboy 3000 menu in Fallout 3 seems to have the mouse hang more consistently than in other parts of the game.)
The Logitech mouse does broadcast in the 2.4 GHz frequency band (like wireless routers), but after I moved my wireless router to another room, it seemed to resolve the signal conflict and allow smooth operation in Windows XP. In Windows 7, it works fine until it drops out. I've given it over 30 seconds to become responsive, but it never does until I unplug then plug the receiver back in (generally to another USB port).
I've not been able to find a Windows 7 driver for my specific product, so not sure what other approaches I can take.
This is a major pain in the ass, and I've been unable to find current documentation on this issue or someone with a similar problem.
Additionally, it looks like most of the sound glitches have been fixed in the latest release, though I am noticing that music plays back on only two of my speakers (the fronts), even though other sounds play properly through my 5.1 speaker set up. Haven't found a solution for that yet. I'm using the (now old) Audigy 2 ZS Platinum Pro.
Here's a copy of a post I did on another forum where a similar problem was mentioned by another user (though no fix had been found):
I have a similar problem.
Windows 7 64-bit. Latest release client (I downloaded it from Microsoft three days ago).
I too downloaded and installed the latest version of setpoint, though it did NOT solve the problem.
For my MX revolution, the mouse won't just drop out for a few seconds, once Windows 7 decides to ignore it, it ignores it until I unplug and plug the USB reciever back in to a different USB port.
I have to repeat this frequently. It's a total pain in the ass. Since it sounds like the symptomology varies a bit, I'll list my system specs. Let's see if we can solve this or isolate the factors causing this (and maybe someone will offer a fix in the meantime).
If I plug in my wired old MS mouse, the MS mouse works fine.
Windows 7 Ultimate 64-bit - Release Candidate. Build 7100.
5.0 score on the Windows Experience Index
AMD Athlon 64 x2 Dual Core Processor 4400+ 2.20 GHz
4 x 1 GB Corsair XMS DDR 400 RAM
ASUS A8N32-SLI Deluxe (BIOS memory hole enabled for Windows 7, so I can use my 4 GB of RAM)
dual XFX 7950 GT extremes in SLI mode (via latest Windows 7 NVIDIA driver)
Sound Blaster Audigy 2 ZS Platinum Pro
Western Digital Caviar Black 1 TB HD (currently dual partitioned with Windows XP and Windows 7. Used to also have linux distros for triboot via the GRUB launcher).
Dell 2405 FPW 24" widescreen LCD (I usually connect my mouse's USB reciever to the powered USB hub on the monitor. The mouse will still be dropped by Windows 7 if I use a "direct" USB port on the computer itself).
I tend to run BOINC and Valve Steam in the background. There are currently two "unknown devices" listed in the device manager... I THINK one of them is the "creative game port", though not certain. Not sure what the other is.
The only other possible factor I can think of is possibly Windows 7 confusing the 2.4 GHz wireless router signals with the mouse's 2.4 GHz wireless signal and perhaps shutting it off as a security measure (a guess)? I know when I had my wireless router 2 feet from my mouse, the MX didn't play nice with Windows XP. After moving the router to another room, my mouse has operated just fine in Windows XP.
In Windows 7, I get the mouse drop outs and it won't work until I unplug and replug the USB reciever back in, with or without Logitech setpoint installed.
Facebook
Twitter