Slashdot Mirror


Windows Drains MacBook's Battery; Who's To Blame?

ericatcw writes "Users hoping that Windows 7's arrival will mean less power drain on their MacBook laptops may be disappointed, writes Computerworld's Eric Lai. Running Windows 7 in Boot Camp caused one CNET reviewer's battery life to fall by more than two-thirds. But virtualization software such as VMware Fusion suffer from the same complaints. Some blame Apple's Boot Camp drivers (the last ones were released in April 2008); others lay the blame at Windows' bloated codebase. With Apple and Microsoft both trying to avoid responsibility for improving the experience, Windows 7's reported improvements in power management will be moot for MacBook users for a while."

8 of 396 comments (clear)

  1. Not just Windows by dr.newton · · Score: 5, Interesting

    I have a MBP 5.1, one with both the on-board and discrete Nvidia cards. OS X switches between them depending on whether it is going for power savings or performance.

    The drivers for Windows XP and Linux do not seem to have this ability. When I'm doing nothing but surfing, I get about 4.5 hours of battery life in OS X, but only about 2.1 hours in Linux (Ubuntu Jaunty) and Windows XP.

    I always assumed it was the inability of XP and Linux to switch to the on-board graphics card.

    --
    Just another proletarian malcontent.
    1. Re:Not just Windows by lukas84 · · Score: 5, Interesting

      I have a ThinkPad W500, which has onboard Intel graphics or a Ati Radeon 3650. They too can be switched automatically or at will.

      The reason you can't do it on XP is because Apple hasn't bothered to release drivers for it.

  2. Can we question the author's qualifications? by BadAnalogyGuy · · Score: 5, Interesting

    FTFA: Other than that, Windows 7 has been working great on my MacBook Pro... It looks good, too, even prettier than when it is installed on PC hardware.

    This reminds me of the iPod Nano review here at Slashdot that claimed that the Nano sounded great, even in a moving convertible with the top down. (http://apple.slashdot.org/article.pl?sid=05/09/08/1439244)

    Yes, it's the Apple magic that makes the software look better.

    How can we know that the battery isn't simply returning strange battery level information to the OS that OSX knows how to parse but Windows doesn't? What a strange review.

  3. Re:Don't use bootcamp, but I use Fusion by dr.newton · · Score: 4, Interesting

    I agree that there would be issues, but going from 4.5 hours of battery life on OS X on a MBP to 2 hours on any other OS is a little extreme!

    I would love to be able to use Linux on my MBP as the primary operating system, but often it is impractical because of the limited battery life.

    That being said, 2 hours is about standard for any other laptop I've owned, so maybe I should think of it as OS X being uncannily power-efficient. ;)

    --
    Just another proletarian malcontent.
  4. Re:Doubt it's the "bloated codebase" by jimmyfrank · · Score: 4, Interesting

    I bought a macbook because I wanted to run Leopard and XP. Consumer reports also rated Apple laptops #1 in all screen size categories. I'm also not poor so I spent a few xtra bucks.

  5. Re:Don't use bootcamp, but I use Fusion by fullgandoo · · Score: 4, Interesting

    I agree with you. For instance on my previous generation Macbook Pro, there is no way to tap the touch pad for a mouse click under Windows. You are forced to use the touchpad button.

    On the face of it, it looks like an innocent little accidental omission by Apple, which they steadfastly refuse to fix. Since all the Windows drivers are provided by Apple, I believe it is deliberate on their part to degrade the user experience on anything but OSX. That is just typical mean-spirited behavior by Apple.

  6. I think I know the reason, disk by Ilgaz · · Score: 4, Interesting

    On latest gen (nv9300 based) Mac Mini, I have installed Win7 64bit. It installed all the drivers and even clever to figure mainboard driver giving direct link to nvidia driver exe which is absolutely a very serious risk but anyway...

    The ATA chipset driver is missing from Win7 since Apple didn't really put nv9300 chipset in exact way. So, it falls down to non DMA generic MS driver. Every single byte transferred to/from disk is guaranteed to use massive CPU along with horrible (down to 15MB/sec from 70MB/sec under OS X) slowness.

    So, if Macbooks have similar issue with Windows 7, it could be same issue. As they are battery powered, it would be visible in battery life too.

    BTW, there is no point testing Windows 7 until Apple releases boot camp for Windows 7. Apple computers aren't really PCs. If MS was really clever and wanted Windows 7 to be _really_ tested, they should have printed a very clear privacy policy on screen and actually make machine report all kinds of anonymous stats. That way, they could really figure what is going on. For example, a core duo powered 2009 machine shouldn't really max to 15mb/sec with a SATA 2 drive.

    I couldn't even find something similar to bugreporter.apple.com when I wanted to report issues. All I saw is a stupid forum which beginner level MS engineers are monkeying with templates. They even made their own wrong answer as 'answer to the issue' while it would create massive compatibility problems in one occasion.

  7. Re:Doubt it's the "bloated codebase" by PeterChenoweth · · Score: 4, Interesting

    Nope. There is. Keyboard backlighting works just fine on my MBP when bootcamped to XP. It does not, however, automatically adjust the keyboard backlight intensity with ambient lighting conditions as OSX does. One can still manually adjust the intensity with the keyboard buttons, if desired.

    Come to think of it, I'm not actually sure the screen brightness adjusts dynamically in bootcamped XP either. It might be the same deal as the keyboard. I can't recall.

    It could be little things like that adding up. Screen brightness is a major drain on battery power. It could be that since OSX can and does (by default anyway) aggressively ramp down the brightness whenever it can when on battery power, it's able to save more watts. Where if XP can't/doesn't do that (on an Apple), you'd get more of a battery drain. Just a thought.