MacInTouch Tiger Compatibility Page

Good, we agree then. Please realize that I'll continue to post about bugginess as it continues to be lamented about on the Mac web, though. I don't need to rehash this discussion every time I point to other sites that are covering issues with Tiger (some of which, like the Safari memory leak and the problems that Spotlight seems to cause in certain situations with external drives, would seem to be present whether you've upgraded, done an archive and install, or a full erase and install.)

We don't disagree there, C.K. I fully admit, after having gone through both other "faulty" methods myself, that Apple _really_ let us all down on this one. There comes a time, though, when you just have to be realistic. These problems aren't just going to go away, and Apple updates can't fix, say, Adobe CS's missing files. What Apple needs to hear is: "This is ridiculous, and we aren't going to accept such a horrible job migrating from you anymore." What Apple Users need to hear is: "Geez, this sucks for us, but if you *really* want to get rid of all these problems, do an E & I, and send feedback to Apple as to how angry you are." Otherwise, what you're going to have are an increasing rift between the two sets of Tiger users. On one side are everyone who trusted the Upgrade and the A&I routes. On the other side will be the E&I's and everyone who purchases a new Mac. E&I sure is the Windows right. Just because it was the wrong way for Apple to work, doesn't mean that it is the wrong way for users. You are forsaking lasting system benefits why? Out of principle? Be rational. Your machine (and your readers) won't fix themselves because you hold to a higher cause. Oxford English Dictionary: STUBBORN (a) having or showing dogged determination not to change one's attitude or position on something, especially in spite of good arguments or reasons to do so Apple broke it, but they can't fix your machine now. People need practical advice at this stage, not whines and rants on things that Apple couldn't apply post-upgrade fixes to even if they wanted to.

djones, this is exactly where we disagree. If you bother to look around the mac web right now, you'll see *tons* of "mac-web-leaders" posting things like the MacInTouch Compatibility Chart which I link to in this post. No matter how much you continue to argue that Apple *should* only offer one upgrade path, the erase & install, as that is the one that works, the fact of the matter is that Tiger comes with several more options than that and there are a lot of people out there who have taken those other paths. "So what? Backup and do it the right way!" you continue to argue, but as I continue to point out: after going over everything with a fine tooth comb, the problems I'm experiencing are small and intermittent, and I've already wasted a good amount of time on this OS, as have many others. It *is a huge* indicator of a buggy OS if only one of the multiple installation choices are useful and if there is no good way to troubleshoot problems for those of us who took the other paths. Erase and install is a Windows solution. It never has been a Mac one on such a large scale. Now, before you reply back with a singular vision, "why don't you just erase and install, you're not being fair to Tiger" rant again, try actually clicking on the link in this post and looking at some other websites in the Mac community where you will see a lot of teeth-gnashing about all these small problems with Tiger. "They all have bad installs," may continue to be your argument, but it is a bad argument, as all of them installed according to the little basic directions and via a basic installer which Apple provided. That is the problem.

I'll let it go as soon as you "let go" of all of the problems you're encountering. If you're going to bother to post on a blog about how bad Tiger's bugs are, or continue to bring up problems that you're having, I'm going to continue to remind you why. You don't have a day? How long do you think it will take you to go through that list of problems and solutions individually? Priorities are what they are. If your job requires you to have a fully functioning work-reliable machine, and the same for your co-workers, why in the *heck* did you go upgrading everyone to Tiger in the first place? Take some bleeding responsibility. You are a Macintosh community leader. Make the time to take the steps necessary to give yourself a clean base. You'll not only get rid of all these problems, but you will then be in a position to be fair to the platform, the OS, and your thousands of readers. WWSD.

djones, let it go. "Or one measily day to Erase and Install and reinstall *all* of your applications." I *don't* have one measily day right now. Maybe in two months, but right now I'm swamped and 99% of that swamp is dependent upon a working computer. Tiger *is* working for me; there are just a lot of niggling little bits that are driving me batty considering that I cannot take a day off to rectify the situation.

"and I'd rather not reinstall" I don't get this philosophy. You have one visible problem resulting from files missing because the program wasn't installed under your current OS. Who knows how many latent hidden problems you might also have? It will steal 5-10 minutes of your life to reinstall the application. Or one measily day to Erase and Install and reinstall *all* of your applications. How can you place such a low value on long-term function and stability of your machine that you really /can't be bothered/ to take the few moments to do something *one* time, the right way. This is completely analogous to a child not wanting to get a vaccination because he thinks the shot will hurt--not realizing that the pain, both in severity and duration, will be much worse when he gets the illness than the brief inconvenience of the shot.

Interesting... I have had that Photoshop problem since I got my Mac. But I used to be a Windows user, so I did what any good Windows user does... ignored it.

from Adobe Solution 1: Copy the Adobe Unit Types file to Library/Scripting Additions. Copy the Adobe Unit Types file in the Previous System folder to [hard disk]/Library/Scripting Additions. I don't have the previous system folder, and I'd rather not reinstall CS... is it possible to grab that file from someone else's CS install?

The fix is described here: http://www.adobe.com/support/techdocs/329996.html

FWIW, take a look at the definition of "stubbornly". Apply that definition with a brief analysis of the time you've already wasted in productivity loss dealing with Tiger problems. Add to that the idea of going through that exhaustive list linked in this post and trying to apply fixes to applications and parts of your system one by one. Most of the fixes will require a reinstallation of the application. If you're going to reinstall a bajillion apps anyway...