You DON'T want them to turn off to save power.
 

Right now I'm in a "wait and see" mode because after I connected the midi interface two days ago the mouse has been working just fine!  And I've been running Sonar and playing tunes with lots of data going thru the midi and some thru soft synths too.  What's with that?? 
 
So while waiting to see what happens, I have not made any other changes (including changes to the SB power management).
 
I'll send another status in a day or two.
 
-- Larry

larrymcg
 
OK, what should I check for?  The device manager lists a ton of USB related items.  I've checked the power management on the ones that say Generic USB Hub and USB Root Hub.  They all say it's OK for the PC to turn the device off to save power.
 
-- Larry

Control Panel\Hardware and Sound\Power Options
click "change plan settings"
click "change advanced power settings"
go down the list to +USB settings click the '+' to open 
USB selective suspend setting click the + to open
click setting to open drop down and select disabled
 

Sounds to me like your midi interface and wireless mouse receiver are sharing the same USB controller.
 
Move one to a different USB port, preferably far away (If one is on the front, have the other on the back, or vice versa), to get them on different controllers.
 
Dave's suggestion of adding a PCI/PCI-e USB card would do the trick.  You can pick up a card online, starting around $20.

I think I've been in "wait and see" mode long enough now.  What I see is that there is no conflict between my wireless mouse, Sonar, or the midi interface.  I have been testing quite a lot with no issues.
 
However, as soon as I fired up my external disk (WD My Book) the cursor got jumpy and froze and all that bad stuff.  It didn't matter what else I was running or if I was running anything else at all.  As soon as I powered the external disk off, all got good again.  It's curious that I have been using this external disk for a couple years with no mouse related issues but now, since installing Sonar and the midi interface, I consistently get issues.  That's why I suspected Sonar and the midi interface.  I happened to have the external disk open when I installed Sonar because the install files for Sonar were on it.  Hmmmmm......
 
The external disk has a USB3 interface and it is plugged into a USB3 port.  The mouse adapter is plugged into a USB2 port.  These two ports are physically fairly close to each other - there is an unused USB3 port between them.  I guess it's time to move some USB connections around to see what happens.
 
-- Larry

Windows tries to stabilize itself for connections, and when conflicts occur it will dynamically reassign things, but seems to only do so on boot. Depending on hardware, some have reported having to connect things in specific order, but I personally have never seen this. Windows does try to remember device by USB connection, so cycling connections isn't often useful. That being said, simply unplugging/re-plugging in a USB connection can force Windows to re-evaluate itself.
 
I assume the USB3 port is on the motherboard, and not sure what drivers it is using. You may want to try plugging that into a USB2 port just to check it.
 
Driver updates for your system may also be contributing. As the machine is new, it is unclear if drivers are up to date for hardware components (the stock drivers in on the Win7 DVD are outdated in most cases).

slartabartfast
I simply do not see how Sonar itself could interfere with a mouse. Communication with your mouse is entirely within Windows.

That's what I would have thought, but I've had this exact same problem with my wireless mouse.  Only with Sonar running would the pointer stall and jump all over the place.  Painful.  I can't imagine what Sonar does to affect wireless communication this way.  Maybe it loads down something that indirectly affects the USB/wireless connection.
 
What finally solved things for me (after trying different usb ports on the back, then the front of my floortop) was to run a USB extension cable so that the mouse's dongle is only a few inches away from my mouse.  No problems since.
 

Another quick point came to mind... if Windows is seeing that disk for the first time, it will go to town running through the files to sort through/verify them all. Depending on Windows indexing options, it may also be trying to generate an index file at the same time (these indexes default to the C drive). This event should be significantly quicker on subsequent uses of the device, but Windows will set priority to reading that drive each time it is connected.

If you want to find out what is connected to each USB socket and port open Device Manager and in the view menu tell it to show devices by connection.

I've not seen anything interfere with a wireless mouse or keyboard other than when Windows puts the port to sleep. As well as the USB sleep settings in the Windows power scheme if you check the sockets/ports properties in Device Manager there's also a tickbox for the same function there. For whatever reason that tickbox isn't set by the power settings dialogue and often contradicts it with the result that the ports will sometimes go to sleep even if the power settings say they shouldn't.

As for USB3 check you've installed the drivers provided by the motherboard manufacturer. The standard generic ones Windows installs are often not optimal.

I had something like this happen and it got fixed when I put the mouse and Keyboard on a PCIexpress card. When on a PCI card or the motherboard they would jerk around and stall. I have tried them on a USB3 card and they worked fine but it's a PCIe card. The only things left on the PCI card are Waves and Steinberg license usb sticks.  I don't know why this works for me but I know it does.