[Prev][Next][Index][Thread]
Re: binhex/compact probs?
>Hiya alls - i've dl's (ok, ftp'd :) a couple of files off of the net to
>try to use with executor. For somee of these, I need to use the binHex4.0
>converter in Compact pro, in others, I need to use the binHex5.0 that's
>included with exectutor. Occasionally, I'll get a file that I would de
>hex with binHex 4.0, and I would get a .sit file - however, unstuffit
>refuses to see this file! Any ideas here? Perhaps I should try to use
>binHex 5.0 on the file? (though, if 5.0 doesn't like the file - it hangs
>the emulator).
>
>BTW - this is executor running under linux (I'm still stuck in demo mode -
>since i can't register till next week sometime - would that be part of the
>problem?).
>
Hi, Daniel:
Pretty frustrating, isn't it? I have the same problems, also. Not every file
is like that, but I would say close to half of them are. I haven't figured
out the answer, either. It has to do with those dang-blasted MAC headers,
you know... the data fork, the resource fork, and (of course) [we can't
forget] the finder fork. If those headers are NOT intact, the MAC won't see
them, properly. I would like to see some kind of program that could generate
finder forks.... for example....
Let's say I create a file in Word For Windows and save it as a MAC Word 5.1
file. One would think that one could save it to a MAC formatted disk, put in
in a MAC and expect the MAC to recognize the file, right? Well.... that has
NOT been MY experience. The MAC will NOT see it as a WORD file... it brings
up that dang-blasted "teach text" malarky. So.... what's a mother to do?
<grin> What I did was to create a MAC WORD 5.1 file (in a MAC) and save it
to a MAC disk. Then I copied the WORD 5.1 file to a DOS formatted disk where
the data and finder forks were split off. Those finder forks are 16 bytes
long, BTW. I copied the finder fork file and changed the same to the same
name as my original Windows file with the proper extension for a finder. I
then copied both files to the MAC formatted disk which merged into one MAC
WORD file. When I put this diskett into the MAC, the MAC saw it as a WORD
5.1 file and processed it, accordingly.
If someone out there has a better way to do this, please share it with us. I
am sure there is more than one way to "skin a MAC".
Preston J. Tuchman
preston@indy.net
Follow-Ups: