景色文章名列前茅50 景色錄影景色軟景色幫助

偷看入未來遺產兼容性在窗口

窗口3.1 能力跑十年老應用在窗口最新的發行幾乎成為了段落禮拜式。多數人同意軟件逆兼容性在窗口容易地是其中一個重要因素為它的成功。然而與每發行，微軟開掘自己深和深入支持這個坑，當軟件的廣度和深度增長指數地。那麼一些非常預言它最終將破壞窗口，如果它已經沒有。

一個最近出版專利申請，「環境為在當地人執行遺產應用操作系統」為那些您在家演奏，歸檔在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.