How to install clean OS X Mavericks on a Mac running a newer version of OS X (macOS). How to install Mac OS X on a regular PC

Sooner or later the day comes when you need to reinstall the Mac OS operating system on your MacBook PC. This task is no more difficult than reinstalling Windows. This is what we will talk about.

operating system on MacBook

The reasons for reinstalling the MacOS operating system on a Mac computer are as follows:

  • Damage or wear of the built-in storage device (HDD);
  • selling or donating a MacBook to another person;
  • “moving” to another MacBook (a newer model, but maintaining the previous version of the MacOS system);
  • transferring data to Apple gadgets or to another computer.

What happens when reinstalling MacOS:

  • “from scratch”, including formatting the built-in disk;
  • reinstallation “on top”, preserving personal data and applications (macOS update).

For example, using the MacAppStore, you can upgrade your version of OS X Lion and OS X Mountain Lion to a newer version - OS X Mavericks.

Here are the steps to follow when selling or transferring your Mac to someone else. It deserves special mention.

  1. Backup personal data from a MacBook to a separate media or cloud service.
  2. Disabling special services and functionality that manage data copying and transfer.
  3. Erase all personal information from the disk.

Attention! Before you start reinstalling MacOS on your MacBook PC, take the trouble to save all your data on an external drive! This will be discussed first.

Backing Up Data Using Time Machine

The Time Machine application is designed to backup personal files from a MacBook and restore them back to it. But it requires external USB drives (HDD, SDD drives) formatted in MacOS Extended or Xsan - FAT/NTFS file systems designed for Windows and Android are not supported. If the disk was previously formatted in FAT/NTFS formats, the MacBook will not accept it if you refuse to reformat it “for yourself.”

The Time Machine application is launched from the MacOS system preferences in the Apple menu. When you connect an external hard drive, a corresponding notification will appear.

Do you really want to destroy all data recorded on this drive in a different format?

If the external drive has already been formatted, the Time Machine application will give the go-ahead for its use. Confirm your request.

Do you really want to copy your data to this drive?

If Time Machine does not show disk selection, do the following.


Interestingly, backups in the Time Machine program are fully automated - the backup copy is “refreshed” hourly, and their storage is organized, so you won’t get lost in them. In addition, copying is also possible to an Apple server (like iCloud) and to local network storage that supports the Apple File Protocol. All this often helps, if you need to reinstall MacOS, to avoid losing precious working time.

After copying all your data, you can start reinstalling MacOS.

Reinstalling MacOS on Mac

There are several ways to reinstall the MacOS operating system on a MacBook: a “clean” installation from a flash drive, installation “over” a previous version (updating from MacAppStore) and restoring MacOS from a backup.

How to reinstall Mac OS from an installation flash drive

The preliminary steps are as follows.

  1. Download the Mac OS X installation image from the Mac App Store or third-party sites.
  2. Once the download is complete, right-click on the downloaded file and select “Show package contents.”
  3. Go to the /Contents/SharedSupport/ folder, copy the InstallESD.dmg file to a safe location on your disk, and mount it to your MacOS desktop.

We will need the Disk Utility application included with MacOS. The next steps are as follows.


Disk Utility will create an installation flash drive automatically, and it does this operation quite reliably. When copying is complete, Disk Utility will notify you.

Congratulations! The MacOS installation flash drive has been created! You can restart your MacBook. Preparing to install MacOS is as follows.


All! MacOS installation has started. The MacOS operating system will install automatically - this will take 30-100 minutes, depending on the performance of your MacBook. After it, your PC will be immediately ready for use.

How to install the system without formatting the internal drive

Installing MacOS without erasing the disk means downloading and installing MacOS updates directly from the MacAppStore. An installation flash drive is not needed here. This is reminiscent of updating iOS on smartphones and tablets over the air. This method is good for those who once bought a MacBook - and are not going to change it, but, on the contrary, will work on it for many years, because MacBook computers, like Apple iDevice gadgets, are very high quality, reliable and convenient.

Before updating, check whether your MacBook meets the hardware requirements of the new version of MacOS - otherwise it will slow down.

Not every previous version of MacOS can be updated to the desired version. So, if your MacBook is running macOS Snow Leopard (10.6.8) and your MacBook will run macOS Sierra, first upgrade to macOS X El Capitan.

The version of MacOS Sierra is taken as an example. Other copies are searched for and “installed” in exactly the same way. Your actions are as follows.


If you have OS X El Capitan 10.11.5 (or more recent), the macOS Sierra version downloads silently. You will then be prompted to install this version.

Click on the install button

During the installation of MacOS, the PC restarts several times. If this version does not suit you (the performance of the MacBook has dropped), “roll back” to the previous one (for example, OS X El Capitan), with which the PC performance was very satisfactory.

Restoring MacOS from a backup

For example, we take a “rollback” from MacOS Sierra (10.12) back to OS X El Capitan (10.11) or OS X Yosemite (10.10). Let's say there are backups made in the Time Machine application before installing MacOS Sierra.

Important! You can only restore a MacOS system from a backup to the same MacBook. Trying to transfer your copy of the MacOS system with data to another PC in this way is useless. Use other methods.

  1. Connect your external drive to your MacBook and save your existing files to Time Machine, naming the new copy MacOS Sierra.
  2. Open your previous copy of OS X Yosemite with Time Machine on a different drive after connecting it to your MacBook.
  3. Restart your MacBook while holding Command+R on your keyboard. The familiar MacOS recovery menu will open.
  4. From the OS X Utilities menu, select Restore from Time Machine Backup.
  5. Once in the “Recover from Time Machine” recovery window, click on “Continue”, and then specify the source - the disk with the OS X El Capitan “backup”.
  6. The saved copy should be: In the case of OS X El Capitan, the MacOS version should be 10.11.x. Click the Continue button. Specify the installation disk to restore from a copy, click on “Restore”.

Ready! The OS X El Capitan version will be reinstalled.

Transferring a copy of the operating system and your data to another MacBook

Go to Programs/Utilities and open Migration Assistant. The structure of your files and folders will be preserved.

Click to continue

When running, the application requires closing all other running programs.

If both computers are working, but you still want to duplicate your version of MacOS and all data on the second computer, connect the computers to each other using a LAN cable via a Wi-Fi wireless network. Connecting directly using a Thunderbolt or FireWire cable will require running your previous Mac in backup mode, which will make the Assistant experience a little more complicated. However, both methods work clearly. You can connect an external disk with a backup copy to the new PC instead of the previous PC - in this case, the operation of the Assistant on the new PC will not change significantly.

So, the procedure is as follows. As an example, we take the normal operating mode of a previous PC with “Assistant”.


All! The copy session has started. This can take anywhere from 30 minutes to two hours, depending on the amount of data and the performance of both Macs.

Problems encountered when reinstalling MacOS

