|
|
Use wireless networking in safe boot mode
Starting up in Safe Boot mode doesn't bypass the VRAM--the VRAM is a set of chips containing the Mac's video image, and if these chips were bypassed, you'd see nothing onscreen. Safe Boot doesn't let some extensions load, which activate specific extended functions of various chips, including some function controlled by circuitry that's damaged in your friend's Powerbook. The "troublemaking" extension may be one of the ATI extensions at System/Library/Extensions; when it loads, it encounters an unexpected hardware fault, which prevents OS X startup from proceeding. So, if you want to start up the Powerbook without turning off all the extensions that Safe Boot mode turns off, use a process of elimination to find the specific extension that's causing the trouble, and move it out of System/Library/Extensions--first drag one of them out, restart, see if the problem still exists, and if it does, restart in Safe Boot mode, drag the next ATI extension out, restart, etc. Once you've found the troublemaker, drag the other extensions you removed, back into System/Library/Extensions, then repair permissions (since moving extensions out of, then back into, this location will mess up their permissions).
Use wireless networking in safe boot mode
To potentially speed this process up, startup in verbose mode by holding command-v on startup (or view the system logs after a failed start). You can often figure out what driver or hardware is causing the problem by noting the last item listed before the system fails.
Use wireless networking in safe boot mode
Agreed, but note that all 12" PowerBooks had Nvidia GPUs, so you'd want to look at the GeForce and/or NVDA kexts. |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.09 seconds |
|