Exploring Windows 7 on the Mac: installation via Boot CampMac users who have a need to run Windows applications or games may have good reason to keep an eye on the development of Windows 7, due for release later this year. Among its features are easier setup and installation.
This series looks at the features Windows 7 offers to Mac users, and what is involved in moving from XP. This segment looks specifically at how Windows 7 differs from Mac OS X in setup and installation, and how Microsoft has made improvements over the experience offered by XP and Vista.
Mac users have a number of reasons to install Windows; some might want to run Windows in a virtual environment such VMwares Fusion, Parallels Desktop, or Suns free VirtualBox to run a custom corporate app (or some other software that only works on Windows), right on the Mac OS X desktop.
Others might want to install Windows natively on their Mac using Boot Camp for full the performance required to run many Windows-only games. And many Mac users are also owners of generic PCs, and want to setup their Windows PC to share files and sync data with their Mac.
Portions of this article will apply to all these users, with a focus on Mac users who install Windows (and Windows 7 in particular) directly on their Mac using Boot Camp. A previous article looked at what is involved in installing Windows 7 within a virtual environment.
Using Boot Camp
While Apples Boot Camp Utility (below) is sometimes portrayed as a translation layer that allows Windows to run on Mac hardware, it is really just a two-step preparation tool that first formats the boot drive so that Windows can be installed, and then provides the installed copy of Windows with Apple-supplied driver software to properly access all of the unique hardware on Macs.
Neither of these steps are necessary when running within a virtual environment, as those tools both run Windows from a virtual disk image that sits in the regular Mac OS X file system, and supply drivers for the virtual hardware they emulate, presenting a generic PC environment of standard network, graphics, and other virtual components to whatever version of Windows is installed.
Reformatting the disk with Boot Camp
If your hard drive is full or nearly full, you might have some initial pains preparing for Boot Camp. Youll need at a minimum 15 GB of free disk space to install Windows 7, and by free we mean really free; if you throw away just enough files to give yourself 15 GB, chances are your drive will still have files scattered around to the point that Boot Camp wont actually be able to clear out a partition space for Windows.
Thats because Boot Camp doesnt just allocate for Windows some of your drives disk space; it actually reformats the entire disk in place, lopping off a contiguous area of the disk to set up a blank disk partition, and shrinking down your boot volume to account for the difference.
This is a potentially dangerous operation, so make sure you have a full backup of your drive, either using a disk cloner utility or Time Machine to backup to an external USB drive or network server such as Time Capsule.
While weve never experienced any problems with repartitioning the disk in place, it makes no sense to perform this high wire act without a net, because any interruption or disk error could result in an invalid partition map and an unreadable volume that very likely cant be recovered.
Once you identify the amount of space you want to allocate for Windows, Boot Camp moves around your files on disk like Tetris pieces to create a free contiguous area it can partition for Windows. If it runs into too many files that cant be moved, it will ask you to solve the problem by imaging your drive to another disk and then moving it all back.
That operation, which can be done using Disk Utility, takes some time. Youll need to first select your drive and create an image of it (below) on another drive (such as an attached USB drive), then put your system in Firewire target mode and restore the image to the disk using another system. Another option would be to boot your system up from your Mac OS X install DVD and run Disk Utility from the disc to restore the image to your boot drive.
It may also be possible to defrag your drive using a disk optimization tool such as iDefrag, which can sometimes move around files that Boot Camp wont.
Ideally, Boot Camp will be able to find enough room to make those steps unnecessary. Even so, it will take some time (as much as a couple hours) for Boot Camp to complete the repartitioning step. Also, keep in mind that Boot Camp only knows how to start with a drive with one partition, so if youve already partitioned your boot disk, Boot Camp will insist you reformat it back to one single partition first.
Once complete, your drive will show up with two usable partitions, the first being your regular Mac boot drive, and the other with a horrible name along the lines of disk0s3. That stands for disk 0, slice 3, where slice means partition. There are two other invisible partitions, slice 0, the partition table, and slice 1, a 200 MB partition allocated to EFI. (Remember when the whole drive was less than 200 MB?) Slice 2 is your original Mac partition.
Making Windows feel at home on the Mac
Windows doesnt really know how to handle GPT, the type of partition table used by EFI, the boot firmware system used on all Intel Macs (and their equivalent to the OpenFirmware used by PowerPC Macs). However, Intel developed EFI with Windows in mind, so it made the standard backward compatible with MBR, the simpler partitioning scheme used by generic PCs that still depend upon BIOS rather than EFI.
Windows, including the new Windows 7, expects to find a BIOS boot environment and an MBR (master boot record) to identify the disk partition to be used during installation. Boot Camp prepares a dummy MBR in the GPT that identifies the new partitions it created, and the Macs EFI firmware pretends to be BIOS for Windows during the reboot process.
That allows Mac users to simply insert a Windows install DVD and directly boot from it; the software thinks its installing on an old fashioned, generic PC when really its running on a state-of-the-art EFI PC made by Apple.
Among other things, the fancy EFI firmware that Macs use support the same kinds of Mac-only features OpenFirmware has long provided, including:
Firewire target mode, which makes the disks partitions visible to another system via Firewire
Option boot for selecting a startup disk and partition at reboot
C boot for starting up from an optical drive
BIOS PCs have to manually configure the boot volume, and cant boot the system into target mode. They also typically only offer experimental-quality USB booting, something Microsoft doesnt officially support in Windows. That greatly complicates the task of trying to install Windows on an external USB drive, making it something that Apples Boot Camp subsequently doesnt support either.
Brave souls can download an EFI utility and edit their copy of the Windows installer to attempt to install Windows on an external USB disk, but this isnt a task for the faint of heart. Install Windows to a Macintosh USB drive (without Bootcamp). « Tube Shards
While Windows cant take advantage of all the benefits of the Macs modern firmware, EFI does make it easy to select between Mac OS X and Windows at boot, and also enables the system to select the desired boot device from within either operating system (using Apples supplied control panel under Windows), something Windows cant do when running on a dual-booting, generic PC.
Direct installation of Windows using Boot Camp
The install process of Windows keeps getting more sophisticated. The new Windows 7 beta is now on par with the first releases of Mac OS X. Starting with Windows 2000, Microsoft moved its desktop operating system from a DOS-based startup and installer to one using the NT kernel. However, Windows still dropped down into text mode during the installation, just as NeXTSTEP, the predecessor to Mac OS X, once did. The Windows install experience is now entirely graphical from the initial screen (below top) thorough the install progress steps (below bottom), which are presented as if in an active, Aero-styled window (albeit non-functional, as the window is only ornamental).
Apples Mac OS X installer boots a pared down version of Mac OS X from the DVD to run its install process. That enables the install DVD to also run some handy and familiar Mac OS X apps prior to the install process, including the full version of Disk Utility for examining, verifying, and formatting volumes. The Windows 7 installer runs as a custom system with some integrated options for performing just a few disk operations.
One is required when installing Windows 7 on the partition prepared by Boot Camp, because Windows 7 demands an NTFS disk partition to begin installing. In the install image below, Windows reports seeing all of the disk partitions, although it thinks the GPT partition 0 is unallocated.
The partition we want to install Windows on is partition 3, labeled BOOTCAMP, but the installer says thats not possible. To get around this problem, click on Drive options (advanced), which reveals the option to Format partition 3 (below). Click Ok to dismiss the warning that the partition might have something on it (it doesnt). The format is done rapidly, as the FAT volume only needs a quick NTFS volume format written on it.
Once that step is past, Windows 7 installs itself for about a half hour, then presents some installation options related to setting up an initial user account, automatic system update preferences, and the new HomeGroup sharing features. Windows 7 then sets up networking, allowing you to select a WiFi network and log in. If you allow it, Windows 7 immediately downloads and installs a couple of updates, although they arent actually identified until they are being installed.
On page 2 of 2: Easy drivers with Boot Camp; and Installing third party security and Apple apps for Windows.