Problems when updating or “rolling back” may be as follows.

  1. No recent backups. You once disabled backup yourself. Copy your files now to avoid losing them by starting the process manually. Enable backup.
  2. An error occurred during the next backup or when restoring personal data from a previous copy. The external drive that was previously recorded is unsuitable for further use. Contact an Apple service center or certified computer repair shop to restore your data. This procedure is not free.
  3. Error during the next MacOS update. Your Mac PC may no longer be supported. This happens once every few years. You will continue to use the current version of MacOS until you replace your Apple PC.
  4. The computer began to work noticeably slower than before the update. The minimum system requirements of the next new version are equal to or exceed the technical specifications of your PC. “Roll back” to any previous version of MacOS. Typically, Apple tries to prevent this from happening - it simply stops supporting older computers, just as it is no longer possible to install iOS 10.x on iPhone 4x devices.
  5. After several active years, your PC suddenly began to freeze despite the fact that you did not update MacOS. Maybe it's time to replace the internal HDD/SSD drive? Try to back up your important data before replacing the internal drive - while something is still being read from it.
  6. It is impossible to “roll back” to one of the previously installed versions of MacOS. The “rollback” must be done gradually. If there are no previous backups, download a new “image” and “roll back” to this version first, and then repeat the “roll back” to an even earlier version of MacOS.

Video on the topic

Reinstalling MacOS - “on top” or “from scratch” - is not difficult. It is only important to secure your data. This is a real way to extend the life of your beloved MacBook for another number of years. You will succeed!

This manual/guide/etc was written for those who are too lazy to piece together this or that information about installing a Mac on a PC, everything is clear and straightforward.

To begin with, before actually installing the system itself on a PC, we need to decide whether we need it or not, since the system itself is very specific in terms of installation and configuration, unless, of course, you have an Apple device. There is no point in explaining that deploying a system that was not originally planned for desktop PCs is a complex matter and it can take anywhere from 2 to N hours, depending on the compatibility of the hardware.

Now, let’s figure out what Hackintosh is: the word “hackintosh” was formed from the merger of two words “Macintosh” and “Hack”, which essentially means “hacked Mac”, although there is nothing to do with “hacking”.

In this guide, we will look at creating an installation flash drive from Windows (since this is the most popular system among “beginner hackintoshers”), installing the system on a blank disk, kernel extensions for your hardware and, in fact, installing and configuring the bootloader (it is at this point that many and problems arise)

CPU: Intel Core i5 4460 3.2 GHz (Haswell)
Memory: 16 GB Crucial Ballistix Sport
Graphics: MSI GeForce GTX 760 2048MB
Motherboard: Gigabyte GA-H81-S2V (UEFI Bios)

I would also like to point out that in this article we work with NVidia video cards and UEFI BIOS.

Well, let's go.

Step 1. Iron assessment and analysis

Yes, despite the fact that Hackintosh runs in one way or another on almost any configuration, it always does it differently. Therefore, it’s worth immediately analyzing our hardware.

Processors

So, let's start with the fact that on machines with AMD processors the system WILL NOT work(it is very difficult to call the dying state of agony in which she will arrive “work”). Yes, in fact, you can install a custom kernel, reflash it, and so on, but there’s no point in reinventing the wheel if it breaks anyway. The system runs without problems on Intel processors, starting with Core i3 (we are talking specifically about macOS Sierra 10.12; previous releases can also run on Core 2 Duo and Pentium processors). In my case, the i5 4460 stone fell out (4 cores, 4 threads, turbo boost up to 3.4 GHz).

ACHTUNG 2

Problems are observed on socket 2011-3 processors, in particular on the X99 chipset. Usually it appears due to too many bells and whistles on the motherboard.

Video cards

List of supported Intel graphics cores

Intel HD 3000
Intel HD 4000
Intel HD 4600 (laptops)
Intel HD 5000

Radeons (AMD) start, but again with a bang. For example, new cards (RX-4**), as well as the well-known R9 380 or R9 380x, can simply display the loading in a black screen.

List of exactly supported AMD cards

Radeon HD 4000 series
Radeon HD 5000 series
Radeon HD 6000 series (Preferably 6600 and 6800)
Radeon HD 7000 series (Preferably 7700, 7800, and 7900)
Radeon R9 200 series (R9 290 does not start)
Radeon R9 300 series (There may be problems with the R9 380. I haven’t personally tested it, but judging by the reviews on Reddit with these cards There is Problems)

In this manual we will not consider the AMD graphics plant, since it all comes down to framebuffer patches and Device ID changes in the bootloader (which is individual for everyone). More information about AMD cards here: click (English).

The situation is completely different with cards from NVidia. Almost everyone gets turned on, with the exception of some especially gifted ones. Problems are observed in the 10th episode, but most likely they will not appear soon. On GTX cards, the graphics start up with half a kick, GT cards are also not lagging behind, although there are some exceptions.

List of working NVidia cards

GeForce 7000 series
GeForce 8000 series
GeForce 9000 series
GeForce 200 series
GeForce 400 series
GeForce 500 series
GeForce 600 series
GeForce 700 series
GeForce 900 series

I am more than sure that you will find your card in the list.

Network Controller

I think there is no need to chew on how you can identify your network card...

Newby guide

Open the Task Manager → performance tab → Ethernet (Windows 10), there will be a network connection in big black letters.

By the way, you can also look in the BIOS

One way or another, we will not dwell on this in detail. In any case, you will have to install a network card, so I will simply provide a list of supported network cards.

Network cards

Intel Gigabit

5 Series – 82578LM/82578LC/82578DM/82578DC
6 and 7 Series – 82579LM/82579V
8 and 9 Series – I217LM/I217V/I218LM/I218V/I218LM2/I218V2/I218LM3

Realtek

RTL8111, 8168, 8101E, 8102E, 8131E, 8169, 8110SC, 8169SC
RTL8111/8168 B/C/D/E/F/G
RTL8101E/8102E/8102E/8103E/8103E/8103E/8401E/8105E/8402/8106E/8106EUS
RTL8105/8111E/8111F/8136/8168E/8168F

Atheros

AR8121, 8113, 8114, 8131, 8151, 8161, 8171, 8132,8151, 8152, 8162, 8172
AR816x, AR817x supported

Broadcom

BCM5722, 5752, 5754, 5754M, 5755, 5755M, 5761, 5761e, 57780, 57781, 57785,5784M, 5787, 5787M, 5906, 5906M, 57788, 5784M

Marvell

88E8035, 88E8036, 88E8038, 88E8039, 88E8056, 88E8001

Killer

Memory

There are no restrictions. The system runs on two gigabytes. Recommended 4. Author recommends 8.

Actually, we sorted out the hardware. If at this stage you have not changed your mind, move on.

Step 2. Make a bootable USB flash drive and deploy the installer to it

So, here we come to practice. Let me remind you that we do all this from Windows. I’ll say right away that we will not use images from the root tracker, which are so ardently recommended by people for whom everything works with hackintosh “up to 18”. First, we need the BDU (BootDiskUtiliy) utility.

You will need a flash drive >8 GB. Any.

1. Launch the utility
2. Destination disk → select our flash drive
3. Format disk

Now we wait. The flash drive will be formatted in Apple HFS and split into two partitions, one of which will have the bootloader installed (CLOVER), and the second will remain blank so that the installer can be deployed there.

After the completed manipulations we get approximately the following picture:

Next, you need to deploy the installer to the second partition. We also do this through the BDU utility. However, the question here is where to get the image from. There are two options: take a ready-made one, already unpacked, or personally get it from Install Mac OS Sierra.app from the AppStore. Since the second method requires quite a lot of time, and searching for this .app itself takes a very long time, we will use the first. Craftsmen have already prepared ready-made HFS files for this utility and extracted them from the .app for us. All we need is to download it (the image weighs almost 5 gigs, so you can just put it on download). Actually, download macOS 10.12 Sierra from here.

