joe_intel wrote:
However, we need to bear in mind that most of the information related to specific files or processes is not meant to be publicly available.
What?!
What the heck is not meant to be publicly available about things going on MY PC, processed by MY PROCESSOR(should i recall who i gave money to for owning it, or it's obvious?), stored on MY HDD and powered up by MY HACKEN ELECTRICITY?! Are you nuts or completely stupid saying that to people who already PAYED THEIR MONEY to your glorious corporation? Have you forgot, who is the source of it's existence, wealth and glory?
Incomes are not going as well as you wish at your xyIntel, huh? Let us guess, why... Well, one your lovely competitor DOES NOT INSTALL ANY NOT-MEANT-TO-BE-PUBLICLY-AVAILABLE-INFORMATION-SHITWARE as part of their CPU driver. And they surprisingly ask LESS MONEY for their processors, you know?
Maybe, people just DON'T WANT to pay for development, deployment, running and manual wiping out such useless shitware? Maybe, they want to pay for simple, fast and effective solutions of THEIR problems, but not YOURS? Have you catch the idea?
I've got a Intel-based system first time. I avoided buying Intel in the ages of RDRAM, Pentium IV, Core DUO architecture... And had a hope that after learning lesson with EM64/T Intel finally turned to customer with it's face...
A big NO-NO, man. The not-meant-to-be-publicly-available-shitware and dotNet-based-hardware-utilities(are your bosses too greedy to pay salary to WinAPI-qualified programmers or just your marketers are too stupid to know about WinAPI existence?)
Finally, it still turns to be a perfect idea - to purchase as less Intel, as possible!