Although I may have not replied to everyone, I have tried to follow
all suggestions I have read here so far. If your suggestion is not on
this list please remind me to try it again.

Here is my dilemma.

Here is what I have done.
I reset the CMOS
I have all three boot options set to HD0
I have boot from external disabled
I have onboard RAID disabled

My computer is a Abit KT7A RAID
1G Athlon
Nvidia 5500 Video
430W PS
Sil 3112A SATA RAID 14.2.47 1997-2004 Silicon Image Inc. PCI
controller card
80 G IDE WD boot drive
IDE WD 160G
SATA WD 500

I am trying to add a SATA WD 750

Everything was working fine. I added the 750 drive. It wouldn't
work. It hangs the computer at boot. I went to WD support page and
found this:
http://wdc.custhelp.com/cgi-bin/wdc....ted=1112379341

I installed the jumper and the drive worked! I copied all the files I
had on a 150G IDE drive to the new 750 drive. I then took the IDE
hard drive out. I mounted the 750 in its place. Well it quit working
again and started hanging at the boot screen.

When I try to boot the PCI SATA controller reports
WDC WD 5000 AAKS 00TMA 5 000 000
WDC WD 7500 AAKS 00RBA < It hangs here

I can unplug the 750 and everything boots fine.
I have tried the 750 on controller 0 and 1
If I plug the 750 into slot 0 then it hangs without reporting the 500

The 500 has been working fine without using the jumper, but I have
installed a jumper on the 500 now.

So now the 500 will work with or without the jumper. the 750 will
not work with or without the jumper.

The 750 will work fine in my other machine, but I want it in my old
KT7A machine. I have also tried using the 750 only without the 500.

What else can I try to get the 750 going?

Terry wrote:
> Although I may have not replied to everyone, I have tried to follow
> all suggestions I have read here so far. If your suggestion is not on
> this list please remind me to try it again.
>
> Here is my dilemma.
>
> Here is what I have done.
> I reset the CMOS
> I have all three boot options set to HD0
> I have boot from external disabled
> I have onboard RAID disabled
>
> My computer is a Abit KT7A RAID
> 1G Athlon
> Nvidia 5500 Video
> 430W PS
> Sil 3112A SATA RAID 14.2.47 1997-2004 Silicon Image Inc. PCI
> controller card
> 80 G IDE WD boot drive
> IDE WD 160G
> SATA WD 500
>
> I am trying to add a SATA WD 750
>
> Everything was working fine. I added the 750 drive. It wouldn't
> work. It hangs the computer at boot. I went to WD support page and
> found this:
> http://wdc.custhelp.com/cgi-bin/wdc....ted=1112379341
>
> I installed the jumper and the drive worked! I copied all the files I
> had on a 150G IDE drive to the new 750 drive. I then took the IDE
> hard drive out. I mounted the 750 in its place. Well it quit working
> again and started hanging at the boot screen.
>
> When I try to boot the PCI SATA controller reports
> WDC WD 5000 AAKS 00TMA 5 000 000
> WDC WD 7500 AAKS 00RBA < It hangs here
>
> I can unplug the 750 and everything boots fine.
> I have tried the 750 on controller 0 and 1
> If I plug the 750 into slot 0 then it hangs without reporting the 500
>
> The 500 has been working fine without using the jumper, but I have
> installed a jumper on the 500 now.
>
> So now the 500 will work with or without the jumper. the 750 will
> not work with or without the jumper.
>
> The 750 will work fine in my other machine, but I want it in my old
> KT7A machine. I have also tried using the 750 only without the 500.
>
> What else can I try to get the 750 going?

The drive won't work with the SATA controller. Like I said previously,
I've had the same problem. Nothing you can do except buy a better
controller or upgrade the computer.

Ari

--
spammage trappage: remove the underscores to reply
Many people around the world are waiting for a marrow transplant. Please
volunteer to be a marrow donor and literally save someone's life:
http://www.abmdr.org.au/
http://www.marrow.org/

