View Full Version : AMI BIOS Problems
04-26-00, 12:58 PM
Putting together a small desktop computer for my girlfriend's parents. I put everything together and boot up to this message after it tests the memory:
Trend ChipAwayVirus(R) On Guard
It never reaches the point in POST that I can get into the CMOS setup, it just hangs at "WAIT..." and I have to shut it down. I've already reset the CMOS settings and this has done nothing except make a new error during POST (just telling me that processor speed reported incorrectly, probably from resetting the clock multiplier when I reset CMOS). No beep codes either.
Anyways, anyone have any clue as to what this could mean?
04-26-00, 01:48 PM
Well, now you look like a fool...Hehe. Kidding. But anyhow, the BIOS will not POST? There are a few possibilities. It could be fried, or another piece of hardware is causing it to lock up. Try removing all the cards in the ports and booting. If you hear some beeps and the hard drive spins up, good. Then add the vid card, turn on, wait for beeps, and so-on.
If you get impatient with that damn AMI, get AWARD bios. It runs about $20 and I feel its the best.
Also, press & hold delete, or press and hold ESC or try CTRL+ESC at bootup.
04-26-00, 02:17 PM
hehehe .... http://www.speedguide.net/ubb/wink.gif
Anyways, the M/B has all controllers built onto it. Don't think I've said it before, but this is a cheap board. It has onboard controllers for a 56k modem, video (8mb shared RAM), sound, usb, and the normal serial, parallel, ps-2, and DIN. The system has 64 MB of PC100 RAM running on an AMD K6-2 450 MHz. I'm going though testing the individual components that attach to the m/b and disconnecting one and booting up. So far, havn't gotten passed the same point during POST.
I've already cleared CMOS via jumpers. Also, I cannot get into CMOS ... instead, it just stalls on "WAIT..."
Any ideas anyone?
04-27-00, 07:32 AM
Ack! I know what you mean. A friend of mine had a cheapy computer with all stuff on the mobo and it started to screw up. Why do they gotta do that to us?
04-27-00, 09:50 PM
So, after about an hour or so of attaching one device, booting, and testing for errors, I've determined that this was a problem with the 20.5GB HDD that I installed to the system. The thing doesn't even sound like it's alive. Here goes another week of hassle with an online company. Thanks for all your input.
Powered by vBulletin® Version 4.2.0 Copyright © 2013 vBulletin Solutions, Inc. All rights reserved.