[alphasubzero949]

Tiger developers: Any compatibility issues with DiskWarrior 3.0.2? Will it be safe to run when Tiger ships?

[Millennium]

As I understand it, Tiger doesn't actually make any changes to the filesystem itself: Spotlight stores its metadata in ordinary (though hidden) files. As such, it should be safe to run DiskWarrior on such files. You may need to rebuild or re-index your metadata afterwards (if such an operation exists), but the filesystem itself should not break. This is inconvenient, but hardly fatal.

This is similar to the what happened with 10.2.3, which introduced HFS Journaled. DiskWarrior would work with this, but it would deactivate Journaling in the process; you had to activate it again afterwards. When DiskWarrior was updated for OSX, this was fixed.

My guess is that an update will follow soon after Tiger, fixing this inconvenience. In the meantime, however, it is unlikely that there will be any problems with using it.

WARNING: I'm not a Tiger developer, nor do I have Tiger by any other means. This is just what I can figure out from what they've said publicly, coupled with how they've worked with HFS+ in the past. I could, in theory, be wrong.

[Angus_D]

You could always ask Alsoft when Tiger ships.

[bewebste]

Alsoft won't know whether 3.0.2 will work with Tiger until the final version of Tiger actually ships. Sometimes stuff breaks with intermediate seeds of an OS release, sometimes it gets fixed again. If you're running a seed, of course, you're running at your own risk anyway. But just wait until Tiger final ships and Alsoft will announce compatibility then.

[alphasubzero949]

If the filesystem hasn't been changed between Panther and Tiger I don't see how stuff in the app could have been broken. Either way, looks like I'll be sitting out on the Tiger opening night when it happens.