I have an iBook G3 that is now working thanks to a donor iBook. I got a Mac OS 10.4 DVD and installed Tiger on it without any problems. The problem I am having lies with the OS 10.4.11 Combo Update from Apple, I can't get it to install correctly. The first time I downloaded it and tried to install it, (via Software Updater) it failed installing it. So I downloaded a copy off of Apple's website and tried it that way. It worked, the iBook restarted and it would stall at the Apple logo and spinning wheel. After 30 minutes, I hard booted it. It seemed to get further (finally got to the "Starting Mac OS X" screen) and then it would stall with the status bar at 100%. It also wouldn't recognize the trackpad and I had to plug in an external mouse to move the cursor around (even though you couldn't do anything). This morning I reinstalled 10.4, it went to restart and it produced a kernel panic (Sys. Failure: cpu=0, code=00000001 (Corrupt stack) ). I rebooted, and I got the infamous "You need to restart your computer" message at the Apple logo screen. So for a third time, I reinstalled Mac OS X 10.4. Everything works, got through the installation and back to the desktop. I tried to install the Combo updater for 10.4.11 again (via. package from Apples site, not the software update), it goes all the way through it and at the end says "Update failed, try again". I tried to reopen the installer but it would automatically close after I open it. So I go to the apple menu and click "About this Mac" and it says I'm running 10.4.11 now. I reboot, and now I'm back to where I was, the iBook just stalls at the Apple logo and the spinning wheel. The hard drive sounds like its doing something every now and then, but not much activity. Any suggestions on what to do from here? I ran the "Apple Hardware Test" CD, and everything passed. Previously (before the RAM upgrade and swapped hard drive) I had problems with Mac OS 9 giving me bomb errors at random (even after a clean installation). Somebody told me that the RAM soldered to the logic board could be bad, but I have no idea what to do with that (thought it was more of a hard drive issue at the time). I do have another 256MB stick in there now which seems to be working fine.