Is a Hackintosh hard to maintain?

[MacUser2525]

Hi there.

 

I have scrubbed the drive completely. Set it up in GUID with one partition HFS+

 

Am just in the process of reinstalling the OS and trying again.

 

I had tried the active setting of the partition before you had replied. No luck

 

Do you have any ideas if it fails again?

 

Many thanks.

 

Edit : I had the drive as GUID beforehand as well so its not that that was the problem

 

It should just work but I seem to remember something about a startupfiletool I think it is called that can be used just checked my notes from my original retail install way back here they are.

 

 3. install EFI bootloader from video partition after having ejected all volumes on target drive.

MacUser2525s-mac-pro:~ MacUser2525$ sudo -s
Password:
bash-3.2# bash-3.2# cd /Volumes/video/Retail_Install_Folder/EFI/pc_efi_v80/

bash-3.2# ./startupfiletool /dev/rdisk2s2 ./boot_v8
HFS+ filesystem detected
Looking for 1 words free
reading 4096,4096
Marking word 410
writing back 4096,4096
allocated blocks 32 at start 13120

bash-3.2# dd if=./guid/boot1h of=/dev/rdisk2s2 bs=512 count=1
1+0 records in
1+0 records out
512 bytes transferred in 0.012084 secs (42370 bytes/sec)
bash-3.2# dd if=./guid/boot0 of=/dev/disk2 bs=400 count=1
1+0 records in
1+0 records out
400 bytes transferred in 0.035598 secs (11237 bytes/sec)

 

You find the rdisk2s2 (disk2) by looking at the Info for the partition in diskutil and I don't think this is really necessary but it can't hurt doing this then installing the Chameleon.dmg and chameleonsm later in the install.

pc_efi_v80.zip

[stuppy]

LOL.

 

Ok your suggestion in the last post changed something.

 

Now I get

 

boot0: booting

boot0: done

HFS+ partition error

 

If it was working properly, would I be presented with a command line thing saying Darwin, and i can type stuff if I want? It shows me the drive with Leopard, but when I select it, it loads a couple of lines then the computer just reboots.

 

Its just an endless bootcycle now. Have tried -x for safe mode and -v and all that, but whatever I do, it loads a few lines really quickly and then just reboots. I can't even make out what its loading in the background.

 

Something about kext files.

 

One of the files that is trying to be accessed is extensions.mkext if that means anything to anyone.

[MacUser2525]

LOL.

 

Ok your suggestion in the last post changed something.

 

Now I get

 

boot0: booting

boot0: done

HFS+ partition error

 

This is better try the solution in this post boot from your Mac attach the USB and use diskutil list in the Terminal to find the proper numbers to use for the drive.

 

http://www.micropctalk.com/forums/showthread.php?t=2660

If it was working properly, would I be presented with a command line thing saying Darwin, and i can type stuff if I want?

 

It would be a few lines then a timer counting down from five to give you time to hit any key to enter some boot parameter to pass to the kernel you would need to use the -s switch here to get to single user mode which I believe is what you are describing. Otherwise once done the timeout you should see a text boot like I think you start to describe below then the graphics should load at the end to your Desktop after the machine has been configured the first time that is.

It shows me the drive with Leopard, but when I select it, it loads a couple of lines then the computer just reboots.

 

Is this after you start to boot the USB device because you should not have to select anything to boot it should already be there pre-selected then once timer runs down it boots.

Its just an endless bootcycle now. Have tried -x for safe mode and -v and all that, but whatever I do, it loads a few lines really quickly and then just reboots. I can't even make out what its loading in the background.

 

Something about kext files.

 

One of the files that is trying to be accessed is extensions.mkext if that means anything to anyone.

 

Hmm perhaps the Caches are corrupted or one of the .kext does not like to clear the caches attach the drive to your Mac then use.

 

 rm -r /Volumes/Your_Install_Partitions_Name/System/Library/Extensions/Caches
rm -r /Volumes/Your_Install_Partitions_Name/System/Library/Caches
rm /Volumes/Your_Install_Partitions_Name/System/Library/Extensions.mkext

 

