🚀 go-pugleaf

> o Xbin is buggy!:  Almost all of the problems we saw with Boston II was with
> 	xbin! Some people were able to get it through xbin, most were not.
> 	Many people who could not get xbin to tear apart the file were able
> 	to download it and use BinHex just fine. I vaguely remember that
> 	someone found and fixed a bug in xbin a while back -- I bet we're
> 	running into old versions of that program again.  I suggest heavily
> 	that someone with a good version of xbin (i.e. one that worked on
> 	Boston, or one from someone who remembers what the bug was and
> 	knows that the thing is fixed) please clue us in and post a good
> 	version of the program...

Well, I guess I was one of the ones who successfully downloaded Boston II
(microsoft word/new york font replacement) with xbin and xmodem.  The
version I used is 2.3, which appeared over the net last October.  I don't
mind posting the source if that looks like the thing to do, but surely this
is the version most people are using.  Here's the first part of the README 
file that came with it, along with the author's address:

    This is version 2.3 of xbin.  The major changes include
    perfomance improvements from Dan LaLiberte of UIUC, fixes
    for 16-bit machines from Jim Budler of AMD, and a fix for
    a bug in the run-length encoding code.
    
    This version of "xbin" can handle all three BinHex formats
    (so far).  Thanks to Darin Adler at TMQ Software for providing
    the code to compute and check the CRC values for all three formats.
    (There are no plans to support binhex5.0, as its use of binary
    encoding makes it useless for sending programs through e-mail).
    [...]
    Dave Johnson
    Brown University Computer Science
    ddj%brown@csnet-relay.ARPA
    {ihnp4,decvax,allegra,ulysses,linus}!brunix!ddj
    

Brian Allison         {allegra, ihnp4, uiucdcs, ctvax}!convex!allison
Convex Computer Corp.
Richardson, TX