1. We extract from the archive HFS Partition File (HFS+), a file with the extension .hfs.
2. In the BDU “Destination disk” utility window, select Part 2 of our broken flash drive.
3. Open “Restore partiton”.
4. Search and select our *.hfs file. Please note that it must be no larger than PART 2 partition.
5. We are waiting for it to be unpacked.
That's it, the installer on the flash drive is unpacked and ready to go.

Now we will need some files for your system. I have collected everything I need in this archive. Later I will explain what and why.

You will also need this kext, download it too: click. We unpack the folder from the archive into the root of the Clover partition, and the kext into the folder that we unpacked. All is ready. The flash drive is done. Go ahead.

Step 3: Install macOS Sierra on Intel PC

We check that the flash drive is inserted into the 2.0 port. Reboot, go into BIOS. Let me remind you that our BIOS is UEFI. Disable virtualization (Intel Virtualization). Set boot priority (BOOT) to our flash drive. Make sure that it will boot in UEFI mode. Save and apply the settings, reboot. We get to Clover’s menu.

Clover is a Hackintosh downloader and installer.

Press the down arrow until we get to the Options menu. Press Enter. All we need here is this line:

We write the following into it:

< span class = "hljs-attr" >kext - dev - mode = 1< / span > < span class = "hljs-attr" >rootless = 0< / span >- v< span class = "hljs-attr" >npci = 0x2000< / span > < span class = "hljs-attr" >nv_disable = 1< / span >

Let me explain what each of these arguments does:

kext-dev-mode=1 is a necessary arg, without which the hack will not run. Allows you to load kexts into the system (Initially, FakeSMC.kext).
rootless=0 - disables SIP (System Integrity Protection). Required arg.
-v - “Verbose mode”. Instead of a beautiful apple, we will see a “console” loading so that we can identify an error if one appears.
npci=0x2000 (or 0x3000, depending on the PCI-e version) - optional. We prevent the download from stopping at the PCI scanning stage. You don't have to register it.
nv_disable=1 - optional. To avoid loading artifacts and other garbage, disable the graphical shell. We load in native graphics mode in Orthodox 144p resolution. You don't have to register it.

Apply the arguments by pressing Enter. Select Boot Mac OS Sierra from OS X Base System. And so, the birthplace download began. Let's look at some errors right away: still waiting for root device - the IDE controller does not have time to connect.

Fix

We reconnect the flash drive to another 2.0 port, boot with the following arguments:
kext-dev-mode=1 rootless=0 cpus=1 npci=0x2000 -v UseKernelCache=No

Missing Bluetooth controller transport - the video card did not turn on, or FakeSMC.kext was not connected. Check that there is FakeSMC.kext in the kexts/other folder. Bluetooth has nothing to do with it.

Fix

We load like this:

kext-dev-mode=1 rootless=0 -v npci=0x2000
Or like this:
kext-dev-mode=1 rootless=0 -v -x npci=0x2000

If such errors still remain, then we try to load like this:

< span class = "hljs-attr" >kext - dev - mode = 1< / span > < span class = "hljs-attr" >rootless = 0< / span >- v< span class = "hljs-attr" >npci = 0x3000< / span > < span class = "hljs-attr" >darkwake=0< / span > < span class = "hljs-attr" >nv_disable = 1< / span > < span class = "hljs-attr" >cpus = 1< / span >

In other cases, only Google will help, although these fixes should solve these problems.

We wait. At some points it may freeze. If it freezes for more than a minute, reboot. Should help in some cases.

And here we are, actually, in the installer. Select a language and click on the arrow. The language pack will load (it may freeze for a minute). Now open Utilities>Disk Utility, we need to format the disk for macOS. Select the desired disk and click “Erase”. For convenience, we call the new disk “Macintosh HD”. Format and close Disk Utility. Next, select the disk on which we will install the system (in our case, Macintosh HD), and install it.

Installation takes from 15 to 30 minutes, it all depends on the speed of writing to the disk. After installation, the system will prompt us to set up an Internet connection - skip it, we’ll do this later. We create a user. Done, we're in the system. Or rather, in her stump. Nothing is working for us yet. If you reboot the machine, it will be impossible to get into the system (due to the absence of a bootloader).

Fix

If the computer still reboots or switches off, you can choose to boot from a flash drive, then select “Boot macOS Sierra from Macintosh HD” in the clover menu, not forgetting to write boot arguments in the options menu.

Step 4. Basic system setup and installation of kexts

So, here we are in the system. While she can do little, we won’t go online, the graphics don’t work, and in general everything looks very bad. This needs to be fixed.

Let's figure out what kexts are.

Kext(Kernel Extension) - kernel extensions that run this or that equipment that is incompatible with the original Mac (For example, where in the aimak can we find a network card from Realtek or a sound card?). These are what we need now.

First, we need the PostInstall folder, which you unpacked into the CLOVER partition on the bootable USB flash drive. From there, we first need the Kext Utility, which allows us to install kexts on the system. We launch it, enter the user’s password, wait until we see the inscription “All done”.

We install the kext on the network card (Network folder, sorted into folders for each network card), simply drag it into the program window. We wait until the “All done” message appears. Next, go to the CLOVER section of our flash drive, then to kexts, then to Other. Copy FakeSMC.kext from there to any place (Better in the same PostInstall), then install it in the same way as the kext on the network card. You will also need a USB 3.0 kext. It was in the Legacy_13.2_EHC1.kext.zip archive, which you extracted in PostInstall. Let's install it.

Done, we set up the Internet, USB and allowed the system to boot at all (FakeSMC.kext imitates the System Management Control chip, which is present only on Apple motherboards. Without this kext, the system simply will not start).

Now let's install the bootloader. Go to the PostInstall folder → Clover_v2.3k_r3949. There is a *.pkg file, open it.

Click continue, read the information about the bootloader (I’m lying, click continue too). Next, in the lower left corner, click “Configure”.

For UEFI boot, set the following settings:

We'll talk about legacy loading later, since everything is a little more complicated there and you'll have to patch DSDT.
Click “Install”. Let's go through the bootloader installation process.
Done, the bootloader is installed.

Step 5. Bootloader setup

After installation, we will receive a clean, unconfigured Clover bootloader, which needs to be slightly configured. Open Clover Configurator (in the future I do not recommend using this program for point-by-point editing of the bootloader config).

First, we need to get to the EFI partition with the bootloader. In the left menu, click Mount EFI. Next, click Check partition, a table of all partitions will appear. The partition we need should be on the same partition as Apple_HFS, it appears as EFI EFI. Click Mount partition. In the list, select the disk we need (For example, disk0s1). Please note that there is a bug where all sections are not visible. Roll the mouse wheel so you can scroll between sections and select the one you need.

Next, click Open Partition. It will open a “folder” with the desired section. Go to EFI>CLOVER. Copy plist.config to the PostInstall folder for convenience. Also, just in case, copy it somewhere else, since the one we just copied will be edited. And one more for backup. Copy and open plist.config.

We see something like this:

ACPI - We don’t touch the fixes, we drop (DropOEM) our video card (DropOEM_DSM works when two DSDT patches are encountered. Therefore, we leave the original autopatch method as the bootloader, and disable ours, if one appears).
Go to the BOOT section.

So this is where we need to dig in. We set the arguments ourselves, depending on the system.

