Yesterday I went and ought an Athlon 2500+, Abit NF7-S, 2x256 OCZ PC3200 and a new case. I took a GeForce 4 Ti4200, Maxtor HD, CD-R/W, and a 450PSU from my old case at put it in the new one. When I turned on the computer everything seemed fine until I looked at the monitor and saw it got no signal. I tried putting in my old Voodoo3 and had the same effect. Then I tried a diffrent monitor and still got no signal. I put the GeForce4 back into the old computer and it's running fine.
Anyone know what's going on? My only thought is that both PCI and AGP slots are screwed up on this mobo. The computer seems to boot fine, the CD-R/W flashes as in a normal boot and there are no beeps.
Yeah, sounds like slots are screwed. But you might try to post w/o the vid card and see if it gives the proper beep code. Don't know for sure, but I'm guessing if the slots are bad you w/n get the beep code.
Get the beep codes here if you don't already have 'em. I don't think they're in the manual.
Read the first post in this forum, it sounds like you assembled something wrong.
<font color=blue>Only a place as big as the internet could be home to a hero as big as Crashman!</font color=blue>
<font color=red>Only a place as big as the internet could be home to an ego as large as Crashman's!</font color=red>
Uh, what? Did you even read my post? I looked at the first topic (Motherboard FAQ) and it has nothing related to what my problem is.
Coyote: Thanks for the help. I took out the video card and turned it on and still no beep. I'm taking it back tomarrow, unfortunatly it's gunna be awhile until I can rebuild it. I'm going to have them check the CPU and RAM also, incase the faulty mobo did something to them.
<P ID="edit"><FONT SIZE=-1><EM>Edited by KMFDMAddict on 05/14/04 07:11 AM.</EM></FONT></P>
Yes, I read your post. From what I gather you turned the system on and all you got was a black screen. This can be caused by several things, including not having the square ATX 12v connector attached to the board (old power supplies didn't have that connector), a grounded board, or a drive cable problem. All that stuff was in the post I referred to.
It could also be a RAM problem, a board problem, or a CPU problem. But those are less likely to be the issue that the first things I referred to.
<font color=blue>Only a place as big as the internet could be home to a hero as big as Crashman!</font color=blue>
<font color=red>Only a place as big as the internet could be home to an ego as large as Crashman's!</font color=red>
You are about to answer a thread that has been inactive for more than 6 months. If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.