Restored vol - document icons trashed

[supuhee]

Originally Posted by dnanian

This really seems to indicate a damaged drive -- you have to understand that the command isn't "mine", as such, but the normal procedure for rebuilding the LaunchServices cache.

You can't really assign the icons "on the fly", either, because they're generated at runtime based on the application associations.

What happens if you try to inspect one of the "bad files", and then change its launch association with the "Get Info" inspector -- and then click the "Change all" part, too?

Being sure that your diagnosis was correct even if the cure did not work, I tried a backup from HD to clone: "Safety clone- shared apps and users" and "Copy newer files...". Having used HD for the last few days because the clone acted up, I figured that Frameworks on HD would be newer. Indeed, that seems to have done the trick. During the backup Sys/Libr/Frameworks was copied, and the cure has lasted through 2 restarts.

On File Buddy, the bad files show the correct creator and type so File Buddy does not let you change anything. I then changed one file to a different type and told FB to match a good file. It was changed properly except for the icon.

I doubt if the (20 GB) drive is at fault. I run SMART Reporter every hour, and the Tiger clone on another partition works OK. Mac HD sits on another, brand-new drive (300 GB, but my Sawtooth G4 sees only 120 GB; could that be the problem? I tried an Acard controller which fixed the size problem but caused both internal drives to be regarded as SCSI, with SMART disabled).

Anyhow, the problem seems solved.

[dnanian]

You definitely shouldn't use "Copy Newer" for this, supuhee -- "Smart Update" is the way to go (which is a *superset* of Copy Newer).

It's weird, though -- the Frameworks shouldn't be newer at all if you didn't install any OS updates. But, it would copy the LaunchServices cache, and maybe that made a difference.

I don't think the drive's at fault -- but rather the OSX install. It's possible that the Sawtooth is causing some issues -- I don't have one to verify -- but, again, this is really not something we've had reported, and other than the LaunchServices cache -- which is doing the associations -- I don't know what the problem could be.

I'll continue to try to reproduce it at this end, though, and if you come up with any additional information or insight, let me know.

Thanks!