On Feb 26, 2005, at 1:39 PM, John C. Welch wrote:
The problem is, on a broken system, AppleJack induces a new
variable...oh,
option 2 didn't' work...is it AppleJack or something else?
john
Sure, but there is a better than good chance that AppleJack will run
just fine.
Look at it this way:
I can have a savvy designer run AppleJack. I can have 1st and 2nd level
support in a mostly MS enterprise try AppleJack. If it doesn't fix it
or doesn't run then the system is fuxored to the point that I would be
going on-site to fix it anyway. Why throw away that easy first stab at
it? I have better things to do than drive all over he place running
fsck and diskutil. Certainly you have supported people who try running
DiscWarrior or something similar on a Mac before they ask you to come
out right? IMHO, AppleJack is a safer tool than that.
Josh
