Iterested why wireless mouse needs new batteries with windows earlier than linux
 

I am just wondering why my wireless mouse (Genius non optical) works fine in slackware but when I go to windows xp it doesn´t if I change the batteries it will start working again in windows , but as I don´t use windows a lot I haven´t bothered.:scratch:

Maybe it's a coincidence, since you don't use Windows a lot.

I'm tempted to say it's Microsoft accessing the mouse to make sure it's properly licensed! ;)

By the way, I use a Logitech optical cordless mouse and I use NiMH batteries in it. They last quite a while before they need recharging. Very pleased with this setup. (Great mouse, too.)

I am sure its not a coincidence cause the thing is I don´t notice it I just decide to load windows and the mouse doesn´t work... If I load up slackware again its fine. The only way I can get my mouse working in windows again is buy putting new batteries in it.:eek:

Its not work the hassle of buying new batteries for now :D

This gives a whole new meaning to the notion of Windows as being "a resources hog"! :D

I am just interested to know why it is... its kind of interesting... its like when the batteries don´t have some much juice in them somthing changes.

What I don´t know... and from the reponses here no one else has had this happen to them??:study:

Doesn't an input device (mouse, keyboard) get "polled" in order for the operating system to receive any input from it? I imagine it's possible that the polling mechanism in Windows might be more power-hungry than in the Linux setup you use. Every response from the input device consumes a tiny amount of power, and it all adds up.

Just a guess.

Hey jonr thanks for your reply. That could make sense... the only thing is that my mouse turns off it its not moved for about 2 minutes so when I turn the computer on and start up windows without moving the mouse I would have thought it wouldn´t work either.... but it does with good batteries:scratch:

I know it switches off because when I first move it nothing happens then it starts working.

Does it "switch off" like that during inactivity when you're running Slackware, too? I've never had mine appear to switch off... But I guess it could depend on power-control settings. Seems to me I read somewhere once (probably here) about power-control settings in Windows causing unwanted hard-drive activity. I know when I was using Windows 98 I never could get the power-control settings to do what the menu settings said they'd do. With Linux, I don't even try! I just let things run, usually. (I can power down the hard drives, etc. manually with a push of the power button, as setup in at BIOS setup time, but then coming out of that standby mode is a little uncertain, so I seldom do it.)

Anyway, wondering if the "automatic" power control settings could be a question here.