Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

TheLandOfSmeg

macrumors newbie
Aug 7, 2006
7
0
I have a Late 2006 MacBook Pro. I installed Windows 7 32-bit, then I installed Boot Camp 2.0 from the Leopard DVD (as the Boot Camp 2.1 update wouldn't run), rebooted, and then I was planning to install the 2.1 update.

After rebooting, the desktop loads for a few seconds and then the whole computer hangs. This only happened after installing Boot Camp 2.0. I have tried booting into Safe Mode and disabling a heap of stuff (Radeon X1600 drivers, Firewire, Ethernet, Bluetooth, iSight, etc.) but it still won't boot.

I narrowed down the cause of my rebooting problem to the C:\Program Files\Boot Camp\KbgMgr.exe startup entry. I am not sure why having it in Startup causes a complete system hang, while starting it separately from startup just causes it to crash ("has caused a problem and has been closed").
 

buddhaface

macrumors member
Jan 24, 2009
32
0
No!

No, that's Windows. It can't power manage. You see this in XP and Vista as well. OS X is great at power management.

No. It has nothing to do with Windows power management, but rather Bootcamp's crappy Apple drivers and EFI emulation of the BIOS.

Running Windows via Bootcamp will insure that you get about one-half the battery life of a generic PC running Windows with the same battery capacity and graphics card.

I bet you are the type of person to also compare on your Mac the boot-up times of Windows in Bootcamp against OS X, and then declare Windows to be slow, while clearly forgetting the EFI emulation step used in Bootcamp.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.