Jump to content

Help me understand the config.plist file


drumlin
 Share

9 posts in this topic

Recommended Posts

I'm new to the Hackintosh world, and having some trouble understanding fundamental concepts. I basically understand the idea of the bootloader, as well as the need to cherry pick kexts specific to the hardware used. But I'm not clear on just what the config.plist file is. I do get that it must be carefully configured for each HacKintosh machine, and that this process is anything but easy for a noob who doesn't have a background in computer science.

 

Can someone offer up an explanation of what the config.plist is and what it actually does, in layman's terms?

 

Thanks in advance.

Link to comment
Share on other sites

Hi,

 

I guess your talking about the config.plist of your bootloader?

Would this be Chameleon or Clover?

 

A config.plist file can be compared to a ini file in Windows. It holds all the settings for a program to use, in this case, you can look at the bootloader as if it where a program. 

In this file you can adjust all settings the bootloader supports, the bootloader will read these settings, and apply them to your OS X installation so that you can boot it on your PC. 

 

The options and lay-out differ between Clover and Chameleon. 

Link to comment
Share on other sites

Hi,

 

I guess your talking about the config.plist of your bootloader?

Would this be Chameleon or Clover?

 

A config.plist file can be compared to a ini file in Windows. It holds all the settings for a program to use, in this case, you can look at the bootloader as if it where a program. 

In this file you can adjust all settings the bootloader supports, the bootloader will read these settings, and apply them to your OS X installation so that you can boot it on your PC. 

 

The options and lay-out differ between Clover and Chameleon. 

 

Hello Lex--As new as I am here, I'm not decided on which bootloader is the best to choose. I've read that Clover is regarded as more advanced and has certain technical merits, but I don't have the background to understand the reasoning.

 

I had figured that since Clover is described in various places as preferable to Chameleon, then Clover is what I'd like to try and understand and implement. 

 

My current hardware is: Asus Z97-AR motherboard; i5-4590 w/HD4600 (no discrete gpu); onboard Intel i218v ethernet; ALC892 audio. This system is now running Win 7 Pro 64bit, and an end goal would be a dual-boot system, but that's not as important as learning to get a functional Yosemite install on its own SSD to start. I think that the needed BIOS settings for Clover/OS X will prevent booting my already installed Win 7, so for now I can simply disconnect the Win 7 SSD while fooling around with the Hackintosh side of things.

 

Thanks for your reply.

Link to comment
Share on other sites

Hi,

 

The only bios settings that could prevent your Windows 7 from booting, would be CSM boot to UEFI boot, or IDE to AHCI mode. Various CPU related settings should not give problems.

If you would install OSX with a boot loader to a separate SSD or HDD, you can alter the boot order, to boot from the OSX SSD/HDD first, when Clover is installed to that SSD/HDD, it will load Clover, and from there you can also select your Windows 7.

 

Installing OSX/Clover next to your Windows7 on the same SSD/HDD would require a bit more effort. 

Link to comment
Share on other sites

Hi,

 

The only bios settings that could prevent your Windows 7 from booting, would be CSM boot to UEFI boot, or IDE to AHCI mode. Various CPU related settings should not give problems.

If you would install OSX with a boot loader to a separate SSD or HDD, you can alter the boot order, to boot from the OSX SSD/HDD first, when Clover is installed to that SSD/HDD, it will load Clover, and from there you can also select your Windows 7.

 

Installing OSX/Clover next to your Windows7 on the same SSD/HDD would require a bit more effort. 

 

Lex--I would definitely be installing OS X to its own SSD for least complications. Hackintoshing is complicated enough with dual-boot setups. 

 

If I can get a bootable and working Yosemite install, then I'll turn to solving the question of dual-booting with Win 7.

One tip: Clover WiKi also is great for knowledge about how some patch works in config.plist

 

:wink_anim:

 

Allan--I have spent time perusing the Clover Wiki, and came away largely baffled, but that's because I am not a programming professional, but just a home hobbiest. I printed much of the Wiki information so I can try again in my spare time to figure out whatever I can from it.

 

It does seem that config.plist customizing is rather a "black art," even for the experienced, judging by many hours' worth of reading through Hackintosh forums.

Link to comment
Share on other sites

Allan--I have spent time perusing the Clover Wiki, and came away largely baffled, but that's because I am not a programming professional, but just a home hobbiest. I printed much of the Wiki information so I can try again in my spare time to figure out whatever I can from it.

 

It does seem that config.plist customizing is rather a "black art," even for the experienced, judging by many hours' worth of reading through Hackintosh forums.

 

If you want learn more and in simple way about Clover, this is your place: Clover

And this topics:

 

Instructions:  Clover v.2 Instructions

Ask anything about Clover: Clover General discussion

 

Link to comment
Share on other sites

Allan--I have spent time perusing the Clover Wiki, and came away largely baffled, but that's because I am not a programming professional, but just a home hobbiest. I printed much of the Wiki information so I can try again in my spare time to figure out whatever I can from it.

 

It does seem that config.plist customizing is rather a "black art," even for the experienced, judging by many hours' worth of reading through Hackintosh forums.

 

 
 

You must understand that Apple populates it's copies of MacOS with only the information that it needs to install on it's specific models of computers. When you build a PC to run MacOS, you are using components outside the Apple norm. That is why you need a config.plist to identify the specifics of the parts used in the PC, In addition you can benefit from the DSDT.aml and the SSDT.aml which also define other parts of the computer.

The real advantage of using Clover boot loader is that it builds a DSDT on-the-fly, as it loads the OS when starting up. Clover really is very simple to get going. You would do well to use a modern motherboard as well. The UEFI boot process is much easier to use that an older BIOS only boot process. Clover is really meant (in my opinion) to use UEFI booting. 

Link to comment
Share on other sites

You must understand that Apple populates it's copies of MacOS with only the information that it needs to install on it's specific models of computers. When you build a PC to run MacOS, you are using components outside the Apple norm. That is why you need a config.plist to identify the specifics of the parts used in the PC, In addition you can benefit from the DSDT.aml and the SSDT.aml which also define other parts of the computer.

The real advantage of using Clover boot loader is that it builds a DSDT on-the-fly, as it loads the OS when starting up. Clover really is very simple to get going. You would do well to use a modern motherboard as well. The UEFI boot process is much easier to use that an older BIOS only boot process. Clover is really meant (in my opinion) to use UEFI booting. 

 

 

I do understand that a crucial part of what's done to get a Hackintosh working is to "fool" OS X into seeing Apple hardware when it's really just standard PC stuff. What makes things difficult for me, not being a software engineer of any kind, is that the multitude of tick boxes in the various Clover panes don't have any intuitive meaning (to me), and the Clove Wiki is characteristically hyper-technical or vague in defining them. All that means is that the definitions are simple and clear for those who already understand it all. In the end, everything is simple once you're already expert at it.

 

My current hardware is fairly "modern" or common--Z97 chipset; Haswell i5; HD4600 iGPU; Intel i218v ethernet; Realtek ALC892 audio.

 

After looking around, it seems that maybe combining the Hackintosh Vietnam tool + Clover Configurator might help, since the Vietnam tool contains some clearly labeled selections for the less tech-immersed person who wants to try a Hackintosh.

 

I had to take a break from this stuff for a while due to rebuilding my own Windows box, as well as getting a Mac Mini set up in the home for a family member. So at least I have a genuine Mac nearby now, but still would like to succeed in getting a functional Yosemite Hackintosh where I can do my own personal stuff.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...