I'm running Jag on both my file server and on the 10 or so clients on my network. I have a network NetInfo db set up using NFS so that any user can access his/her account, files, and environment from any machine in the office. I am also using NFS to export a share filesystem, where we save all of our collaborative work.
The problem I have is that prior to starting with this organization, there were many files (primarily Office docs) that were not saved with file extensions. These files will not open correctly on any of the client machines, because the file association does not exist. If I try to use the Open With section of the Get Info pane, and click on the Change All button, it prompts me to accept the change, but says:
This change will apply to all Microsoft Word documents with type "????"
The file association is not saved, and the problem persists.
I wonder if this has something to do with resource forks in NFS? I saw an older AppleCare doc that applied to OSX server, which said that NFS didn't export resource forks, but that was for the first version of OS X, and it had a note that it didn't apply to later versions. Any thoughts here?
If it is a resource fork issue, is there another way to do this with a different protocol? (It MUST be automountable).
Anybody?
Top
