TO: MaLd0n, oldnapalm, janek202, nawcom, el coniglio & others

[fbifido]

Hi,

 

I have seen software to help build a hackintosh:

 

AutoPatcher, SystemInfo, DSDTEditor, Chameleon, OSX86Tools, Kext Wizard, and others.

 

It would be nice if you could put all these macware into one program to make the post-install work a little better.

 

Like SystemInfo, it can tell what hardware you have, but it does not give you options as to what kext you need!

 

I don't know how to say this, or if what i am saying is not making any scene, but hair me out:

 

What i am looking for:

 

1. AutoPatcher or DSDTEditor will generate the dsdt.aml file with corretcion and stuff!

 

2. SystemInfo will generate the hardware list information, say sysinfo.list.

 

3. <need software> will look at the sysinfo.list to see if a dsdt fix can be done to make any of the hardware work, if not it list and download all the .kext file needed to make the hardware work, plus generate a like of the kext and which directory they must be in (E/E or S/L/E), say we call that kextinfo.list.

 

4. Kext Wizard would then take the kextinfo.list and install the .kext to their respected directories and then do a repair permissions and rebuild mkext/cache

 

5. Chameleon Wizard would then install the lastes version of the bootloader.

 

 

 

 

6. this is just a note: if you ask how to get the needed kext, well SystemInfo as a database of .kext located at http://olarila.com/kexts/, i have never downloaded any kext from this site, i think the download is disable. and i think kexts.com should have a few .kext to download from.

 

7. Video - i have never ever gotten any video card to work properly in any version of mac os x with QE/CI, so i have no idea as to how to get this part fix, sorry. i have a:

 

8086; Intel Corporation

 

2e32; 4 Series Chipset Integrated Graphics Controller;Display controller;VGA compatible controller

 

 

most motherboard i can buy have this video chipset or the 4 Series Chipset.

[XLR]

Thread needs moar e/e kexts who automatically inject hardware device vendor&id's in s/l/e kexts innit.

[Dellmantt]

What we don't need is another OSX86Tools type program.

This search will tell you the Video chip you have & there is NO support for it

http://www.google.com.au/search?hl=en&...0l0l285l285l2-1

[bubbaganoush]

There is no be all end all solution to definitively telling users what hardware will work and what kext is needed for their hardware. This is especially true for laptops since many laptops can use exotic hardware or hardware that differs a lot from standard Apple parts. (keep in mind that the less similar your hardware is to what Apple uses the less likely it is that it will work on OSX)

 

This task is in the hands of you and you only. Know your hardware. Search the forum. Read all the threads.

[Gringo Vermelho]

Another thing to consider is that in the end, if/when there's a problem with your Hackintosh, there is no point-and-click software to hold your hand and help you make the right choices.

 

And because you used all those helpful GUI apps to get going, you have no real idea about how things work, which means you won't be able to troubleshoot, you won't know where to begin or at worst, even what to type into google to find out where to begin.

 

As a simple example, there are several helpful apps that will install sleepenabler.kext for you, but exactly none that will delete it for you when it causes your hack to not boot after updating.

 

Don't get me wrong, I have nothing against GUI tools - until the point where they cause brain deterioration or complete lack of curiosity on the users part.

 

And this is where you go completely off into dreamland:

3. will look at the sysinfo.list to see if a dsdt fix can be done to make any of the hardware work, if not it list and download all the .kext file needed to make the hardware work, plus generate a like of the kext and which directory they must be in (E/E or S/L/E), say we call that kextinfo.list.

That's simply not possible, it will never work. Realistically - who will maintain the kext database, who will host it, who will make sure that is is up to date? Would you? There are millions of different PC configurations out there. What works for me will not necessarily work for you, even on similar hardware! What about differences between motherboard revisions or BIOS revisions? What if the user ran this amazing wonder tool but already has patched kernel extensions or some alternative solution that the tool doesn't know about, what would happen then? Would you maintain kext repositories for each and every version of OS X or only for the latest version? And so on. Keep dreaming man.

[Swhay]

It's a nice idea, but like the others said, if you want to run OS X on a PC, you better learn to get your hands dirty and learn all you can. If you just want an easy simple solution that works, go buy a real Mac.

[XLR]

It's a nice idea, but like the others said, if you want to run OS X on a PC, you better learn to get your hands dirty and learn all you can. If you just want an easy simple solution that works, go buy a real Mac.

 

This.