|
|
Apple Double Files - causing problems with Directory Scanner Hi, I'm just wondering if anyone else has come across this bug. I have 6 mac minis all running the same app, which were all copied onto the machines from the same (FAT32 formatted) memory key. 5 are running fine, but on 1 the apple double files (._) are being picked up as images by the directory scanner. I am going to try using a HFS formatted key to copy the files across, but just wondering if anyone else has seen this, and whether its Quartz specific, or a system level problem. Thanks, Maryann
|
Are you setting the Directory Scanner to scan only for Image files? There is an input parameter for this. A Directory Scanner loads whatever file is dictated by the file path, not just images, unless you specify this.
The FAT32/HFS on the memory stick thing is likely a red herring here that you shouldn't be obsessing about - the OS is what places the hidden files.
Less likely : are these computers networked, and one of the Apps is searching another computer's contents by mistake?
Hi, Thanks for your reply.
The directory scanner is set to scan only for images. It reads the apple double files as images too, so for a folder of 4 images, quartz thinks there are 8.
Thanks for the advice on the memory stick, its just one of a number of solutions I was trying.
The computers are networked. I will check but don't think that could be the issue.
Its just very strange because the 6 mac minis were all set up the same way, and its only one that this is happening on.
Oh, so there are "image" extension files that have "." in front of them for some reason, in the folder that is being scanned? Do those exist on the other installs then? You may want to ignore my previous suggestion - moving files to some types of disks will create those "." files. I've used a FAT32 formatted drive like you describe and not had that problem, but again, maybe your intuition is right, worth a try.
It sounds like maybe you're moving over the files, and then one of the machines you've had it mounted to has created the extra "." files...but I'm not exactly sure why your images would have resource forks.
There's no reason that Directory Scanner (Blocking) [the Kineme Plugin] wouldn't load files with a "." in front if they have an image extension, that I'm aware of.
I was thinking that you were somehow having the .DS_store getting loaded because you were using the stock [Apple] Directory Scanner, which has no provisions for file type. Sorry.
I would definitely try that idea you have of using the non FAT32, or if you don't have that handy, you could try zipping stuff up before you move it onto the FAT32 drive, and then move contents to the destination drive before unzipping, to try to make sure that none of the doubles get created. You can always clean up the one install by trying to erase them (?).
If the other installs do have the "." double files in them, and they aren't getting loaded for some reason, then I'm as miffed as you...
Yep, all the other installs do have the "." double files and they aren't getting loaded, it's just in the one mac mini!
So, no nearer finding out why this is happening, but if anyone else gets this problem, I'm using:
find . -type f -name "._*" -exec rm -f {} \;in Terminal to delete all the double files in the directory.
Any other suggestions welcome!