Microsoft Takes a Big Step Towards Putting Xbox Games On Windows (arstechnica.com)
An anonymous reader quotes a report from Ars Technica, written by Peter Bright: Ever since the first Xbox was released, an obvious question has been hanging in the air: Microsoft already owns one of the premier gaming platforms, the PC, and both the original Xbox and the current Xbox One are more or less PCs anyway, so when is Microsoft going to bring the two together and let us play Xbox games on Windows? With the new Windows 10 builds, it looks like the company is taking some big steps in that direction. Microsoft has put big chunks of the Xbox infrastructure into Windows 10. This starts right from the moment you download the game: it's coming from the Xbox distribution servers, not the usual ones for Store apps. The game package itself uses a format called .xvc, which is used for Xbox One games, and there are PowerShell commands to work with these .xvc files and install .xvc games. Microsoft Gaming Services includes portions of this Xbox infrastructure; it includes a couple of drivers ("Microsoft Gaming Filesystem Driver" and "Microsoft Gaming Install Filter Driver"), along with a number of libraries that provide Xbox APIs.
The last few Windows 10 preview builds have included some vague instructions from Microsoft to install a special edition of a game, State of Decay, and report any problems with the process. There are no problems with playing the game but, rather, problems with installing and launching it. The instructions didn't give any indication as to why or what to look for. Naturally, people have been taking a closer look to see what's special about State of Decay and figure out why Microsoft is having Windows Insiders test it. Nazmus Khandaker, Rafael Rivera, and the pseudonymous WalkingCat have been poking around both the special edition of State of Decay and a helper application called Microsoft Gaming Services that insider machines are running. Brad Sams wrote up his findings. [...] The State of Decay package does nonetheless contain PC-oriented elements. In particular, it tries to install and update the DirectX runtime during its setup. We the users don't seem to be at the stage of simply running Xbox games unmodified on our PCs, or at least, not yet. But it looks as if the groundwork is being laid. The strange preview of a 2020 Windows release looks like it contains even more of this infrastructure, with signs of a layer to support Xbox's Direct3D variant on PC. "Microsoft could go the whole hog and simply make a Windows 10 PC with a suitable hardware spec into an Xbox that can play any Xbox game," writes Bright, adding: "it might just be there as a simple option for developers to enable if they choose."
The last few Windows 10 preview builds have included some vague instructions from Microsoft to install a special edition of a game, State of Decay, and report any problems with the process. There are no problems with playing the game but, rather, problems with installing and launching it. The instructions didn't give any indication as to why or what to look for. Naturally, people have been taking a closer look to see what's special about State of Decay and figure out why Microsoft is having Windows Insiders test it. Nazmus Khandaker, Rafael Rivera, and the pseudonymous WalkingCat have been poking around both the special edition of State of Decay and a helper application called Microsoft Gaming Services that insider machines are running. Brad Sams wrote up his findings. [...] The State of Decay package does nonetheless contain PC-oriented elements. In particular, it tries to install and update the DirectX runtime during its setup. We the users don't seem to be at the stage of simply running Xbox games unmodified on our PCs, or at least, not yet. But it looks as if the groundwork is being laid. The strange preview of a 2020 Windows release looks like it contains even more of this infrastructure, with signs of a layer to support Xbox's Direct3D variant on PC. "Microsoft could go the whole hog and simply make a Windows 10 PC with a suitable hardware spec into an Xbox that can play any Xbox game," writes Bright, adding: "it might just be there as a simple option for developers to enable if they choose."
Yes, I know Windows used to come out for multiple architectures, but that hadn't happened since when, Windows NT 4?
The WindowsNT family has always supported multiple architectures in their current builds. Some people (me included) may say that X86 and AMD64 are different enough to be considered different architectures...
But, let's go with the conventional wisdom and count x86+AMD64 as a single architecture.
Pre-windows2000, there was support for x86, Alpha, MIPS and PPC.
In windows2000 they stopped supporting PPC and MIPS (early betas had PPC and MIPS support). There was a Win2000 port for Alpha that got Axed by DEC shortly after release. Also in Windows 2000 there was the port of NT server for Itanum (last windows to support Itanium was server 2008R2, released on 2009, with no end of support in sight).
As you clearly note, PowerPC was a supported architecture From NT 3.1 all the way to the Xbox360 (mantained until 2016).
2012 brought Windows Phone 8 and windows RT supporting ARM, support which continues to this day.
So, NT never has stopped supporting multiple architectures. But right now, the current builds support X86/AMD64 and ARM only.
*** Suerte a todos y Feliz dia!