Jun 21, '05 09:39:00AM • Contributed by: macassist
I had a couple of Classic applications that had been refusing to open since an Archive & Install upgrade to Tiger. They would show up as only an "application" in the Get Info window, and would also say that they were set to Open with Script Editor. Double clicking on them would result in Script Editor launching and complaining about being unable to load the dictionary.
I did a search on the Apple discussions areas a couple of weeks ago with no luck -- the same search tonight turned up this thread in which the suggested fix was to add a ".app" extension to the offending program(s). This did work, but it got me thinking that maybe the problem was related to file extension interpretation.
When I looked at the names of all the programs affected, I saw that they all ended with a single numeral "extension," which was part of the version number of the app. That is, any app with a single numeral from 1-9 following a full stop was exhibiting the problem, while those with a ".0" or double digit "extension" were OK. I changed a working copy of "Adobe PageMaker 6.52" to "Adobe PageMaker 6.5.2," and it changed its status in the Get Info window and made it fail like the other apps. Then I changed a non-working "Disk Copy v6.4" to "Disk Copy v6.40," and it fixed the problem.
It doesn't explain why someone else on the discussions area is having problems with .sea files, but it probably solves most of the problems people are having with this.
