Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

10.4: A fix for certain Classic apps not starting Classic
Tiger only hintI 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.
  • Currently 1.80 / 5
  You rated: 2 / 5 (5 votes cast)

10.4: A fix for certain Classic apps not starting | 3 comments | Create New Account
Click here to return to the '10.4: A fix for certain Classic apps not starting' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
duplicate hint
Authored by: dom on Jun 21, '05 12:19:43PM
duplicate hint
Authored by: macassist on Jun 22, '05 03:44:27AM

Well, I see them as complementary - I didn't see the other hint when I did a search (for "Classic") because it's a specifically Classic problem I saw and which was covered on the Apple Discussions, so I started a new hint, which also has a fairly detailed description of the source of the problem.

Adding .app is one solution, but there's a part of me which doesn't like making something look like something it ain't, and these Classic Applications aren't Application bundles. So, I'd rather modify the version number so that it ends with two digits, hence my differing suggested fix.

If others are having problems with specifically Classic apps not starting, the subject and content of my hint will be found, whereas the other won't be, so I'd rather not delete mine and add it as a comment to the other hint.



[ Reply to This | # ]
10.4: A fix for certain Classic apps not starting
Authored by: vykor on Jul 26, '05 06:19:36PM

Another possible fix for these recalcitrant Classic apps is to blow away the file and the associated cache files at /Library/Caches/*-.csstore, and then rebooting the system.

I just had this problem crop up in one of my user accounts. Forcing LaunchServices to rebuild its database seemed to have resolved the problem.

[ Reply to This | # ]