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."
Windows Drains MacBook's Battery; Who's to blame?
I blame Microsoft. Much like the title, I was expecting Windows 7 to actually recharge my laptop battery, not drain it.
This is a whole new and special kind of whining.
/. has reached a new level.
Waaaaahhhh!!!
I have a new MBP and use Fusion. I have an XP image and a Vista image loaded up. I have not noticed any unusual power drain, but that's kind of to be expected, IMO. Also, I have to question the wisdom of using a VM session for more than an hour or so on just the battery.
I can see some instances where this would be an issue for some, but this seems like senseless "hating" to me. No, I'm not trying to troll or anything else, I'm just having a hard time figuring out why someone would spend a long-ish amount of time in Fusion running a guest OS on battery power. It seems obvious to me that there are issues running a non-native OS on a laptop designed for a specific OS...
Sent from your iPad.
Macbooks are essentially the same hardware as Windows machines, down to battery capacity. It is unlikely that a "bloated codebase" would chew through the battery like nobody's business on one x86 machine and suddenly become perfectly benign on a practically identical x86 machine. Bloat doesn't magically appear when you put an Apple logo on something.
No kidding!!! What do you say at this point?
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.
No matter how bloated Windows is, battery life is only a function of ACPI drivers --- bootcamp's fault
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.
Boot Camp just resizes the hard drive so it can accomodate a Windows install and then you are able to dual-boot your system. It's also possible to install Linux on the other side for example. So it seems like Windows has an issue with the Intel or NVidia chipset, the processor or just plainly consumes more resources than Mac OS.
A good comparison would be to install Linux on the other side and see what it's battery life is then. Mac OS X offloads a lot (all) of the desktop rendering to the GPU while the Windows XP desktop doesn't and although Vista's top-end version does, it is offset by the amount of graphics that need to be rendered and the low-end version still doesn't.
There is a reason that the battery dies quicker and since there is no layer of Mac OS X between Windows and the hardware I doubt it's because Apple did something wrong. It's either Windows or the Intel or NVidia drivers. You can't really compare VMWare or Parallels performance because it's running Windows on top of Mac OS X, it is of course going to consume more resources.
Custom electronics and digital signage for your business: www.evcircuits.com
Can you expect "power savings" when VMware is running? You are basically running two computers at once.
Running Windows XP dual-boot on a MacBook Pro (what you people call "boot camp") also drains the battery a lot faster than OSX. I'm pretty sure Apple didn't put much effort into making sure all the hardware drivers worked anywhere near as well under Windows as they do in OSX. (additionally, I've seen display driver quirks and more iffy trackpad operation)
Apple and it's customers are the only losers if something doesn't work on the Macbook. Microsoft never claimed it would. This situation is very similar to the Palm Pre / Itunes fiasco. If you're a Palm Pre owner, just STFU if Itunes doesn't behave the way it should.
First, a quibble with your argument. You do not pay a "massive premium". Depending on what product you bought, you paid a slight premium or slight discount vs. a similarly-spec'd Dell.
Second, it should be pretty clear why one would occasionally need to run Windows in native mode. Aside from saving the additional cost of virtualization software, Boot Camp simply runs some programs faster. Also, if I hand my IT department my notebook to configure and it is in Mac mode, they'd have absolutely no ability whatsoever to load it up with the VPN software since they don't do Mac. Put it in Windows mode, and they give no complaints.
W..w..W - Willy Waterloo washes Warren Wiggins who is washing Waldo Woo.
The problem is not specific to Windows or MacBooks. Many developers code as if the only machines that will run their software are permanently el-grid-connected servers or workstations. Polling loops with insane timers (like 1000hz), and they also take the advice "don't optimize prematurely" to mean "don't optimize unless you are payed for it". Re-drawing the display even if it is not needed at all, copying data structures all over, etc. No wonder batteries drain.
In this case I believe all three are to blame - neither alone is the culprit - I mean Windows usually is compatible with real hardware enough to last couple-three hours on an average laptop battery doing average desktop stuff, MacBook is about the same. Probably BootCamp taking battery awareness too lightheartedly and/or unable to optimize for specific cases like virtualized Windows code running.
This is /. ain't no ladies round here.
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.
I write driver level embedded code for a living. Everything from bootstrapping embedded linux to SoC level power management.
Power management is usually the last thing to get done (if at all)... why? Because management usually sees it as icing on the cake. Attitudes are typically just make it work and we'll ship a bigger battery to make it last. Or we'll ship an upgrade in 6 months, if the product starts to take off and we decide to fund further development.
Time to market is everything.
Power management is also really hard to get right 100% of the time. It's really hard to debug code/hardware where stuff is shutting itself off, or worse, a controller uP is shutting you off unexpectedly.
It has NOTHING to do with 'bad code' or 'shitty programmers'. It's just management grinding down on the engineers to do it: better, faster, cheaper, pick two. Usually faster and cheaper win.
http://nvidia.custhelp.com/cgi-bin/nvidia.cfg/php/enduser/std_adp.php?p_faqid=2243 Pretty straight forward. Regular PC laptops with the dual/triple gpu's can use Nvidia's Hybrid SLI.
Maybe it's because you've used Windows since release 1.0, have a ton of applications for it, and just want to run them on a really sharp looking laptop?
IMO Apple would do well to open up their market a bit and offer MacBooks preloaded with Windows. They would destroy Dell & HP in the high end market.
To do something like that, it must be supported by the drivers. As an example a coworker got a new Thinkpad with that feature, may have been the same one you got not sure. The switching works fine in XP. However he wanted to run the Windows 7 RC on it. There, we couldn't get it to work, I had to go in to the BIOS and shut down the Intel card. Why? No Windows 7 drivers for it. In fact at the time, Lenovo had no 7 drivers at all. All drivers had to be obtained from manufacturers of the various parts.
Any feature like this that deals with hardware must be supported in drivers. That is the responsibility of the OEM that puts the computer together. They don't necessarily write the drivers, but they work with the companies that make the hardware to get drivers for the OSes they wish to support. If Apple elects not to release drivers for Windows that support that, well then it won't work.
Yep.....
http://arstechnica.com/apple/news/2007/08/mac-os-x-leopard-receives-unix-03-certification.ars
Why not?
I, for one, have a Mac and a technet subscription - the only reason I don't have the RTM downloading right now is because I've only just signed up and am waiting for my account to be processed.
ANYONE is free to get a technet subscription and get access to any and all microsoft products (for time-unlimited "evaluation" on unlimited machines for personal use) for about the same price as a copy of Windows ultimate.
If you're a geek (i.e., the type of person to run bootcamp) and want a copy of Windows RTM now, its "generally available" so long as you have broadband and about 300-400 bucks.
I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
> Someone subscribed to TechNet or MSDN is not going to be running Windows 7 on a Mac.
Actually, I think you're 180 degrees wrong. If you're switching to the Mac for the hardware only, you're specifically running Windows, it's quite likely you're a Windows developer. There is MS Office Mac for business users, and creative people discover the Mac tools and never go back, and Web-oriented people get the real HTML 5 Web out-of-the-box on Mac OS, but if you program in C Sharp and .NET then you have to run Windows and Microsoft's tools. You can switch to Mac but you're keeping Windows.
I've heard from a few different developer types that they were at conferences and they'd be at a table with 10 developer nerds and 10 MacBook Pros, but if you go around and look it was actually like 4 Mac OS, 2 Linux, and 4 XP. I heard from at least one Windows developer that he switched to Mac hardware so he could reboot in Mac OS X and make iPhone/iPod apps in addition to booting into Windows to make Win32 apps as before. He can't be the only guy who had that idea, it is a great one. And there is a blog called .NET Addict that has a Mac Pro grille in the masthead, the guy is using MacBook Pro and Mac Pro to do his MSDN programming and not only loving it, but sharing that far and wide.
A key thing is that Apple has 90% market share in $1000+ PC's, they have taken the high-end PC market in the same way they took the music player market with iPod. Developers typically want high-end hardware because they're going to use it everyday and they want compiles to be fast and because they want to focus while they're working on the code they're writing, not troubleshooting their workstation (even if they have those skills.) And installing Windows from scratch is actually a feature for developers, they can install it all exactly how they want.