Cougar428 wrote to ARELOR <=-

I don't buy it. We are already giving the IT industry too much leeway
to produce crappy products. Let them own their failures.

I would be happy to let them own their failure, like I said AMD chips
operated at such a high frequency to one up the competition that they
did actually catch fire. I guess if you never had it happen to you,
you would not appreciate the chaos.

I supported Dell systems for a bunch of years. We started seeing
failures with video failures on one model of laptop. Turned out the
system put out enough heat to make a video component on the motherboard
fail. Dell's solution, rather than re-engineering the existing
motherboards and sending replacements, was to put our a BIOS update
that set the fan blowing at a much higher (and more annoying) speed. We
were large enough that they sent us a shipment of replacement systems
with re-engineered motherboards to swap some of them out, but we still
had a lot of systems blowing hot air.

Those were bad times for Dell customers. About the same time, Dell
Optiplexes began popping capacitors because of heat buildup. They got
really good at swapping out motherboards.



--- MultiMail/Win v0.52
þ Synchronet þ .: realitycheckbbs.org :: scientia potentia est :.

Codefenix wrote to phigan <=-

I thought it handled the jargon just fine, not dwelling on any
particular terms or concepts. It was more about the characters, their personalities, struggles, ambitions, and relationships between each
other.

I thought that the use of time jumps helped to solidify your connection
to the characters. At the end of season 4, you really felt like you'd
been along for a much longer ride with the characters that 4 years.

I really connected with the characters, probably because I lived
alongside some of those events.



--- MultiMail/Win v0.52
þ Synchronet þ .: realitycheckbbs.org :: scientia potentia est :.

Quoting Arelor to Cougar428 <=-

Re: Intel: Once mighty, now f
By: Cougar428 to ARELOR on Mon May 19 2025 08:41 am

I think the fix was to download the update and reboot the system. Of
course I may be wrong about how it was done, but you update drivers for
different hardware all the time. At every OS update.

First of all, we are not talking about a driver. We are talking about
a bellow OS operation so it is a serious affair even if it seems clicky-clicky.
Second, you may upgrade your drivers all month log, but how many
upgrades are designed to prevent your hardware from catching fire?
I check the changelogs of the stuff I run quite often and I must say updates aimed at preventing catastrophical failure exist in the realm
of astronomically unfrequent events.
Seriously, if I was running production on a specific CPU model and it caught fire mid-operation, and the Intel representative told me that
it is ok because it is not a hardware problem, that it only takes a
UEFI update to fix, I would shove a whole rack full of servers up that guy's ass.

I get your point. Just like AMD, they tried to one up the competition
and push the silicon too far past its limits. Intel is not the lone ranger
in this regard.

I understand your reasoning. People are angry they had problems with
their CPU/Mobo. However, that doesn't change the fact that it was a
micro code issue, not a hardware issue. Your whole line of reasoning is
subjective. Sometimes you have to be objective, step back and look at
the big picture. Yeah, your mad and angry that Intel hardware you paid
good money for screwed up your system. But the underlying cause was not
hardware, it was Intel trying to get their hardware to be better than
the competition. With the code.

Not assuming you had one of these, just stating.

You have a great day Arelor!


... Well, to be frank, I'd have to change my name.

___ Blue Wave/QWK v2.20
---
þ Synchronet þ CJ's Place, Orange City, FL - cjsplace.thruhere.net