Dela via

Don't miss the Longhorn Q&A with Microsoft's Chris Jones

  • Artikel

It can be found here and is part II of a two-part interview. Part I appeared on 17 June.

Here the important part about 64-bit Longhorn:
"Q: Are there any 32-bit parts in the current 64-bit Windows core? Which parts, if so? Will you have 32-bit parts in Longhorn core? Will there be a 32-bit version of Longhorn?

A: For compatibility, the WoW, or Window on Window system has 32-bit components, so when running in 64-bit, you actually need to deliver both 32- and 64-bit components because the APIs get dumped. We will continue to have 32-bit parts in the Windows core for two reasons, one to support compatibility, and two, to support legacy applications. For example, if an application needs the 32-bit MAPI.DLL for mail, it needs that MAPI.DLL to run normally. Another example is where there are legacy parts of the system, where you have end of life components, where they're just not going to be moved to 64-bit, they'll only ever run in a 32-bit environment. However, there should be no reason for an ISV, a manufacturer or customer to be running in 32-bit if the right device support is available for 64-bit. And yes, there will be a 32-bit version of Longhorn. Every day in our build-lab, we build three versions of Longhorn, x86, x64 and Itanium systems."

BTW, couldn't find part I anymore ...

Comments