Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!bbn!bbn.com!levin
From: levin@bbn.com (Joel B Levin)
Newsgroups: comp.sys.mac
Subject: Re: Mass de-binhexing
Keywords: binhex, stuffit
Message-ID: <39671@bbn.COM>
Date: 9 May 89 14:32:23 GMT
References: <wYNPz6y00WB44PDUoC@andrew.cmu.edu> <8230@phoenix.Princeton.EDU>
Sender: news@bbn.COM
Reply-To: levin@BBN.COM (Joel B Levin)
Organization: BBN Communications Corporation
Lines: 53

In article <8230@phoenix.Princeton.EDU> bskendig@phoenix.Princeton.EDU (Brian Scott Kendig) writes:
|I'll expand on the general request here: Does anyone know of any mass-deBinHex
|or mass-unStuffIt utilities that exist for either the Mac or any Unix systems?
|I can use my CMS system here to de-BinHex a file before I download it, making
|it smaller and more quickly downloaded, but I hesitate to do that on each of
|dozens of files at once manually.
|
|And it would be REALLY nice if I could take a BinHexed, Stuffed file on my
|Unix system and, in one fell swoop, download it to each of its constituent
|files on my Mac, each file ready to go with no further action!  (Dream on...)

I use xbin, unstuff, and macput on my Sun workstation (or I can use
them on the VAX with Ultrix), and VersaTerm at 19200 via the Sun's
serial port (or the VAX at 9600 over our terminal controller).  I put
all the .hqx files in a directory.  I use a program called comb to
extract the junk from a combined multi-part .binaries item.

	xbin -v *.hqx
(I examine the names of the unpacked files; almost always the stuffit
archives match *xsit.* or *xSIT.*)

	foreach a (*xsit.data)
	unsit -v $a
	end				(C-shell)
or
	for a in *xsit.data
	do unsit -v $a
	done				(Other shell (if I remember right))

Then after deleting the used *.hqx and *xsit.* files:

	foreach a (*.info)
	macput `basename $a .info`
	end				(C-shell; make appropriate
					 changes for other shells)

Some possible gotchas:
  Even with the latest changes, some characters
  in filenames break xbin.  I don't bother; I generally ship the .hqx
  file to the Mac and do it by hand.

  If you do a lot of files at once, a later file with the same name as
  an earlier file could wipe the earlier one out (e.g. two files named
  READ_ME).  READ_ME and Read_Me would co-exist on the Unix system OK
  but could be a problem on the Mac (I forget what Versaterm does).
  This is why I use the -v(erbose) options above.

This is what works for me.  I could make it more automated, but I
don't do it often enough to make it worth while.

	/JBL
UUCP:     {backbone}!bbn!levin		POTS: (617) 873-3463
INTERNET: levin@bbn.com