[Prev][Next][Index][Thread]
Re: binhex/compact probs?
On Wed, 16 Nov 1994, Preston J. Tuchman wrote:
> >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
yeah, this bugs me too. The kludge that has worked for me in the past
(this is *highly* questionable, but it has worked) to binhex some random
file, and name it something like "pretend.bin". Then I've just left the
%pretend.bin file lying around and simply copied whatever file I want to
deBinHex right onto pretend.bin, leaving the %pretend.bin unchanged.
Amazingly, this has never failed for me. After doing this, I just
unBinHex pretend.bin and it seems to work fine. Of course, I use the
Linux version, so long filenames w/ capitalization might be handled
differently in Ex/Dos....
btw, I just went to the Linix 1.1.62 kernel, and the executor segfaults
right after the opening screen. :( Will this be fixed in future
Executors, or is there a kernel "cutoff" after which I should forget it?
-gmt
======================================================
"If you get confused just listen to the music play!"
======================================================
References: