VME Broken on AMD Ryzen

Re:VME Broken on AMD Ryzen by qb45 on Saturday May 13, 2017 @02:53AM (#14329826)

DOSBox can't run various firmware update and low-level hardware diagnostics tools that are still used in real life under DOS running on bare metal.

And Windows XP might be out of support but it still is used in some places too. And even if it wasn't, somebody could still think of using it as a test case to increase coverage. It would be extremely lame if some bug which crashes newer Windows in 0.1% of cases turned out to be trivially detectable in XP.

[ Parent | on HN ]

Re:VME Broken on AMD Ryzen by nikanj on Saturday May 13, 2017 @03:47AM (#14329941)

As we have learned today, the UK NHS is very much still on XP.

[ Parent | on HN ]

Re:VME Broken on AMD Ryzen by floatboth on Saturday May 13, 2017 @06:50AM (#14330314)

They probably aren't gonna buy Ryzens.

IIRC Ryzen and Kaby Lake were both announced with "only Windows 10 is going to be officially supported"…

[ Parent | on HN ]

Re:VME Broken on AMD Ryzen by Dylan16807 on Saturday May 13, 2017 @09:34AM (#14330872)

Ah but XP isn't supported on anything, and the update-blocking code doesn't affect you when there are no updates.

So no reason not to use Ryzen.

[ Parent | on HN ]

Re:VME Broken on AMD Ryzen by qb45 on Saturday May 13, 2017 @08:59AM (#14330720)

Yes, they will have to buy Intel to avoid this bug.

[ Parent | on HN ]

Re:VME Broken on AMD Ryzen by awordnot on Saturday May 13, 2017 @04:03AM (#14329979)

But this bug literally couldn't crash any modern OS as the feature is not available in 64-bit mode.

[ Parent | on HN ]