Welcome to the MacNN Forums.

atomiks · May 22, 2003, 10:47 PM

Hey there, All,

I've just helped a friend install OS X on his G3-upgraded 7600, using XPostFacto. Everything was going OK until we tried to enable a PCI-Radeon hack that went awry. He also has another Voodoo3 card left over from the time that they were still made.

Now, when the system is started up, the grey Apple appears, but then eventually turns into a circle with a slash through it, something similar to a "No Smoking" sign. The machine doesn't boot after this at all.

Does anybody know what this screen means?

OptimusG4 · May 22, 2003, 11:40 PM

Non supported? Either that or it can't find a valid system folder. I had this once before on a BRAND NEW G4 1.25GHz machine. A fresh reinstall helped.

moonmonkey · May 22, 2003, 11:56 PM

Originally posted by atomiks:
Hey there, All,

I've just helped a friend install OS X on his G3-upgraded 7600, using XPostFacto. Everything was going OK until we tried to enable a PCI-Radeon hack that went awry. He also has another Voodoo3 card left over from the time that they were still made.

Now, when the system is started up, the grey Apple appears, but then eventually turns into a circle with a slash through it, something similar to a "No Smoking" sign. The machine doesn't boot after this at all.

Does anybody know what this screen means?

Take the voodoo3 out, unplug all SCSI and USB (if it has USB) and restart.

atomiks · May 23, 2003, 09:07 AM

Well, after a good night's sleep, and a wipe of the disk, OS X will at least re-install, but we're getting all sorts of fun with it not booting right now.

But, the I think OptimusG4 is correct, that it has something to do with a broken/missing System folder.

Thanks, all.

kupan787 · May 23, 2003, 04:39 PM

Originally posted by atomiks:
Well, after a good night's sleep, and a wipe of the disk, OS X will at least re-install, but we're getting all sorts of fun with it not booting right now.

But, the I think OptimusG4 is correct, that it has something to do with a broken/missing System folder.

Thanks, all.

Try booting in verbose mode (hold down cmd-v at startup) and see if anything happens. Hopefully some text will start going by, and you can see where it craps out.

Angus_D · May 23, 2003, 06:02 PM

If it can't find the kernel you won't get to verbose mode. If you installed YDL recently and you have a dual-HD system, that could be the problem (I experienced this, known bug - see their site for the fix).