"Davy" <(E-Mail Removed)> wrote in message
news:Xns9A795877514EBmeremoveallthistextc@216.196.109.145...
> Terry
>
> I have very similar problems adding a Samsung 700Gb SATA II drive to a
> three year old IBM Thinkcentre M50 with a Phoenix BIOS.
>
> I copes with my 160Gb SATA (I ?) boot drive but fails with a BIOS IDE
> configuration error if I add the 700Gb SATA II drive. But it is not
> consistent, sometimes after the POST failure I can press F2 (resume) and
> then it cannot find an OS - or sometimes after entering and quiting the
> BIOS setup it boots but sees the 700Gb drive as being only 128Gb. Try
> entering BIOS setup at a restart and then exiting without saving anything
> - see if you get similar. You might have to do this several times.
>
> From yours and other posts it seems that the problem is with drives
> bigger than 500Gb? Either a BIOS or SATA controller problem.
>
> So possible solutions:
> - add the 750Gb drive via an USB external enclosure
> - buy a 500Gb drive
> - buy a modern SATA II PCI internal adaptor
>
> Anyone any views on whether these options are likely to be successful?
> cheers, Davy
>

If no one has an answer here to install the drive internally then I'd be
checking to see if I had the latest bios for the Abit. If that is not an
issue I'd be calliing WD tech support to see if they have any possible
remedies. If the issue can't be resolved I'd get back to Abit and see if
they have dealt with this issue and can solve it with the correct setting.
--
Jan Alter
(E-Mail Removed)
or
(E-Mail Removed)

Jan Alter wrote:
> "Davy" <(E-Mail Removed)> wrote in message
> news:Xns9A795877514EBmeremoveallthistextc@216.196.109.145...
>> Terry
>>
>> I have very similar problems adding a Samsung 700Gb SATA II drive to a
>> three year old IBM Thinkcentre M50 with a Phoenix BIOS.
>>
>> I copes with my 160Gb SATA (I ?) boot drive but fails with a BIOS IDE
>> configuration error if I add the 700Gb SATA II drive. But it is not
>> consistent, sometimes after the POST failure I can press F2 (resume) and
>> then it cannot find an OS - or sometimes after entering and quiting the
>> BIOS setup it boots but sees the 700Gb drive as being only 128Gb. Try
>> entering BIOS setup at a restart and then exiting without saving anything
>> - see if you get similar. You might have to do this several times.
>>
>> From yours and other posts it seems that the problem is with drives
>> bigger than 500Gb? Either a BIOS or SATA controller problem.
>>
>> So possible solutions:
>> - add the 750Gb drive via an USB external enclosure
>> - buy a 500Gb drive
>> - buy a modern SATA II PCI internal adaptor
>>
>> Anyone any views on whether these options are likely to be successful?
>> cheers, Davy
>>
>
> If no one has an answer here to install the drive internally then I'd be
> checking to see if I had the latest bios for the Abit. If that is not an
> issue I'd be calliing WD tech support to see if they have any possible
> remedies. If the issue can't be resolved I'd get back to Abit and see if
> they have dealt with this issue and can solve it with the correct setting.

Are you on crack? That board is 7 years old and pre-dates SATA! :P
Why should Abit work on a crappy no-name PCI SATA controller that
doesn't support the drive? Why should WD spend any time on it either? If
anything, hassle silicon image about their sometimes deficient chips!

Ari

--
spammage trappage: remove the underscores to reply
Many people around the world are waiting for a marrow transplant. Please
volunteer to be a marrow donor and literally save someone's life:
http://www.abmdr.org.au/
http://www.marrow.org/

On Mon, 07 Apr 2008 12:53:48 +0800, spodosaurus
<spodosaurus@_yahoo_.com> wrote:

