On Wed, Jun 12, 2002 at 10:23:06AM +0600, K Hinze wrote: > On Tue, 11 Jun 2002 16:14:52 -0500 (CDT) > Michael Vieths <foeclan at visi.com> wrote: > > Err, if it's beeping, there's probably a good reason. Heat is a big > > one. > > > On Wed, 12 Jun 2002 07:33:03 -0500 > > "Robert P. Goldman" <rpgoldman at real-time.com> wrote: > > > It's a celeron 450 on an ASUS motherboard. > -------- > > > I just get one loooooonnnnnnnnnngggggggggg, solid beep. Sounds to > > > me like it's getting one beep, and then stuck on. > > Celeron chips pre-800MHz were 66MHz fsb. If your celeron is running at > 450MHz it MUST be overclocked, and consequently overheating. The one > long-beep typically is overheat alarm. Always has meant that for me. > Clock that chip back to a 66MHz fsb, and hopefully you haven't done > permanent damage. Let's see the popular chip to do this with was the Celeron 300a. 300Mhz / 66Mhz FSB = 4.5 clock multiplier 450Mhz / 4.5 clock multiplier = 100Mhz FSB 66Mhz -> 100Mhz is quite the stretch. Under carefully controlled conditions the system was actually bootable and maybe ran a benchmark before crashing. Definitely put the FSB back to 66Mhz. If the system keeps crashing, throw the chip out and get a new one. If the system is stable and you're still feeling slow, 75Mhz sometimes works. I have a Celeron 433 that I've run at 488 for a couple years without any trouble. But give the system a few months at 66Mhz before you try that. Nate P.S. Even with a Celeron 433, I don't feel the need for a faster box.