It's over, Ryzen is finished. http://www.os2museum.com/

>>60355417
well when you have to mail in rebates to afford a computer of course your going to have some compromises

>running 16bit applications in DOS boxes

Lol
Next you'll be telling me 8080 compatibility doesn't work

>>60355417
This looks like it's implemented in microcode, so a microcode update won't have issues fixing this.
At least it doesn't need new silicon like TSX

>only 32-bit OSes are affected, and only when running 16-bit real-mode code
fringest of fringe cases.

>>60355417
>windows server 2003 and windows xp the OS'es affected
LOL, good bait OP

>>60355753
Doesn't Ryzen officially only support Windows 10?

>>60355785
>OSes that aren't even supported officially by the Ryzen platform
Yea, AMD sure got blown the fuck out OP.

>>60355753
came here to post this

>>60355807
I think so. Literally who gives a shit about XP that's going to be buying a new CPU

I'm glad my life isn't so empty that I'm emotionally invested in which processor manufacturer "wins."

I wonder if you'll make the same thread when Itanic v2 in 2021 doesn't run your favorite game.

>>60355910
>>>/v/

>mfw was thinking about investing in AMD
>mfw Skylake coming out with 6core/12thread and 8core/16thread

Thank fucking god I didn't. I knew AMD wouldn't get their assholes annihilated again.

Everyone is going to jump ship or wait for the real reputable company Intel to create what they've been using for years.

AMD has no hope, there is no point in making competing processor technology. The norm has already been established and for the good of humanity and technological advancement, we have build on a common platform, not different ones. They need to be unified so we don't have issues like the one in the OP.

>>60355417
Time to move on, grandpa. Retrocompatibility is dragging progress down.

>>60356071
>[shilling intensify]

>>60356071
I give this bait a -5 out of 10.

>>60356147
>>60356148

>t. Ryzen owners.

>>60356408
>t. housefire corelet

>>60356071
Competition is bad only buy Intel. Fuck AMD

>>60356071
Could you please stop shitting the threads? Like, really. Stop.

File: yandere 10-tan.jpg (225KB, 800x555px) Image search: [Google]

225KB, 800x555px

>>60355417
That's waht you get for not using latest greatest cutest OS

>>60356486

AMD is a shit company with a low amount of resources and as a result has been dominated in the marketplace for CPUs and is an untrustworthy company.

Intel is a good company with large amount of resources that is trusted by the public because they deliver CPUs that work well.

Do the math, Ryzen will not work out long term. The resources to do the driver updates will fade, so will support. AMD will eventually be bought out or declare bankruptcy and the Ryzen platform will die.

Good luck.

>>60356726
It's probably some kind of disease at this point.

>>60356726
Amazing job, anon; here's your (You) as a reward. Further compensation will be rewarded once you have met the required amount of Intel approved posts.

>>60355417
>Almost immediately since the Ryzen CPUs became available in March 2017, there have been various complaints about problems with Windows XP in a VM and with running 16-bit applications in DOS boxes in Windows VMs.

>How did AMD miss it? Because only 32-bit OSes are affected, and only when running 16-bit real-mode code. Except with Windows XP and Server 2003 it’s much worse and they may not even boot.

I don't think I could care any less than I do right now.

>>60356726
FUCK AMD

>>60356071

THEY'RE DONE!

File: 1488570026148.jpg (157KB, 724x802px) Image search: [Google]

157KB, 724x802px

>>60356726

what a surprise, another fucking kike in this thread

Such hate, do you think AMD sodomized his cat or something?

AMD = Black & Decker
Intel = Festool

>>60356818
They sodomized his Itanium.

>>60355848
Those who virtualize shit might need it.

Of course it's solveable with microcode.

>>60355785
how can you even install a os that old on modern hardware? theres no drivers for anything older that win7 available to new hardware.

>>60355807
wait no linux?

>>60356920
Was talking strictly Windows, Linux supports everything under the sun.

>>60355807
>>60356920
AMD released Zen patches for Linux before it even launched.

>>60355417
whatever. im still going to buy an amd cpu when i upgrade from i5 2500k

>using windows to virtualize windows
if you're gonna be running bloat you might as well skim the fat

>>60356959
Oh. Good to know.

Lol, at least it can multiply correctly.

Intel managed to fuck that one up.

>>60356920
full support as you'd expect, it would happen even if they didn't help though. No weird hyper threading issues as long as you're running a somewhat up to date kernel.

>>60356962
AMD doesn't have an upgrade from an i5 2500k though.

Oh I get it lol.

>>60357137
i will only do it because the current matx board does not have enough ports. the cpu is still more than enough for me.

File: 1490472047431.jpg (599KB, 1312x1740px) Image search: [Google]

599KB, 1312x1740px

>>60357137
Don't you have to go somewhere where your presence isn't shameful?

>>60356071
>not buying AMD stock when it was in the upper 9's
Look where it's at now genius

>>60356920
linux is unrelated to the issue, as it doesn't run 16bit DOS applications, but of course linux is officially supported.

>>60357429
dosbox and virtualbox runs on linux too

>>60357429
yes and we have qemu to emulate this shit. It's not like some 16 bit application is realistically going to use much resources.

VMWare on 64-bit host would be good enough for 16-bit OS.

Looks like a way less priority fix than the FMA bug.

>>60357515
Wouldn't they be running in protected mode and not affected by this bug though?

>>60357215
This should not be forgotten at any point. Shills need to learn their place.

File: LRM_EXPORT_20170411_145818.jpg (1MB, 1293x1730px) Image search: [Google]

1MB, 1293x1730px

>>60357137
Kill yourself you perma-BTFO'd tripfaggot

>>60355617
>>running 16bit applications in DOS boxes
This is actually an issue in corporate environments. It isnt unusual to PXE boot devices to dump an image to them, and the PXE boot images may run various forms of DOS.

>>60355785
32 bit OSes, and many PXE boot images will be 32 bit OSes for compatibility with legacy hardware.

>>60358868
Good point, but well, considering we're looking at a microcode update for a fix and not a new stepping it'll probably be fixed, if it hasn't already.

>>60359076
>have to apply a update before you can image a system out of the box
this isnt going to go over well with large corporate IT departments evaluating new desktops to deploy. If it is a microcode update corporate IT probably wont want to touch these for at least 6 months to make sure all the old stock is out of the distribution channels.

>>60359152
It's a good thing they haven't started shipping these things yet.

>>60355807
Ryzen is AMD64 and should (ideally) run whatever x86/amd64 code you throw at it. No idea why a CPU would limit what OS you can run.

AMD support linux and have released ryzen chipset drivers for Win 7/8.
Microsoft support nothing but Win 10.

>>60355417
Intlel shills are so desperate it's delicious.