Seagate ST32140A + ST31276A = Trouble?!
Jason Arthurs
I have a setup which currently includes a ST32140A (2.1Gb) primary
drive and a Conner CFA540A (540Mb) slave which has worked fine.
Having replaced the Conner with a ST31276A (1.2Gb) I cannot get the
system to acknowledge the existence of this drive, despite having
removed the jumpers to indicate that it was a slave drive.
The new drive spins up and appears to behave correctly but the machine
does not automatically configure the drive, nor will it work if the
drive is manually configured.
I am also unable to get this drive to work as a master, the machine
boots straight to floppy if I try to set it up as a master drive.
Do I have a dead drive or has Seagate introduced some new step into
the setup?
I've tried accessing the details for this drive on their site but all
I get is an error message saying that the page is not present.
Any suggestions?
Jason.
"When a cat is dropped, it always lands on its feet, and when toast
is dropped, it always lands with the buttered side facing down. I
propose to strap buttered toast to the back of a cat; the two will
hover, spinning inches above the ground..."
Jason Arthurs
>I have a setup which currently includes a ST32140A (2.1Gb) primary
>drive and a Conner CFA540A (540Mb) slave which has worked fine.
>Having replaced the Conner with a ST31276A (1.2Gb) I cannot get the
>system to acknowledge the existence of this drive, despite having
>removed the jumpers to indicate that it was a slave drive.
>
>The new drive spins up and appears to behave correctly but the machine
>does not automatically configure the drive, nor will it work if the
>drive is manually configured.
>
>I am also unable to get this drive to work as a master, the machine
>boots straight to floppy if I try to set it up as a master drive.
>
>Do I have a dead drive or has Seagate introduced some new step into
>the setup?
I've since tried a different drive and initially got the same results,
however it seemed to be a spin-up fault (the drive didn't reach an
'acceptable' speed quickly enough and the motherboard didn't detect
it.
Once I'd set a spin-up delay in the BIOS the machine accepted it
fine...
Just for the records...