alvisd@silver.bacs.indiana.edu (dean alvis) (11/16/89)
Can someone out there help this novice by explaining the steps needed to transfer a *.hqx type file (BinHex 4.0) on a unix system down to a Mac? Can the file be fed directly to a transfer program (eg. kermit)? Does it need to be processed at the unix end first (eg. by mcvert? xbin?)? Thanks for any help ... ---------------------------------------------------------- Dean Alvis internet: alvisd@silver.bacs.indiana.edu "real" : Math. & Comp. Sci. Dept. Univ. of Indiana at South Bend South Bend, IN 46634
roy@phri.UUCP (Roy Smith) (11/17/89)
In <29793@iuvax.cs.indiana.edu> alvisd@silver.bacs.indiana.edu (dean alvis): > Can someone out there help this novice by explaining the steps > needed to transfer a *.hqx type file (BinHex 4.0) on a unix > system down to a Mac? You need to copy the hqx file to your mac using some sort of file transfer program. I use NCSA telnet, but kermit, or just about any other communications program for the mac should be able to handle ascii file transfer. Once you have the file on your mac, then you have to unbinhex. I use StuffIt for the unbinhexing, but other programs should work too. Once you've got it unbinhexed, you might possibly have to do more processing; many binhex files yield StuffIt archives, which in turn need to be unpacked. My gripe is the number of steps it takes me to get a file from some ftp server. A typical sequence is to ftp the binhex file to my Sun and then ftp it to my Mac (NCSA telnet lacks client ftp, hence the need for the intermediate staging on the Sun). Then I have to unbinhex it. Then I have to unstuff it (this is especially annoying when the stuffit archive contains but a single file!). Somehow it seems all these functions could be combined into one program. -- Roy Smith, Public Health Research Institute 455 First Avenue, New York, NY 10016 {att,philabs,cmcl2,rutgers,hombre}!phri!roy -or- roy@alanine.phri.nyu.edu "The connector is the network"