General Question

bluemukaki's avatar

Why can't I instal Leopard on my PowerBook G4?

Asked by bluemukaki (4332points) February 26th, 2008

Here’s the thing, I have installed Leopard on my PowerBook G4, but I installed an update, 10.5.2, which killed my computer and started making it Kernel Panic. I re-installed Leopard, but when I went to install it, I got an error message repeatedly that said “Could not install some files in Volumes/Macintosh HD”. The weirdest thing is that I can still install Tiger and everything works fine, and I know Leopard works fine on my machine, so what’s going on!

Observing members: 0 Composing members: 0

8 Answers

cwilbur's avatar

At a guess – how old is your computer? how large is your hard drive? Is it possible or likely that you did an Archive and Install when you installed Leopard for the second time, and ran out of disk space?

segdeha's avatar

fsck is your friend. Go here and do as Apple says!

blunckhouse's avatar

Were you using Unsanity’s Application Enhancer on Tiger prior to installing Leopard? There was a known issue where installing with APE installed would corrupt the Leopard installation. Happened to me with a G4 Powerbook and my C2D iMac.

As cwilber asked, Leopard can’t be installed on machines slower than 867mhz, so if it’s a Titanium PBG4, it might be slower than that.

bob's avatar

Yeah, good call, it’s probably the Application Enhancer conflict, but most people (including me) don’t know 1. what that is or 2. how to get rid of it. blunkhouse, do you have a link to how to fix that problem?

blunckhouse's avatar

Here’s Apple’s “official” fix for the Unsanity APE error:
http://docs.info.apple.com/article.html?artnum=306857

There is plenty of information out there. Just Google Leopard and Unsanity and you’ll find hundreds of articles about the conflict.

Hope this helps.

bluemukaki's avatar

No my HD is completely free, no space occupied. Secondly, Leopard has worked on this computer before.

segdeha's avatar

My guess is your hard drive is beginning to bite the dust. I’ve heard of “journaled” hard drives masking significant problems. That’s why I suggested the Apple support article that walks you through booting into single-user mode and running fsck until your disk has no more errors.

bluemukaki's avatar

Fixed it by installing using target mode and an iMac. The combo drive was too slow to read the install according to the people in the apple retailer I talked to. Thanks for your help guys!

Answer this question

Login

or

Join

to answer.

This question is in the General Section. Responses must be helpful and on-topic.

Your answer will be saved while you login or join.

Have a question? Ask Fluther!

What do you know more about?
or
Knowledge Networking @ Fluther