>Terry wrote:
>> Although I may have not replied to everyone, I have tried to follow
>> all suggestions I have read here so far. If your suggestion is not on
>> this list please remind me to try it again.
>>
>> Here is my dilemma.
>>
>> Here is what I have done.
>> I reset the CMOS
>> I have all three boot options set to HD0
>> I have boot from external disabled
>> I have onboard RAID disabled
>>
>> My computer is a Abit KT7A RAID
>> 1G Athlon
>> Nvidia 5500 Video
>> 430W PS
>> Sil 3112A SATA RAID 14.2.47 1997-2004 Silicon Image Inc. PCI
>> controller card
>> 80 G IDE WD boot drive
>> IDE WD 160G
>> SATA WD 500
>>
>> I am trying to add a SATA WD 750
>>
>> Everything was working fine. I added the 750 drive. It wouldn't
>> work. It hangs the computer at boot. I went to WD support page and
>> found this:
>> http://wdc.custhelp.com/cgi-bin/wdc....ted=1112379341
>>
>> I installed the jumper and the drive worked! I copied all the files I
>> had on a 150G IDE drive to the new 750 drive. I then took the IDE
>> hard drive out. I mounted the 750 in its place. Well it quit working
>> again and started hanging at the boot screen.
>>
>> When I try to boot the PCI SATA controller reports
>> WDC WD 5000 AAKS 00TMA 5 000 000
>> WDC WD 7500 AAKS 00RBA < It hangs here
>>
>> I can unplug the 750 and everything boots fine.
>> I have tried the 750 on controller 0 and 1
>> If I plug the 750 into slot 0 then it hangs without reporting the 500
>>
>> The 500 has been working fine without using the jumper, but I have
>> installed a jumper on the 500 now.
>>
>> So now the 500 will work with or without the jumper. the 750 will
>> not work with or without the jumper.
>>
>> The 750 will work fine in my other machine, but I want it in my old
>> KT7A machine. I have also tried using the 750 only without the 500.
>>
>> What else can I try to get the 750 going?
>
>The drive won't work with the SATA controller. Like I said previously,
>I've had the same problem. Nothing you can do except buy a better
>controller or upgrade the computer.
>

It did work Fine for one day. Strange.

"spodosaurus" <spodosaurus@_yahoo_.com> wrote in message
news:47fa1a4e$0$13297$(E-Mail Removed)...
> Jan Alter wrote:
>> "Davy" <(E-Mail Removed)> wrote in message
>> news:Xns9A795877514EBmeremoveallthistextc@216.196.109.145...
>>> Terry
>>>
>>> I have very similar problems adding a Samsung 700Gb SATA II drive to a
>>> three year old IBM Thinkcentre M50 with a Phoenix BIOS.
>>>
>>> I copes with my 160Gb SATA (I ?) boot drive but fails with a BIOS IDE
>>> configuration error if I add the 700Gb SATA II drive. But it is not
>>> consistent, sometimes after the POST failure I can press F2 (resume) and
>>> then it cannot find an OS - or sometimes after entering and quiting the
>>> BIOS setup it boots but sees the 700Gb drive as being only 128Gb. Try
>>> entering BIOS setup at a restart and then exiting without saving
>>> anything
>>> - see if you get similar. You might have to do this several times.
>>>
>>> From yours and other posts it seems that the problem is with drives
>>> bigger than 500Gb? Either a BIOS or SATA controller problem.
>>>
>>> So possible solutions:
>>> - add the 750Gb drive via an USB external enclosure
>>> - buy a 500Gb drive
>>> - buy a modern SATA II PCI internal adaptor
>>>
>>> Anyone any views on whether these options are likely to be successful?
>>> cheers, Davy
>>>
>>
>> If no one has an answer here to install the drive internally then I'd be
>> checking to see if I had the latest bios for the Abit. If that is not an
>> issue I'd be calliing WD tech support to see if they have any possible
>> remedies. If the issue can't be resolved I'd get back to Abit and see if
>> they have dealt with this issue and can solve it with the correct
>> setting.
>
> Are you on crack? That board is 7 years old and pre-dates SATA! :P Why
> should Abit work on a crappy no-name PCI SATA controller that doesn't
> support the drive? Why should WD spend any time on it either? If anything,
> hassle silicon image about their sometimes deficient chips!
>
> Ari
>
> --
> spammage trappage: remove the underscores to reply
> Many people around the world are waiting for a marrow transplant. Please
> volunteer to be a marrow donor and literally save someone's life:
> http://www.abmdr.org.au/
> http://www.marrow.org/


I clearly ignored the timeframe on the mb and didn't notice the cpu being
used and should have suggested that the OP get in touch with the Silicon
Image SATA controller folks to see what they can do to get the WD hdd
recognized by the controller. Having used the KT7A mb myself for awhile some
7 years ago I must have thought they were timeless.

--
Jan Alter
(E-Mail Removed)
or
(E-Mail Removed)