V (verbose) - the already familiar “text” boot mode. It is better not to enable it, but to register it manually if necessary.
arch - architecture. In my case x86_64
npci is a key already known to us. We post if necessary. I recommend doing the first boot without it, but in Verbose mode.
darkwake - responsible for sleep mode and hibernation. Has 7 modes. If the dream does not start by changing hibernatemode in the terminal, then I recommend using trial and error to find the desired darkwake mode.
cpus=1 - launch using only one core. I don't recommend choosing.
nvda_drv=1 - activation of the NVidia web driver, which we will install a little later. Choose if you have nVidia.
nv_disable=1 - disables non-video graphics and runs on the native Mac driver. It’s better not to select, but to register manually if necessary.
kext-dev-mode=1 and rootless=0 have already been explained earlier.

Let's go to the right subsection.

Default Boot Volume - the partition from which the disk selection to boot will begin by default. By default LastBootedVolume (last selected partition).
Legacy - Legacy Boot for older versions of Windows and Linux. It very much depends on the hardware and the design of the BIOS, so several algorithms have been developed:
LegacyBiosDefault - for those UEFI BIOSes that have the LegacyBios protocol.
PBRTest, PBR - PBR Boot options, this is just overkill. In my case PBR works.
XMPDetection=YES is an important parameter. Fixes the amount of RAM, slots, dies, frequency and number of channels.
DefaultLoader - if there are several loaders on the partition, select the default one. Must not be empty!
Timeout - time before automatic boot.
Fast - a parameter that skips the selection of a partition and immediately proceeds to downloading.
-1 (Timeout -1) - disable autoboot.

We skip the CPU section, the bootloader itself will pick up the necessary values. Devices is also better to skip if you have nothing to fake. Disable Drivers - disable unnecessary drivers at boot. GUI - customizing the appearance of the bootloader. I think there is no need to explain anything here, there are no special parameters here. Screen resolution, language and menu theme. It's simple. Graphics - graphics settings and injections.

Do not touch the Inject NVidia parameter! There will be artifacts at launch. It is designed to run older GT line cards

Kernel and Kext Patches - patches and kernel customization. By default, Apple RTC is selected. It's better not to touch. SMBIOS is the juice, customization and counterfeit of the poppy.

To configure factory information, click on the magic wand icon. Next, select iMac (if PC) or MacBook (if laptop).

ACHTUNG 3

You can also look among older configs, such as MacMini or Mac Pro. Your task is to choose the one that is most similar to your hardware.

Don't add anything to Memory and Slots. These are purely cosmetic parameters that clover picks up at the loading stage. Incorrectly set parameters can cause conflicts.

WARNING: Nvidia video cards without policy-kext edits only work on iMac13.1 and iMac14.2 Mac models.

In AppleGraphicsControl.kext/Contents/PlugIns/AppleGraphicsDevicePolicy.kext/Contents/info.plist we correct Config1 to none here:

It should work now.

Ready. We don’t touch anything else, we’ve done the basic settings. We save our file. Now copy it to the CLOVER folder of the EFI partition, log in, and replace it. Let me remind you that before this you should have made a backup.

Step 6. Install the graphics driver and reboot for the first time

We're almost there. Now all that remains is to start the video card. The PostInstall folder contains the WebDriver*.pkg package. Open it and install it. Then he asks us to reboot. Let's reboot.

Now let's make sure that we are not booting from a flash drive, but from hard drive in UEFI mode. Select Boot macOS Sierra from Macintosh HD. Let's start.

Note

I recommend using the -v switch for the first run, so that if something goes wrong, you can immediately identify the error. If the bootloader is broken and you cannot get into the system, then boot from the flash drive, enter the necessary keys in the options and boot the system into Verbose mode.

Done, here we are in the system. In the picture I showed approximately what the axis will look like after all the settings. Pay attention to how the system understood your Mac, as well as the processor frequency.

A sure sign that the Nvidia driver is working will be its logo on the taskbar. I turned it off, by the way, because it gets in the way, but you can access the invisibility control panel through “System Settings...”. We can check the Internet through Safari. USB 3.0 is trite by plugging a flash drive into a 3.0 port.

Additionally

- Sound

When it comes to sound, the situation is different. If you have an external sound card, then simply download the drivers for it from the manufacturer’s website (analog devices, such as mixing consoles, do not require drivers and start up immediately). For an integrated sound card, use one of these kexts:

Regarding AppleHDA

The following conditions must be met for it to work:

  1. Availability of vanilla (pure) kext AppleHDA.kext in the system.
  2. The presence of the HDEF section in your DSDT (or the clover fix FixHDA_8000->True)
  3. Specify the layout in DSDT (or in the config.plist of the clover Devices->Audio->Inject->1,2,28...etc. Select from those specified for your codec above)
  4. Put away ALL sound patches (if they were in your config.plist) from the KextsToPatch section
  5. Remove DummyHDA.kext (if used)
  6. If you used VoodooHDA.kext, delete it. Also delete AppleHDADisabler.kext and rebuild the cache.
  7. For Intel HDMI 4000/4600, a clover fix is ​​required: UseIntelHDMI->True

Actually, that's all. Afterwards we get macOS Sierra ready to work.

Last updated by at December 27, 2016.


You cannot write code for iPhone on PC. Apple party politics. Although the iPhone SDK is classic GCC, I don’t know of cases where it was written on a PC. But you can still install the iPhone SDK on a jailbroken device, write and run code directly on the phone/tablet.

There are rumors that installing MacOS on a regular PC is "difficult and uneasy".
In fact, it all depends on luck :) On luck and on hardware.
In my case, installing MacOS X was a little more difficult than installing Windows 7.

There are a lot of installation paths. I will describe the simplest and most straightforward one. Complex options are not for me. If something doesn’t work out, it doesn’t mean that you can’t install MacOS. Perhaps it is possible, but in more complicated ways. For laptops, you can look for ready-made images of boot disks (modified by craftsmen).

The latest line of Macs is just a regular PC. An ordinary PC with a slightly modified bios. And MacOS only has drivers for a limited set of devices that come with Macs.

There is no need to reflash the bios (although this is one of the possible ways). I now have MacOS X, Win XP, Win 7 running on one hardware. But I’ll have to look for the firewood (written by craftsmen, even in the source code).

Briefly: "Download a special boot disk, reboot from it, insert the original MacOS X DVD, install it, update it, search for and install drivers. That's it."


0. Setting up bios

Optional, but desirable part.

1. Set the SATA controller to AHCI mode (I have always had it as AHCI).
2. Turn ACPI on (some people advise, on the contrary, turn it off).
3. Switch HPET (timer) to 64-bit mode (I didn’t find one like that).
4. Turn off all processor cores except one (I haven’t found one like this).
5. Turn off SpeedStep.

Everything works for me regardless of the ACPI and SpeedStep settings.

1. Is it worth visiting at all?

Burn .iso to CD-RW. We boot from it, if a disk selection menu appears - hurray, your PC is now almost a Mac. If it doesn’t work, try another .iso. I downloaded the very first one, for regular hardware: empireEFIv1085.iso.

If all .isos do not work, you can try older versions of EmpireEFI. If nothing suits you, then the simple option is not for you. There are a lot of complicated installation options left ( Google, forum and wiki to help), or buy Mac-compatible hardware (list), or buy a PC with MacOS already configured and installed (there are companies that do this), or find those who will supply MacOS, or still buy a real Mac ( having overpaid twice).

2. You need a regular MacOS X installation DVD

