If you believe the CD drive is not working, you might be able to boot from an external Hard Drive with a bootable version of MacOS X installed, or from another mac running in "Target Disk" emulator mode connected by firewire cable (boot it holding down "T"). If that still fails, and you think it's the CD that's bad, I'd encourage you to find another - perhaps borrow one from a friend. You might try booting your computer while holding down the "C" key to force it to boot from CD-Rom. However running repair disk "in the background" doesn't let you see the result of running the repair disk function. If Repair Disk fails to repair your disk, you'll need Alsoft's fine Disk Warrior program. Once to repair the problems, and a second time to make sure it really did solve the problems and doesn't find any more. If Verify Disk does find problems, run Repair Disk twice. If Verify Disk finds no problems, we'll need to consider using a bigger hammer. Note that you can use the "Verify Disk" button without rebooting, however you'll need to boot your Mac from a different disk, or from the MacOS X Install CD (then quit the installer and select the Disk Utility from the menu bar) in order to use the "Repair Disk" button on the drive you are currently booting from. The more important thing to do as well if you haven't yet is to use the "Verify Disk" button, and if it reports any errors then for sure use the "Repair Disk" button - both of which you will find in the same Disk Utility window where you found the "Repair Disk Permissions" button. I wouldn't worry about the messages it displayed. Repairing the disk permissions was a good move. That's about it, if anyone has any ideas, much appreciated. I also created a new user acct, and it also has the same trash problem. The privileges have been verified or repaired on the selected volume We are using a special uid for the file or directory. System/Library/Filesystems/cd9660.fs/cd9660.util. We are using special permissions for the file or directory. Repairing disk permissions always returns this: The only other weird/coincidental thing I've noticed is that Cyberduck no longer works. I also started up in single-user mode, ran fsck, found two 'overlapped extent allocation' errors (two files in the same folder as the two corrupted ones), I deleted the overlapping files, and fsck doesn't report any more errors. I finally safe booted, made it to the desktop, restarted and have been able to use my machine normally (except for the trash thing) all this week. Once at the finder, my machine would freeze. The next day, I got kernel panic on boot up - several times - and was only able to make it to the finder up once I unplugged the network cable. I backed up my work and shut down for the day. ![]() This all came about after I noticed a couple of image files for a design I was working on became corrupted unexpectedly. Trash folder in my finder, and can move them in and out. ![]() ![]() I cannot open the Trash to view the contents by clicking on the Trash icon, though I can see the contents in the. I also tried the 'TrashIt!' app, but that does not work, though after I run TrashIt I am able to empty the trash once normally. I've been able to empty the trash regularily in the time being with the 'SuperEmptyTrash' app. ![]() It's not an option-key / locked file thing. Basically, when I attempt to empty the trash, the finder crashes (all desktop icons disappear and then reappear) and the trash does not empty.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |