[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?).

I don't completely follow what the problem is here, but here is some  
data that may or may not be relevant: Some programs that can process  
binhex files are very sensitive to line ending characters.  The binhex  
4.0 file format may be a 'text only' format, but some get upset if they  
find line-feeds or carriage-return-line-feeds at the end of the data  
lines.  They only want carriage-returns.  thus, if you ftp the files as  
text only files to, say, a unix or dos box, and then try to run them  
through some of these converters, you'll get CRC errors or other  
ailments.
Binhex 5.0's format is, of course, a binary one, so one should never try  
to transfer it as anything but.
Another thing to do is make sure the binhex 4.0 file looks like a  
reasonable binhex file.  As I recall, every line is the same length, and  
the first starts with a colon and the last (which may be incomplete)  
ends with a colon.  Most things I've seen that deal with binhex files  
don't care what comes before that first line with a colon (so long as  
none of those lines start with a colon, themselves)
As for Stuffit not recognizing the file, does this mean that it doesn't  
show up in its 'open file' dialog'?  or it shows up, you open it, and it  
reports an error then?  This is an important distinction.  If the former  
is the problem, it sounds like the 'creator' and 'type' of the file are  
not set properly.  If you're using the de-binhex-ifyer in compactor,  
does it put up any info about what type and creator it is creating in  
the new file?  I know the binhex 4 app does, and it's a useful sanity  
check, but I am not familiar with thecompactor one.

I hope this doesn't confuse things more than they are.

david john