Now your PC is almost a Mac. You can insert the MacOS X boot DVD and install it.
For iPhone SDK 4.0, you need version 10.6 or older. I installed 10.6.3, auto update updated it to 10.6.4.

Where can I get such a disk?
1. From a friend of a poppy grower.
2. Buy in a store.
3. Download the image from the Internet and burn it to DVD-R DL (double layer) which is 8Gb.
4. Download the image from the Internet and make a bootable USB flash drive.

If you have a familiar Mac driver with a bootable DVD, this is the best way. It will help you install and configure MacOS.

If the “hi-tech crime department” often comes to visit you, buy the official disc. Installing MacOS on a PC violates the Apple license, but this license is not valid in the Russian Federation, because violates the laws of the Russian Federation (specifically, Article 1280 of the Civil Code). This license also violates laws and is not valid in Europe, but not in the USA.

You can download the image, for example, from here.
It is in Mac .dmg format.
This format for Windows can write (and convert to .iso): PowerISO, UltraISO.
You can simply convert to .iso using dmg2img.

You need to write to a two-layer DVD-R DL disc, at the minimum possible speed and with a recording check. If the installer cannot read anything from the disk, he will write to you that you can throw the disk out the window.

To make a bootable USB flash drive, you need an already installed MacOS (even one running under VMWare will do) and a flash drive with a size of 8Gb or larger.

3. Where will we put it?

I don’t know how to install MacOS on one physical disk without erasing the already installed Windows. Paragon Partition Manager can create MacOS partitions on the same disk with Windows; the MacOS installer even sees this partition, but refuses to install it on it. He wants a GUID for the entire disk, but refuses to install it on the MBR.

But you can install MacOS, and then Windows (using BootCamp).
I did a simple thing - I bought a new disk specifically for MacOS.

4. Installation

We boot from the EmpireEFI CD, when the disk selection menu appears, remove the CD and insert the MacOS DVD (or bootable USB flash drive), select the disk from which the installation will take place. That's all.
For advanced installation diagnostics: in the disk selection menu, press Tab (which will switch to text mode), select the disk (up/down arrows) and type "-v".

If you see a language selection menu, then you're lucky the second time :)

If the USB keyboard or mouse does not work, then try removing and inserting them until they work. This only happened to me once, all other times everything worked without problems.

Switch languages: Win+Space.

The installation is no different from installing on a Mac.

When prompted to select a disk where to install, go to the menu (which is at the top): Utilities -> Disk Utility, select the disk, go to the Erase tab, set Format as Mac OS Extended (Journaled), and click on Erase. After formatting, we exit the utility and see that a new disk has appeared suitable for installation.

MacOS will take up 7 GB of disk space.

5. After installation

After installation, my network card and Internet immediately started working. Updating the system to 10.6.4 via the Internet was successful (Apple -> Software Update), it downloaded more than a gigabyte. If the driver for the network card does not work, you can always configure it later.

I disabled all sleep modes (System Preferences -> Energy Saver). I have them disabled in Windows, and they wrote on the forums that there could be problems: either it won’t fall asleep, or it won’t wake up. I didn’t even try it myself. Restart and Shut Down - work.

MacOS will not boot on its own. To boot, you must first boot from the EmpireEFI CD and select the drive where you installed MacOS. To boot ourselves, we need myHack or Chameleon, both of which are on the EmpireEFI (Empire EFI/Post-Installation) CD. First, install myHack; if MacOS will not load, install Chameleon. And don’t forget to set the first boot disk with MacOS in bios.

If MacOS does not boot (wrong bootloader or driver does not fit), you can always boot from the EmpireEFI CD.

I have a new myHack, downloaded from the Internet, but it doesn’t work. Chameleon - got up, the old myHack with CD Empire - also got up, stopped on it, because... it boots MacOS without any extra clicks.

MyHack and Chameleon prompt you to select a boot disk at startup - this way you can boot into Windows (if you have one). You can also select the boot disk when you start the computer using Shift+F8 (my bios can do this).

6. Drivers

Drivers in MacOS have the extension .kext
The main (system) drivers are here: /System/Library/Extensions/
Drivers for PC: /Extra/Extensions/

A basic set of drivers is on the EmpireEFI CD: /EmpireEFI/Extra/Preboot.dmg/Extra/Exten sions/
Copy all these .kext to /Extra/Extensions/

Information about hardware as MacOS sees it: Apple -> About This Mac -> More Info.

If the network card does not work, you can search for drivers under Windows. MacOS can read NTFS and FAT drives. My MacOS sees all WinXP and Win7 disks in read-only mode. You can also download the drivers onto a flash drive.

Place the drivers in /Extra/Extensions. Sometimes you need to put the driver in /System/Library/Extensions, replacing the system one (this is written in the driver description). Sometimes you need to erase the system driver.

After changes in drivers, you need to update the driver cache.
This is easy to do using pfix. We launch it, it will ask for the password for the system and the number of the disk where the system is located. It works for a long time, about 15 minutes. If the system has an empty password, pfix does not understand this; it needs at least a 1-letter password (change the password here: System Preferences -> Accounts).

The driver for NVidia installed right away, I tried the first one I came across: NVEnabler 64.kext
After updating the driver cache and rebooting, the mode changed from 1024x768 to 1920x1080 and new modes appeared in System Preferences -> Displays.

I didn't find a driver for my mother. Everything worked as is, except for the sound. I read on the forums that my mother needs a universal sound driver, VoodooHDA.kext. I tried different drivers: either there was no sound, then volume did not work, then volume worked, but there was noise at maximum. This driver worked with a bang when the system AppleHDA.kext was erased.

Parallel installation of Mac OS and Windows may be required in various cases. Two users on one computer, Windows is needed to run certain programs and games with maximum performance, etc.

Methods of parallel use:

  1. Installing operating systems on different hard drives. In this case, we will make the selection at boot by pressing the F12 key at boot and selecting the specific hard drive on which Mac OS X or Windows is installed.
  2. Installing and selecting the operating system using the bootloader. We will look at the example of using the Clover bootloader, but if you wish, you can use any bootloader for Hackintosh that is more familiar and convenient to you.
  3. Installing Windows on a Parallels Desktop virtual machine. In this case, you get Windows as a program running on Mac OS X. Performance in this case is slightly reduced, since two systems are running simultaneously. you can read our article.

Installing operating systems on different hard drives

The simplest, but at the same time effective way of combining two systems. When used this way, all PC settings are taken by Windows directly from Bios, which does not lead to even a minimal decrease in performance.

The method is very easy to implement and does not require special skills. The boot system is selected through the Boot Menu, which can be called up by pressing the F12 key when booting the PC. By choosing a specific hard drive, we thereby determine which operating system we will work on.

Installing Mac OS X and Windows on different partitions of the same hard drive

When using this method, the operating system is selected using the bootloader window. In this article we will look at the example of a bootloader Clover.

You can use any other Mac OS Hackintosh bootloader.

In this method, the installation sequence is very important:

  1. Installing Mac OS X on PC. If you have not done this yet, you can read the instructions in our articles(,). This is important because in a Windows environment we will not be able to format the partition in Mac OS Extended (Journaled), and this is the most important condition for installing Mac OS X.
  2. Installing the Clover bootloader on your hard drive. You can find out how this is done in the articles on installing OS X listed above. Sometimes, for security reasons, Clover is not installed on a hard drive, but is launched from a flash drive, which in this case acts as a key to OS X. Important! So that the EFI partition that is on the flash drive is fully configured to boot Mac OS on your PC, since in many cases the installation settings and boot settings have differences.
  3. Windows installation.

