🚀 go-pugleaf

In article <42005@nigel.ee.udel.edu>, johnston@oscar.ccm.udel.edu writes:
|> MacBinary == BinHex 5.0 format.  It does not support encoding/decoding
|> multipart files.  However, Binhex 5.0 format is not "hqx" format.
|> The files created with the MacBinary encoder are given the default file
|> name extension "mbin".  Frankly, I don't know what BinHex 5.0 is used for.
|> -- Bill (johnston@oscar.ccm.udel.edu)
	Well, I use Binhex 5.0 all the time! First, Binhex 5.0 format is a
raw MacBinary (I) file on the Mac. It is identical to a macbinary file on
UNIX or COMPUSERVE or .... (within architectural differences). This
Macbinary data is entirely contained within the data fork of the file.
Binhex 5.0 does locally exactly what most file transfer programs do when
downloading a binary file - it converts the Macbinary format into a real
Mac format file. It will also do the reverse AND it will decode Binhex 4.0
format as well.
	As to how I use it... I get a Mac file onto my local SparcStation
at work (usually via ftp over the internet.) If this file is in hqx format
I use mcvert to convert it to a binary file. I then use binary mode ftp to
move the file onto a PC (Novell Netware) file server which I can access
directly from a Mac which is also connected to the Novell server. I can
then use Binhex 5.0 to convert this binary file on the Novell server to a
real Mac file anywhere the mac can access. Simple, eh!

                ftp                ftp
	source ----> SparcStation -----> IBMPC             MAC
                                           \               /
                                            \             /
                                             \           /
                                              \         /
                                              file server

	Peter C
-- 
      (O)(O)(O)(O)(O)(O)(O)(O)(O)     (O)(O)(O)(O)(O)(O)(O)(O)(O)
      (O) !the doctor is out! (O)     (0) peter@viewlogic.com (0)
      (O)(O)(O)(O)(O)(O)(O)(O)(O)     (O)(O)(O)(O)(O)(O)(O)(O)(O)