My Powerbook G4 will not get to the login screen and stops at the splash screen only.

I was using 3.5 and thought that my have been the issue, so I booted from a 3.51 CD and installed.

No luck.

I tried erasing the PRAM by removing the battery and holding the power button down.

No luck.

It still only boots to the splash screen.

Booted from the CD and access the system partition and all seems ok. Ran SFS doctor and it didn't find any issues.

Still no luck...

I did notice the light on the button to open the keyboard stays on at the splash screen. Not sure if that means anything...


Any ideas???

[ Edited by matt3 08.03.2014 - 21:00 ]

Update:

The dh2: partition which I use for extra storage won't mount when I boot from the MOS 3.51 CD. Not sure if this helps...

How is your HD-partition layout?

There should be (single bootsystem):

1. boot-partition , normaly called "Boot", Filesystem HFS, choosed button "mountable" (not "bootable")
2. Systempartition with bootable MorphOS, normaly called DH1 or SYS or something else on your choice. Filesystem SFS, choosed buttons: mountable and bootable, priority 0
3. some more partitions on your choice, SFS and mountable....(Filesystem may be changed to 64bit-filesystem "ICE-FS" later)

On boot partition must be following files (found in directory mac-ppc32 on your MOS-CD)
boot.img (quark kernel)
boot.txt (booting-guide)
bootinfo.txt (tells open firmware to load and run boot.img and where MorphOS-Systempartition is located)
VolumeIcon.icns (Icon for MOS-HD you can see in MAC-bootmenue)
macofboot (needed to identify the MAC - only needed for first installation)

On System-partition you need only to install the content of the MOS-Iso, without the different boot.images and mac-ppc64 and mac-ppc32.

Normaly installer should do this for you. Maybe there went something wrong - check that.....

If Mac hangs on MOS-bootscreen (*NOT* Open Firmware-Screen), it may be helpfull to delete file Sys:Prefs/env-archive/sys/poseidon.prefs from HD and reboot....

Thanks for the help Harry.

I fixed the problem by running SFS Doctor even though it didn't seem like anything really was wrong with the filesystem.

> boot.img (quark kernel)

...plus ABox.