Preparing to install Windows

Formatting a partition

In a running Mac OS X system, format the disk partition that is intended for Windows in MS-DOS (FAT) using disk utility. This operation is required so that when installing Windows, the partition for installation is detected. The Mac OS Extended (journaled) format used by Apple is not recognized by Windows and the partitions will not be detected.

BIOS setup

If, when installing OS X, you had to disable virtualization settings in the BIOS, you must enable them. Without enabling these parameters, the installation will fail in 90% of cases.

By the way, these BIOS settings are disabled only when installing Mac OS; after installation, you can safely enable them; they will not affect the system startup in any way.

Setting up config.plist

It is very important that the timeout is specified in config.plist before starting the system. Otherwise, you will not have the choice and the system specified in it or the last loaded system (the default setting in Clover) will start automatically.

To do this, open config.plist in CloverConfigurator and change the parameter to 5-20 seconds (if you want the last running system to start automatically, if there is no choice). The value “-1” is so that the bootloader does not start the system automatically, but waits for our choice.

Then we save.

After restarting the computer with connected, we will see an additional icon for installing views in the Clover window.

After starting the installation, we format the FAT partition we selected in advance and format it with the Windows utility to NTFS, after which the process is not much different from a regular installation.

Now our Hackintosh is completely ready to install a second system, in our case Windows.

Installing Windows is similar to installing Mac OS.

Valery Kosikhin, _3dnews.ru

As you know, at the moment, Apple computers consist of the same components as PCs. This means that it is also possible to install Mac OS on the latter. How to do this - read in this news.

Installing Mac OS X on PC

Introduction

“Hackintosh” is an ironic name for Mac OS X, installed not on an Apple computer, but on a regular PC. This phenomenon became possible when the Cupertino company began migrating its machines from the PowerPC platform to x86 in 2005, and Macs began to be equipped with the same processors and Intel chipsets that are used in personal computers. Since its initial modest victories, the so-called OSx86 project has grown from a hobby of a few enthusiasts into a mass movement with a growing user base. Today, when Apple officially released a new version of its operating system, Lion, it’s time to tell everyone who doesn’t have a Mac, but has an interest in Mac OS X and a desire to experiment, about Hackintosh.

Help from excellent specialists and enthusiasts on the Mac OS operating system can be obtained if desired at http://www.cyberforum.ru/mac-os/.

The first questions a person asks when he sees a Mac operating system on a PC: “Is it difficult to install?” and “Is everything working fine?” The answer to both is no. Installation has now been simplified to the extreme, so you can play with Mac OS X on almost any modern computer, but the full functionality is not available to everyone - for a fair share of users, hardware graphics acceleration will either not work, or the network, sound, or something else will fail.
Hackintoshes also have big problems with sleep mode. All these difficulties can be overcome, but you will probably have to spend a few sleepless nights. In general, the situation completely copies what happened with desktop Linux distributions a few years ago. However, this is a very flattering comparison both for the hacker community and for Apple itself: given that no one has ever prepared Mac OS X to work with non-native hardware, everything could have been much worse. Yes, some hardware will never run under Mac OS, while others will require dancing with a tambourine to do so. But at the same time, a huge fleet of components either works out of the box or starts after simple manipulations. And software for Mac OS in all cases installs and works exactly the same as on a real Mac. It turns out that he’s not so scary, this Hackintosh.

If there is no difference, then why pay more? Or is there?

So, if a small crime doesn’t bother you, and technical difficulties only cause healthy excitement, let’s try installing Mac OS X on a PC together. In this article we will describe two simple ways to install the previous, but still popular version of the OS, Snow Leopard (10.6), and one method for the new one, Lion (10.7). There is no point in installing Leopard (10.5), much less Tiger (10.4). If you like the result, then these instructions will become the starting point for mastering Hackintosh yourself. The last section provides links to popular OSx86 community resources where you can learn from other users' experiences and find solutions to specific problems.

Preparing Hackintosh

Actually, why can’t Mac OS X just work on a PC and how to overcome these obstacles? Reason number one is that in Macs, not the good old BIOS, but EFI is used as a layer between the OS and hardware firmware, and in order for Mac OS to start, EFI is emulated at the level of a special “hacker” bootloader (by the way , we owe this achievement to a Russian hacker under the nickname Netkas). The most popular and rapidly developing loader today is Chameleon and its derivatives, for example Chimera.

The second reason: Mac OS X has a kext (from kernel extension, remember this term) called Dont Steal Mac OS X. It is required to decrypt the applications that make up what looks like an operating system to the user (Dock, Finder, loginwindow, SystemUIServer and others), based on keys from the SMC chip, which is only available on real Macs. Well, if “there are no legs, then there are no cartoons.” The FakeSMC kext comes to the rescue, which successfully emulates an SMC Device, for which, again, thanks to Netkas. A special bootloader and FakeSMC.kext are all that is needed to boot Mac OS X, if the hardware of the computer is not very different from real Macs.

And this is precisely the third reason. There are no drivers for unsupported hardware under Mac OS X, or there are built-in drivers, but the system cannot use them because it does not recognize hardware with unfamiliar identifiers.

The hardware requirements for Hackintoshes are the same - you need a processor that supports SSE2 instructions, best of all - Intel Core 2 Duo and older. AMD users will have to replace the OS kernel with a “hacked” version, and as a result, there will be problems updating the system from the Apple server. The same applies to netbooks on the Atom platform. Support for AHCI mode on the part of the SATA controller is highly desirable. To install Mac OS X Lion you need 2 GB of RAM, for Snow Leopard one is enough. The first rule for selecting hardware: the more the computer resembles real Macs, the fewer problems. Second rule: the newest and most advanced devices may not work no matter how hard you try, because... hardware support depends primarily on the Mac OS itself (heavy hardware drivers are not written for Hackintosh), and Apple is in no hurry. The site wiki.osx86project.org, which contains HLC (Hardware Compatibility Lists) for different versions of Mac OS X, will help you assess the chances of success.

For installation, it is best to use a separate drive with a SATA interface, and, out of harm’s way, turn off the Windows drive. If you are not afraid to conduct experiments on one HDD with a working operating system, then you will have to create a new partition on it using some disk utility (10 GB is enough for pure Mac OS X). Just keep in mind that during the installation process, the Hackintosh bootloader will be written to the HDD, and then you will only be able to get into Windows through it. The existing data is not at risk, but a backup won't hurt either. The disk must be connected to the south bridge port of the motherboard; the SATA controller in the BIOS must be set to AHCI mode. It is recommended to remove overclocking, remove all expansion cards except the graphics adapter in the top PCI-E slot, disconnect peripherals other than the keyboard and mouse, and reduce the RAM volume to 4 GB (if more is installed). If the installation with minimal functionality is successful, then all this can be returned step by step. Too many conditions? Then you can practice in a virtual machine. There are even ready-made images for various hypervisors on the Internet, although using them will not bring you experience in creating Hackintosh.

We warn readers: although Hackintosh is a completely harmless pastime that will not break your computer and is unlikely to corrupt any data, all manipulations described in the article are done at your own peril and risk. In addition, you need to be familiar with the computer and know what the bootloader, OS kernel and hard drive partitioning scheme are.

Installing Snow Leopard from iATKOS 10.6.3 v2

