I still have one of these running Win98se for my sister in law. Have you check Hardware monitor setup in bios? There are 4 choices, they should be set to [ignore] for testing puposes.
I don't know if this helps but I found this on google;
It's the beeping of that hideous heart! [02/21/2000]
Wesley Rast asks:
Ok, here's the deal:
I've made the decision (or mistake, depending on how you look at it) to start using windows 2k at work. My system consists of a 700mhz Athlon on an Asus K7M mainboard with 386mb of Ram and a Creative Labs DDR GeForce in the AGP slot. Ever since I built the system, the pc speaker's been blaring a continuous siren-like series of beeps no matter what I do (reseat all the components, change out memory, switch video cards, you name it.) Nowhere on Asus's site is a reference to this type of beep error-code. In a fit of total frustration, i simply unplugged the pc speaker and tried to boot the thing up. It worked perfectly...for a while. It locked up after about an hour of use and wouldn't respond to ctrl-alt-del, so I had to cold-boot it. I've been looking for a solution to this one for a loooong time now. Asus has not responded to my emails and I'm at my wit's-end. Is there any help you could offer me on this one?
Ator responds:
Well, it depends on what you mean by continuous. In other words, how long have you waited before shutting it off? The Asus K7M uses an AMI BIOS. Each BIOS, as you probably know, has various error codes differentiated by the number (and sometimes length) of a series of beeps. The AMI error codes go all the way up to 11:
# of beeps Error
1 Refresh failure
2 Parity error
3 Base 64K memory failure
4 Timer not operational
5 Processor error
6 8042 - gate A20 failure
7 Processor exception interrupt error
8 Display memory read/write failure
9 ROM checksum error
10 CMOS shutdown register read/write error
11 Cache memory bad
11 beeps can be an awful long time to wait, especially when your computer is screaming at you. However, having said that, I don't think the error codes are your problem. The reason why is that, of these codes, all but 8 represent fatal errors, and since you mentioned already swapping video cards, that's not likely to be the problem.
The K7M, like many motherboards these days, has hardware monitoring capabilities. In the case of the K7M, it's one of the popular Winbond chips, the W83782D to be specific. This particular setup monitors voltage, temperature, and any fans plugged into the motherboard. Each of these areas of monitoring can be assigned an error threshold, beyond which it will sound an alarm. For details, see page 68 of your K7M manual. This alarm is what you are hearing. Also note that the intrusion detection function can set off an alarm (thanks to all who wrote in with that tip).
Now, if these errors are false ones (e.g., a fan monitor is looking for a fan where none is plugged into the motherboard, or expecting a higher RPM fan than it's getting), you can set that particular flag in your BIOS to [Ignore]. You did more or less the same thing by unplugging your speaker. Given the fact that your system locked up afterwards, however, the error wasn't a false one. If you can stand to ignore the beeping, boot up the machine and go into the BIOS and see which setting might be tripping the alarm. Alternatively, you could snag yourself a program such as Motherboard Monitor, which will allow you to see the Winbond readings from within Windows. Given your description of the crash, I am inclined to suspect that you are having some temperature problems, and you may need to improve the cooling in your case.
Facebook
Twitter