[Prev][Next][Index][Thread]

Re: HFV files



>>>>> "Mat" == Mat Hostetter <mat@ardi.com> writes:

>>>>> "Gene" == Gene McCulley <mcculley@greatwall.cctt.com> writes:
    Gene> I downloaded the nihimage.hfv file and placed it in my
    Gene> /usr/local/lib/executor directory.  Now what?  I don't see
    Gene> it when I fire up executor.  I must have to do something
    Gene> else, but I have no clue what it is.  I have tried with and
    Gene> without the environment variable that points to the system
    Gene> folder in my home directory.

    Mat> You can say this in your .bashrc:

    Mat> export MacVolumes=/usr/local/lib/executor/nihimage.hfv

    Mat> This environment variable is a semicolon-separated list of
    Mat> hfv's (and devices, if you want).  I use a similar line to
    Mat> let me use an hfv I keep in my Linux home directory.

Actually, if the MacVolumes environment variable isn't altered, all
that Gene needs to do is put nihimage.hfv in /usr/local/lib/executor
and the right thing will happen automatically.  An explanation
follows.

Under both DOS and Linux If you don't set the MacVolumes environment
variable at all, it will default to "+/exsystem.hfv;+".  The part
before the semi-colon means that the first HFV file that will be
opened is exsystem.hfv in the Executor Library Directory.  The
Executor Library Directory is /usr/local/lib/executor under UNIX and
C:\EXECUTOR (or wherever you install Executor) under DOS.  The "+"
which follows the semi-colon then tells Executor that any HFV file
with an extension of ".hfv" that is found in the Executor Library
Directory should also be mounted as an HFV file.  It's because of this
additional "+" that Gene, and other E/L users, can just drop the .hfv
file in /usr/local/lib/executor without modifying anything.

On one of our Linux systems, we use the command

export MacVolumes="+;/dev/sdb"

to tell Executor that in addition to looking for .hfv files in
/usr/local/lib/executor, our second SCSI drive should also be
considered an HFV, so we can attach an external Mac formatted SCSI
drive and use that too.  Usually we hook up a 1 gig formatted Mac
drive for testing purposes.

Under DOS, we don't have to do anything special to see the SCSI drive,
because E/D and E/L have slightly different rules about how they look
for Mac formatted SCSI drives.  In essense, E/D looks for you and E/L
needs to be told.

	--Cliff
	ctm@ardi.com


References: