Linked by Thom Holwerda on Wed 18th May 2011 21:50 UTC, submitted by fran
Windows The ARM version of Windows 8 might have just become the most desired version of Windows in our hearts and minds. After us talking about legacy code and backwards compatibility in Windows for years now, an Intel senior vice president, Renee James, has just stated that Windows 8 on ARM will not have any form of compatibility for legacy applications whatsoever. Update: Microsoft has responded to Intel's claims. "Intel's statements during yesterday's Intel Investor Meeting about Microsoft's plans for the next version of Windows were factually inaccurate and unfortunately misleading," the company said, "From the first demonstrations of Windows on SoC, we have been clear about our goals and have emphasized that we are at the technology demonstration stage. As such, we have no further details or information at this time."
Thread beginning with comment 473621
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:


Does anyone know what a 'legacy' application is in this context? Is it just a binary that hasn't been targeted to ARM when it was compiled, or is it more than that - no support for older APIs or 32-bit mode?

In this context, I think "legacy" means Windows 7 applications (as opposed to native Windows 8 applications for either x86 or ARM).

- Brendan

Reply Parent Score: 2

PlunderBunny Member since:

Ok, but what is a Windows 7 application? Is it anything that runs on Windows 7 today? If I take a Win32 API exe targeted for x86, it won't run on Windows 8 ARM - fair enough because it's not built for that chip. But what if I use a new version of Visual Studio to target it to ARM and re-compile - is the resulting exe able to run on Windows 8 ARM?

If anyone knows of a document that provides a formal explanation of what legacy means w.r.t. Windows 8 on ARM, I'd like to see a link to it posted. As it stands, the statements being made so far by Intel are so vague as to be almost meaningless.

Reply Parent Score: 2

Adurbe Member since:

If I understand it correctly it will be similar to the OSX switch.

OS9 Apps did not run on OSX. There were some carbon (fatt) apps that were compiled to run on both but these tended to not be able to take advantage of functionality a native (cocoa) application could in OSX. CoreAudio for example.

I can see MS introducing something similar (fatt apps) as I doubt they want to force their whole dev community to rewrite their apps from scratch.

Reply Parent Score: 2