Ok, last night if you saw my post I spent all night attempting to figure out why my computer would not recognize my harddrive in my bios.
Well this is how it was. I could hook up my harddrive ALONE and the bios would see it. If I hooked up my CDROM with it, then it only recognized the CDRW and not the HDD. I hooked it up alone as a secondary master, and as a slave to the HDD, and both ways it never recognized both. And the funny thing was, I have 5 ribbon cables, and only one of them seemed to ever allow me to recognize the HDD.
So I called a tech and we were on the phone for quite some time. He thought it was my CDRW that was causing the problem. So after about 2 hours of switching around the HDD and CDRW, I went and got a CDRW from another computer and hooked it up. Well the same thing happened. BUT, after I got off the phone with the tech, I did end up getting the HDD and CDRW to both be recognized in the BIOS. So I thought good deal, I began downloading XP boot disks on another comp and I come back to stick them in, and reboot, and it no longer recognized the harddrive again.
Anyways after about another 10 boot ups messing with the harddrive and CDRW by changing them around on the primary and secondary and slave, it starts making this wierd "CLINK CLINK CLINK" everytime I boot. And in the BIOS it allows me to recognize it alone with nothing else connected, but now it says "MAXTOR RIGEL" and it shows it as a "0GB" HDD. Well I search on the net and it says it does that when the HDD is failing and no longer can read the disks in the HDD itself.
Well what my question is, was it my HDD all along that was causing it to only be recognized every 15 or so bootups, and only when it was by itself. (It didnt recognize it EVERY time by itself, only 1 out of every 5 or so bootups)? Could it be my harddrive that was making it do that? Or could it be more of my motherboard IDE slots doing that? AND did my HDD fail because I had reconnected and switched it around so many times (50+) and rebooted, or did it fail because it was actually the problem in the first place?
Well this is how it was. I could hook up my harddrive ALONE and the bios would see it. If I hooked up my CDROM with it, then it only recognized the CDRW and not the HDD. I hooked it up alone as a secondary master, and as a slave to the HDD, and both ways it never recognized both. And the funny thing was, I have 5 ribbon cables, and only one of them seemed to ever allow me to recognize the HDD.
So I called a tech and we were on the phone for quite some time. He thought it was my CDRW that was causing the problem. So after about 2 hours of switching around the HDD and CDRW, I went and got a CDRW from another computer and hooked it up. Well the same thing happened. BUT, after I got off the phone with the tech, I did end up getting the HDD and CDRW to both be recognized in the BIOS. So I thought good deal, I began downloading XP boot disks on another comp and I come back to stick them in, and reboot, and it no longer recognized the harddrive again.
Anyways after about another 10 boot ups messing with the harddrive and CDRW by changing them around on the primary and secondary and slave, it starts making this wierd "CLINK CLINK CLINK" everytime I boot. And in the BIOS it allows me to recognize it alone with nothing else connected, but now it says "MAXTOR RIGEL" and it shows it as a "0GB" HDD. Well I search on the net and it says it does that when the HDD is failing and no longer can read the disks in the HDD itself.
Well what my question is, was it my HDD all along that was causing it to only be recognized every 15 or so bootups, and only when it was by itself. (It didnt recognize it EVERY time by itself, only 1 out of every 5 or so bootups)? Could it be my harddrive that was making it do that? Or could it be more of my motherboard IDE slots doing that? AND did my HDD fail because I had reconnected and switched it around so many times (50+) and rebooted, or did it fail because it was actually the problem in the first place?
