?? how can i tell

[MLW]

how can i tell if my cpu is bad or if my motherboard

[homer15]

test the cpu in another motherboard or test another cpu in your motherboard. what's the problem?

[MLW]

just cant get two cpu's and two motherboards but the boards are getting power but they post

i and think its the cpu.

[homer15]

i know, that's the problem with testing parts like that.

so they post and then what?

[MLW]

i am sorry they dont post that was mistype

[homer15]

do you get any beeps?

[MLW]

no, the cpu fan comes on and the onboard led, i tried other ram. and still no post, hdd light comes on, but no power led on case...

could i look at a cpu and tell if it was burnt?

[homer15]

sometimes there are physical signs that the cpu is burnt. it'll smell funny too. are you getting any video feed out of it?

[MLW]

no video at all. could i take a pic of the cpu and could you tell if its bad?

[homer15]

if it's a close one, i might be able to tell, but you can't always visibly tell if a chip is fried.

[Cricket]

Are you testing the parts out of the case? If not, remove the motherboard from the case and try for POST that way. If the motherboard is shorting out to the case, your system will get power but will not POST or run properly.

Follow the instructions here (http://forum.pcmech.com/showthread.php?s=&threadid=12753).

:) Cricket

[MLW]

yes i have tested them out of the case and still get no post..

[yellohut]

are you using onboard sound?
i had this happen to me once and it was the onboard sound chip. took me forever to finally figure it our because i was expecting at least a beep. but the memory and cpu were good. good thing mobo was under warranty still. :)

[Cricket]

Do you have working CPU you can swap into that motherboard to test with?

Have you tried another power supply yet?

What are the specs?

:) Cricket

[MLW]

I am wanting on the a new CPU to come in, soon as i get i will let you know.

could a bad mobo brun a chip>?

[MLW]

OK cpu came in and i got it to post but now, when it boots up it finds the HD and CD and then locks up....now what do i do?

[MLW]

locks up when finding the CDrom

[Cricket]

Do you have a OS CD in the CD-ROM drive? Is the CD-ROM drive set as first boot device in BIOS?

Does the hard drive have an OS on it already or is it blank?

Make sure the drive jumpers are set properly for the type of IDE cable you're using. If you're using 80 wire IDE cables, set the jumpers to CS or CSel (cable select). If you're using 40 wire IDE cables, set the drive jumper to master or slave depending on what priority you want for that drive.

:) Cricket

[MLW]

how could i tell what the which cabel i am useing?

[MLW]

Also i have an old mobo that has two different types of ram how can i tell what they are..
i think one is pc-100 or pc-133 and the other i think is EDO..

but i am not sure, and can you run both at one time??

[grasshopperbe]

well pc 100 and pc133 are both sdram
as far as iknow . you can use these together normally, but the 133 will work at 100 speed. (check if your bios is set to 100 and not 133 if you want to use the pc100 safely .

I think you can run edo too, but its a lot slower and my guess would be that it will slow down everything on your pc.

always check properly if the ram slot is the correct one, you dont want to destroy your mobo by forcing in the wrong chip in the wrong slot.
the lenght and place of the 'divider' in the bottom of the ram chip are what you should check for.

for ide's first check the connector on your motherboard which is ide1 and ide2 (fine print near the connectors) . put the hd on ide1 and make sure the hd's jumper is set to master or cable select.

now if your ide cables have two connectors, you can either place your cdrom as slave (see jumper) on ide1 cable , or as master/cable select on ide2 cable. usually the master is placed at the end of the cable.

then check in your bios if boot order is set correctly (hd, cdrom, disk drive should be chosen, in which order is less important.

hope this can help.

[MLW]

hey thanks alot
that helped alot

[grasshopperbe]

did you find what the problem was exactly?

[MLW]

yes a bad sitck of mem