# Apple–Intel architecture

The Apple–Intel architecture, or Mactel, is an unofficial name used for Macintosh personal computers developed and manufactured by Apple Inc. that use Intel x86 processors, rather than the PowerPC and Motorola 68000 ("68k") series processors used in their predecessors or the ARM-based Apple silicon SoCs used in their successors. As Apple changed the architecture of its products, they changed the firmware from the Open Firmware used on PowerPC-based Macs to the Intel-designed Extensible Firmware Interface (EFI). With the change in processor architecture to x86, Macs gained the ability to boot into x86-native operating systems (such as Microsoft Windows), while Intel VT-x brought near-native virtualization with macOS as the host OS.

## Technologies
### Background

Apple uses a subset of the standard PC architecture, which provides support for macOS and support for other operating systems. Hardware and firmware components that must be supported to run an operating system on Apple-Intel hardware include the Extensible Firmware Interface.

### The EFI and GUID Partition Table

With the change in architecture, a change in firmware became necessary. Extensible Firmware Interface (EFI) is the firmware-based replacement for the PC BIOS from Intel. Designed by Intel, it was chosen by Apple to replace Open Firmware, used on PowerPC architectures. Since many operating systems, such as Windows XP and many versions of Windows Vista, are incompatible with EFI, Apple released a firmware upgrade with a Compatibility Support Module that provides a subset of traditional BIOS support with its Boot Camp product.
GUID Partition Table (GPT) is a standard for the layout of the partition table on a physical hard disk. It is a part of the Extensible Firmware Interface (EFI) standard proposed by Intel as a substitute for the earlier PC BIOS. The GPT replaces the Master Boot Record (MBR) used with BIOS.

## Booting
### To Mac operating systems

Intel Macs can boot in two ways: directly via EFI, or in a "legacy" BIOS compatibility mode. For multibooting, holding down "Option" gives a choice of bootable devices, while the rEFInd bootloader is commonly used for added configurability.
Legacy Live USBs cannot be used on Intel Macs; the EFI firmware can recognize and boot from USB drives, but it can only do this in EFI mode–when the firmware switches to BIOS mode, it no longer recognizes USB drives, due to lack of a BIOS-mode USB driver. Many operating systems, such as earlier versions of Windows and Linux, could only be booted in BIOS mode, or were more easily booted or perform better when booted in BIOS mode, and thus USB booting on Intel-based Macs was for a time largely limited to macOS, which can easily be booted via EFI.

### To non-Mac operating systems

Booting to non-Mac operating systems is possible by holding the option key while booting to select an operating system other than macOS to which the user would like to boot.
On April 5, 2006, Apple made available for download a public beta version of Boot Camp, a collection of technologies that allows users of Intel-based Macs to boot Windows XP Service Pack 2. The first non-beta version of Boot Camp is included in Mac OS X v10.5, "Leopard."

## Differences from standard PCs

