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


Click here to return to the 'And prevent ._ files on windows shares ?' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
And prevent ._ files on windows shares ?
Authored by: demental on Feb 26, '03 09:25:13AM

Hello, this tip would really be helpfull to me if it'd work on a windows shared partition.

Is there a way to prevent Mac from making ._myfile.ext when I copy or modify myfile.ext onto the windows partition ?



[ Reply to This | # ]
And prevent ._ files on windows shares ?
Authored by: knucklecheese on Feb 26, '03 12:01:55PM

This is a file system problem rather than a network protocol problem. Remember that HFS volumes contain multiple data-bearing forks. I believe that by transfering files between HFS and NTFS, FAT, FAT32, and UNIX file systems, the current technology strips the data fork from the mac file and places it in a seperate file in the single-branched pc or UNIX file system.

The reason?
When the file gets xferred back to the Mac, the extra files are necessary to re-combine both forks on the HFS file system in order for the "Classic" System and Apps to know what to do with them. If the PC simply discarded the additional data, you would have a huge problem on your hands when the older Mac Systems tried to use the resulting files. I understand that this is irrelevant to exclusive OSX users, but remember that most OSX installs still exist on HFS volumes and will behave the same way as classic files in this situation.

The solution?
I don't know of a solution right now, but there will be in the future. Once all aspects of the "Classic" operating system are extinct, Macs will be able to use alternative (UNIX) file systems, which will put an end to the problem.



[ Reply to This | # ]
And prevent ._ files on windows shares ?
Authored by: demental on Feb 27, '03 05:39:46AM

Do you mean that if I reinstall my Os on an UFS formatted disk (as I don't use classic anymore), this could work ?



[ Reply to This | # ]
And prevent ._ files on windows shares ?
Authored by: germsteel on Oct 10, '03 07:04:56PM

No just reinstall OS X without classic on HFS+ Stay away from UFS



[ Reply to This | # ]
And prevent ._ files on windows shares ?
Authored by: germsteel on Oct 10, '03 07:07:05PM

Actually I've done that and the ._ files are still created. So nix this theory it doesn't work.



[ Reply to This | # ]
And prevent ._ files on windows shares ?
Authored by: nodje on Nov 22, '03 02:53:26PM

I'm actually facing the same problem, but even a littlebit worst than that.
I can manually delete the .DS_Store file on a windows share (which is boring but still fine), but I've got some .DS_ file that are created and these files are simply unaccessible, undeletable ...
I've got a "Cannot read the source file or disc" from windows when trying to delete it, copy a folder that contain one .DS_. The windows partition get kind of corrupted!
I've tried everything but could'nt find any solution
Does anyone have an idea of where those .DS_ file come from?
Does anyone did already see them?
I can't find any reference on them on the web.

nodje



[ Reply to This | # ]
And prevent ._ files on windows shares ?
Authored by: Vocal Velocity on Oct 11, '04 04:10:22PM

Under Macintosh OSX .DS_Store holds the information which controls the way a folder will be opened; i.e., the shape and size of the window, the position of the window on the desktop and whether file, folder or icon view has been selected. If you were to delete the .DS_Store the folder would revert to the system default next time it is opened and a new blank .DS_Store would appear (invisibly).
I wanted to post this here for a clear understanding what the .DS_Store file is and help everyone understand that it probably will not be going away anytime soon.



[ Reply to This | # ]