The simplest and most universal option is to install Mac OS X with a specially modified distribution. Since the release of Snow Leopard, such hacker builds have given way to a more elegant solution - installation from a copy of a proprietary disk using a separate bootable CD, and this is described below. But users of CPUs from AMD or Intel Atom cannot do without assembly, because... the original Mac OS X kernel (which our English-speaking friends call the vanilla kernel) only supports Intel processors with Core architecture and older, and the build allows you to immediately select the “patched” version during the installation process. And after you have entered the world of Hackintosh through assembly and gained some knowledge, you can create a clean installation, the components of which you have complete control over.

iATKOS 10.6.3 v2 is one of the latest builds released, and despite the rather old version of the OS (Snow Leopard has already been updated to 10.6.8), all the “hacker” software on it is quite modern. After downloading the image (we won’t tell you where from), write it to a disc. Boot from the iATKOS disk and wait until the “hacker” bootloader works and the OS starts.

This process takes several minutes, but if it suddenly takes longer than reasonable limits or displays an error message, it means that something went wrong.

In this case, you need to boot from the DVD again, but on the bootloader screen with the green chameleon, press F8, highlight the optical drive, enter “-x” from the keyboard and press Enter. This is the so-called safe mode, but if you have no luck with it, then you need to boot with the “-v” argument, which will allow you to observe the boot log. At the moment where the process is stuck or the phrase Kernel Panic appears, you can take a photo of the screen and then, in a calm environment, try to understand what is happening, using thematic sites, Google and advice from experienced “hackers”.

The appearance of a window with a choice of language indicates that the download was successful and your system is able to run Mac OS X. We recommend, if possible, choosing the Shakespeare language, since most instructions and problem analyzes on the Internet are written in it.

Scroll through the pages of the installer until the disk selection window appears.

Open the Utilities section in the menu and launch Disk Utility. If you have given a blank disk to Hackintosh, then using this program you need to “partition” it (the Partition tab). To install on a partition adjacent to Windows, the partition is simply formatted in the HFS+ file system (Erase tab). For reliability, it is better to choose the HFS+ Journaled option, and most users will not need the Case Sensitive option.

Once the HDD is prepared for installation, you can close Disk Utility and specify the partition in the installer window. And now the important point is the choice of drivers and settings that allow Mac OS X to fully work on your hardware. The list is opened by the Customize button. All users are advised to look into the Bootloader thread and select the Chameleon v2 RC5 option instead of the default option. Owners of AMD and Intel Atom processors must select a modified kernel in the Patches, Modified Kernels section.

You should not select any “drivers” for the graphics adapter in the Drivers, VGA section. It is better to check the box next to the Graphics Enabler option in the Bootloader Options section - in this case, the bootloader itself will try to activate hardware acceleration. Be that as it may, the OS almost always boots in 2D mode, and if the Graphics Enabler method does not work, then you can try your luck with separate “drivers”. By the way, these are not drivers, but only injectors that allow drivers built into Mac OS X to work with unfamiliar video cards, which is why they are put in quotes.

Select the appropriate package for your network card in the Drivers, Network section - there is a good collection there. For a laptop, the contents of the Drivers, Laptop Hardware section will be useful. You can take some driver for CPU power-saving functions from the Drivers, Main Hardware, CPU Power Management section. The “native” kernel extension called AppleIntelCPUPowerManagement.kext, which carries this function, is prudently blocked in the assembly, because it is only suitable for Intel processors, and even then not for all, and in case of errors it does not allow the system to boot.

Do not check Sleep Enabler in the Patches section - if you need sleep mode, then after updating the OS this extension will still have to be replaced.

The Language Translations section came to iATKOS from the official distribution and contains OS interface localization packages, including Russian.

It is advisable to write down a list of the options that you have chosen, in case the newly installed OS does not start and you have to look for the culprit. Once your selection is made, you can click OK and then Install. Go!

At the end of the installation, the computer will reboot. You can remove the iATKOS disk and boot from the hard drive that we've loaded Mac OS X onto. While the Chameleon boot loader is counting down the seconds until the OS starts by default, you can press any key and see a list of partitions that can boot from. If at first there was already Windows on the hard drive, then it starts from a service partition called System Reserved, or directly from its root partition, if the service partition is missing for some reason.

But we can't wait to see Mac OS, right? In this case, we just wait, and if the options were selected correctly during installation, a registration window will appear on the screen, and if the Graphics Enabler option worked, a welcome video will also be shown.

What to do if the operating system gets stuck at the loading stage or displays an error message? The first tip in this case is to boot up and view the log. To do this, you need to stop the bootloader while it counts down the time until the OS starts, select the partition with it, enter the “-v” argument and press Enter. Based on the messages on the screen, you can find the component causing the failure. Then you can try to boot into safe mode with the “-x” argument, and if this is successful, then it is likely that the problem is some kind of kext - a driver or device injector that you checked in the Customize menu of the installation disk, and it needs to be replaced. How to work with kexts is described in a special section of the article.



Installing Snow Leopard from a proprietary distribution

A “Hackintosh” can also be created using the “native” image of Snow Leopard, which you can even buy to ease your conscience. At the same time, all the software that makes Mac OS X compatible with PC is recorded on a separate disk. But this method is only suitable for owners of Intel CPUs, because both the distribution disk and the copy of the OS that will be installed from it use the original kernel without AMD support. In addition, the unmodified Snow Leopard installer will not allow you to roll the system onto a hard drive partitioned using MBR, and only supports the GUID partitioning scheme. Therefore, the disk with the MBR will have to be repartitioned.

If Windows is already installed there and you are not ready to say goodbye to the most popular operating system forever, then there is a non-obvious solution: using Disk Utility, first partition the disk with a GUID, create its own partition for “windows” and install Windows, and then on the second partition - Snow Leopard. The key word here is Disk Utility. This program, which, as you already know, also runs from the Mac OS X installation disk, creates a hybrid partition with synchronized GUID and MBR. And the MBR is required to install Windows.

The creator of the iBoot disk, which we will use for a “clean” installation, also warns that for Mac OS X you need to allocate a partition with a minimum size of 1 TB. Those interested can familiarize themselves with the original manual on the page. However, when preparing this article, the OS installed and launched perfectly from a 20 GB hard drive.

So, first we need an iBoot boot disk image and a MultiBeast driver package - the latest versions of both are posted on the tonymacx86 website (registration is required to download). We burn the iBoot ISO image to a disc and boot from it. When a window appears asking you to select a partition to boot, you need to replace iBoot in the drive with the “native” distribution with Mac OS X, press F5, highlight the DVD and press Enter.

The further procedure is completely similar to what is written about assembling iATKOS, only in the Customize menu there are no “left-handed” drivers, but only standard Snow Leopard packages - interface localizations, fonts, etc.

But once the installation is complete, you won’t be able to boot directly from the hard drive, because... the copy of the OS is pristine and no different from what is on real Macs. Therefore, you need to boot from the iBoot disk again and select the partition with Snow Leopad.

If an error occurs, you already know what to do: boot with the “-v” argument and run diagnostics, then try to start the OS in safe mode with the “-x” argument. The tonymacx86 site also recommends the PCIRootUID=1 argument, which can be combined with "-x" and "-v".