Now once booting and you see the count down use the hit any key to type in then enter key -f this will force the reloading/caching of all .kext on the system. BTW what changes have you made to the BIOS setting I don't remember anywhere you having mentioned doing the ones I suggested you may even want to consider upgrading to the latest one available if outdated.

[stuppy]

Hi

 

Yeah I have been fiddling with the BIOS all the time trying different things.

 

I cannot find an option to disable IDE controller full stop. But I have tried disabling a lot of stuff.

 

Just tried your idea of clearing mkext and that. Then tried -f at cmd line. It showed a load of stuf on the screen then rebooted. Does the same thing for -s

 

BIOS is the latest one by the way

 

Any more ideas?

 

Many thanks.

[MacUser2525]

Hi

 

Yeah I have been fiddling with the BIOS all the time trying different things.

 

I cannot find an option to disable IDE controller full stop. But I have tried disabling a lot of stuff.

 

Just tried your idea of clearing mkext and that. Then tried -f at cmd line. It showed a load of stuf on the screen then rebooted. Does the same thing for -s

 

BIOS is the latest one by the way

 

Any more ideas?

 

Many thanks.

 

One more take the Jmicron files in the the Extras I posted just on the off chance that is what is on your board and then move the corresponding .kext in the USB drive /System/Library/Extensions folder like we did with the ones in the guide. Then copy and repair the permissions on the ones in the Jmicron floder you downloaded delete the caches/.mkext file and use the -f again when booting.

[stuppy]

Hi

 

That didn't work either. Im gonna read the P5W threads again. Don't understand why it would be failing if you think it should work.

 

Any more help would be appreciated. Many thanks.

[stuppy]

Getting further now. After playing the BIOS a bit more, it now appears to be booting - showing it initialising the hardware. It stops at the following line though :

 

localhost mDNSResonder [22] : Could'nt read user-specified local hostname; using default bDevice-0018F3C54ED8.localb instead

 

It says that 4 times each with different xxxx.localb bits. Ideas Thanks.

[stuppy]

Thanks for all your help MacUser2525 but I think I am going to call it quits. I have been trying for 2 days to get it working so its obvious I don't really understand it all. And I don't have enough time to read up and troubleshoot all the time. I'm gonna stick it out with my Macbook Pro )

 

Thanks again for all your advice. Sorry I couldn't put it to better user

[MacUser2525]

Getting further now. After playing the BIOS a bit more, it now appears to be booting - showing it initialising the hardware. It stops at the following line though :

 

localhost mDNSResonder [22] : Could'nt read user-specified local hostname; using default bDevice-0018F3C54ED8.localb instead

 

It says that 4 times each with different xxxx.localb bits. Ideas Thanks.

 

That is the part where it is getting the network going I noticed that board has two nic's if I remember from the specs I seen perhaps disabling one could help, might even be an idea to try the iDeneb (that was it you tried right) again if it is getting that far using the method were trying here.

 

Thanks for all your help MacUser2525 but I think I am going to call it quits. I have been trying for 2 days to get it working so its obvious I don't really understand it all. And I don't have enough time to read up and troubleshoot all the time. I'm gonna stick it out with my Macbook Pro )

 

Thanks again for all your advice. Sorry I couldn't put it to better user

 

Nah you put it to good use that damn board just does not seem to like this method. You may want to reconsider your original plan getting the EP45-DS3R board, a SATA burner and if necessary a power supply with the 8 pin connector reusing your other parts to keep costs down. I can tell you from personal experience with it that this vanilla install method will work without problems and the files you already have are more than enough to get it going. I could even generate you a DSDT.aml with the proper video card contained in it along with the networking if you wanted to give it a try, let me know if you do want to do it.

[chevy2410]

Dude don't give up!! Get the Gigibyte mobo you will have way less headaches. That Asus board is a good board to use, but can be tricky at time to get the install right. You might want to try a different disto. Try iPC OSX86 10.5.6. I just installed it on an external usb drive and for the most part everything worked out of the box. It has lot of options to check off at install, so most hardware is supported. It was created by the OSX86 guru ~pcwiz. Great guy who has made quite a few utilities to help out newbies with installing kexts files and so on.

 

 

Cheers,

Chevy

[stuppy]

Hi there...

 

Right - After being disheartened at not being getting it to work - I started looking at the Price of Mac Pros. I want to replace my Macbook Pro and Desktop PC with a beefy computer to run both OSX and Windows (!!!!). So I can build a fast computer to do both of these for half the price of a Mac Pro. So I think I am going to go down the hackintosh route. I am really greatful for all the help you have given me and I hope it will continue on my new venture haha

 

So I guess I should have said from the start the new build would need to run Windows and OSX. OSX being the primary OS and Windows the secondary. Is there a lot more stuff to do to dual boot? I intend on running them on one drive - split into two partitions.

 

I have several external hard drives connected on FW800. Will a third party FW controller work ok on a hackintosh or will I need to slow down to the FW400 port on the Gigabyte board?

 

My PSU is an Enermax - http://www.newegg.com/Product/Product.aspx...N82E16817194004 - I think this one will be ok with the new Gigabyte board?

 

I am just building my shopping list. Will post full final spec when done

 

Edit : chevy : Downloading the iPC one now Will let you know how I get on

[stuppy]

This is my proposed system.

 

Advice?

 

Thanks

 

http://www.scan.co.uk/Products/Chenbro-Gam...SU-Ultra-Hi-End

 

http://www.scan.co.uk/Products/Arctic-Cool...n-their-H-S-Fs)

 

http://www.scan.co.uk/Products/500-GB-West...6MB-Cache-89-ms

 

http://www.scan.co.uk/Products/120mm-Scyth...1F-Fan-1600-RPM

 

http://www.scan.co.uk/Products/120mm-Scyth...nt-Fan-1200-RPM

 

http://www.scan.co.uk/Products/Intel-Core-...ltiplier-Retail

 

http://www.scan.co.uk/Products/4GB-(2x2GB)...AS-4-4-4-12-DHX

 

http://www.scan.co.uk/Products/Gigabyte-GA...I-SATA-RAID-ATX

 

http://www.scan.co.uk/Products/512MB-XFX-9...x-DL-DVI-I-HDTV

 

http://www.scan.co.uk/Products/Thermalrigh...lated-heatpipes

 

http://www.scan.co.uk/Products/Scythe-Ninj...and-940-and-AM2

 

http://www.scan.co.uk/Products/1TB-Western...-300-32MB-Cache

 

http://www.scan.co.uk/Products/Sony-DRU-V2...-(Black-Silver)

 

Oh and http://www.newegg.com/Product/Product.aspx...N82E16817194004 that PSU

[MacUser2525]

Hi there...

 

Right - After being disheartened at not being getting it to work - I started looking at the Price of Mac Pros. I want to replace my Macbook Pro and Desktop PC with a beefy computer to run both OSX and Windows (!!!!). So I can build a fast computer to do both of these for half the price of a Mac Pro. So I think I am going to go down the hackintosh route. I am really greatful for all the help you have given me and I hope it will continue on my new venture haha

 

It can get just a bit frustrating that is for sure just PM me or start a new thread and PM with the link to it when you get the parts.

So I guess I should have said from the start the new build would need to run Windows and OSX. OSX being the primary OS and Windows the secondary. Is there a lot more stuff to do to dual boot? I intend on running them on one drive - split into two partitions.

 

Do yourself a favor two drives one for each OS it really is much easier to do that way you only need hit f12 when booting to select the drive to boot and hopefully it will be a 64bit version of windows as you will need to have two different sets of BIOS settings otherwise to load on boot one for 32 another for 64.

 

I have several external hard drives connected on FW800. Will a third party FW controller work ok on a hackintosh or will I need to slow down to the FW400 port on the Gigabyte board?

 

If it says it supports OS X then it should work fine although Mac hardware seems to priced considerably higher than PC most times with the controller type cards.

 

