On 2012/01/03 12:12, Bruce Johnson so eloquently wrote:
On Jan 3, 2012, at 10:31 AM, Tina K. wrote:
DW is probably more likely to fix it, but running fsck from Open Firmware
instead of the boot drive, and possibly permissions repair, might be
helpful.
Applejack doesn't run fsck from Open Firmware, but from single-user mode, and
the results of running fsck and Disk Utility are indistinguishable, because
what DU is doing is running fsck under the GUI.
Yes, I got mixed up again. Sometimes my brain can't distinguish OF from SU. But is
it not better to run fsck from SU or a different drive/partition/disc? Like
testing RAM in SU rather than the boot volume?
Permissions repair will do nothing whatsoever for this issue, since that
applies to executable files only. Only things listed in /Library/Reciepts will
ever figure into Permissions repair. (and not all of those...PR only ever looks
at Apple-supplied files.)
I'm generally hesitant to recommend PR but it is possible some important file
somewhere has incorrect permissions and is gumming up the works. Can't hurt
anyway, better to try every non-destructive possibility before taking more drastic
measures.
Tina
--
Acceleron: HP Presario 2.8GHz Celeron D 2GB RAM Discrete graphics XP Pro
Luxo Jr: iMac 20" USB 2 1.25GHz G4 2GB RAM GeForceFX5200 Ultra 64MB VRAM 10.4.11
Worm: PowerBook G4 15" HR-DLSD 1.67GHz G4 2GB RAM Radeon 9700 128MB VRAM 10.5.8
Quadrophenia: Mac Pro Mid-2010 2.8 GHz QC 6 GB RAM Radeon HD 5770 1GB VRAM
10.6.8
--
You received this message because you are a member of G-Group, a group for
those using G3, G4, and G5 desktop Macs - with a particular focus on Power Macs.
The list FAQ is at http://lowendmac.com/lists/g-list.shtml and our netiquette
guide is at http://www.lowendmac.com/lists/netiquette.shtml
To post to this group, send email to [email protected]
For more options, visit this group at http://groups.google.com/group/g3-5-list
