I have a 2004 model Dual 1.8GHz 2.2Gbs RAM. The problem is that it keeps booting into Open Firmware. Once it gets to Open Firmware and i can mac-boot and start up off the Tiger disc, but I can't get it to find an external firewire OS. I don't have a hard drive in there at the moment but that should not effect this issue, Although I can see the firewire 800 in disk utilities but not on the Firewire 400. And still no Start up folder when i go to startup disk 800 or 400. If I put a hard drive in which i will when the new one arrives I believe i will be able to start up with it but I still think that it might boot into Open Firmware again. (I think a bus is bad maybe the Firewire bus if it is can't I bypass it somehow? so that is won't boot into Open Firmware.
Note: everything passes Hardware Test
I have Reset PRAM and NVRAM Rest all
Had the same problem. I took mine into a "Mac Genius" at the retail store and he thought he had fixed it by rebuilding the directory. It booted and shut down perfectly while in the store. When I got home it was went right back to booting into open firmware.
I figured out by accident that the reason it was booting fine in the store was because he was using a cheap SVGA monitor on the DVI output - not the ADB connector I use with my older Apple monitor. Note that Apple has phased these type of connectors out. It gave me a great excuse to upgrade my monitor to a 20" cinema display and everything is working great (can't believe how I've deprived myself all these years).
If you have an older monitor that uses an ADB connector, try a different monitor that uses the DVI output on your video card. Even a DVI-VGA adapter (one probably came with your computer) with a VGA monitor is sufficient for testing. If your computer boots up, it's either the older monitor, or the ADB output on the video card that is bad. There is no easy way to know where the actual problem resides (the Geniuses couldn't tell me - they have no monitors in the store with ADB connectors), but I can tell you that my computer is working fine now. I do know that the ADB connector ran power, USB and video all together and that seems to be the reason they quit using them. The newer desktops have only 2 DVI outputs (instead of 1 ADB + 1 DVI), while the new monitors run power, USB and video separately.
(Sorry this is in here twice - I'm pretty experienced with Macs and PCs but a little new at message boards - pls forgive)
Had the same problem. I took mine into a "Mac Genius" at the retail store and he thought he had fixed it by rebuilding the directory. It booted and shut down perfectly while in the store. When I got home it was went right back to booting into open firmware.
I figured out by accident that the reason it was booting fine in the store was because he was using a cheap SVGA monitor on the DVI output - not the ADB connector I use with my older Apple monitor. Note that Apple has phased these type of connectors out. It gave me a great excuse to upgrade my monitor to a 20" cinema display and everything is working great (can't believe how I've deprived myself all these years).
If you have an older monitor that uses an ADB connector, try a different monitor that uses the DVI output on your video card. Even a DVI-VGA adapter (one probably came with your computer) with a VGA monitor is sufficient for testing. If your computer boots up, it's either the older monitor, or the ADB output on the video card that is bad. There is no easy way to know where the actual problem resides (the Geniuses couldn't tell me - they have no monitors in the store with ADB connectors), but I can tell you that my computer is working fine now. I do know that the ADB connector ran power, USB and video all together and that seems to be the reason they quit using them. The newer desktops have only 2 DVI outputs (instead of 1 ADB + 1 DVI), while the new monitors run power, USB and video separately.
I was having the same problem with similar hardware and the auto-boot true seems to have worked... (3 correct restarts so far). Shouldn't the reset-nvram have set the auto-boot as well though?