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


Click here to return to the 'A fix for an 'Open With: Not Applicable' errors' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
A fix for an 'Open With: Not Applicable' errors
Authored by: IslandDan on Aug 25, '04 08:46:12AM
From: http://developer.apple.com/carbon/tipsandtricks.html#RebuildLS

How do I rebuild the LaunchServices database?
So you've just added a beautiful large icon to your application but it's not showing up. The problem may be that the LaunchServices database needs refreshing. The best way to force LaunchServices to rebuild its database is to delete its files by do the following: From the "Terminal" application:

cd ~/Library/Preferences/

rm LS*
rm .LS*
Then log out and log back in.

[ Reply to This | # ]
A fix for an 'Open With: Not Applicable' errors
Authored by: DavidRavenMoon on Aug 25, '04 10:14:32AM
That page must be old. Apple hasn't used the LS files for a while. Running that in the terminal returns "rm: LS*: No such file or directory" and "rm: .LS*: No such file or directory" This might work on Jaguar (which I doubt) but doesn't work on Panther.

This has been covered here before. The correct way to do this is:

/System/Library/Frameworks/ApplicationServices.framework/Frameworks/LaunchServices.framework/Support/lsregister -kill -r -domain local -domain system -domain user

Keep in mind that after you rebuild your LaunchServices database, it will also reset the warnings asking if you want to open that file with that application, as I mentioned above.

As I mentioned, the reason for "Not Applicable" being listed in the "Open With..." list is due to not having opened that application since the last time the database was rebuilt. It has nothing to do with Type/Creator codes or the LaunchServices database needing to be rebuilt, since rebuilding it will just make you have to reenter much of this data all over again. Type/Creator codes just bypass the data base, since the OS doesn't have to look up the file extension. Apple started doing this after the Safari exploit, where an "unknown" file could be downloaded, mount a disk image, and launch a terminal script without your consent. Now instead you get the notice asking if you want to launch that application. "Unknown" applications cannot be assigned to a file in the "Open With..." pull down, so you get "Not Applicable" instead. Try launching the application first, and then you will see that you can now assign it to a file.

---
--
G4/466, 1 GB, Mac OS X 10.3.5

[ Reply to This | # ]

A fix for an 'Open With: Not Applicable' errors
Authored by: gvitale on Aug 25, '04 11:52:30AM

David,
the lsregister DBs are driving me crazy after the last security updates: every time I launch some (specific) files (word. powerpoint and other carbon apps) I repeatedly get the first time launch dialog, so it seems that some application-file combinations do not manage to register as trusted in my system (PBG4 10.3.5)!
Any idea of what the reason could be?
Thanks in advance,
gaetano



[ Reply to This | # ]
A fix for an 'Open With: Not Applicable' errors
Authored by: DavidRavenMoon on Aug 25, '04 12:13:11PM

gaetano, I find for the most part that they stick for me. It's important to launch the program first, then select one of the files associated with that program, Get Info and change the "Open with:", and click the "Change All" button to make it the default.

The only time I have problems is with Classic apps, and/or different versions. For example, PageMaker 6.5 files still require me to dismiss the dialog before PageMaker 7 will launch in Classic.

You can try rebuilding your database, but you will have to reset all your custom file/app combinations (i.e.PDF files default to Preview) and once again open most of your applications and reset the Open With setting.

It seems possibly that files that can be opened by more than one application need to be set, and files that only open on one application do not. Also files with Type/Creator codes, which many applications still use in OS X, seem to override the need to set this.

---
--
G4/466, 1 GB, Mac OS X 10.3.5



[ Reply to This | # ]