[02bfoot]

Running a PowerMac G4 (AGP) with OS 10.3. Machine had 128 mg ram when purchased and was working perfectly with all applications. No problems until I ordered (from OtherWorld Computing) and installed a 256mg memory module. First the mouse froze; then on restart, could not get beyond spinning wheel. Started up with install disk which reported volume could not be repaired. Tried removing the memory module and restarting but still no luck. Bought DiskWarrior and ran that program which said the disk had been repaired; however, on restart could not get beyond spinning wheel.

I am using a new USB keyboard and mouse and have tried resetting the PRAM and firmware; starting up in safe mode and in single-user mode without success.

Anyone have any ideas as to what might be causing the problem; a work around or solution?

Thanks.

[reader50]

When DiskWarrior repaired the disk, what did it report in the way of problems? ie - what did it fix.

Try starting up in Verbose mode: hold command-v during bootup. Note where the boot process hangs, and what messages came immediately before it gives up.

In DiskWarrior, go to the Hardware tab and let it test your HD. You want to know what the SMART diagnostics report. Those are the HD's internal hardware diagnostics, they can indicate impending drive failure.

[02bfoot]

reader,

I could not save the report from DiskWarrior as immediately after using it the mouse froze and on an on. I believe it said the volumn had been repaired but what else???I will be working again tomorrow on the G4; will try starting up in Verbose mode and follow your instructions. I can't get past the spinning wheel to DiskWarrior at the present.

[mountainash]

Have you tried it with just the 128Mb stick in and/or just the 256Mb stick in? Some people have had problems mixing RAM. You could try the RAM in different slots in case you have a bad slot. Also, did you have the Mac unplugged when you added the RAM?

Sorry if the above is obvious. But my problems often have obvious solutions that I've overlooked

To see if it is a hard drive problem you can hold down 'option' while the mac boots (just when it chimes). If you can get to the startup disk selection screen without the mouse dying, it is a good sign. Also, if you have another mac with firewire ports available you can start it in target disk mode (hold down t as it boots), connect it to your PMac G4 with a firewire cable, and then from the 'startup disk selection screen' you can try booting from the other disk.

Also check the hard drive and optical drive cables. If one came loose, or is damaged you can get weird problems.

Also, you could try booting from CD (like the OSX install disk, or even better AHT). If you get the same problems, it isn't the hard drive (well probably not). If you are booting from the DiskWarrior CD (or are you running it from Hard drive??) and getting these problems, then it sounds like it isn't the hard drive.

So, you could have a RAM problem or a USB problem, or a logic board problem. Are they the original apple Mouse and Keyboard? I have had problems with some third party devices. You could check the USB ports for obvious physical damage. Bad connections can give you strange problems.

So you have any other cards in the machine or any other peripherals? Disconnect everything except the graphics card, monitor, and keyboard/mouse.

I think that's enough for now

[02bfoot]

First off, thanks to everyone for their help. What finally worked to get to terminal was reader50's suggestion that I start up in verbose mode, which is as far as I was able to get. I'm hoping, again, that someone can assist further.

Rather than retype all the text (which I did write down), the following is what seems pertinent: localhost syslogd: kernal boot file is /mach_kernal......ApplePMU::PMU FORCED SHUTDOWN, CAUSE =
-122.....v\mach.sym.....conf. kernal extensions.....vvvdyld: kextd can't open library:/System/Library/PrivateFrameworks/Bom.framework/Versions/A/BOM (No such file or directory, errno = 2)/etc/rc: line 133: 82 Trace/BPT trap kextd.....vvvvvvvStarting virtual memory.....vvvvWelcome to Macintosh.....vvUnable to open parameters file/System/Library/Startup Items/LDAP/StartupParameters, plish for item LDAP. (No such file or directory).....System Starter can't open library, blah, blah, blah, no such file or directory. Text ended at Starting kernal event agent.

DiskWarrior tech thought the bad memory stick may have damaged the logic board.

Thanks again.

[chris v]

It seems unlikely that a RAM module would harm the mother board, but that could be. Get the bad RAM out, & try resetting the parameter ram. Reboot holding down option+command+p+r until you've gotten maybe three chimes. Then see if you can boot from the OS X installer and run an archive and install & retain your user & application settings under Options... in the installer.

Just a shot in the dark.