Quote:
Originally Posted by DaTwo 
OK, you are confusing the data signaling with the power rail from my statement. Basically if the power rail is week... one may work but not the other due to a dip in voltage. This can be caused by something as simple as a failed capacitor.
|
OK, but I would have thought that if the Promise controller and southbridge were on the same rail, that a power problem would manifest in both controllers. However, I suppose it could be that the chips are competing with each other for power in a low voltage condition and one is winning out over the other, or that the BIOS is intelligently managing components for such a condition (highly unlikely IMHO). But I really don't know how exactly the BIOS relates with the PDC and southbridge, which is one reason why I'm asking all these questions.
To me, the fact the HDD controller failed intermittently over a period of time before failing completely (with the CD drive always working fine) would indicate that the HDD controller (or a cold solder joint/cable issue) was the problem. The BIOS re-odering may have had nothing to do with the device being recognized.
Quote:
| He was saying the cd-rom was working intermittently based on his election in the bios. I opinion is that the promises controller isn't getting the correct power due to a failed capacitor and is causing it to report to the bios incorrectly causing a halt in the boot process. This is why when the cd-rom is selected as the first to boot it will work fine. |
No, I think he was referring to his HDC failing, not his CD drive.
Quote:
| Basically the has the 50 pin interface connector to a 44 pin 2.5 connector so the drive can sit inside it. |
What has the 50 pin/44 pin slim to IDE adaptor? Looks like you left the word out.
Quote:
| Just select it in the bios boot order. |
This is what I did before to get it working, and it's all I should have to do. The solution Denn found seems awfully convoluted to me... However, now, even if I re-arrange the boot options, the USB HDD does not appear to be detected by the BIOS and will not boot. This most certainly appears to me to be a BIOS issue. I can't imagine why Sager would have crippled the 9860 BIOS even further in later revisions.