Ever since I installed Tiger I've been having oddities with the "Open With" contextual menu option.. specifically, some of the programs that show up are listed twice!
When I upgraded to Tiger, I installed it to a new partition. Once installed, I copied over my primary apps from the /Applications folder of the 10.3.9 partition over to the Tiger /Applications folder. It appears any app that I copied over to the active OS partition are the ones that show up twice in "Open With".
Bear in mind that I've long since deleted that old partition, so those old apps shouldn't be affecting Tiger anymore. It's almost as if whatever db Tiger uses to know which apps open which programs is remembering that I had two copies of the app visible to the OS at one time.
It's most unusual!
Attached is a grab of that I'm talking about.
edit: I should note, I had performed a complete search of all my partitions and there is infact only one copy of each program on my hard drives, so that rules out any other copies being picked up by Tiger. I've also had Spotlight reindex all my drives just to be sure it wasn't responsible for the problem.
When I upgraded to Tiger, I installed it to a new partition. Once installed, I copied over my primary apps from the /Applications folder of the 10.3.9 partition over to the Tiger /Applications folder. It appears any app that I copied over to the active OS partition are the ones that show up twice in "Open With".
Bear in mind that I've long since deleted that old partition, so those old apps shouldn't be affecting Tiger anymore. It's almost as if whatever db Tiger uses to know which apps open which programs is remembering that I had two copies of the app visible to the OS at one time.
It's most unusual!
Attached is a grab of that I'm talking about.
edit: I should note, I had performed a complete search of all my partitions and there is infact only one copy of each program on my hard drives, so that rules out any other copies being picked up by Tiger. I've also had Spotlight reindex all my drives just to be sure it wasn't responsible for the problem.