🚀 go-pugleaf

In article <14326@duke.cs.duke.edu>, currier@romeo.cs.duke.edu (Bob Currier - DCAC Network Comm. Specialist) writes:
> 
> I have been able to transfer hqx files from Sumex-aim, rascal.ics.utexas,
> etc etc with no problems.  Stuffit unpacks, decodes these files perfectly.
> The bin files do NOT work, tho... I have tried ftp in both bin and ascii mode,
> and Kermit (from my Unix host) in no and even parity, only to have Stuffit and
> and binhex barf.  What is special about the bin files?  What am I doing wrong?
> I am trying to get McSink from rascal, and am about to pull my hair out...
> Is it possible that the copy of McSink on rascal is munged?  

	it is of course possible that the copy of McSink on all the
	archives is "bad", but I doubt it;  we would have heard about it.

	if what you are saying is that any and all files do not work for
	you once you get them in binary, even when you retrieve and download
	the *.hqx version, then I must assume that somewhere along the path
	you have a "6-bit" narrow ... (-:

	Seriously, though, if you retrieve a *.bin file and download it with
	binary XMODEM or MacBinary Kermit, and you also GET the corresponding
	hqx-file, download that and use Binhex or equivalent on your Mac,
	and if the 2 binary files are identical when you compare them
	with MacZapTools (or equivalent) - and neither of them work....

	... then have someone else try to download the files at another
	site (like the maintainer - me) and if the binary file proves
	unusable there also, we probably have found a BAD original binary
	file submitted to the archives....

	you can find McSink on RASCAL in:

werner on rascal <301> cd ~ftp/mac
werner on rascal <302> ll NEW-in-89*/* | fgrep McSink
   1 -rw-r--r--  3 werner        566 Mar 14 00:11 NEW-in-8903/McSink_6.5_DA_intr
o
  61 -rw-r--r--  3 werner      62080 Mar 13 22:02 NEW-in-8903/McSink_6.5_sit_bin
  84 -rw-r--r--  1 werner      85369 Mar 13 21:59 NEW-in-8903/McSink_6.5_sit_hqx