I can see both sides to the argument.
Intel has a business case to make, be it limiting their liability or maximizing their profitability, either way there are literally thousands of people whose livelihoods and jobs depend on Intel making the tough decisions needed to ensure the cash flow is healthy enough to keep paying those folks their salaries so they in turn can keep paying their mortgage and buy food and send their kids to school and pay taxes, etc.
On the other side, my absolute favorite rig build of all time was my dual-550MHz Celeron machine using the
Abit BP6 mobo.
So not only were you buying the dirt-cheap CPU version from Intel (their Celeron line), you were (1) overclocking them from 333MHz to 550MHz (w00t!), and (2) putting them into a silly cheap dual-socket mobo and running them in SMP like a boss!
Now then, Intel obviously took measures to prevent this from happening again but for a brief period in time enthusiasts could build quite the powerful and cheap box.
So I have to ask myself, how would I have felt in 1999 if Intel reached out through Microsoft with a microcode "update for security" that totally borked my BP6 duallie and operationally made it a single-socket mobo running at near-stock clockspeeds?
I'd be pissed. Disgusted and pissed.
So I can understand the emotional response that Intel is getting from this total dick move on their part.
It is all about the upsell. Intel really is no different than your local car dealership when it comes to their marketing and sales strategies.
Get your enthusiasts to pay a premium for the "K" chip (upsell #1), then make them pay a premium to get the right chipset as needed to actually use the unlocked features of your CPU (upsell #2), and don't forget to lay it on heavy and thick that they better buy that "extended warranty" performance tuning plan (upsell #3).
Upsell, upsell, upsell.
If your livelihood depends on Intel having a healthy robust fiscal outlook then you are pleased to see Intel doing what it needs to ensure you have continued job security, that is a very natural and understandable human desire. I've been there (not at Intel, but at others) and it sucked to see my management not minding the shop well enough to safeguard the financial future of employees like myself.
But for the rest of the consumer market, this stuff just creates friction as it pits consumers against the seller in an adversarial way and the history of commerce shows this always, always, results in a detrimental outcome for the business that is waging war on its customer.
Intel needs to find ways to add value to customers, not find ways to reduce or minimize the value it is adding to its customers. This move, while justified, is an act of war on its own customers and those are the kind of war wounds that people remember for a long long time.
My answer might actually surprise you.
BOTH the things that you mentioned, actually happened to me.
I also loved getting the Abit BP6's (best to put a tiny fan on its too hot chipset). I think I remember going to the computer shop (or it might have been mail order), and buying like 10 Celerons at a time, because they were so relatively cheap (about $50 in US then I guess, and about £50 here). Sometimes worrying about the exact batch numbers, for best overclocking.
The advantage of buying 10, is that I could find the best "overclockable" ones to match up on the wonderful Abit BP6 motherboards.
The overclocks then were amazing, and most of the extra clock speed, really gave extra speed.
Often the £50 bottom chip, could be overclocked by about 50%, approaching the performance of the top £450 Pentium chip.
And then of course, you could have 2 of them on each board, when most people ONLY had one core.
Now the 2nd twist of the tail.
The windows update that kills the overclock, unbelievably, happened to me.
(Ok, I'm partly lying here, but let me explain what happened).
Of course I had to make up multiple Abit BP6 computers, as they were so cheap, and I wanted many, many cores. I won't embarrass myself here and admit to how many systems I joined together to sort of make one super computer.
Now, this is where I got hit with the "windows update, computer killer" effect.
I think I had to use windows NT to support the dual processors (there may have been other options, I'm not sure, can't remember).
So I networked them all together.
But Microsoft (if you think I hate Intel (I DON'T), then meet me in real life, and ask me what I think of Microsoft, and Bill Gates, and you will know that I am NOT 100% delighted with them, lol) was programmed to detect that I was networking these computers together, without using a server version of their software.
So to my HUGE annoyment, it seemed to automatically "CRASH"/stop, after a certain limit of network traffic/computer numbers. I don't know the exact criterion Microsoft used, but much, much later, I found articles on the internet, which seemed to confirm my suspicions, of these artificial limits, to prevent saving money buying Microsoft server editions.
Why multi computers ?
I like doing all sorts of computing stuff, such as (at that time, potentially), extensive prime95 mersenne prime searches, complicated Chess puzzle analysis, running my own programs for long test runs, etc etc.
Computers were relatively slow then, so multiple computers (many were not only slow then, but most were single core, single cpu), made more sense, than it does these days, as you can get a 6 core, relatively high speed computer, which will handle most things, on its own.
Back on topic:
Yes, there are indeed multiple sides to this issue. On the one side Intel protecting its earnings, and on the other, fairness to consumers.
I think a few years or so, ago, Intel trialled Internet upgradeable processors. You buy a relatively cheap Intel cpu, and have it in your computer. You then choose a better Intel cpu, and buy an upgrade code from Intel, via the internet.
The special code then changes options in the cpu, which improves its performance, and features, etc.
People absolutely HATED the idea, and I think it was a complete and total flop, due to massive unpopularity with customers.
Anyway, thanks for the informative reply!
EDIT: It was a very long time ago. I can't clearly remember what I did, and did not run on the computers. So take the "what I ran" list as VERY approximate. It may have applied to computers I had before, or after the BP6 era, I'm not 100% sure.