• Hackintosh: installing Apple OS X on PC. Install Mac OS X Yosemite on a PC from Windows. We use a ready-made flash drive image

    4

    What's the point of using OS X versus Windows? As a person who lives under Windows, but regularly finds himself using a poppy for 3-5 slaves. days I want to understand. For what? Just don’t talk about a computer with a human face, I want to hear something practical - this is more convenient/faster, this excellent software is not available for Windows, etc.

    @direless, it’s just for people to try what and with what before buying a Mac. Or a person at work on a Mac, can’t stand Windows, but hasn’t saved up on a Mac yet at home. So he will launch his native system on the Internet, if only for the sake of not seeing the vile Internet exporter. In short, once they did it, it means someone needs it. I wrote the first thing that came to mind, there are probably other reasons why this is necessary.

    @koreasony,

    “Just try” is for children. No matter what the child scratches, as long as time passes. I’m still waiting for understanding - why makos is cool, I want enlightenment! Then we'll roll.

    @direless,
    There's a whole section on this. Saturate yourself with information.

    @Artem Bausov, everything under this tag resembles shamanism with a tambourine, because I look at the titles and this is what I see: how to shamanize with an automate to do ordinary simple things, like turning on/off simple things, like turning on. mode so that the poppy works when closed lid laptop, file viewer, etc.
    Dubious advantages!)))
    Nothing like that! I myself am the owner of several poppies, but now the advantages of Macos have become worthless. All professional software has been trashed (I'm talking about aperture, logic and final cut), the rest works great on Windows and here.

    @dimixx, aperture professional software??? they didn't fuck him, he was shit.
    or am I wrong? tell me why it was good, seriously, maybe I didn’t understand something. I did it twice, but all times it ended with him making some kind of trash out of my good collection. it's for amateurs. I don’t use anything other than bridge for navigation. and of course edit in the shop

    @direless, I once had a netbook, it initially had Windows 7 Starter, well, it was very hard to work with, the Atom processor was weak. I decided to hang it up, it got better.
    somehow an image of a Macosi was circulating on the Internet of a netbook specially created for this purpose, by the way, it was called Samsung NC10.
    As soon as I installed it, everything worked, I felt the speed of operation compared to Xpi and Seven. That's when I met Makos.
    After that I decided to buy a MacBook.
    The speed of operation and all the other goodies became the reason to buy a MacBook as a novice Mac owner)))

    @direless, until you try, you won’t understand... there are things that are much easier to solve on a Mac than on Win. But, there are familiar tasks that are difficult for the user to solve on a Mac (in the usual way). As a rule, highly specialized application software cannot be launched on a Mac (often this software is under Win 98, XP, NT, etc.)… I have 14 years of experience in using Windows, and 3 years on Macs (after Windows). I switched first at home, then at the office. I don't regret a minute. I forgot what reinstalling the system is. Windows needs to be rearranged once every year and a half. The mac axis simply moves to new computer with all settings, files, etc. Automator helps at work... I gave up a lot of software for Windows altogether. On a Mac there are many microprograms for one or two actions with a file (converters, taggers, etc.). I have a computer on Windows 8.1. Sometimes I turn it on and see what’s new. I'm waiting for 10 to review. IN win the latest versions, the interface has become friendlier and features from the Mac axis appear there too. I think soon there won’t be much difference in terms of convenience. But the vulnerability and cost of Windows will always be higher than the Mac axis)

    READ ME PLEASE

    If you CANNOT unzip files onto a flash drive, please step away from the keyboard and urgently read the book “Computer for Dummies: A Detailed Guide on How to Use a PC”!!!

    1. All files are uploaded to MEGA. Those who are having problems with it have re-uploaded it to the torrent in the comments.
    2. Please don't ask me about installing Macs on laptops. I beg you. Please. This is a very hemorrhoidal process. Install Ubuntu and connect the Mac theme. You will get the same experience
    3. I rarely answer on Habré, write to VK for all questions.

    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 all this can take 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 installation flash drive from under 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 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 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 installs without problems Intel processors, starting with Core i3 (we are talking specifically about macOS Sierra 10.12, previous releases may also be available on Core processors 2 Duo and Pentium). 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

    Next, let's decide on the graphics. If you are using the built-in Intel graphics(in my case it’s HD4600), then most likely you will need a separate graphics “factory” (although they can start natively).

    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, consider the plant AMD graphics we won’t, since it all comes down to framebuffer patches and Device ID substitutions in the bootloader (which is individual for everyone). Read more about AMD cards here: poke (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. Everything is already normal. On GTX cards The graphics start up in a jiffy, the 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
    UPD 14.05 GeForce GTX 1000 Series


    I'm 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

    E2200

    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.

    Downloaded.

    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 section with Clover, and the kext into the folder that we unpacked. That's it, it's ready. The flash drive is made. Let's move on.

    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). We set our flash drive to boot priority (BOOT). Make sure it will load exactly in UEFI mode. Save and apply the settings, reboot. We get to the Clover 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:

    Kext-dev-mode=1 rootless=0 -v npci=0x2000 nv_disable=1
    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 PCI-e versions) - 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 artifacts during loading and other garbage, disable 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:

    Kext-dev-mode=1 rootless=0 -v npci=0x3000 darkwake=0 nv_disable=1 cpus=1
    In other cases, only Google will help, although these fixes should solve these problems.

    We are waiting. 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. Loading will begin language pack(may freeze for a minute). Now open Utilities>Disk Utility, we need to format the disk for macOS. Choose required disk, click “Erase”. For convenience we call 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.


    Let's move on...

    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 launch 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 only present on motherboards Apple. 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 quantity RAM, slots, slots, 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 will pick it up itself required 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 icon magic wand. 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 they 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 anymore basic settings we did. We save our file. Now copy it to the CLOVER folder EFI partition, log in, replace. 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 With 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 a flash drive, write it in the options the necessary keys 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, since 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 built-in 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 ready for macOS work Sierra.

    UPD from 05/14/2017

    - In the comments good people re-uploaded the file from mega to torrent. This is due to the fact that many people have problems downloading a file from mega. To be honest, I didn’t know that Mega has a limit on download speed (I use a premium account). Also, please write all questions to me on VK, but check the comments first. There is a chance that your problem has already been solved there. Again, I am not responsible for any risk this may cause to your computer. I also want to clarify one point that the article is presented solely for educational purposes. The very fact of installing a hackintosh on a PC is a gross violation of Apple's policy regarding their system, which is punishable by law. The author does not encourage using MacOS on non-Apple computers and does not encourage changing the system's source code.
    - The end

    Tags: Add tags


    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 complicated Windows installations 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 on ACPI (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 know a poppy grower with bootable DVD- this is the most 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 already need installed MacOS(even one running under VMWare will do) and a flash drive 8Gb or larger.

    3. Where will we put it?

    How to bet on one physical disk MacOS without erasing already installed Windows - I don't know. Paragon Partition Manager can do MacOS partitions on the same disk with Windows, the MacOS installer even sees this partition, but refuses to install 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 usb keyboard or the 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- they 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 disk number 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 what I need for my mother universal driver sound VoodooHDA.kext. Tried it 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.

    Even if you're a longtime Windows fan, you've probably thought about giving Apple's rival OS X a try. Perhaps you wanted to try out OS X before deciding to switch to a Mac, or perhaps you are planning to build a Hackintosh yourself, or maybe you just want to run some of the applications under Mac OS X directly on your PC .

    Well, whatever the reason, you can easily install and run OS X on any PC with an Intel processor. And a wonderful program called VirtualBox will help us with this.

    Installing and running OS X on Windows is not a difficult task and will not take you much time. However, the end result will pleasantly surprise you.

    So what do we need

    Before we begin installation, please make sure that your computer complies with system requirements, and also that you have prepared everything you need:

    A computer with Windows on board (Mountain Lion is a 64-bit system, so Windows must be the same), at least 2 nuclear processor and 4 GB of RAM. If you use a 32-bit OS, don’t worry, you can install Mac OS X Snow Leopard.

    VirtualBox: VirtualBox is our favorite virtualization program for Windows and it's completely free. We've already used VirtualBox to increase storage space on Dropbox. Keep in mind that if you need USB support ports inside OS X, then you also need to download the VirtualBox Extension Pack.

    Special ISO image Mountain Lion. Unfortunately standard way(which uses the officially purchased Mountain Lion installer) to install OS X Mountain Lion will not work here. Instead, you will need a jailbroken version of OS X, also called a distribution. The Olarila hacker team has posted a ton of ISO installers online, so you can easily find them on Google or any torrent tracker and download them using a torrent client.

    HackBoot 1 and HackBoot 2 - ISO files. Hackboot 1 will help us launch the OS X installer, and Hackboot 2, in turn, will help us launch Mountain Lion itself.

    MultiBeast 4– which will ensure that audio and other functions function correctly. To download it, register at Tonymacx86.com. It's free.
    Step One: Installing and Configuring VirtualBox

    Before installing OS X, we need to configure VirtualBox so that our installation file was able to work correctly:

    Launch VirtualBox and click Create. In the window that appears, enter the name of your virtual machine (I simply named it “Mac OS X”). In the Type tab, select Mac OS X, and in the next Version tab, select Mac OS X (64 bit).

    Installing and configuring VirtualBox

    Click Forward. Now we need to decide how much RAM we are ready to allocate for the needs of our virtual machine. It all depends on how much RAM you have installed on your computer. You can allocate 2GB - this will be quite enough, but if you have enough RAM (for example, 8 or 16 gigabytes), then it is better not to be greedy and allocate more. 4 or 6 GB are the best options.

    Click Forward again and select Create a new virtual hard drive. Create your new disk in VDI format and with dynamically allocated space. When you're done, VirtualBox should return you to the home screen.

    Now right-click on our just created virtual machine and select Configure. Go to the System tab and uncheck the Enable EFI option (if you have it checked).

    Next, go to the Media section. Click on the CD icon labeled Empty, which is located in the Storage Media panel. Then click on the CD icon, but this one is on the right and select Select image optical disk. Select the HackBoot 1 ISO file that we downloaded earlier and click OK.

    Your virtual machine is now ready for installation. Make sure you have the correct Mountain Lion ISO image and move on to the next step.

    Installing OS X in VirtualBox

    The next step involves directly installing OS X on your virtual machine. When you are ready to install, launch VirtualBox and follow the instructions below:

    In the left pane, select your virtual OS X system and click Launch. Next will appear loading screen HackBoot with an icon in the middle HackBoot

    Click on the CD icon at the very bottom of the VirtualBox window and select Select optical disk image. Select the hacked Mountain Lion ISO image downloaded earlier.

    Selecting the OS X installer

    Return to the HackBoot loading screen and press F5. The window should reboot and this time display the OS X Install DVD. Select and press Enter. After a while, you will be redirected to the OS X installation window.

    After you select your language and agree to the terms of use, you will see that OS X cannot detect any hard drives of a valid format. To solve this problem we go to top menu and select Utilities >

    Disk Utility.

    Go to disk utility

    The fact is that Mac OS X can only be installed on a completely clean hard drive. Therefore you need to take advantage Disk Utility to clean up the virtual hard disk you created in VirtualBox for Mountain Lion. So, being in Disk Utility, select our HDD from VirtualBox and clean it.

    Cleaning the virtual HDD

    Once Disk Utility has finished formatting, a formatted drive should appear in the left sidebar. You can then exit Disk Utility and continue installing OS X.

    Further installation is quite simple and should not cause you any difficulties. The entire OS X installation process took us only about 20 minutes. When the installation process is complete, a black window with white text should appear in front of you. Once the installation of Mountain Lion is completed successfully, you can click on the "X" on the right top corner windows, thereby turning off the virtual machine.

    Bringing beauty

    We're at the finish line! We've already installed OS X on PC, but we still need to tweak a few things to get our graphics and audio features to work properly. So here's what we need to do.

    Fixing an audio bug using MultiBeast

    Launch VirtualBox. In the left panel we find our virtual OS X and right-click on it. Select the Configure item and go to the already familiar Media section. Click on the disk icon located on the right side of the window and select the HackBoot 2 ISO file.

    Click the Start button to reboot your virtual machine. After this, the HackBoot menu will appear in front of you again, but this time with the option to boot your new virtual OS. Select it and press Enter.
    Running OS X for the first time in Virtual Box

    In a minute or two you will see the signature Mountain Lion desktop screensaver. Opening Safari browser, go to Tonymacx86.com and download MultiBeast as described in the section

    What do we need?

    Open System Preferences > Protection and Security. Click on the lock in the lower left corner of the window, enter your password and in the Allow downloads of programs from subsection: set From any source. This will allow us to run MultiBeast on our Mac OS X.

    Launch Multibeast. When you get to the Installation type item, check the boxes as shown in the screenshot below. Click continue and wait for the Multibeast installation to complete. The installation process may take several minutes.

    Fixing audio using MultiBeast

    Our audio features aren't working yet, so we need to do a couple more things.

    Launching OS X without HackBoot

    So, in order to boot our OS X without the help of HackBoot, we need to delete the problematic kext file.

    Open Finder and select Go > Go to Folder.
    Type in /System/Library/Extensions and press Enter.
    Find the AppleGraphicsControl.kext file in this folder and delete it. This will allow our virtual machine to boot without iso file HackBoot. Delete the kext file

    Next, remove the HackBoot CD; To do this, right-click on the CD icon in the lower right part of the VirtualBox window and uncheck HackBoot, since we won’t need it anymore. Restart the virtual machine. Now your Mac OS X can boot normally and play audio fully. Congratulations!

    Setting the screen resolution for the virtual machine
    You may have noticed that our VirtualBox is running at a fairly low resolution. Naturally, we are not happy with this, so let's make a couple more settings so that the VM runs at the same resolution as our monitor.

    Again in the Finder, select Go > Go to Folder and go to /Extra/. Double click by file org. Chameleon.boot.plist and add the following lines between the and tags: Graphics Mode 1920x1080x32 Save the file and close TextEdit. This will allow OS X to run at a higher resolution. Keep in mind that you can set it to whatever resolution you want, just replace 1920x1080 with the resolution you want.

    Editing chameleon plist

    If you set the resolution to greater than 1280x1024, there is one more thing you need to do to make sure everything works correctly. Shut down your virtual machine and open command line Windows. Enter the following commands, pressing Enter after each: cd “C:\Program Files\Oracle\VirtualBox” vboxmanage setextradata “MyVirtualMachine” “CustomVideoMode1” “1920x1080x32”

    In the first line, specify the path to the VirualBox folder on your computer. In the second line, replace MyVirtualMachine with the name you gave your virtual machine (in our case, Mac OS X), and finally 1920x1080x32 with the resolution you specified in the first paragraph in the Chameleon plist file.

    Running OS X on Windows

    When done, reboot your virtual OS X and enjoy high resolution and working audio functions. Now you can install your favorite apps, customize your keyboard and mouse, and do whatever you want. So now you have a fully working virtual OS X Mountain Lion right on your Windows computer!

    The network is now full of copy-pastes, essentially the same article, about installing MacOS X on hackintosh with about the same title. I’ll tell you how to install Mac OS X from a flash drive on a mac.

    There is nothing complicated here, but not everyone is a pro, and reinstalling the system on a Mac is quite a rare thing, this is not Windows. When is this necessary? In my case, I needed to update from old version Mac OS X Leopard (10.5) up to next Mac OS X Snow Leopard (10.6).

    The question is, why write about such old stuff when OS X 10.9 is coming, but today we’ll leave the topic of novelty alone, the essence of the question doesn’t change. Disk image OS X Snow Leopard Install DVD 10.6.3 Retail I took it from the inmac.org torrent.

    In general, you can install both OS X Lion (10.7) and Mountain Lion (10.8) from a flash drive. You can legally purchase OS X Mountain Lion from App Store(issue price is only 625 rubles).
    Once the download is complete, a utility will appear in the Applications folder. installing Mac OS X Mountain Lion.
    Right-click on the installer and select “Show package contents.” Next, copy the OS image from the “SharedSupport” folder to any convenient location InstallESD.dmg.

    Creating a bootable USB flash drive or Mac OS X disk

    To record an image of Mac OS X Snow Leopard, a double-density DVD is required (6.3 GB will not fit on a regular disc), and there was no drive for recording this either. I wasn't upset. At a time when spaceships are roaming... use CDs is bad manners.

    We plug a suitable flash drive into the computer and launch Applications > Utilities > Disk Utility.

    1. First of all, we format our flash drive. In the “Erase” tab, specify a new name (for example MAC_OS_X) and file system Mac OS Extended (Journaled).
    2. Mounting the image future system by double clicking on the image file. In my case it's Mac.OS.X.10.6.3.Retail.dmg(or InstallESD.dmg as described above). The image will appear in the left pane of Disk Utility.
    3. Go to the “Restore” tab. From the sidebar of Disk Utility, in the “Source” field, drag (Mac OS X Install ESD). In the “Destination” field, drag the created partition on the flash drive (MAC_OS_X).
    4. Click the “Restore” button. This process is not fast, so you will have to wait a little.

    Booting Mac from USB flash drive

    We boot the system by holding the Alt key (aka Option) until a selection of boot options appears. Well, then all you have to do is follow the installer’s instructions.

    By the way, all user data, right down to the desktop screensaver, when switching from one Mac versions OS X to the other remained untouched. Although at the time of installation, a lonely cold ant ran down the spine when it suddenly became clear that the user did not store some of the documents on the server and did not make backup copies. So, I recommend not to be lazy and, just in case, create a backup copy of important documents in advance.