On Nov 27, 3:32 pm, Michael Black <
et...@ncf.ca> wrote:
> On Tue, 27 Nov 2012, Paul wrote:
> >> Your damn battery is dead in your PC!!!!
>
> > In a typical PC, a CR2032 coin cell battery, maintains BIOS settings
> > and the real time clock. If the CR2032 is discharged, there is
> > nothing to maintain accurate time when the computer is unplugged.
> > If you don't want to replace the coin cell battery, then the
> > time settings must be re-entered, on each power-up of the PC.
> > Enter BIOS and set the clock, save, exit, boot.
>
> It's more than that. All the BIOS settings are in the RAM that is battery
> backed up. In the old days, you'd have to enter details of the hard drive
> (or select from a menu) and that would go every time the computer forgot.
> Same with boot sequence and all that.
>
> With a dead battery, the cluelss might believe the computer is broken.
I just bought a BiosedStar MB a couple months ago and returned it
because it wouldn't hold BIOS settings. Who wants to turn on a
computer that flashes in your face: Warning! Warning! Will Rogers --
Danger Due to CMOS MisMatch!
It wasn't a 2032 but close enough (according to WIKI) to open -very
first thing- the computer next to it, handy dandy like, and pull its
2032 for a substitute.
Some -- not many, yet some nevertheless do have BIOS issues. Had
another one, I sold identified for such, that had a knack for dropping
CPU multipliers to x4 instead of x12, were the CPU properly picked up.
I flash them, too, first thing as a manner of course. Although the
replacement for the BiosedStar, a nice little P4 Gigabytle, I did a
revisionary flash to a BIOS dated prior to what was provided. Seemed
different. How many people do you know that buy a new MB and put an
old BIOS on it for no particular reason? It's not at all like I
planned it.
(Actually, it had at USB slotted entry BIOS progressions, that, in
order turn on USB S3, a normal series of recognizable USB settings had
to be first engaged for an on state. However, I did, again without
reason, leave on the S3, and that appeared caused me some grief
because the computer wouldn't work right, had streaming/speed issues
with USB and HDs, until S3 was disengaged. Of course not nearly as
fast as this is transpiring. Hardly that. I suspect I may in the
physics of anomalistic retaliation have been spirited to a rebuttal in
form of a former BIOS revision. But, I've still got that S3 in
there. Do you know what in hell it is?)