Looking in my now outdated "Upgrading and Repairing PC's" (Que) 6th Ed. ,
there is a long list of beep codes (about 50 or so).  Rather than copying
down the whole list for you, if you could repeat the error and be more
specific I may be able to translate it into these codes.

However, looking through the codes, all codes that appear to begin with 2
beeps seem to be related to RAM failure.  For instance, the beep code 2-4-3
indicates Bit 14 first 64K RAM failure.  Perhaps a bad memory module could
be your problem.  I can't tell if the codes distinguish between long and
short beeps.  I'll try to remember to see if there's an explanation in the
book when I get a chance.  You could probably find a copy at your local
bookstore (or library) and just turn to the back section with the technical
data and see if you can make sense of it yourself.

Hope this is of some help,

Bill Nussbaumer

At 11:24 PM 6/21/00 -0400, you wrote:
>Hi,
>
>Today, in the process of trying to help a friend with what seemed to be a
>bad
>NIC, the system died on me.
>
>The system is a Pentium 120 with an AMI Apollo II series 742 motherboard,
>running Win98.  I had replaced the suspected bad NIC and rebooted
>successfully, but had to abort the NIC driver installation, and shutdown
>when
>I realized that I needed to get the NIC model number to be sure I had the
>correct driver disk.
>
>On the next reboot attempt, however, the system started giving me BIOS
>error beeps:  2 short, followed by about 6 or 7 long beeps.  (Since I didn't
>have a listing of the beep codes handy, I didn't try too hard to get the
>exact
>number of long beeps.)
>
>The AMI web site lists beep error codes ranging from 1 to 11, with no
>mention
>of the initial 2 short beeps I'm getting.  Does anyone know if the initial 2
>short
>beeps are meaningful, or can they be ignored, for the purpose of determining
>the
>error from the table?
>
>I was very careful not to disturb any cable connections when installing the
>new
>NIC, but reopened the case to double-check for any problems.  I didn't see
>any, but this time noticed, when I tried to boot with the cover removed,
>that the
>CPU cooling fan wasn't spinning.
>
>So, I guess that puts a heat-damaged CPU high on the list of possibilities.
>However, I would still like to be able to correctly interpret the beep
>codes, so
>that I can be sure of where the problem is occurring.
>
>Any help is greatly appreciated.
>
>Thanks,
>    Barry

        The NOSPIN Group provides a monthly newsletter with great
       tips, information and ideas: NOSPIN-L, The NOSPIN Magazine
             Visit our web site to signup: http://nospin.com