If Mac OS X showed a registration window, then it’s time to accustom it to the PC. You need to launch MultiBeast from the archive that we downloaded in advance, and scroll through all the installer pages right down to the component selection menu. Here, all users must check the EasyBeast Install item - which specifies the installation of a minimum set of kexts. To enable support for specific hardware, you should look at the individual branches of the list and select the necessary extensions. At the end of the procedure, the computer will reboot and you can safely boot from the HDD.

In addition to kexts, the Chimera bootloader will be installed on the disk, and if Windows was previously installed, it is loaded by selecting the appropriate partition.



Installing Lion

Here's the tastiest thing - the latest version of Mac OS X. So far only Intel users can appreciate it. At the time of writing, Apple has not yet released the source code for the Lion kernel, which means there are no modified kernels. But most kexts written for Snow Leopard work with Lion.

To install Lion, we will need a working Snow Leopard version no lower than 10.6.6, a free partition on a 5 GB hard drive to accommodate the installer files, the Lion distribution (available for $29.99 in the App Store and you know where for free), xMove utility and the already familiar MultiBeast package.

The Install Mac OS X Lion program is launched directly from the running operating system, and as the partition for installation you need to select exactly the one from which Snow Leopard is running, which will not affect the OS in any way. Once the files are copied, you can agree to reboot and log back into Snow Leopard.

Now it's up to the xMove utility. Having launched it, you need to mark the empty partition that we prepared in advance for Lion, and xMove will transfer the files unpacked by the Install Mac OS X Lion program there. If Snow Leopard is installed using the iBoot + MultiBeast method, then just boot from the hard drive and select the partition with “Lion” in the Chimera bootloader menu. If iATKOS or another solution was used for installation, but the bootloader and kexts are also not the latest, then you will have to boot from the iBoot disk. The further procedure completely repeats the process of installing Snow Leopard from a proprietary distribution. Moreover, as a target, you can select a partition with an already running Mac OS X, and then it will be updated painlessly.

Installing and removing kexts

How can I remove a problematic driver, injector, or add support for devices that did not start after the initial installation? The storage for kexts (kernel extensions) in Mac OS X is the /System/Library/Extensions directory, and they are loaded from a single cache at /System/Library/Caches/com.apple.kext.caches/Startup/Extensions.mkext, where the OS puts only the necessary extensions. But modern Hackintosh loaders (already familiar to us Chameleon and Chimera) can load additional kexts from the /Extra/Extensions directory, and from them their own small cache /Extra/Extensions.mkext is formed. MultiBeast and iATKOS use exactly this scheme, only in the latter case the /Extra directory is hidden. Showing hidden files is enabled using a command in the terminal.

Defaults write com.apple.finder AppleShowAllFiles TRUE killall Finder

To install many kexts, just copy them to /Extra/Extensions. But some will not be able to resolve dependencies (there are no necessary extensions in the /S/L/C/c/S/Extensions.mlext cache), and you will have to create a single cache of all “native” and “third-party” extensions in the /Extra directory. which the OS will not be able to remake. The following command does this:

Sudo kextcache -m /Extra/Extensions.mkext -- /System/Library/Extensions /Extra/Extensions

Before these files in /Extra/Extensions need to be assigned the necessary permissions. Teams:
sudo chown -R 0:0 /Extra/Extensions sudo chmod -R 755 /Extra/Extensions

And one more nuance: if, even with the correct permissions, the kext is not included in the cache and is not loaded, you need to open it using the Show Package Contents option in the file’s context menu and view the Info.plist file in the Contents directory. This is an xml file, and at the end, before the closing tags, there should be the following entry:

OSBundleRequired Root

Otherwise, it needs to be added or changed.

Things are a little different in Mac OS X 10.7. Lion uses a different cache format - prelinked kernel. By default, Chameleon does not read it and scans the entire contents of the /Extra/Extensions directory, which slows down loading. The only thing that can be done for now is to create a shared cache in the system directory /System/Library/Caches/com.apple.kext.caches/Startup. Team:

Sudo kextcache -c /System/Library/Caches/com.apple.kext.caches/Startup/kernelcache -v -t -K /mach_kernel -- /System/Library/Extensions /Extra/Extensions

And in order for the bootloader to pick up kernelcache, you need to use the “UseKernelCache=Yes” argument at startup. But unlike the contents of /Extra, this file is subject to the operating system, and from time to time it will update it, forgetting, of course, about our “hacker” extensions. A solution to the problem is to move the kexts from /Extra to the /System/Library/Extensions directory and give them the necessary permissions with the commands:

Sudo chown -R 0:0 /System/Library/Extensions sudo chmod -R 755 /System/Library/Extensions

OS update

Hackintosh can be updated from the Apple server using the built-in Software Update utility. But at the same time, you need to be prepared for the fact that after the update some kexts will stop working or start causing crashes and you will have to find a replacement for them. Fortunately, developers of popular extensions quickly respond to the release of new versions of Mac OS X. In addition, after the update, you need to rebuild the kext cache by first loading the system with the “-f” argument. Users of AMD processors should make sure that the latest version of the modified kernel is available before updating the OS, or you can leave the old one.

Bootloader setup

The operation of the Chameleon bootloader or its analogues is controlled by the file com.apple.boot.plist in the /Extra folder. It can be modified manually, but there is also a special GUI utility - Lizard, which can be downloaded from the page. It is advisable to enter the screen resolution, loading arguments (for example, the aforementioned “UseKernelCache=Yes”) into the configuration, and for owners of “non-standard” processors the name of the modified kernel file. In iATKOS this is the custom file (look, it is in the root partition of the disk). Also check Graphics Injection if this option helped you enable 3D acceleration.

The 32bit Compatibility Mode option will force the kernel to boot in 32-bit mode, which may be necessary for some kexts. At the same time, support for large amounts of RAM is maintained, and applications can run in 64-bit mode regardless of the kernel. A similar command line argument is “-x32”.

The argument list may also contain special options for individual kexts.

The program automatically opens the file /Extra/com.apple.boot.plist, and if it is missing, it will create it when you try to save changes. This is exactly what will happen with iATKOS, because... This assembly by default stores the bootloader configuration in the system file of the same name /Library/Preferences/SystemConfiguration/com.apple.boot.plist. This is not correct, so it is best to clear the system file after creating the file in /Extra, leaving only those lines that are shown in the screenshot.

Another Lizard feature is editing the /Extra/SMBIOS.plist file. It contains information about the computer model and installed hardware and helps to present the computer as some kind of Macintosh in the System Information program.

Peripherals from Apple

A question that worries many people, but they don’t want to spend money on an experiment: do Mac devices like Apple Cinema Display, Magic Mouse and Magic Trackpad work with Hackintosh? So, the monitor is compatible with any video card equipped with DisplayPort (DP Mini or a full-format version of the port with an adapter is suitable), and both the light sensor and brightness adjustment in System Preferences work. The mouse and touchpad require a Bluetooth USB adapter - some work right out of the box without any additional kexts, and the connection process is again no different from that on real Macs.

Free swimming

Now that you know how to change kexts and configure the bootloader, the Hackintosh configuration is completely in your hands. After the initial installation of Mac OS X, there are probably some rough edges left: something either doesn’t work or works poorly. Knowledge from web resources dedicated to OSx86 will help you bring the system to life.

Well structured forum with friendly audience. There is a Russian-language section;

The above-mentioned encyclopedia with a database of compatible hardware;

Website with installation guides and useful links;
manuals and software for Hackintosh;

a forum similar to InsanelyMac contains more in-depth technical information on some topics;

base
original and third-party kexts for Mac OS X.