Forwarding Address: OS X

Monday, May 02, 2005

Tiger tired of Classic?

Well, Tiger's arrived and the first machine it got installed on here is my wife's dual-processor G4. One of the main things she uses it for is Photoshop -- specifically, running Photoshop 6.0.1, not Photoshop CS. (CS is slow, and she doesn't feel like paying $BIGNUM for something she doesn't need.) Which means she's been running under Classic for a long time now. Here's the odd thing: unlike some folks we've not had any problems starting Classic, but Tiger's Finder seems to have decided that the Photoshop 6.0.1 application is actually a Script Editor document. Re-installing Photoshop worked for a while, but now the same thing's happening again. A get info on the file shows it as being an application, but for some reason the Finder wants to open it in Script Editor. Anyone got any clues?


  • maybe something to do with the new extended attributes in the file system. you could try poking around with some of the utilities mentioned here, like "xattr --list"

    By derek, at 10:31 PM  

  • Each version of Photoshop has been faster than the preceding one. So CS, being two versions later than 6, is actually significantly faster.

    By Jerry, at 1:40 PM  

  • from Macintouch...

    Karl Ploessl
    I had problems opening some applications under Tiger (G5, Dual 2GHz), especially Adobe Photoshop 7.0.1 and Adobe Acrobat 5.0. The applications lost their icons after upgrading. Using "disk utility " to repair permissions did not change that. The applications opened with the application "Script Editor".

    Checking with "get Info" revealed that the applications were set to use "Script Editor" to be opened with. Resetting them to be opened as themselves, resolved the problems.

    By Anonymous, at 10:25 AM  

  • This may be related to something posted on Macintouch the other day: it could be the ".0" ending on the file name. (Yes, that's lame.) Try adding ".app" to the file name and see if that fixes it.

    By Paul, at 12:10 PM  

  • paul is absolutlely correct. I had a copy of LiveMotion 2.0 which opened in script editor.

    I changed the name of the app to "Adobe" from "Adobe LiveMoiton 2.0" and it worked again.

    Note I needed to do this in the app's "get info" window. The first time I tried it in the Finder, nothing happened. Then I did a "get info" and found the name had changed to "Adobe". I deleted the ".0", got the confirmation dialog, and all is well.

    By Anonymous, at 6:11 AM  

  • I've encountered a few Classic and Carbon applications that Tiger has opened as Script Editor documents as well (an ancient version of CodeWarrior and a couple games from the early days of OS X). I was stumped, but adding the ".app" suffix as Paul suggests has saved the day! Wish I had found this page a few weeks ago, would have saved me some trouble. Thanks! -Jim

    By Anonymous, at 4:59 PM  

Post a Comment

<< Home