Mac storage hardware, [OS9 Disk Setup]<not supported> 9GB SCSI drive

My beloved 'FrankenMac' - more or less a Beige G3 (Gossamer logic board
with rev. A. ROM) kept running with salvaged parts - was due for a hard
disk upgrade from an abominable Seagate Barracuda 4.3GB drive to a
lightning quick Seagate Cheetah 9.1GB 10k drive. It had always run OS
9.1 smoothly (softwarewise, that is, those old Barracudas sound like a
jet engine with badly balanced blades around take-off). I use an ATTO
ExpressPCI PSC SCSI controller.

So having connected up the Cheetah (which I know works, I pulled it from
my Windows system yesterday) I boot up from the OS 9.1 install CD, go
into Disk Setup to initialise the 'new' drive, only to see:

<not supported> SCSI, BUS 0, ID 0, LUN 0

At first I thought it might be the size of the drive (9.1GB) causing
trouble, so I tested with a 40GB Maxtor IDE drive (on the onboard IDE) -
which it would let me initialise. Then I thought there might be
compatibility issues between the ATTO controller and the Cheetah - so I
stuck the controller and drive into a Windows PC I had, which promptly
recognised both. The presence of an NTFS partition wasn't the problem
either - the Maxtor also had an NTFS partition, yet it could be initialised.

I also tried the Cheetah on the onboard SCSI - exactly the same <not
supported> message. So it's definately between the drive and the OS (or
at least the Disk Setup), not controller related. But what?


So, anyone have an idea as to either how to get this drive initialised
for use by the OS 9.1 installer, or, alternately, a technical
explanation why it's not possible (note that absolutely everything I
have done with this Mac is not supported by Apple, so the fact something
is not supported is NOT a _technical_ explanation).

In article <df7b1$429ef7d4$d52e19e3$ XXXX@XXXXX.COM >,





Any slave/master switch or jumper that has to be set?

We're talking SCSI here, SCSI works with ID between 0 and 15 (where 7 is
usually the controller). I've tried at ID 0 (standard for disk to boot
from) and ID 1. The Barracuda boots fine from both IDs.

Only other relevant setting is LVD or Single Ended. Normally an LVD
drive connected to am SE controller wil default to SE anyway. To be
certain I jumpered it to forced SE anyway. That didn't make any difference.

Apple put in pretty generic support into Drive Setup to handle IDE
drives as they went through the later OS 7 and 8 versions of the OS.
But they only put in support for SCSI drives that they used or had
Apple ROM'd versions of the drives made for original equipment use.
So drives made after the version of Drive Setup you have may not
work directly. Options you have are buying third party formatting
software, or searching the web for hacks for Drive Setup so that it
will recognize the drive you have. When this was more needed, you
would probably get a response here fairly quickly with a link to a
Drive Setup hack site. I would provide one, but lost my bookmarks
to several when a machine here was replaced.

Joe

RE the posting:
<< So, anyone have an idea as to either how to get this drive initialised for
use by the OS 9.1 installer, or, alternately, a technical explanation why
it's not possible (note that absolutely everything I have done with this Mac
is not supported by Apple, so the fact something is not supported is NOT a
_technical_ explanation). >>

Perhaps someone does, but since you're posting anonymously, you provide no
path for someone to get the help you need _to_ you....

- John

In article <df7b1$429ef7d4$d52e19e3$ XXXX@XXXXX.COM >,



Something weird is going on. I just recently got and initialized a pair
of 50 Gig Seagate SCSI drives using Drive Setup v. 2.0.1, which came
with some variant of OS 9. Earlier versions of Drive Setup might not
work; I don't know.

I've also initialized 18 Gig Seagate SCSI drives the same way.

Is your old drive still attached? Do you have a SCSI conflict? It really
does not matter what adress you use (other than 7, which is the Mac), as
long as they're all different. I don't know about your PCI card, but the
Beige can only support addresses 0-6 for drives.

Go to the Seagate site and D/L the docs for your particular drive, and
check all the jumpers. Maybe there's a "write protect" or something in
the wrong place.

Isaac

dion_b < XXXX@XXXXX.COM > writes:

Yep. Apple's formatter ("HD SC Setup" or "Drive Setup" depending on
your version of MacOS) only supports specific brands/models of SCSI
drivers. (I think it's only those models that Apple sold.)

There are two possibilities.

The easiest is to use a third-party formatter. I know of three:

- FWB's Hard Disk Toolkit
- CharisMac's Anubis
- LaCie's Silverlining.

I think Silverlining is not sold, but is only available as a bundle
when you buy a LaCie drive.

I have personally used (an older version of) Anubis, and I happen to
like it. Here's the manufacturer's product page:

http://www.charismac.com/products/Anubis/

It's $90. It should run on just about anything. Their data sheet says
any Mac from a Plus through modern systems.

The more difficult, but cheapest option is to hack the Apple formatter.
A Google search should reveal several hits. Not having actually used
any such patch (I format my third-party SCSI drives with Anubis), I
can't say how well any of them work.

-- David

In article < XXXX@XXXXX.COM >,



on a SCSI Drive?????? That is a N/R answer......


Me

<< The more difficult, but cheapest option is to hack the Apple formatter. A
Google search should reveal several hits. Not having actually used any such
patch (I format my third-party SCSI drives with Anubis), I can't say how well
any of them work. >>

It works just fine if you do it right.

Required: current version of Drive Setup (which version depends on which
version of the System is used) and ResEdit.

Steps:
1. Use SCSI Probe to obtain vendor and product ID of target drive
2. Write that down!
3. Open Drive Setup with ResEdit
4. Open the fscr resources
5. Pick a resource already there for the vendor (brand name) of target drive
6. Duplicate that fscr resource
7. RENAME the product ID to that of the target drive
8. Quit ResEdit and save changes

There are other possible methods as well, but in many cases the above one
works fine. No need to spend $$$ on any 3rd-party software.

- John

Thanks, this looks perfect. I will try it out and report back if it works :)