Find me a hackintosh owner who has had easy upgrades every time
I have since 10.5.2- maybe 10.5.6 might count as 'not easy' since I skipped it on my main Hack due to problems I saw others having. I didn't miss it one bit, as I saw nothing it offered over 10.5.5 anyway, and then with 10.5.7 (which was a breeze) it was moot anyway.
and never had to reinstall the os due to kp or has never had issues with sound, sleep, opening dmg's, using over 4 gig ram, dvd burners, usb issues and I will revoke my statment
Start revoking. I don't even know what would cause problems with half of that stuff. (Opening dmgs?)
No DVD burner has caused me any problems, nor do I see that any big issue with other Hack users.
USB issues? like what? None here. That could just be bad hardware.
I haven't had to reinstall the OS unless I wanted to.
Sound is an 'issue' for all of the two minutes it takes to patch it. If the onboard audio is really a consistent issue, then one can use an $8 USB sound adapter that actually sounds better anyway, is driverless, and presents no problems with any OS.
Over 4GB of RAM is simply a limitation of the motherboard. One can simply get a mobo that takes 8GB or 16GB, etc depending on budget and need. If there's any actual 'issue' with using more than 4GB of RAM, I haven't heard of it. (Briefly, in the early days of retail installs, I recall an issue with some boards using over 2GB of RAM- but that was brief, and long since fixed.)
Fact is most have had to do countless installs to get things working perfect as a wrong kext will eff up your system
It'd be foolish to do 'countless installs'. One simply has to realize "Hey, I'm using a Hack, not a real Mac", and then follow a few rules accordingly.
First off, the 'a kext can kill your OS' thing: If that's the case, then the solution is bone simple- create a backup partition of at least 12GB- it can be on any drive, including the main drive- and either clone the OS or do a second install of OSX on it. OSX doesn't care how many times the same OS is installed on the same system, or even on partitions of the same hard drive. It's like putting together 2+2 to realize you can use this fact to your infinite advantage, and all it costs is the 12GB or so for a backup install.
Use each install to label the system/library/extensions folder of the other. (Hey, it's OSX, with nifty features like
file labels. Why not USE these features to one's advantage?)
Now do any questionable update or kext install on the backup install with a labeled system folder. If it doesn't boot? Guess what? Open the system folder from the OTHER install, and... oh gee- there's a kext or two in there WITHOUT A LABEL. Let's scratch our heads of for a moment figuring out which kexts we'd then remove and have the system back to the exact same state of pristine it was before.
On the other hand- if the install goes perfectly, we now know it's safe to apply the same kext on the main install. (And also give it a different label, so we know that kext(s) was added after the main set).
A simple procedure like this -done every so often as needed, not just willy-nilly on an otherwise perfectly working system- will keep things running pretty effortlessly. It just requires a little thought first, not pretending every little thing will be
exactly the way Apple would do it.
Remember, I picked out components that were known to be very compatible with 10.5 when i bought the parts
Didn't make it anyless aggravating at times
Rather than just declare everyone's experience as the same though, consider that people just work out ways around things, knowing that the possibility exists. In the end, it makes life a whole lot easier- following just my own backup rule above, my main Hack has had no down-time since July 2008 when I first built it. Currently I'm at 10.5.8 with no issues- just I haven't yet installed Snow Leopard. Granted,that probably will present a pretty good challenge since some things have changed, but I recall that Leopard itself was the same way when it first came out.