Re: Docs to Unix files ?s
- From: John McGhie <john@xxxxxxxxxxx>
- Date: Fri, 04 Dec 2009 00:35:17 +1100
Hi Norm:
Just apply the fix Corentin gave you, to each file as you find it.
Now you know why I suggested you should not use the Migration Assistant :-)
Mac OS keeps a database of which file extensions are mapped to which
applications. The old File Type and Creator Code mechanism from OS 9 has
been deprecated.
By "deprecated" I mean it should still work for creator codes and file types
that were known in OS 9. But the mechanism is probably not fully up-to-date
because Unix/Mac OS X runs on file name extensions.
During application installation, the Installer publishes a list of the file
extensions each application can handle, and a priority order (the
application's native file format is top priority, other formats it can
handle are given lower priorities).
If Migration occurs before an Application has been installed, or if the
application cannot be installed, the Launch Services database entry for that
file extension is "blank".
If the file extension is blank, the file will automatically be assigned as
"unknown".
In either case, the file will show up as a "Unix file" (which is basically
the Launch Services daemon saying to the OS X system "I have no idea, you
figure it out").
In some cases, of course, the file legitimately IS a Unix file. Unless you
know what it is, it's not easy to determine which of the three possibilities
it is.
If it is a Unix file, or the file contains embedded metadata, the system can
figure it out by reading the file header. If you later install an
application that publishes the fact that it can open the extension, all the
files with that extension will suddenly flip to the correct icon.
In rare cases, you will have to help, using the technique Corentin told you
(which manually updates the Launch Services Database to associate that file
with the correct application).
Hope this helps
On 3/12/09 8:19 AM, in article
3sOdnTUglbZyRIvWnZ2dnUVZ_qJi4p2d@xxxxxxxxxxxxx, "Norm"
<NOSPAM@xxxxxxxxxxxxx> wrote:
In article <1j9mpcc.ete7wyg4o3e8N%korventeen@xxxxxxxxxxxxxxx>,
korventeen@xxxxxxxxxxxxxxx (Corentin Cras-M�neur) wrote:
Norm <NOSPAM@xxxxxxxxxxxxx> wrote:
A curiosity question from a novice....
Anyone know why several (found 4 or 5) of my Word documents would change
to "Uniix Executable Files" and when opened would present a login to
Terminal? The modified dates for most are several months ago for 4 of
them and one last week.
Thanks for any info.
Bad entry or corruption in your Launch Service database.
Hopefully, simply selecting the file in the Finder, pressing command-i
to select Open With and chinsing Word (apply to all) should do the
trick,
Corentin
Corentin:
Thanks again for the help with this.
I'm curious.. .... I found one more file.
All these Unix files seem to be dated near or at the time I migrated to
Snow Leopard.
What causes this problem? And should I be looking for other problems
with this?
Thanks again,
Norm
--
The email below is my business email -- Please do not email me about forum
matters unless I ask you to; or unless you intend to pay!
John McGhie, Microsoft MVP (Word, Mac Word), Consultant Technical Writer,
McGhie Information Engineering Pty Ltd
Sydney, Australia. | Ph: +61 (0)4 1209 1410
+61 4 1209 1410, mailto:john@xxxxxxxxxxx
.
- Follow-Ups:
- Re: Docs to Unix files ?s
- From: Norm
- Re: Docs to Unix files ?s
- References:
- Re: Docs to Unix files ?s
- From: Norm
- Re: Docs to Unix files ?s
- Prev by Date: Re: Bibliography cannot show correctly with an unrecognize font.
- Next by Date: Re: error message "this command is not available in this version of Microsoft Word"
- Previous by thread: Re: Docs to Unix files ?s
- Next by thread: Re: Docs to Unix files ?s
- Index(es):
Relevant Pages
|
