Let me update this thread with some of my experiences so far.
Updating from 10.5.2 to 10.5.3 was a little tricky and required several reinstalls before I got it working. I used a combo updater put out my “Mysticus C.” This was the only updater that worked for me. The other updaters would only partially update the system or lock it up in the middle, which would result in kernel panics upon restart.
Once that was done, I switched over to using some EFI strings for my hardware rather than using injectors. The only injectors I used previously were for the video and audio. Using EFI strings is a way of getting OSX to see your hardware and support it natively. It’s a bit tricky and I used
this guide (it may require registration; I don't remember) to add strings for my video and audio. This way you can actually remove the injectors from your system altogether, which speeds up the boot process and makes your OSX behave more like a real Mac.
I (mostly) solved the problem with not being able to boot with both cores enabled. The problem was only partially related to the NIC. The real problem was actually the drivers for the nForce SATA controller. I had noticed that when the system locked up, it wasn’t really locked up; it was just in an unresponsive state. Windows still updated, the pinwheel still spun around, and the terminal window I had open still had stuff going on. Seeing the terminal window respond let me get the idea of watching the system logs when it locked up. So I figured the problem out by booting with both cores enabled, then setting up a scenario that would guarantee a lockup. Before I made the system lockup, I ran “tail -f /var/log/system.log” from the terminal to watch what was going on when the system locked up. When it locked up, a bunch of strings that looked like “Macintosh kernel[0]: disk2s2: data underrun.” started popping up after a couple minutes. This told me the problem was related to the SATA drivers and not the NIC drivers. The guy who wrote the drivers, MeDevil, had released an updated “TEST” driver that was meant to fix some SATA DVD drives. I decided to give these drivers a shot and surprisingly, the system no longer locked up under the same scenario.
However, there were still problems with the onboard NIC. With both cores enabled, the system would now freeze with
any network activity. Since I haven’t got the Intel NIC working yet in OSX, and I didn’t feel like putting my RealTek 8139 back in to test some more, I got the idea of using FireWire. Since I have my real Mac right next to my PC, I just ran a firewire cable between the two, enabled internet sharing on the real Mac, and that was it. My network now works flawlessly and I can use both cores.
The SATA drivers are still not perfect and I can get the system to lockup when doing work with large files. As long as I don’t try to edit 8 GB files, the system will boot and work flawlessly.
The only thing left to solve, which I don't think can be solved with my motherboard, is enabling the use of the
HPET. The use of this is kept inside the power management kext, which will not load on many, many, many systems. Loading this kext will almost always guarantee a kernel panic.