I've explained this very perpelixing problem to several people and we are all just as baffled. So here it is.

I got all the parts to a brand new comp I was making for school, everything was okay, then I started having real problems with the computer, it came down that the first mobo I got had a bad IDE controller and was messing up the ability to use the HD. So I sent the mobo back and got a replacement.

But, right before I took it down to send back, it stopped working all together, all it did was power up the fans and drives, like it was stuck in witht he reset button in, and that was the final straw to send it back.

Well, I just got the new one, and it just sits there with the fans running and the drives powering up, but it won't even try to boot. This is where I stand right now witht he problem.

Now what I've tested, and what it does. The system does the same thing whether or not the CPU and the RAM are install or not. I was concerned that I had a bad power supply, so I replaced that, which I wanted to anyway, its an approved 300w supply, so that isn't a problem.

I have a grave concern that its the chip, that somehow I fried it with teh first system, but I have no way of checking, also, if might be the ram, but I do not know anyone in my area that has a comp that uses DDR, so I do not have a way of testing that either.

So if ANYONE has some tips, I'd be more than happy for any help. I've worked with computers for many years now and NEVER seen anything like this before. Thank you in advance.

Jay Kirby

If thats the case, i say if they allow it, send it all back and get all new. I have a 1.4ghz athlon also, only i have an Asus A7A266 mobo. And when i tried to set my CPU from the mobo by jumpers i had the same problem. Im not to sure but i think your mobo might have a jumperless configuration for the CPU. Try switching to that. Finally, you might also need a BIOS Update. My 1.4 is only running at 1.33 right now because of the BIOS. There isnt a final update for mine yet, but there is a german Beta. **** that, ill still with 1.33 until the final. But enough with my problem. Check here and make sure you have the latest BIOS. http://www.asus.com.tw/products/Motherboard/bios_socka.html#a7m266

------------------
- - Load Universe into Cannon. Aim at Brain. Fire. - -

[This message has been edited by Paleo Pete (edited 08-07-2001).]

Also while your there, check for an updated manual for your mobo. Your jumper config might not be correct someplace. I dont know how usefull this info might be to you, but aleast its a start for figuring this out.

If you figure this out and get your system running come back and tell me the outcome. I like to hear about peoples success stories.

------------------
- - Load Universe into Cannon. Aim at Brain. Fire. - -

Dr DRAM:

The kind of language used in your first post in this topic is a violation of the PC Guide Discussion Forums' Acceptible Use Policy (http://www.pcguide.com/cgi-bin/Ultimate.cgi?action=agree) and will not be tolerated. If you must use profanity in your attempts at assistance, there are plenty newsgroups out there.

------------------
Support the right to keep and arm bears.
Note: Please post your questions on the forums, not in my email.

Computer Information Links (http://www.geocities.com/paleopete/)

[This message has been edited by Paleo Pete (edited 08-07-2001).]

Originally posted by Paleo Pete:
Dr DRAM:

The kind of language used in your first post in this topic is a violation of the PC Guide Discussion Forums' Acceptible Use Policy (http://www.pcguide.com/cgi-bin/Ultimate.cgi?action=agree) and will not be tolerated. If you must use profanity in your attempts at assistance, there are plenty newsgroups out there.



Im sorry, i wasnt aware of that. I will try to watch my mouth from now on.

------------------
- - Load Universe into Cannon. Aim at Brain. Fire. - -

Do you get any beeps? The A7M266 manual has a small table on p. 45 describing the meaning of various diagnostic beeps. If it's something like a bad video card (or just a mis-seated one), your system won't go anywhere.

Paul
~{:-)

I really wasn't too happy when I finally solved the problem. I was really concerned that it might be the CPU, and it was. So right now I'm using a duron 750, which is still useable, while I hassle out getting a new chip sent to me.

Thanks to all that tried to help.