Not bad considering how hot the GPU was running. I will be tackling it all next week, but, if I did my maths correctly it should all just literally slot in and I shouldn't have to use any new hose. The rad is the same thickness, same width and the same spacing between the G 1/4 ports. All I need to do is flush it all with distilled vinegar then I can build.

Can you do a video and put it on Youtube?

500 word video?

That's the best of both worlds; a video showing someone typing their opinions out in a Notepad window.

I think I've seen a few videos *exactly* like that

Yeah me too haha. I think they obviously don't have confidence in their voice. They still go too fast

To be fair, whenever I've seen it done it's been quick and dirty stuff rather than lengthy lectures so it's probably someone that doesn't have a mic but can grab screen recording software easily. I've never seen anyone use that technique to present a lot of text, as that would be properly stupid.

It's annoying when you are following something verbatim and they open something by mistake lmao. Straight back to Google....

A *competent* CPU engineer would fix this by making sure speculation doesn't happen across protection domains. Maybe even a L1 I$ that is keyed by CPL.

I think somebody inside of Intel needs to really take a long hard look at their CPU's, and actually admit that they have issues instead of writing PR blurbs that say that everything works as designed.

.. and that really means that all these mitigation patches should be written with "not all CPU's are crap" in mind.

Or is Intel basically saying "we are committed to selling you shit forever and ever, and never fixing anything"?

Sounds like your upgrade just moved up the schedule!

I did have this all explained to me by a guy who writes for CPC (Gareth Halfacree).

I remember him from some of the uk.comp newsgroups 15+ years back. A very nice chap indeed.

A description of Retpoline, a Google-developed binary patching technique which protects against the bugs and claims to have almost no performance penalty (I have no insider information here, I’m quoting the doc): https://security.googleblog.com/2018/01 ... cpu_4.html

Re: Meltdown/Spectre

Maybe I'm just an old-fashioned arse, but the idea of the CPU running code that it hasn't (yet) been explicitly told to run is horrifying to me.

Maybe I'm just an old-fashioned arse, but the idea of the CPU running code that it hasn't (yet) been explicitly told to run is horrifying to me.

It'd be fine if Intel didn't design their CPU architecture as Linus Torvalds gracefully phrased it, like 'shit'.

It'd be fine if Intel didn't design their CPU architecture as Linus Torvalds gracefully phrased it, like 'shit'.

Let us note that Mr Torvalds has spent the last 20 years writing kernel code to take advantage of the performance gains provided by that exact CPU architecture and hasn't had cause to complain until now.

Let us note that Mr Torvalds has spent the last 20 years writing kernel code to take advantage of the performance gains provided by that exact CPU architecture and hasn't had cause to complain until now.

Maybe he was running with the assumption that Intel's CPU would appropriately protect restricted kernel memory areas?
.

Meltdown / Spectre like flaws on the Xbox 360 chips -found and resolved a long time ago (interesting read)

https://randomascii.wordpress.com/2018/ ... -xbox-360/

That's almost as good as when Gaywood posted about it!

Here is the summary of what we have found so far:

With Windows 10 on newer silicon (2016-era PCs with Skylake, Kabylake or newer CPU), benchmarks show single-digit slowdowns, but we don’t expect most users to notice a change because these percentages are reflected in milliseconds.

With Windows 10 on older silicon (2015-era PCs with Haswell or older CPU), some benchmarks show more significant slowdowns, and we expect that some users will notice a decrease in system performance.

With Windows 8 and Windows 7 on older silicon (2015-era PCs with Haswell or older CPU), we expect most users to notice a decrease in system performance.

Windows Server on any silicon, especially in any IO-intensive application, shows a more significant performance impact when you enable the mitigations to isolate untrusted code within a Windows Server instance. This is why you want to be careful to evaluate the risk of untrusted code for each Windows Server instance, and balance the security versus performance tradeoff for your environment.

Does it have jumpers?

Pro tip, the software is balls, and none of the other lighting options look as nice as the default, so just leave it as it is out of the box.

This is making me laugh, for some inexplicable reason