My PSU is an Enermax - http://www.newegg.com/Product/Product.aspx...N82E16817194004 - I think this one will be ok with the new Gigabyte board?

 

Looks good it has it all 80+ efficiency active PFC decent amount of wattage that will be more than enough I have owned 3 or 4 Enermax's they were rock solid never had a problem with them.

 

I am just building my shopping list. Will post full final spec when done

 

The rest looks good other than the video card I still say something like the 8800gt or family of card you will be able to you will be able to get them included in the DSDT.aml as I don't remember seeing any of the 9000 ones in there.

[stuppy]

It can get just a bit frustrating that is for sure just PM me or start a new thread and PM with the link to it when you get the parts.

Do yourself a favor two drives one for each OS it really is much easier to do that way you only need hit f12 when booting to select the drive to boot and hopefully it will be a 64bit version of windows as you will need to have two different sets of BIOS settings otherwise to load on boot one for 32 another for 64.

If it says it supports OS X then it should work fine although Mac hardware seems to priced considerably higher than PC most times with the controller type cards.

Looks good it has it all 80+ efficiency active PFC decent amount of wattage that will be more than enough I have owned 3 or 4 Enermax's they were rock solid never had a problem with them.

The rest looks good other than the video card I still say something like the 8800gt or family of card you will be able to you will be able to get them included in the DSDT.aml as I don't remember seeing any of the 9000 ones in there.

 

 

Ok cool. I'll use the 200gig drive that is in my current machine for Windows and the 500gb for OSX.

 

I feel like a right child now :/ I placed the order bout 5 minutes before you posted. I am buying it on credit so I am awaiting approval at the mo. So my order might not get processed. Are 7900GS cards supported? I could put one of those in in until a 9800gtx driver is sorted.

 

Fingers crossed my credit order should be approved and i'll have the system by the end of the week .

 

On the assumption the system comes - what method do you suggest I go with for installation? As you said previously - install to USB HDD and then clone to internal drive? What would you say is the best pre-patched ISO image out there?

 

Many thanks

[MacUser2525]

Ok cool. I'll use the 200gig drive that is in my current machine for Windows and the 500gb for OSX.

 

Good less headaches.

I feel like a right child now :/ I placed the order bout 5 minutes before you posted. I am buying it on credit so I am awaiting approval at the mo. So my order might not get processed. Are 7900GS cards supported? I could put one of those in in until a 9800gtx driver is sorted.

 

Yes I have the 256mb version in my extra machine right now feels snappier some times than my main machine even for some reason although the main install is about a year old the new a couple of weeks so probably cruft laying around.

 

On the assumption the system comes - what method do you suggest I go with for installation? As you said previously - install to USB HDD and then clone to internal drive? What would you say is the best pre-patched ISO image out there?

 

Many thanks

 

Yep install then clone not much for changes needed at all for it to boot if you move the IntelCPU aside and install the Chameleon.dmg and dsmos.kext in there it should boot right up add the DSDT.aml, chameleonsm, com.apple.Boot.plist, Openhaltrestart.kext and put the Audigy sound card in then install the kX driver and you should have a fully functioning system. I have not used a pre-patched system since the end of this month last year when I got my retail disk so can't really say much on them you don't need it anyway these boards are perfect for a retail install hackintosh.

[stuppy]

My order has been accepted!

 

Woohoo.

 

Are the defo no ways to get the 9800GTX working in OSX? Will it be long before a driver is released that works?

 

Thanks :D:D

[MacUser2525]

My order has been accepted!

 

Woohoo.

 

Are the defo no ways to get the 9800GTX working in OSX? Will it be long before a driver is released that works?

 

Thanks :D:D

 

It is not included in the DSDT patcher I think, but a quick search lead me to this looks like aquamac has a EFI string for it so it should be easy enough to include in the com.apple.Boot.plist would be better if you can get it in the DSDT.aml but that method works fine as well.

 

http://aquamac.proboards106.com/index.cgi?...&thread=509

 

