Yes sorry I meant plus the MacBinary deal. However, you can always unstuff them on newer macs too.
What's in that resource fork? Will stuffit expander fail to extract an older .sit file that is missing its resource fork? I didn't think that was the case but I could be misremembering.But you have to convert them into something other than a .sit to upload them because they have a resource fork.
I'll try to put something together, but for me, this was like a month ago, I don't have the machine I was using set up, and have moved the hard disk into another computer.I know. That's why I'm asking for an actual example so we can work out what happened. I wasn't casting doubt on your account
I'll try to put something together, but for me, this was like a month ago, I don't have the machine I was using set up, and have moved the hard disk into another computer.
I'm so used to there been unusable files on Mac Garden that I've given up and I have a Pismo or iBook set up at all times to deal with it.
The reason for using hqx is that it is built into DropStuff, while .bin isn't. It's a laziness thing. Purely - "it was on the OS install disk". I'd have to go and find software to create a .bin.I totally agree - the core problem here (and something I rant about too much) is the lack of a good and reliable upload format standard that’s well-supported across platforms. As I said earlier in the thread, there is no reason to use .hqx for anything ever anymore (the point of it was to allow ASCII mode transfers, like uuencode) but wrapping everything in .bin is very sensible and would ideally be done by everyone.