Archived from groups: alt.comp.periphs.mainboard.asus (
More info?)
"Ron Reaugh" <rondashreaugh@att.net> wrote in
alt.comp.periphs.mainboard.asus:
> No, the first thing that happens most often when you call tech
> support is "do you have the latest BIOS?".
But why _do_ people call tech support? Exactly - when they have
_problems_.
And where did I state that you shouldn't flash BIOS if you have problems?
Exactly. _Nowhere_.
I said: "if it ain't broke, don't fix it."
I did _not_ say: "even when it's broke, don't _ever_ fix it".
> Get ahead of that curve and get the
> latest stuff BEFORE a problem comes up and then you wont wonder nor
> have to deal with flashing in the middle of some other problem.
If your system works properly on a daily basis, you won't experience
problems - why would you? After all you didn't change anything.
You're very convinced about the risk of BIOS flashing being "next to
ZERO" as an argument to flash, so logically that means you're convinced
that the risk you will run into problems with your current BIOS running
smoothly on an unchanged configuration will be considerably bigger than
that.
There's no fact supporting your statement. The vast majority of PC users
never flash their BIOS, and never run into hardware problems without
changing their systems. All they do is push the on/off button, push the
keys on the keyboard, and use their mouse. If they run into problems, it's
_software_ problems.
As soon as you start swapping components, you might decide to flash BIOS -
either before swapping, or after running into problems.
But that was not what I was talking about. As I stated clearly in my
original message:
>> And always ask yourself why you want to update BIOS. If it ain't broke,
>> don't fix it. Don't do it just because you _can_.
Flashing BIOS because you're changing configuration isn't "doing it
because you can". It's doing it because you're changing configuration and
have reasons to believe you might run into BIOS trouble.
> Giant meteroid impact could also result in unfortunate consequences.
But we were discussing BIOS flashing, not giant meteor impacts.
BIOS flashing is a very common occurance. Are you implying that there are
as many giant meteor impacts a year as BIOS flashes?
Are you suggesting that there are on a yearly basis more people
experiencing "unfortunate consequences" from giant meteor impacts than
there are people experiencing "unfortunate consequences" from BIOS flashes
thus making it a valid comparison?
Even if the score in this newsgroup alone (a few in the last few days) is
all there is, your statement about comparable risks has been proven
invalid already.
> Anyone who has the wherewithall to find
> his/her way to this NG should be told to always flash the latest BIOS.
Before you start repeating your beliefs like a mantra - and you have every
right to do that- also remember to carefully read what I said.
In your responses you talk about nothing but the need for BIOS flashes
because of people encountering problems, people calling tech support - how
interesting that might be - I wasn't talking about people with problems.
> That's been the rule of thumb amongst all the competent techies I
> know since 1980.
Well, on a sidenote: given the reliability of home computer systems
created and support by those "competent techies since 1980" that's hardly
a recommendation in my opinion.
--
CeeBee
"I don't know half of you
half as well as I should like;
and I like less than half of you
half as well as you deserve."