Intel-based Mac computers use very similar hardware to PCs from other manufacturers that ship with Microsoft Windows or Linux operating systems. In particular, CPUs, chipsets, and GPUs are entirely compatible. However, Apple computers also include some custom hardware and design choices not found in competing systems:
* System Management Controller is a custom Apple chip that controls various functions of the computer related to power management, including handling the power button, management of battery and thermal sensors, among others. It also plays a part in the protection scheme deployed to restrict booting macOS to Apple hardware (see Digital Rights Management below). Intel-based Mac doesn't implement TPM.
* Laptop input devices. Early MacBook and MacBook Pro computers used an internal variant of USB as a keyboard and trackpad interconnect. Since the 2013 revision of MacBook Air, Apple started to use a custom Serial Peripheral Interface controller instead. The 2016 MacBook Pro additionally uses a custom internal USB device dubbed "iBridge" as an interface to the Touch Bar and Touch ID components, as well as the FaceTime Camera. PC laptops generally use internal variant of the legacy PS/2 keyboard interconnect. PS/2 also used to be the standard for PC laptop pointing devices, although a variety of other interfaces, including USB, SMBus, and I2C, may also be used.
* Additional custom hardware may include a GMUX chip that controls GPU switching, non-compliant implementations of solid-state storage and non-standard configurations of HD Audio subsystem.
* Keyboard layout has significant differences between Apple and IBM PC keyboards. While PC keyboards can be used in macOS, as well as Mac keyboards in Microsoft Windows, some functional differences occur. For example, the Alt (PC) and ⌥ Option (Mac) keys function equivalently; the same is true for ⊞ Win (PC) and ⌘ Command (Mac) – however, the physical location of those keys is reversed. There are also keys exclusive for each platform (e.g. Prt Sc), some of which may require software remapping to achieve the desired function. Compact and laptop keyboards from Apple also lack some keys considered essential on PCs, such as the forward Delete key, although some of them are accessible through the Fn key.
* Boot process. All Intel-based Macs have been using some version of EFI as the boot firmware. At the time the platform debuted in 2006, it was in a stark contrast to PCs, which almost universally employed legacy BIOS, and Apple's implementation of EFI did not initially implement the Compatibility Support Module that would allow booting contemporary standard PC operating systems. Apple updated the firmware with CSM support with the release of Boot Camp in April 2006, and since the release of Windows 8 in 2012, Microsoft has required its OEM partners to use UEFI boot process on PCs, which made the differences smaller. However, Apple's version of EFI also includes some custom extensions that are utilized during regular macOS boot process, which include the following:
** Drivers for the HFS Plus and APFS file systems with support locating the bootloader based on the "blessed directory" and "blessed file" properties of HFS+ and APFS volumes. The EFI System Partition is thus not used or necessary for regular macOS boot process.
** Rudimentary pre-boot GUI framework, including support for image drawing, mouse cursor and events. This is used by FileVault 2 to present the login screen before loading the operating system.
** Other non-standard EFI services for managing various firmware features such as the computer's NVRAM and boot arguments.
Some of these differences can pose as obstacles both to running macOS on non-Apple hardware and booting alternative operating systems on Mac computers – Apple only provides drivers for its custom hardware for macOS and Microsoft Windows (as part of Boot Camp); drivers for other operating systems such as Linux need to be written by third parties, usually volunteer free software enthusiasts.

## Digital rights management

Digital rights management in the Apple–Intel architecture is accomplished via the "Dont Steal Mac OS X.kext," sometimes referred to as DSMOS or DSMOSX, a file present in Intel-capable versions of the macOS operating system. Its presence enforces a form of digital rights management, preventing macOS being installed on stock PCs. The name of the kext is a reference to the macOS license conditions, using the name used for the OS at that time, which allow installation on Apple hardware only. According to Apple, anything else is stealing macOS. The kext is located at /System/Library/Extensions on the volume containing the operating system. The extension contains a kernel function called page_transform that performs AES decryption of "apple-protected" programs. A system lacking a proper key will not be able to run the Apple-restricted binaries, which include Dock, Finder, loginwindow, SystemUIServer, mds, ATSServer, backupd, fontd, translate, or translated. If the check fails, a short poem is displayed, reading "Your karma check for today: There once was a user that whined, his existing OS was so blind, he'd do better to pirate an OS that ran great, but found his hardware declined. Please don't steal Mac OS! Really, that's way uncool. (C) Apple Computer, Inc."
After the initial announcement of first Intel-based Mac hardware configurations, reporting a Trusted Platform Module among system components, it was believed that the TPM is responsible for handling the DRM protection. It was later proven to not be the case. The keys are actually contained within the System Management Controller, a component exclusive to Apple computers, and can be easily retrieved from it. These two 32-byte keys form a human-readable ASCII string copyrighted by Apple, establishing another possible line of legal defence against prospective clone makers.

## Virtualization

The processors found in Intel Macs support Intel VT-x, which allows for high performance (near-native) virtualization that gives the user the ability to run and switch between two or more operating systems simultaneously, rather than having to dual-boot and run only one operating system at a time.
The first virtualization software for Intel Macs was Parallels Desktop for Mac, released in June 2006. The Parallels virtualization products allow users to use installations of Windows XP and later in a virtualized mode while running macOS. VirtualBox is another piece of virtualization software originally from Innotek (now Oracle Corporation), which had a first public beta release for Mac OS X in April 2007. It supports VT-x and can run multiple other guest operating systems, including Windows XP and later. It is available free of charge under either a proprietary license or the GPL.
VMware also offers a Mac virtualization product competing with Parallels called Fusion, released August 2007. VMware's virtualization product also allows users to use installations of Windows XP and later under macOS.
Regardless of the product used, there are inherent limitations and performance penalties in using a virtualized guest OS versus the native macOS or booting an alternative OS solution offered via Boot Camp.