Forum Moderators: travelin cat
i wanted to connect to my 0s10.2.8 macintosh server at work from my home PC running XP.
so i created a folder on the server
allowed FTP access to its contents
created my user, and there's no problems connecting
but when the contents (usually jpg and tif files) are transfered, about 80% of the fileswere now .BIN files.
eg. filename.jpg.bin
now why does this happen to only a few of them?
why not all?
any ideas on something i should try would rock
thank you
TINK
I hope this link's kosher:
[helpdesk.umd.edu ]
If some of the files are optimized for the web, for instance, they may have not resource forks, and I'd suspect these would transfer over correctly.
You can avoid resource fork problems by compressing the files before transferring via FTP, or by using a transfer protocal that handles the resource folks -- I think Windows File Sharing will do.
All I had to do was Zip the folder.
Why didn't I think of that?
thanks for your help
The only effect having the resource forks stripped would have is maybe the "thumbnail preview" of the file being destroyed. Furthermore, Once you transfer files from a Mac to PC or the other way around, the forks are gone, period. Windows doesn't use them, need them, want them etc. When you take an image off the web, what if it doesn't have forks in it? It doesn't get renamed to .bin. What is happening is the FTP client is trying to ensure that the file is transfered in binary instead of other transfer methods (ascii, etc). The Windows FTP client is unsure of the operating sys it connecting to, and therefore is making sure the file comes through as intended, as a binary file.
What I would suggest is trying a different (less disturbed) FTP client. That may be all it takes.
-- Zak
