Wierd slave drive problem...

[Guest]

I'm running an ASUS A7N8X-E Deluxe motherboard with Windows 2000 SP4

I have enabled 48-bit addressing in the registry and the motherboard
also supports 48-bit addressing.

I have a maxtor 80GB drive as the primary master and a PlexWriter
CD-RW as the primary slave. I have 2 Maxtor 200GB drives on the
secondary IDE port. I also have a Maxtor 200GB drive as an external
USB/Firewire drive. The secondary master drive works fine, the OS sees
it as a 200GB drive and it's formatted as an NTFS volume. The
USB/Firewire connected drive works as well and it also is an NTFS
volume. The only problem I have is that W2K wont see the 200GB slave
on the secondary port. I take the drive out and put it as the slave on
the primary IDE port and the same thing happens, however, if I plug it
in using the USB interface, it works fine. I am using an 80 conductor
ATA133 cable on the secondary IDE port.

I have installed the latest nVIDIA IDE drivers and I have the latest
BIOS update that I know of (1009). The drives are certified on the
Windows HCL (Maxtor 6Y200L0). But the drive just wont work as a slave
on either port. In the device manager it just sits there with the
yellow exclamation point across the device and give me the message
that I need to restart the computer to get it to work properly (Code
14).

Any ideas?

 

[Mike Brown]

I'm running an ASUS A7N8X-E Deluxe motherboard with Windows 2000 SP4

I have enabled 48-bit addressing in the registry and the motherboard
also supports 48-bit addressing.

I have a maxtor 80GB drive as the primary master and a PlexWriter
CD-RW as the primary slave. I have 2 Maxtor 200GB drives on the
secondary IDE port. I also have a Maxtor 200GB drive as an external
USB/Firewire drive. The secondary master drive works fine, the OS sees
it as a 200GB drive and it's formatted as an NTFS volume. The
USB/Firewire connected drive works as well and it also is an NTFS
volume. The only problem I have is that W2K wont see the 200GB slave
on the secondary port. I take the drive out and put it as the slave on
the primary IDE port and the same thing happens, however, if I plug it
in using the USB interface, it works fine. I am using an 80 conductor
ATA133 cable on the secondary IDE port.

I have installed the latest nVIDIA IDE drivers and I have the latest
BIOS update that I know of (1009). The drives are certified on the
Windows HCL (Maxtor 6Y200L0). But the drive just wont work as a slave
on either port. In the device manager it just sits there with the
yellow exclamation point across the device and give me the message
that I need to restart the computer to get it to work properly (Code
14).

Any ideas?

Two thoughts:

1 - This sounds like a jumper issue. Make sure your jumpers are set to
Master for the master and Slave for the slave. (I know it sounds stupid but
I've seen it happen to the best of us.) Don't use Cable Select. Also check
the jumper on the problem drive, make sure there are no bent pins or
'questionable' contacts on the jumper block.

2 - I've had nothing but trouble out of Maxtor drives for years. I know
everyone has their preference, and that usually a flame war starts when
someone states their preference for one brand over another, but in 20 years
of computing, I've not had trouble out of any other drive like I have with
Maxtor. Well, at least not with any company that's still IN business (bye
bye JTS.)

--

Mike Brown
Process Manager

Asset Forwarding Corp.
EPA-compliant Recycling
DoD 5220.22-M Data Elimination
http://www.assetforwarding.com

 

[Chris]

Two thoughts:

1 - This sounds like a jumper issue. Make sure your jumpers are set to
Master for the master and Slave for the slave. (I know it sounds stupid but
I've seen it happen to the best of us.) Don't use Cable Select. Also check
the jumper on the problem drive, make sure there are no bent pins or
'questionable' contacts on the jumper block.

2 - I've had nothing but trouble out of Maxtor drives for years. I know
everyone has their preference, and that usually a flame war starts when
someone states their preference for one brand over another, but in 20 years
of computing, I've not had trouble out of any other drive like I have with
Maxtor. Well, at least not with any company that's still IN business (bye
bye JTS.)

Yeah, jumpers were the first thing I checked. Still no dice. I'm
almost thinking it's a MoBo issue with the nForce2 chipset, but I cant
find any info on the net about a similar issue. Thanks for the info
anyway!