The harddrives are from my old rig:
Western Digital 250GB harddrive SATA
Seagate Baracuda 750GB harddrive SATA
I also have an old IDE DVD Burner as my optical drive.
Problem: I first put together this computer on Monday. The problem I had was that whenever I turned off the power supply (flip the switch after I turned off the computer) and unplug the cable to move it to the room it was intended for and turn it back on, it would not turn on (meaning, no video was on my monitor and my keyboard won't light up). Basically, the computer would turn on, the asus p6t onboard switches lights were on, just no video or POST.
Then, I proceeded to think it was the graphics card (an old 6600 LE NVidia card). I ruled that out after I tested it with my brother's graphics card (NVidia 7600 GT), because it still didn't work.
Next, I took out the battery and plugged it back in. Bam, now the video is on and mouse/keyboard work so I can log in. As soon as I close everything in the case and move it by (turning off computer, then flipping power supply switch, then taking out power cable to move), it won't POST, output video, or show any sign of life in keyboard/mouse.
I called ASUS, they would call back, in the meanwhile I read the manual, I read somthing about resetting the CMOS, I did that, and it worked! However, my issue is that anytime I turn off the power supply, the CMOS needed to be reset, I called ASUS and they told me to get an exchange.
I got my new ASUS P6T motherboard, I plugged everything in and it works. The problem now is that, when I turn off my computer, it starts right back on. The only way to turn it off is that right after it shuts down, I have to flip the power supply off.
I have spent over 10 hours trouble shooting this, my first real problem I have had with building rigs in the 4 years that I have been building them. I searched google and the web and don't seem to find anything. I am probably concern with the power supply but not entirely sure because I have seen mostly positive reviews about that power supply with the ASUS p6t, also I have seen some bad ones with it so it might be 50/50.
My questions and concerns are this:
1. What is the difference between Turbo and Normal on the ABS (originally it was on Turbo but I switched it to Normal)
2. My ASUS P6T had the 8 pin connector on the motherboard, but 4 out of those 8 were covered up, I took off the cap and plugged in all 8 pins. Should I have left it at four pins only? (I read it was good that I did that but I'm not entirely sure)
3. The ABS power supply has this Ground wire. In the manual (first time opening one up since forever), I read that I was suppose to attach it to the motherboard, but in the picture, it shows that it is connected to the hdd cage. In addition, the ground wire is covered with this rubber cap, so I don't know why I should be grounding that to the case (too afraid to even put that thing on the motherboard as the book suggested). I even tried taking off the rubber cap and tapping that on the case while booting it up and powering it off (in case it was a short) but that did not do any good.
Any suggestions? Please help because I am getting frustrated since I thought this was going to be a sweet and easy going rig.
P.S. The case is basically toolless so it is pretty hard to keep it grounded on its own (if it does anything)
P.S.S - I read on google to go into the BIOS and make an option in the bios which tells the computer to keep it off incase there was a short , or crash when the computer fails. They recommended to turn it off but when I went into BIOS, it was already off.
I am having a somewhat similar problem where my ASUS P6T will only POST with only 1 stick of RAM and am going to RMA it soon. I have also read about people with these same sorts of issues and am thinking that the ASUS P6Ts might be glitched.
I have been reading similar stuff, people are having similar issues to mine, but I haven't found anyone that has a same issue as mine though :[ Asus said it was probably a bad BIOS, but I doubt two boards back to back from them would not respond correctly when shutting down. I wonder if it has anything to do with the OS