On Sat, 27 Dec 2003 05:32:34 -0600, "brian" <> wrote:
Have you tried trying to put the HDs on a lower speed, for example DMA
2? Some BIOSs can do this, some can't.
The power supply might be damaged and not be able to power up the HDs
properly.
The cables might not be proper UDMA cables, and might not be able to
handle the data rate.
When you run out of ideas, you might just have to use a different
motherboard.
Lets us know what you ended up doing, ok?
>I was recently forced to upgrade my system, i had an amd 2000xp in which the
>stock heat sink melted onto the processor. i assume the fan failed and the
>k7s5a motherboard didn't have any protection, at least this is my guess. i
>was gone for a week and my roomate is the one who discovered the wreck. i
>didn't overclock or abuse the processor, under a full load it would register
>55C. i don't think it was a power surge, the capacitors on the old
>motherboard look fine.
>I then went and purchased a kt600 with a barton 2500. i transferred my
>existing ati and audigy cards, no problem. i tested my crucial memory in
>the new system, no problem. everything works fine except the bios will not
>pickup up either of my hard drives, i have a maxtor 120bg/133 and a western
>digital 80 gb/66. i have tried for over 6 hours using every jumper postion
>possible. i have numerous sets of ide cables, not the problem. the bios
>will pick up my cdroms without a problem, but no combination of my hard
>drives. Sometimes the bios will hang on the western digital, but it never
>recognizes it. going into the bios manually doesn't work either.
>here's the kicker- i went into my closet and got out my old, old computer
>from college. i took the 3.2 gb western digtial hd from that and the kt600
>had no problem finding that (thus, i am able to type this). this is a very
>new motherboard, both of the unreadable hard drives were made well before
>this mobo came out. everyother piece of hardware (system fans, sound,
>video, memory) show no ill effects. is it possible it was a power surge
>that only hit my 2 hd's and proccessor? i was running windows xp on fat
>32, i don't think it has anything to do with that wither.
>in conclusion, i have read ever troubleshooting forum on ecs, msi, wd, and
>maxtor. i have tried to tackle this issue on several different days, all to
>no avail. I would appricate some input.
Sig:
You know, a lot of things, in this world, they make no sense. But now Im here, everthing make no sense.
|