Edit: It is not really drivers that are needed for the video all that the installer like NVinject do are take this string and inject it into the appropriate driver already included in OS X most likely the NV50 using the string stand alone in the com.apple.Boot.plist does this without any modifications to the system so allows upgrading without potential problems.

[stuppy]

It is not included in the DSDT patcher I think, but a quick search lead me to this looks like aquamac has a EFI string for it so it should be easy enough to include in the com.apple.Boot.plist would be better if you can get it in the DSDT.aml but that method works fine as well.

 

http://aquamac.proboards106.com/index.cgi?...&thread=509

 

Edit: It is not really drivers that are needed for the video all that the installer like NVinject do are take this string and inject it into the appropriate driver already included in OS X most likely the NV50 using the string stand alone in the com.apple.Boot.plist does this without any modifications to the system so allows upgrading without potential problems.

 

Hey there.

 

Good stuff. I posted a build check http://forum.insanelymac.com/index.php?showtopic=144714. Someone else seems to think the 9800family is good to go )

 

If everything goes smoothly I should be setting all this gear up on Friday night

 

I have a few more questions regarding the osx86 project if you don't mind?

 

When you see releases, like iDeneb and iPC - what is different about these releases? What does one offer that the other doesn't and visa versa? Also - if you install say, iPC 10.5.6 on to your computer - is that release locked at 10.5.6 or can you upgrade quite easily to 10.5.7 when its released?

 

The method you have told me (the one I tried with current hardware)... installing to USB and then cloning - what method is that called? Is it Vanilla?

 

Finally - when it does come to upgrading - what is your methodology? You would still a copy on the external USB drive - so would you install 10.5.7 straight away and see if it works? Or do you need to install it, and then remove some kext files (the CPU power one for instance)? How do you go about troubleshooting if you encounter problems? By looking at the logs to see where it failed? I would imagine a problem one person encounters, there will be more on this forum having the same problem - so together they can solve it?

 

I think a lot of my questions can probably be answered on the osx86 Project page - so please feel free to ignore questions that are easy for me to find myself.

 

Again... many thanks!

[chevy2410]

When you see releases, like iDeneb and iPC - what is different about these releases? What does one offer that the other doesn't and visa versa?

 

In my experience some distros take some stuff out, such as powerpc code, maybe languages, things that really aren't needed for most users. They also add the files are needed to boot that disc and make it work on a plain box pc. These distros are made really for first time OSX 86 users that don't want to fool around trying to get some thing to work. Most work right out of the box as long as you know what driver/kexts files you need for your specific hardware.

 

Also - if you install say, iPC 10.5.6 on to your computer - is that release locked at 10.5.6 or can you upgrade quite easily to 10.5.7 when its released?

 

It's not locked, but you could have issues with a system upgrade to 10.5.7. You can do upgrades to iTunes and stuff like that. I think and I'm not 100% sure that if you you used iPC and used the vanilla kernel and tried to keep your install as close to Vanilla as you can you might be ok for a system upgrade without issue. This is also a reason to clone your install to an external drive. That way you have something to test with.

 

The method you have told me (the one I tried with current hardware)... installing to USB and then cloning - what method is that called? Is it Vanilla?

 

Vanilla refers to using a non modified kernel from Apple. Cloning means you make a copy of that fresh install to another drive. Weather it be internal or external usb or firewire.

 

Hope this helps you out,

Chevy

[stuppy]

In my experience some distros take some stuff out, such as powerpc code, maybe languages, things that really aren't needed for most users. They also add the files are needed to boot that disc and make it work on a plain box pc. These distros are made really for first time OSX 86 users that don't want to fool around trying to get some thing to work. Most work right out of the box as long as you know what driver/kexts files you need for your specific hardware.

It's not locked, but you could have issues with a system upgrade to 10.5.7. You can do upgrades to iTunes and stuff like that. I think and I'm not 100% sure that if you you used iPC and used the vanilla kernel and tried to keep your install as close to Vanilla as you can you might be ok for a system upgrade without issue. This is also a reason to clone your install to an external drive. That way you have something to test with.

