home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!think.com!spool.mu.edu!agate!garnet.berkeley.edu!jdsiegel
- From: jdsiegel@garnet.berkeley.edu (Joel Siegel)
- Newsgroups: comp.sys.mac.misc
- Subject: Re: .hqx files
- Date: 23 Dec 1992 09:29:50 GMT
- Organization: University of California, Berkeley
- Lines: 26
- Message-ID: <1h9bieINNbaq@agate.berkeley.edu>
- References: <1gjvofINNsm0@menudo.uh.edu> <N39TVB1w165w@student.business.uwo.ca> <BzBMC7.I3x@undergrad.math.waterloo.edu>
- NNTP-Posting-Host: garnet.berkeley.edu
-
- Re: Decoding BinHex files, esp. if they are binhex decoders
- themselves and the resultant Catch-22:
-
- If you're not downloading directly to your Mac but to a Unix site
- first (like a campus mainframe) you can/probably should do the
- decoding there. (1) It eliminates the catch-22 of needing to find
- a non-hqx'ed file to decode your first hqx'ed file.. etc.etc.
- (2) hqx'ed files are bigger than their decoded counterparts (which
- are usually in one of a variety of compressed formats). Thus, if
- you're downloading to Mac via modem, you save a good chunk of
- time.
-
- So how do you do it? There's a Unix program called mcvert that
- does the trick nicely; it converts a .hqx file into its decoded
- format and appends the suffix .bin. You can then download it to
- your Mac using MacBinary.
-
- Check around and see if it's on your site. I don't know where/if
- it's archived, though Archie probably would. Or ask your
- sysadmin, or email me and I'll see how it's distributed.
-
-
- --
- Joel Siegel <jdsiegel@garnet.berkeley.edu jdsiegel@ocf.berkeley.edu>
- "Politics is the art of preventing people from taking part in
- affairs which properly concern them." - Paul Valery
-