.bin files bringing me down
 

One of my computer illiterate clients, who coincidentally happens to use a mac, keeps putting things up on her ftp site by dragging the files into her address bar rather than using an FTP client. It's been a long time since I left mac world and I guess you don't need an ftp client if you are talking to other people in your secret mac club.

Despite having Stuffit, when I open the .bin files, they end up being 0k. The .bin files are from 50k - 460k.

Another thing that happens a lot is the file comes through corrupted. Emailing is no better. For a variety of reasons, it is beyond my client's ability to access a file and put it in an email. (today: "I don't know how to attach a folder to the email") I did not want to suggest zipping it for the reason of being unable to open the zipped files. I suggested attaching the individual files to the email and for some reason the send failed. (it was far below the file size restriction of gmail)

So I am back to figuring out how to successfully open her .bin files.

I am able to open other people's .bin files however. As a side note this person habitually ignores pop up messages as she uses her computer.

Any help would be appreciated.

A simplistic suggestion might be to try emails and when your client does the Attachment, have her check the box that says: "Send Window Friendly Attachments".

Setting this as the default is no big deal for other Macs, and saves having to customize each email.

( would it be fair to say you are .bin laden? )

I'll ask her to do that, she is probably ignoring those boxes. The problem with email is that there is a file size limit. Some of the documents that are going back and forth are 40-50 MB.

I've never really heard of a web browser that auto-bins things when you use it to upload to FTP. I guess I didn't get that memo from the mac club.

If you've given up on changing her habits, you could try installing a web browser that supports FTP better.

Bravo.

If I remember correctly, Mac files were composed of 2 parts : data fork and resource fork. And I also remmber that Windows had some problems with the resource part.

Could your problem stem from this ?