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.
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.
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.
After 4 seasons, they'd done a lot of character building across the
board, and with the time jumps between seasons, you really feel like
there's a lot of history between them all. Well done.
I'd like to see a season 5 with a time jump to now, but it might be anticlimactic. I really just want to know they ended up alright.
--- MultiMail/Win v0.52
Synchronet .: realitycheckbbs.org :: scientia potentia est :.
Quoting Poindexter Fortran to Cougar428 <=-
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.
Cougar428 wrote to POINDEXTER FORTRAN <=-
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.
I remember replacing boards in quite a few GX280's.
Sounds like you were at a larger shop than me. I worked for
Computerland and would do factory service calls.
Sysop: | BrokenMind |
---|---|
Location: | Central Pa |
Users: | 71 |
Nodes: | 4 (0 / 4) |
Uptime: | 37:23:51 |
Calls: | 29 |
Files: | 6,263 |
D/L today: |
1 files (84K bytes) |
Messages: | 23,282 |