Newsgroups: comp.sys.amiga.hardware
From: cgould@oracle.uucp (Colin A. Gould)
Subject: Re: HDToolBox and non-C= controllers
Summary: how to use hdtoolbox w/ other drivers
Keywords: hdtoolbox scsi driver device
Organization: Oracle Corporation, Redwood Shores CA
Date: Mon, 11 Jan 1993 22:25:13 GMT
X-Disclaimer: This message was written by an unauthenticated user
              at Oracle Corporation.  The opinions expressed are those
              of the user and not necessarily those of Oracle.

In article <jperkski.02qq@kentcomm.UUCP> jperkski@kentcomm.UUCP (Jim Perkowski) writes:
>In article <1ip4p9INNr72@sauna.cs.hut.fi> Camillo.Sars@hut.fi (Camillo S{rs) writes:
>>I've been using my GVP Series II harddisk for quite a while, so now
>>I'm interested in upgrading the software. My retailer knows nothing of
>>Faaastprep or gvpscsi.device upgrades, so I chose to try HDToolBox.
>>Can't get it to see my controller, though... Any clues?
>>
>>Please use e-mail as well as posting...
>>
>
>You can get the latest GVP FastPrep and ExpertPrep off their support bbs.
>The number should be in your documentation or any GVP advertisment. The
>ROM you can get from GVP or one of the mail order houses like Safe Harbour.
>Oops. Just noticed you are from Finland. I hope you don't mind a over seas
>call.:)
>
>--
>______________________________________________________
> (Jim Perkowski) kentcomm!jperkski@legend.akron.oh.us
>                 kentcomm!jperkski@aldhfn.akron.oh.us
>                    (Where am I when I need me!?)
>

Several people on the net have had problems with this. If your
controller supports SCSI-Direct type commands, and most do, HDToolBox
should work fine, or at least partly (I had some problems on hardframe
and Zeus'040, mostly worked.)

The problem lies in that HDToolBox assumes a SCSI device driver name
of 'scsi.device', since this is the 2091/C= controller name. It also
looks for 'xt.device' since they also support XT drives. But, you can
simply supply HDToolBox with your driver name. just give it as a
parameter if you run hdtoolbox from CLI, or in WB, add a ToolType as
follows:

SCSI_DEVICE_NAME=MySCSIdriver.device

There are also tooltypes for XT_DEVICE_NAME, maximum LUN numbers, etc.
hexdump the program file to find the names for these options, since
they aren't mentioned in the manual anywhere (ahem!!). Or you can just
use the dos Search command, or load it into a text editor, and search
for SCSI...I get into the habit of hexdumping files a lot, find some
neat hidden features and left-over stuffs sometimes (like
QuarterBack5.03 has options for selecting a font and screen colors in
it...well, at least it has the text embedded in there for such a
requester, but you can't get at it.)

Note that the device driver name IS case-sensitive, since you are
looking for an Exec list object, not a disk file. You may not be able
to find the driver on disk anywhere, either, since most will be stuck
in the AutoBoot ROM on the controller, not put in DEVS:. Use SiND or
ARTM or SysInfo3.01 or some other Exec snooping tool to find out all
the active devices on the machine, they will tell you the driver name.
You might be able to find those in ARexx too, since you can list
libraries; I haven't tried it ('echo show("D")' ?).

Have fun...
Colin