Subj : Re: I'm still waiting for somebody to offer constructive criticism To : comp.programming,comp.lang.java.programmer,comp.lang.lisp From : rem642b Date : Sat Aug 20 2005 09:32 pm > From: > Icab ( version 2.9.8 is available free on their web site and > will run on a 68k Mac running System 7.1 or better ) OK, I searched on Google and found: http://www.icab.de/download.php where it says: You will be redirected to one of our download servers in 2 seconds, then your download of iCab in English for Mac OS 7.1-8.1, 68k will start... Nope, that didn't happen. Please click here if the download doesn't start automatically ... OK, I did that, and lynx then reported: Downloaded link: http://aegis.at/icab_down/iCab_Pre2.98_English_68k.sit Suggested file name: iCab_Pre2.98_English_68k.sit So it wants to download to Unix not a BinHex, whereby I could then use Kermit to download to my Mac and then unBinHex it there, but a stuffit archive in binary form directly on my Unix shell account, with no known way to convert to BinHex on Unix, hence no known way to get it to my Mac. Any ideas how to proceed? I searched Google for: BinHex Unix and found this: http://kb.iu.edu/data/aewr.html where it says: To create a BinHex file, enter at the Unix prompt: binhex [options] file > file.hqx Replace file and file.hqx with, respectively, the file you wish to encode and the name you wish to give the resulting BinHexed file. This command has the following options: -r With this option selected, binhex encodes file as a resource fork. -d With this option selected, binhex encodes file as a data fork. First question: Is the iCab_Pre2.98_English_68k.sit file just a resource fork, or just a data fork, or a MacBinary file which must be first decoded into resource+data+info files and then re-coded as BinHex, or is it total garbage when residing on Unix as a binary file? -c [creator] Replace [creator] with the file creator code you wish to assign to the document. If you do not specify a file creator, the resulting BinHexed file's creator will be MACA with the -d and -u options and RSED with the -r option. -t [type] Replace [type] with the file type code you wish to assign to the document. If you do not specify a file type, the resulting BinHexed file's type will be TEXT with the -d and -u options and RSRC with the -r option. I think I may be able to find out what the correct creater and type codes are for StuffIt archives, except there are several different versions of StuffIt and I don't know if I have the correct one. .