hunt@rsts32.dec.com (Phil Hunt) (02/08/88)
I couldn't post this to Ray Lau, (Host unknown), so here is.... Hello, I was wondering why your Binhex encode put out a bad header line something like: (This file can be decoded by Binhex or Stuffit) !!!!??? The way you find the start of an HQX message is by looking for the line: (This file may be decoded by BinHex 4.0) (I think that is right, but check one for yourself!!!) Believe it or not, that is how most all BINHEX replacements check for the beginning. That line, THEN look for a colon... Phil Hunt
jbm308@uxf.cso.uiuc.edu (02/15/88)
As far as I recall, a "hqx" file must be decoded with BinHex 5.0, although a "bin" file can be decoded with BinHex 4.0.
mmt@dciem.UUCP (Martin Taylor) (02/16/88)
> I was wondering why your Binhex encode put out a bad header line something >like: > >(This file can be decoded by Binhex or Stuffit) > >!!!!??? > >The way you find the start of an HQX message is by looking for the line: > >(This file may be decoded by BinHex 4.0) > >(I think that is right, but check one for yourself!!!) > >Believe it or not, that is how most all BINHEX replacements check for the >beginning. That line, THEN look for a colon... > >Phil Hunt So THAT's why the csli-abstracts.hqx ftp'd from russell.stanford.edu could not be decoded by xbin, but worked OK with binhex on the Mac. I thought it was the missing newline at the end of the file. -- Martin Taylor ...uunet!{mnetor|utzoo}!dciem!mmt mmt@zorac.arpa Magic is just advanced technology ... so is intelligence. Before computers, the ability to do arithmetic was proof of intelligence. What proves intelligence now? Obviously, it is what we can do that computers can't.
ephraim@think.COM (ephraim vishniac) (02/17/88)
In article <46700009@uxf.cso.uiuc.edu> jbm308@uxf.cso.uiuc.edu writes: >As far as I recall, a "hqx" file must be decoded with BinHex 5.0, although >a "bin" file can be decoded with BinHex 4.0. That's exactly backwards. Notice that when you create a .hqx file, it starts with a line that says, "This file must be decoded with BinHex 4.0." or words to that effect. Ephraim Vishniac ephraim@think.com Thinking Machines Corporation / 245 First Street / Cambridge, MA 02142-1214