Vanilla refers to using a non modified kernel from Apple. Cloning means you make a copy of that fresh install to another drive. Weather it be internal or external usb or firewire.

 

Hope this helps you out,

Chevy

 

Hi,

 

Thanks for the info. Can't wait now to get the parts so I can start playing

[stuppy]

New computer should be here on Thursday

 

MacUser : Are you still ok to guide me through what I need to do to install OSX? I think I only really need help with putting the drivers into the install.

 

The full spec is in my sig. I will be using the onboard sound card for the time being. And my 24" monitor runs at 1920x1200. Someone has recomended NVdarwin ( http://forum.insanelymac.com/index.php?sho...aded&start= ). Sound good to you? Take it I just install it onto the partition before first boot?

 

Many thanks.

[MacUser2525]

New computer should be here on Thursday

 

MacUser : Are you still ok to guide me through what I need to do to install OSX? I think I only really need help with putting the drivers into the install.

 

Sure you don't really need much as I said before you have all the files now to get it to boot.

The full spec is in my sig. I will be using the onboard sound card for the time being. And my 24" monitor runs at 1920x1200. Someone has recomended NVdarwin ( http://forum.insanelymac.com/index.php?sho...aded&start= ). Sound good to you? Take it I just install it onto the partition before first boot?

 

Many thanks.

 

For the sound give a try with the files in the thread below for the graphics you do not need the NVdarwin just use an EFI string in the com.apple.Boot.plist it tells the system the capabilities of the card much better in the long run no need to worry about upgrades breaking the NVdarwin. I will make you Boot.plist up with the EFI string set for the PCI-e slot closest to the CPU (the 16x you want to be using anyways) along with the chamelonsm settings in there for a MacPro running at the stock speed unless you plan to overclock if you do then it is easy enough to edit the file yourself to change the bus and cpu speeds. Plus I will get you a DSDT.aml compiled without the graphics card in there it will be made using the F10 bios I used for mine your board should come with that I would think as it has been out for some time now. For the network card in the DSDT.aml for time machine I used the first NIC in the machine as I have my second card on the board disabled. Are you going to do the same? One more thing for the monitor make sure that you use the DVI connector closest to the motherboard some people have problems using the top one.

 

http://forum.insanelymac.com/index.php?sho...14739&st=40

[stuppy]

Sure you don't really need much as I said before you have all the files now to get it to boot.

For the sound give a try with the files in the thread below for the graphics you do not need the NVdarwin just use an EFI string in the com.apple.Boot.plist it tells the system the capabilities of the card much better in the long run no need to worry about upgrades breaking the NVdarwin. I will make you Boot.plist up with the EFI string set for the PCI-e slot closest to the CPU (the 16x you want to be using anyways) along with the chamelonsm settings in there for a MacPro running at the stock speed unless you plan to overclock if you do then it is easy enough to edit the file yourself to change the bus and cpu speeds. Plus I will get you a DSDT.aml compiled without the graphics card in there it will be made using the F10 bios I used for mine your board should come with that I would think as it has been out for some time now. For the network card in the DSDT.aml for time machine I used the first NIC in the machine as I have my second card on the board disabled. Are you going to do the same? One more thing for the monitor make sure that you use the DVI connector closest to the motherboard some people have problems using the top one.

 

http://forum.insanelymac.com/index.php?sho...14739&st=40

 

 

Hi MacUser.

 

Sterling advice as usual

 

Yeah i'll only need one LAN port and i'll be sure to use the correct DVI port. Thanks

 

Just a couple of questions regarding the DSDT.aml and boot.plist files.

 

The DSDT.aml file - is that some kind of configuration file? Is it native to OSX or is it a hackintosh addition to make the OS function properly?

 

And the boot.plist - is this a native Leopard file or something created for the osx86 project?

 

Sorry if it sounds like a dumb question. Just trying to get it right in my head how things work. I thought that drivers were installed by kext files? Or do you still need kext files to run the card, but then you configure your exact settings in the boot.plist file?

 

Many thanks.

[MacUser2525]

Hi MacUser.

 

Sterling advice as usual

 

Yeah i'll only need one LAN port and i'll be sure to use the correct DVI port. Thanks

 

Good.

Just a couple of questions regarding the DSDT.aml and boot.plist files.

 

The DSDT.aml file - is that some kind of configuration file? Is it native to OSX or is it a hackintosh addition to make the OS function properly?

 

Yes Mac's use a DSDT just not the same way we are supposedly the 10.5.6 was going to require us using it as well as the beta builds did a check for it and would not boot without a proper one apparently this is not the case now. It is still a good idea to use one as it eliminates modifying/removing .kext files that cause problems like the IntelCPU that will freeze the system due to a lot of BIOS's broken implementation of the HPET, ACPI table... plus people have figured out adding in the network fix for time machine, the graphic EFI strings.

 

And the boot.plist - is this a native Leopard file or something created for the osx86 project?

 

Standard Apple file yours on your Mac will be in the same location as on a hack but probably has nothing really specific in it the file is used to pass parameters to the kernel when booting among other things.

 

Sorry if it sounds like a dumb question. Just trying to get it right in my head how things work. I thought that drivers were installed by kext files? Or do you still need kext files to run the card, but then you configure your exact settings in the boot.plist file?

 

Many thanks.

 

Yes that is correct the .kext files are the drivers that make everything work most all of what we need to do is modifying the Info.plist files contained in the .kext to add the additional PCIID numbers that are missing because Apple only adds the ones for their hardware leaving out PC machine ID's that still will work perfectly with the driver but they don't ship that hardware so could care less whether those ID's are in there. This is the big myth that Apple perpetuates that somehow their hardware is different from a PC now that they are running PC Intel components these drivers will work on any old PC that has these chipsets in them. Apple just eliminates running on them by using an EFI firmware instead of a BIOS otherwise OS X would run with a couple of .plist modifications like we do now so it is all a hardware lock in by them to prop up Mac hardware prices above what they should be compared to a PC getting them a hell of a lot higher margins as they are buying the same parts as you or I do except they get a great deal due to their buying volume making them even more money in the long run.

[stuppy]

Yes Mac's use a DSDT just not the same way we are supposedly the 10.5.6 was going to require us using it as well as the beta builds did a check for it and would not boot without a proper one apparently this is not the case now. It is still a good idea to use one as it eliminates modifying/removing .kext files that cause problems like the IntelCPU that will freeze the system due to a lot of BIOS's broken implementation of the HPET, ACPI table... plus people have figured out adding in the network fix for time machine, the graphic EFI strings.

 

DSDT file - I take that just runs on bootup and tells it to ignore the troublesome kext files? Does this mean if I use the DSDT file - I don't need to manually rename the HPET and CPU kexts? DSDT is similar to a script?

 

 

I am starting to see the difference in the Vanilla method over patched images. Vanilla - files are only altered to include more information. The existing coding is not tampered with?. I take it this means Vanilla method means the OS is rock solid, just like it would be on an Apple Mac?

 

Sorry if I am repeating answers you've already given me. I am just trying to ensure I understand the process properly Thanks for bearing with me!.

 

So back to the DSDT file. Is there an App that you can build your custom file, to customising it to your hardware? I take it this means that once configured, you can copy the file to install before first boot, and if configured properly, the system should boot with all hardware installed and working? Or is it a case of coding the DSDT file, copying that AND the relevant kext files? Or can the DSDT replace the need for installing kext files (i.e. the program you use to build the DSDT file will inject the drivers into the file?) And since the DSDT file is never modified, OSX can never overwrite it to not include these drivers in the system? (hope that makes sense lol) - and that is why updating shouldn't case problems?

 

If when running an OS update, if something does break - is there usually an obvious reason why its failed? Like, is it always because the update has caused OSX to not play nice with the driver file? Or beacuse a plist has been edited somewhere along the line?

 

Since your Vanilla days, have you run an update and its completely wrecked your install and its taken you hours to fix?

 

Many thanks You're a lot more patient and supportive than many would be