Drive Fitness Test 4.0x doesn't always work

I'm having problems with Hitachi's Drive Fitness Test vers. 4.07 and
4.08, but vers. 3.68 and older run perfectly.

DFT v. 4.0x worked fine with mobos based on SiS 735 or nVidia nForce2
chipsets but failed with mobos based on the VIA 8237, Intel 810i, or
Intel 440BX chipsets. With some of the problem mobos, DFT v. 4.0x will
abort to the command line prompt during the drive detection phase,
while with others it fails to detect some drives, in one case
indicating that no drives at all were connected (only a 200GB Hitachi
PATA drive was in the system).

It doesn't matter what brands of drives are used or whether they're
connected to the mobo's built-in IDE controller or a PCI PATA
controller (Promise or Silicon Image). Only one drive was connected
per cable, at the master position (drives configures for cable select).

What's going on?

larry moe 'n curly <larrymoencurly@my-deja.com> wrote:
> I'm having problems with Hitachi's Drive Fitness Test vers. 4.07 and
> 4.08, but vers. 3.68 and older run perfectly.
>
> DFT v. 4.0x worked fine with mobos based on SiS 735 or nVidia nForce2
> chipsets but failed with mobos based on the VIA 8237, Intel 810i, or
> Intel 440BX chipsets. With some of the problem mobos, DFT v. 4.0x
> will abort to the command line prompt during the drive detection
> phase, while with others it fails to detect some drives, in one case
> indicating that no drives at all were connected (only a 200GB Hitachi
> PATA drive was in the system).
>
> It doesn't matter what brands of drives are used or whether they're
> connected to the mobo's built-in IDE controller or a PCI PATA
> controller (Promise or Silicon Image). Only one drive was connected
> per cable, at the master position (drives configures for cable
> select).
>
> What's going on?

Just the usual, it takes whoever is involved with it some
time to even notice its got problems with new versions.

Rod Speed wrote:
> larry moe 'n curly <larrymoencurly@my-deja.com> wrote:

> > With some of the problem mobos, DFT v. 4.0x will
> > abort to the command line prompt during the drive
> > detection phase, while with others it fails to detect
> > some drives,

> Just the usual, it takes whoever is involved with it some
> time to even notice its got problems with new versions.

They've had since spring to fix the bug. I'll bet that at least a few
hundred HDs have been exchanged under warranty because of it.