景色文章名列前茅50 景色录影景色软景色帮助

偷看入未来遗产兼容性在窗口

窗口3.1 能力跑十年老应用在窗口最新的发行几乎成为了段落礼拜式。多数人同意软件逆兼容性在窗口容易地是其中一个重要因素为它的成功。然而与每发行，微软开掘自己深和深入支持这个坑，当软件的广度和深度增长指数地。那么一些非常预言它最终将破坏窗口，如果它已经没有。

A recently published patent application, “Environment For Executing Legacy Applications On A Native Operating System”为那些您在家演奏，归档在4月2007年由微软的Hoi Vo和Samer Arafeh (谁在窗口仁运作)显露有些细节怎样他们威力 (和重点可能，因为专利是正义词在一张纸)容纳和巨大改进软件兼容性在窗口未来发行。

如所描述在专利，遗产应用支持的问题在双在(DLLs和EXEs)。当操作系统更新，系统双改变。更旧的系统调用、收回和例外可能不根本存在于新操作系统，也许存在到某一程度或也许引起供选择反应。其中任一，其中可能击毁havok在依靠这些双的遗产应用。

当前有二种常规解答到问题。中的每一与他们的各自好处和缺点。

定刀片

一个使用对“定刀片的”用途。隐喻地讲话，它是基本上稠粘的磁带在边缘附近确定事不掉下来。技术上，它是正在进行中应用的一个custom-written补丁，当遗产应用被装载时和在遗产应用和当地系统双之间坐。微软据报道写了数以万计定刀片为窗口景色和是仍然写. 上部是定刀片是相对地容易实施，但必须引起定刀片在它根本不很好称每应用由应用依据手段的a。

第二种解答采取好处虚拟化技术。通过主持遗产OS虚拟机，遗产应用其中任一不会知道其中任一改善。虚拟化提议最大应用支持，但在重的表现费用。硬件支持也是原始，使它难分享资源象3D例如图表。它也要求用户能安装遗产操作系统的每个版本。

应用兼容性模块

提出的解答在一些方面采取两个的最佳的位。 It works first by detecting if the application was written for the native operating system. If not, it will load the application with its respective legacy system binaries. The accommodate the difference in system calls between the legacy binaries and native kernel, an Application Compatibility Module is placed in between to act as a translator for these calls. In certain cases where a comparative native system calls may not exist at all, the ACM could also be smart enough to provide the same functionality as the missing system call.

Hypothetically speaking, if the system detected an XP application it would load the XP system binaries (ex. system32_xp) and then a XP-to-WinNext compatibility module.

The benefit of this solution is it offers much broader application compatibility with relatively low investment on Microsoft’s behalf on the scale of per-application - they will only have to write a ACM for each legacy system they wish to support. Legacy applications will also be able to take full advantage of the system resources as a native application, because there is no emulation involved.

Notable Windows on Windows - the compatibility system used to provide 16-bit on 32-bit systems support and 32-bit on 64-bit systems support uses a similar concept.

One of the biggest gripes from most Windows enthusiasts has been the bloat legacy compatibility forces into Windows. Whilst this patent doesn’t specifically mention so, I presume such ACMs are modular and can be installed and removed on demand. For example, if you need to run Windows Vista applications in future versions of Windows, you will only download and install the Vista ACM Pack (with Vista binaries) for that operating system. Those who do not require legacy support will then be not required to install any ACMs.

Thinking about it, it could become a business model to sell ACMs separately to Windows - reducing the overall cost of Windows and charging a tiered price for legacy support. A cheaper and less bloated Windows, wouldn’t that be nice.