Path: utzoo!attcan!uunet!decwrl!wuarchive!cs.utexas.edu!tut.cis.ohio-state.edu!pt.cs.cmu.edu!o.gp.cs.cmu.edu!andrew.cmu.edu!jh4o+
From: jh4o+@andrew.cmu.edu (Jeffrey T. Hutzelman)
Newsgroups: comp.sys.apple2
Subject: Re: a2fx/hfslink
Message-ID: <0b3AHHq00VpH41JFRO@andrew.cmu.edu>
Date: 5 Oct 90 17:37:23 GMT
References: <9010051457.AA18841@apple.com>
Organization: Carnegie Mellon, Pittsburgh, PA
Lines: 32
In-Reply-To: <9010051457.AA18841@apple.com>

I have had the need to use both A2FX and HFSlink recently. There are a
couple differences in the way they work, but both can READ but not write
an 800K (maybe also 400K?) HFS volume.  A2FX provides you with 4
possible ways of storing the file which allow you to read just the
resource fork as a text file, just the data fork as an AppleDouble data
file, or both using AppleSingle or AppleDouble (not sure of the exact
details; I haven't used that).  HFSLink always reads both forks, and
stores the data fork as the closest match to the name, and the resource
fork with a .R at the end.

Both programs use an interface very similar to 8-bit ShrinkIt - I think
they might have gotten some of the interface code from Andy.  HFSlink
supports conversin of entire directory trees; I converted a whole disk
full of C sources at once (took 30-45 mins.)

Problems:

I did have a couple disks that A2FX couldn't read, but HFSLink could. 
I'm not sure why, though.

HFSlink needs to be able to copy only the data or resource fork; I spent
quite a while deleting the resource forks from the C sources mentioned
above once the conversion was done.  Also, neither program supports the
idea of converting forked Mac files to forked ProDOS files (a la GS/OS),
which may or may not be useful in the future.  (Mac emulation that uses
GS/OS volumes??)
-----------------
Jeffrey Hutzelman
America Online: JeffreyH11
Internet/BITNET:jh4o+@andrew.cmu.edu, jhutz@drycas.club.cc.cmu.edu

>> Apple // Forever!!! <<