How to avoid creation of _(file.*), coping from tiger to pc?

Question

how to avoid the creation of this file for ever on a pc environment??
I explain: as i copy any image file, it goes to a spooler directory and that begins instantly to process the file to an OPI server, separating CMYK channels, converting it to high and low resolution...
but as this _(file) is created (same name and extension, but 0Kb and with this _ underscore in the beggining of it name), it begins to process it, and as it really does not exists as an image itself, it crashes the OPI server, forcing us to restart it...
and then, you can imagine the mess, because we're a newspaper, with more than 100 machines logged in two cities simultaneously...
thanks for those who replied last topic I posted about some softwares to delete it! it really worked!!
but now, can anyone have a clue how to DON'T create this file?
thanks in advance!
alex borba
[email protected]

Answer 1

I believe that command is supposed to stop the creation .DS_Store files on servers. Also, I think the plist file gets written to the user ~/Library/Pref, it probably ought to exist both there and in the /Library/Pref folder to really work.
I didn't think the Save for Web option would work for your purposes. I don't believe anything will work except to strip the resource fork off the files before you send them. There is an Applescript that will do it, using a UNIX command in the script. You select a folder, run the Applescript, and it strips the resource fork off all files in the folder and creates a sub-folder called Stripped with resourceless copies of the files in the original:
-- Strip resource fork and metadata in Tiger for one file.
-- If a folder is selected creates an unresourced subfolder of the selected folder
tell application "Finder"
     try
          set aFile to the selection as alias
          set aFolder to the container of aFile
     on error
          display dialog "Select a file"
          return
     end try
     set aFile to the quoted form of POSIX path of aFile
     do shell script "rsync -a " & aFile & " " & aFile & "Stripped; mv " & aFile & "Stripped " & aFile
     update aFolder
end tell
The "do shell script" line must be all a single line in Script Editor. It might wrap funny in the browser. Anyway, copy it, paste into Script Editor, hit compile, and save it as an application. I've only fooled with it a little tiny bit, so I'm not sure whether the rsync process would have any strange effects on complex Photoshop and EPS files or not.
As far as I know the only way to send Mac files without resource forks to a server is to strip them from the files.
Francine