- Joined
- Jul 8, 2012
- Messages
- 3
- Reaction score
- 0
- Points
- 1
- Your Mac's Specs
- iMac 2.5Ghz, iPad 2, Powerbook G4 Alum.
Hi all. I have a 12" Aluminum Powerbook G4 1.5 GHz, 512 MB RAM, that has two issues currrently keeping it out of working order, and I'd like to be able to get it working again for a family member who doesn't need a newer computer.
1) The screen is completely dark, but you can still make out screen images and print in light, especially sunlight. From what I have read online, this is a problem with something called an inverter, with which I am not familiar.
2) Whenever I boot up, even if I try to boot up from the install disks, I get an "invalid memory access" message.
I have a new memory module on the way to make it smoother, so I'll be able to try it out with that soon, but I also don't believe it's the replaceable memory that's the problem, because when I remove it, I still get the invalid memory access message. From what I've read on this issue, it seems this can be due to problems with on-board memory, video memory, or the logic board. Unfortunately the issue is not covered in sufficient detail in any thread I've found so far. I guess what I'm looking for is more of a detailed walkthrough to determine what the problem is and what I can do to fix it.
Thanks,
Netherfox
1) The screen is completely dark, but you can still make out screen images and print in light, especially sunlight. From what I have read online, this is a problem with something called an inverter, with which I am not familiar.
2) Whenever I boot up, even if I try to boot up from the install disks, I get an "invalid memory access" message.
I have a new memory module on the way to make it smoother, so I'll be able to try it out with that soon, but I also don't believe it's the replaceable memory that's the problem, because when I remove it, I still get the invalid memory access message. From what I've read on this issue, it seems this can be due to problems with on-board memory, video memory, or the logic board. Unfortunately the issue is not covered in sufficient detail in any thread I've found so far. I guess what I'm looking for is more of a detailed walkthrough to determine what the problem is and what I can do to fix it.
Thanks,
Netherfox