Um, what, it goes where, it crossed the road?

[bsmh75]

Now that I got your attention.

 

One of the things I hate about the hackintosh community is that the most common information your given is what that person used to make their hackintosh. Thats great and all, if I want to build that exact same machine. None of the tutorials I have found tell you why that person chose that method of install or why they used that driver. There seems to be this assumed knowledge that all potential hackintoshers are supposed to poses. I guess were supposed to learn it by osmosis, because I haven't found a guide that explains the basics of hackintosh. Questions like, what is chameleon for example? Why would I use that over another? Is there another? What is vanilla? What files are swapped out to make hackintosh possible? iAtkos? iDeneb? What do these files, apps, scripts do and why do I need them? This community is big enough to support a concise definitions, explanation, description page. It would go a very long way to help future hackintoshers make wise decisions and build stable hackintosh computers.

[Gringo Vermelho]

Bah. It's never enough, is it.

 

One of the things I hate about the Hackintosh community are the clueless newcomers who post here and want everything handed to them.

 

You have to understand that everything you need to know is here already, you're just not looking hard enough.

 

Most of what I know I found out by reading, here on InsanelyMac and some other scene forums, mainly ProjectOSX, EFI-x users and VoodooProjects, and by experimenting - trial and error.

 

If you want to know more about Chameleon, go to the VoodooProjects forum, visit the 'General Discussion' forum for Chameleon and read the documentation.

 

Vanilla means unmodified. For example, "Vanilla Kernel" means the original kernel that ships with OS X. As opposed to a patched kernel (such as the Voodoo kernel and derivatives) that allows OS X to run on incompatible CPUs such as AMD or Pentium 4.

 

Here's a history lesson - two major paradigm shifts in Hackintosh history:

http://tgwbd.org/darwin/boot.html

http://www.insanelymac.com/forum/index.php?showtopic=127896

 

Other links of interest:

http://en.wikipedia.org/wiki/Apple%E2%80%9...el_architecture

http://www.osxbook.com/blog/

http://en.wikipedia.org/wiki/OSx86

[Dellmantt]

Bah. It's never enough, is it.

 

One of the things I hate about the Hackintosh community are the clueless newcomers who post here and want everything handed to them.

 

You have to understand that everything you need to know is here already, you're just not looking hard enough.

 

Most of what I know I found out by reading, here on InsanelyMac and some other scene forums, mainly ProjectOSX, EFI-x users and VoodooProjects, and by experimenting - trial and error.

 

If you want to know more about Chameleon, go to the VoodooProjects forum, visit the 'General Discussion' forum for Chameleon and read the documentation.

 

Vanilla means unmodified. For example, "Vanilla Kernel" means the original kernel that ships with OS X. As opposed to a patched kernel (such as the Voodoo kernel and derivatives) that allows OS X to run on incompatible CPUs such as AMD or Pentium 4.

 

Here's a history lesson - two major paradigm shifts in Hackintosh history:

http://tgwbd.org/darwin/boot.html

http://www.insanelymac.com/forum/index.php?showtopic=127896

 

Other links of interest:

http://en.wikipedia.org/wiki/Apple%E2%80%9...el_architecture

http://www.osxbook.com/blog/

http://en.wikipedia.org/wiki/OSx86 <- some of this is outdated but still very useful

Well said Sir.

 

And i will add that starting a post with "One of the things I hate about the hackintosh community" is not about to win you any friends or any assistance.

Maybe if you apologised and listed your hardware and what you want to achieve!

[eldix]

One of the things I hate about the hackintosh community is that the most common information your given is what that person used to make their hackintosh. Thats great and all, if I want to build that exact same machine. None of the tutorials I have found tell you why that person chose that method of install or why they used that driver. There seems to be this assumed knowledge that all potential hackintoshers are supposed to poses. I guess were supposed to learn it by osmosis, because I haven't found a guide that explains the basics of hackintosh. Questions like, what is chameleon for example? Why would I use that over another? Is there another? What is vanilla? What files are swapped out to make hackintosh possible? iAtkos? iDeneb? What do these files, apps, scripts do and why do I need them? This community is big enough to support a concise definitions, explanation, description page. It would go a very long way to help future hackintoshers make wise decisions and build stable hackintosh computers..

 

You got a PC? install Windows or Linux in it!

You like OS X? buy a Mac.

 

You want run a OS meant for Mac on a PC? fine, seems to be plenty of those around. Read up, join a community, expect trial and error, tons of google searches, endless hours reading to learn the exact bit of info you need (or google it better!) and you'll be there.

 

I started my OSx86 project less than a month ago, without knowing anything about it. Read, learned from other ppls experiences and messing around myself, cause the reason I wanted a OS X is because I like messing with my PC. Windows did my computing needs quite well already.

 

This community has provided tons of invaluable info from others ppl experience and answered my query when someone was able to know what to answer. Without mentioning the drivers and bootloaders ppl created that I wouldn't be able to do myself to achieve a working Hackintosh.

[Gringo Vermelho]

But wait, there's more!

"common sense"

 

What do these files, apps, scripts do and why do I need them? This community is big enough to support a concise definitions, explanation, description page.

 

The community is you. Feel free to start that page.

 

If you're looking for 'concise definitions', you must ask concise questions.

 

"What do these files, apps, scripts do and why do I need them?" is like asking what's the meaning of life, the universe and everything. It is a question that cannot be answered in any meaningful way, or perhaps in the end can only be answered by you and not anybody else. As Beth Gibbons sang back in '94, "no-one can see inside your view".

 

"What is fakeSMC.kext"? is a good, specific question, it is humanly possible to provide a specific answer that will be useful to you.

 

But start by typing 'fakesmc' into google before asking anyway.

 

When asking questions, keep in mind that nobody knows how much you know, nobody knows your level of understanding of what components make up a PC or how those components interact. Intermediate-level knowledge of PC architecture is required, otherwise nothing you read here will make sense to you. "Advanced users" usually will not want to do any hand-holding. When asking about something, show what you know, so that whoever answers you will be better equipped to provide an answer that is meaningful to you.

 

It's confusing when you first arrive here and everything is new. Therefore, when searching, try to tackle one issue at a time. Okay, so you discover that Chameleon is a boot loader (it is a lot more than that, but at its core, that's what it is). If you have no clue what a bootloader is or what it does, the first thing you should do (as with any technical term you might stumble upon, such as "DSDT", "ACPI" and "AHCI" for example) is type wiki bootloader into google, which would take you to this page: http://en.wikipedia.org/wiki/Booting#Boot_loader - likewise you might have seen many, many posts saying to set your motherboards SATA controller to AHCI mode in the BIOS. If you are curious, your first stop could be Wikipedia. Again, you could google wiki AHCI to find some basic information about what you're dealing with.

 

Acquiring some basic knowledge (such as what you can gain from reading Wikipedia articles) will provide you with the vocabulary required to better understand the many technically inclined posts, guides and tutorials that you may find here on IM. It will also help you immensely when you search for information.

[bsmh75]

Of course, all of you are right. I first want to apologize for the above post. It was posted after a frustrating day of fruitless research. Its ironic that I found this post Link right after the above post.