MSI KM4M-V Motherboard - SATA HDD

[zepper]

malgpz,

Thanks for editing. I have one other suggestion: If you set your BIOS to handle the drives as IDE (non-RAID, etc.) you shouldn't need to load the SATA driver during XP install. I don't use RAID and I always set my BIOS to handle the drives as simply as possibe and never have had to F6 the SATA driver. I used SCSI in the past and it was a common practice with those.

I also recommend installing in Win XP one driver that is common for SCSI drives, Adaptec's ASPI layer. Here is some info on it: Radified: ASPI layer drivers updated with Force ASPI [ForceASPI v1.7]

And here is the link to the drivers:
Adaptec - Adaptec Driver: Windows ASPI drivers version v4.71.2 Download Detail

The ASPI pack comes with a utility called ASPICHK that will check to see if an ASPI layer is already installed and what version. I guess later versions of Win already have the equivalent. As Radified says, the ASPI layer does help with some burner issues, etc. and seldom causes problems. If you use Nero software for burning, they offer their own ASPI layer, but IDK if it works any better than Adaptec's - use whichever you prefer.

.bh.

[malgpz900]

Update.

I took the drive to my brother whose PC M/B is running SATA2. His Bios picked my HD up, so ran Hitachi's Feature-Tool software to change the Date Transfer Rate settings, but their software could not find the HD .

Went through into XP and system found HD so he had bought the HD off me.

Problem solved.

Cheers for all of the advise.

Malcolm.

[zepper]

Isn't that silly? How was the BIOS set to handle the drive? But all's well that ends well...

.bh.

[Cmptr-Gy-Dv]

Quote:

Originally Posted by malgpz900

Update.

I took the drive to my brother whose PC M/B is running SATA2. His Bios picked my HD up, so ran Hitachi's Feature-Tool software to change the Date Transfer Rate settings, but their software could not find the HD .

Went through into XP and system found HD so he had bought the HD off me.

Problem solved.

Cheers for all of the advise.

Malcolm.

well thats just great now what are we suppose to do, you come long and bail out on us like that, you go get that drive back so we can help you find the problem,

[zepper]

No fair taking our bone away... ;-) Well, I guess there's always a chance that mine can take up where his left off, but not much of one as mine has passed all tests as it should.

.bh.

[malgpz900]

Quote:

Originally Posted by Cmptr-Gy-Dv

well thats just great now what are we suppose to do, you come long and bail out on us like that, you go get that drive back so we can help you find the problem,

Don't worry the saga is continuing. Response from Hitachi support:-


Dear Mr. Malcolm Dixon,

Thank you for contacting our Hitachi Technical Support Center.

Yes, you can use our Feature Tool and to slow the speed down from SATA II
( 3.0 GB/S ) to SATA I ( 1.5 GB/S ).

Your motherboard can see only SATA I hard drives, so the new drive with
SATA II is not recognized.

Should you have questions, please contact us again.

Best regards,
Yana Vlasenko

Hitachi Technical Support Center

I have replied to their e-mail saying Feature tool does not pick up the HD. See what comes back.


Malcolm.

[zepper]

Geez,

I hope the reply I get is more useful than that...

.bh.

Here's what I got for my first question:

Quote:

Hi Bill,

Thank you for contacting Hitachi Global Storage Technologies.

Actually all SATA models with 3.0 transfer speed are backward compatible.
If this drive is not recognized by the systems it could be related on the
systems (motherboard )limitation and if this would be the case, we have a
Feature tool which can downgrade the transfer speed from 3.0 to 1.5 gb/s.
You only need to hook up the drive in SATA II compliant motherboard and
perform it.

Regards,
Eric R.
_______________________________
Hitachi Global Storage Technologies
US toll-free: 888.426.5214
Fax: 408.717.9007

Part of the answer to my other email:

Quote:

Allow me to answer your question about the 2 pins at the front.
The 2 pins at the front has no used for the end user. It is only used by
our product design and development team.

Regards,
Eric R.