{"id":2332,"date":"2018-09-16T11:26:23","date_gmt":"2018-09-16T03:26:23","guid":{"rendered":"https:\/\/www.aoisnow.net\/blog\/?p=2332"},"modified":"2018-09-16T11:26:23","modified_gmt":"2018-09-16T03:26:23","slug":"tont-41663-%e3%80%8ent%e3%80%8f%e6%9c%80%e5%88%9d%e4%bb%a3%e8%a1%a8%e7%9a%84%e5%90%ab%e4%b9%89%e6%98%af%e4%bb%80%e4%b9%88%ef%bc%9f","status":"publish","type":"post","link":"https:\/\/www.aoisnow.net\/blog\/archives\/2332","title":{"rendered":"TONT 41663 \u300eNT\u300f\u6700\u521d\u4ee3\u8868\u7684\u542b\u4e49\u662f\u4ec0\u4e48\uff1f"},"content":{"rendered":"

\u539f\u6587\u94fe\u63a5\uff1ahttps:\/\/blogs.msdn.microsoft.com\/oldnewthing\/20031201-00\/?p=41663<\/a><\/p>\n

Finally, the real story of what the letters “N” and “T” originally stood for is now public<\/a>, so I can stop being coy about it. (Via LockerGnome<\/a>.)<\/p>\n

\u7ec8\u4e8e\uff0c\u90a3\u4e24\u4e2a\u5b57\u6bcd\u300eN\u300f\u548c\u300eT\u300f\u6240\u4ee3\u8868\u542b\u4e49\u7684\u771f\u5b9e\u6545\u4e8b\u73b0\u5df2\u516c\u4e4b\u4e8e\u4f17\uff0c\u6211\u4e5f\u4e0d\u7528\u518d\u626d\u626d\u634f\u634f\u4e0d\u613f\u8bf4\u4e86\u3002\uff08via LockerGnome\uff09<\/p>\n

\u8bd1\u8005\u8bed\uff1a<\/p>\n

\uff081\uff09\u539f\u6587\u6240\u6307\u5411\u7684\u4e24\u4e2a\u94fe\u63a5\u5df2\u5931\u6548\uff0c\u6545\u8bd1\u6587\u4e2d\u672a\u518d\u91cd\u590d\u5236\u9020\u65e0\u6548\u6570\u636e\uff1b<\/p>\n

\uff082\uff09\u672c\u7bc7\u5185\u6587\u4e3a\u6240\u6307\u5411\u6587\u7ae0\u7684\u5168\u6587\u53ca\u8bd1\u6587\uff0c\u5171\u5206\u4e09\u7bc7\uff0c\u7531\u4e8e\u6587\u7ae0\u957f\u5ea6\u53ca\u7a7a\u95f2\u65f6\u95f4\u5173\u7cfb\uff0c\u5c06\u5728\u672c\u7bc7\u4e2d\u8fdb\u884c\u4e0d\u65ad\u66f4\u65b0\uff0c\u76f4\u81f3\u5168\u90e8\u7ffb\u8bd1\u5b8c\u4e3a\u6b62\u3002<\/p>\n

\uff083\uff09\u5185\u6587\u7ffb\u8bd1\u8fdb\u5ea6\uff1aPart 1\uff08\u7ffb\u8bd1\u5b8c\u6210\uff09\u3001Part 2\uff08\u8fdb\u884c\u4e2d\uff09\u3001Part 3\uff08\u672a\u5f00\u59cb\uff09<\/p>\n

<\/p>\n

Windows Server 2003: The Road To Gold, Part One: The Early Years<\/strong><\/a><\/p>\n

Windows Server 2003\uff1a\u9ec4\u91d1\u4e4b\u8def\uff0c\u7b2c\u4e00\u7bc7\uff1a\u6700\u521d\u90a3\u4e9b\u5e74<\/strong><\/p>\n

Paul Thurrott | Jan 24, 2003\uff082003\u5e741\u670824\u65e5\uff09<\/p>\n

During a recent trip to Microsoft’s Redmond campus with Janet Robbins and Mike Otey, we had the chance the sit down and chat with two of the most notable figures in the history of Windows, Mark Lucovsky and David Thompson. For those of you not familiar with the early days of Windows NT, known then simply as NT, both Lucovsky and Thompson played key roles in the development of this important software project. Mark Lucovsky, Distinguished Engineer and Windows Server Architect at Microsoft, joined the company with the original wave of ex-Digital Equipment Corporation (DEC) employees that accompanied NT architect Dave Cutler. Known primarily for his unusual ability to grok how the thousands of components in NT work together, Lucovsky is widely hailed for his technical acumen and his early efforts to change NT from an OS\/2-based system to one that ran 32-bit Windows applications. David Thompson, Vice President of the Windows Server Product Group, joined Microsoft in 1990 and led an advanced development group in the company’s LAN Manager project before joining the NT team later that year. There, Thompson guided the development of NT’s networking subsystem, ensuring that the product would work not just with Microsoft’s products but with the outside world.<\/p>\n

\u6700\u8fd1\uff0c\u5728\u4e00\u6b21\u4e0eJanet Robbins\u548cMike Otey\u4e00\u540c\u524d\u5f80\u5fae\u8f6fRedmond\u603b\u90e8\u56ed\u533a\u7684\u884c\u7a0b\u4e2d\uff0c\u6211\u4eec\u6709\u673a\u4f1a\u5750\u4e0b\u6765\u4e0e\u4e24\u4f4d\u5728Windows\u7814\u53d1\u5386\u53f2\u4e0a\u6709\u4e3e\u8db3\u8f7b\u91cd\u5730\u4f4d\u7684\u4e24\u4f4d\u5927\u4eba\u7269\u3001Mark Lucovsky\u548cDavid Thompson\u8fdb\u884c\u4e86\u5bf9\u8bdd\u3002\u5bf9\u4e8e\u4e0d\u592a\u4e86\u89e3Windows NT\uff08\u6216\u7b80\u79f0NT\uff09\u65e9\u671f\u5386\u53f2\u7684\u5404\u4f4d\u89e3\u91ca\u4e00\u4e0b\u7684\u8bdd\uff0cLucovsky\u548cThompson\u5728\u8fd9\u4e2a\u5177\u6709\u91cd\u8981\u610f\u4e49\u7684\u8f6f\u4ef6\u9879\u76ee\u7684\u5f00\u53d1\u8fc7\u7a0b\u4e2d\u90fd\u8d77\u5230\u4e86\u5173\u952e\u4f5c\u7528\u3002Mark Lucovsky\u662f\u5fae\u8f6f\u516c\u53f8\u7684\u4e00\u540d\u5353\u8d8a\u7684\u5de5\u7a0b\u5e08\u548cWindows Server\u67b6\u6784\u5e08\uff0c\u4e0e\u524d\u8fea\u5409\u591a\u516c\u53f8\uff08Digital Equipment Corpotation, DEC\uff09\u7684\u96c7\u5458\u4eec\u4e00\u8d77\u52a0\u5165\u5fae\u8f6f\u516c\u53f8\uff0c\u968fNT\u67b6\u6784\u5e08Dave Culter\u4e00\u8d77\u5de5\u4f5c\u3002\u6709\u9274\u4e8e\u5176\u5bf9NT\u7cfb\u7edf\u4e2d\u4e0a\u5343\u4e2a\u7ec4\u4ef6\u534f\u540c\u5de5\u4f5c\u539f\u7406\u4e4b\u5f02\u4e4e\u5e38\u4eba\u7684\u7406\u89e3\uff0cLucosky\u56e0\u5176\u6280\u672f\u65b9\u9762\u7684\u5929\u624d\u3001\u53ca\u5176\u65e9\u671f\u5c06NT\u7cfb\u7edf\u4ece\u4e00\u4e2aOS\/2\u4e3a\u57fa\u7840\u7684\u7cfb\u7edf\u8f6c\u5316\u4e3a\u8fd0\u884c32\u4f4dWindows\u5e94\u7528\u7a0b\u5e8f\u7684\u52aa\u529b\u800c\u5907\u53d7\u8d5e\u8bb8\u3002David Thompson\uff0cWindows Server\u4ea7\u54c1\u7ec4\u526f\u4e3b\u4efb\uff0c\u4e8e1990\u5e74\u52a0\u5165\u5fae\u8f6f\u516c\u53f8\uff0c\u8d1f\u8d23\u5e26\u9886\u4e00\u652f\u7ecf\u9a8c\u4e30\u5bcc\u7684\u56e2\u961f\u7814\u53d1LAN Manager\u9879\u76ee\uff0c\u5e76\u5728\u5f53\u5e74\u665a\u4e9b\u65f6\u5019\u52a0\u5165\u4e86NT\u9879\u76ee\u7ec4\u3002\u5728\u90a3\u91cc\uff0cThompson\u5e26\u9886\u5f00\u53d1\u4eba\u5458\u4eec\u7814\u53d1\u4e86NT\u7684\u7f51\u7edc\u5b50\u7cfb\u7edf\uff0c\u786e\u4fdd\u6574\u4e2a\u4ea7\u54c1\u4e0d\u4ec5\u4e0e\u5fae\u8f6f\u81ea\u5df1\u7684\u4ea7\u54c1\u914d\u5408\u826f\u597d\uff0c\u8fd8\u4e0e\u6574\u4e2a\u4e16\u754c\u5176\u5b83\u7684\u8f6f\u4ef6\u534f\u4f5c\u987a\u5229\u3002<\/p>\n

Here’s how it all began.<\/p>\n

\u4ee5\u4e0b\u662f\u6545\u4e8b\u7684\u5f00\u7aef\u3002<\/p>\n

The NT team arrives at Microsoft<\/strong><\/p>\n

NT\u56e2\u961f\u5728\u5fae\u8f6f\u7684\u53d1\u7aef<\/strong><\/p>\n

“We came together as a group in November 1988,” Lucovsky told us, noting that the first task for the NT team was to get development machines, which were [then] top-of-the-line 25 MHz 386 PCs with 110 MB hard drives and 13 MB of RAM. “They were ungodly expensive,” he said, laughing. The first two weeks of development were fairly uneventful, with the NT team using Microsoft Word to create the original design documentation.<\/p>\n

\u300e\u6211\u4eec\u57281988\u5e7411\u6708\u65f6\u7ec4\u6210\u4e86\u8fd9\u4e2a\u56e2\u961f\uff0c\u300fLucovsky\u8bf4\u9053\uff0c\u63d0\u53caNT\u56e2\u961f\u7684\u7b2c\u4e00\u9879\u4efb\u52a1\u662f\u8d2d\u7f6e\u5f00\u53d1\u673a\uff0c\u5176\u89c4\u683c\uff08\u5728\u5f53\u65f6\uff09\u662f\u9876\u5c16\u768425Mhz 386 PC\uff0c\u5e26110MB\u7684\u786c\u76d8\u548c13MB\u5185\u5b58\u3002\u300e\u90a3\u4e9b\u673a\u5668\u7b80\u76f4\u8d35\u4e0a\u5929\u4e86\u300f\uff0c\u4ed6\u7b11\u7740\u8bf4\u3002\u5f00\u53d1\u8fc7\u7a0b\u7684\u6700\u521d\u4e24\u5468\u5e73\u6de1\u65e0\u5947\uff0cNT\u56e2\u961f\u7684\u6210\u5458\u4eec\u7528Microsoft Word\u64b0\u5199\u7740\u6700\u521d\u7684\u8bbe\u8ba1\u6587\u6863\u3002<\/p>\n

Finally, it was time to start writing some code. “We checked the first code pieces in around mid-December 1988,” Lucovsky said, “and had a very basic system kind of booting on a simulator of the Intel i860 (which was codenamed “N-Ten”) by January.” In fact, this is where NT actually got its name, Lucovsky revealed, adding that the “new technology” moniker was added after the fact in a rare spurt of product marketing by the original NT team members. “Originally, we were targeting NT to the Intel i860, a RISC processor that was horribly behind schedule. Because we didn’t have any i860 machines in-house to test on, we used an i860 simulator. That’s why we called it NT, because it worked on the ‘N-Ten.'”<\/p>\n

\u540e\u6765\uff0c\u603b\u7b97\u5230\u4e86\u5f00\u59cb\u5199\u4ee3\u7801\u7684\u65f6\u5019\u3002\u300e\u6211\u4eec\u57281988\u5e7412\u6708\u4e2d\u65ec\u65f6\u5bf9\u7b2c\u4e00\u4efd\u4ee3\u7801\u8fdb\u884c\u4e86\u5ba1\u67e5\uff0c\u300fLucovsky\u8bf4\u9053\uff0c\u300e\u8fd9\u6bb5\u4ee3\u7801\u662f\u4e00\u4e2a\u975e\u5e38\u57fa\u7840\u7684\u7cfb\u7edf\uff0c\u5230\u7b2c\u4e8c\u5e74\u4e00\u6708\u65f6\uff0c\u5dee\u4e0d\u591a\u8fbe\u5230\u53ef\u4ee5\u5728Intel i860\uff08\u4ee3\u53f7N10\uff08\u8bd1\u6ce8\uff1a\u82f1\u6587\u4e3aN-Ten\uff09\uff09\u6a21\u62df\u5668\u4e0a\u8dd1\u8d77\u6765\u7684\u7a0b\u5ea6\u3002\u300f\u5b9e\u9645\u4e0a\uff0c\u8fd9\u5c31\u662fNT\u540d\u5b57\u7684\u6765\u6e90\uff0cLocovsky\u89e3\u91ca\u9053\uff0c\u8fd8\u8865\u5145\u8bf4\u300e\u65b0\u6280\u672f\u300f\uff08new technology\uff09\u8fd9\u4e2a\u7ef0\u53f7\u662f\u540e\u6765NT\u56e2\u961f\u505a\u5e02\u573a\u8425\u9500\u65f6\u7075\u5149\u4e00\u95ea\u60f3\u51fa\u6765\u7684\u3002\u300e\u6700\u521d\uff0c\u6211\u4eec\u662f\u4ee5Intel i860\u4f5c\u4e3a\u76ee\u6807\u673a\u5668\u5f00\u53d1NT\u7684\uff0c\u800ci860\u662f\u4e00\u6b3e\u8fdb\u5ea6\u4e25\u91cd\u6ede\u540e\u7684RISC\u5904\u7406\u5668\u3002\u7531\u4e8e\u6211\u4eec\u5f53\u65f6\u6ca1\u6709\u4e00\u53f0i860\u7684\u7528\u4e8e\u6d4b\u8bd5\uff0c\u5c31\u7528i860\u6a21\u62df\u5668\u6765\u4ee3\u66ff\u3002\u8fd9\u5c31\u662fNT\u540d\u5b57\u7684\u6765\u6e90\uff0c\u56e0\u4e3a\u5b83\u662f\u8dd1\u5728N-Ten\u4e0a\u7684\u3002\u300f<\/p>\n

The newly named NT team had a basic kernel mode system up and running on the simulator by April 1989. “We started with five guys from DEC and one from the ‘outside’ (i.e. Microsoft), a guy named Steve Wood,” Lucovsky said. “And we stayed a tiny group for a long time, through the summer. We thought, ‘How hard could it be to build an OS?’ and scheduled 18 months to build NT. But we had forgotten about some of the important stuff–user mode, networking, and so on.”<\/p>\n

\u52301989\u5e744\u6708\u65f6\uff0c\u6709\u4e86\u65b0\u540d\u5b57\u7684NT\u56e2\u961f\u5df2\u7ecf\u521d\u6b65\u5b9e\u73b0\u4e86\u8fd0\u884c\u5728\uff08i860\uff09\u6a21\u62df\u5668\u4e0a\u7684\u57fa\u7840\u7cfb\u7edf\u5185\u6838\u3002\u300e\u6211\u4eec\u7684\u56e2\u961f\u4e2d\u6700\u65e9\u75315\u4e2a\u6765\u81eaDEC\u7684\u4eba\uff0c\u8fd8\u6709\u4e00\u4e2a\u662f\u4ece\u300e\u5916\u9762\u300f\uff08\u5373\u5fae\u8f6f\uff09\u6765\u7684\uff0c\u540d\u5b57\u53ebSteve Wood\uff0c\u300fLucovsky\u8bf4\uff0c\u300e\u56e2\u961f\u7684\u5c0f\u89c4\u6a21\u4fdd\u6301\u4e86\u5f88\u957f\u4e00\u6bb5\u65f6\u95f4\uff0c\u4e00\u76f4\u5ea6\u8fc7\u4e86\u5f53\u5e74\u7684\u6574\u4e2a\u590f\u5929\u3002\u6211\u4eec\u539f\u672c\u4ee5\u4e3a\uff0c\u300e\u5f00\u53d1\u4e2a\u64cd\u4f5c\u7cfb\u7edf\u80fd\u6709\u591a\u96be\uff1f\u300f\uff0c\u4e8e\u662f\u5b9a\u4e0b\u4e8618\u4e2a\u6708\u5f00\u53d1NT\u7cfb\u7edf\u7684\u76ee\u6807\u3002\u7136\u800c\u90a3\u65f6\u5019\u6211\u4eec\u5fd8\u4e86\u4e00\u4e9b\u5f88\u91cd\u8981\u7684\u4e1c\u897f\u2014\u2014\u7528\u6237\u6a21\u5f0f\u3001\u7f51\u7edc\u7cfb\u7edf\uff0c\u7b49\u7b49\u3002\u300f<\/p>\n

By late 1989, the NT group began growing. They added a formal networking team and expanded the security team beyond a single individual who, incidentally, had also been previously burdened by file system and localization development. “We grew that first year to 50 people or so,” Lucovsky said. “And within a year, we finally had the first functioning i860 prototypes, so we could use those instead of the simulators. We started looking at context switch times, to get an idea of how well it would perform. It became obvious almost immediately that the i860 would never work out. So we started looking at the MIPS architecture, another RISC design.”<\/p>\n

1989\u5e74\u7684\u540e\u671f\uff0cNT\u56e2\u961f\u5f00\u59cb\u6269\u5f20\uff0c\u589e\u52a0\u4e86\u4e00\u4e2a\u6b63\u5f0f\u7684\u7f51\u7edc\u56e2\u961f\uff0c\u5e76\u5c06\u539f\u6765\u53ea\u6709\u4e00\u4e2a\u4eba\u7684\u5b89\u5168\u56e2\u961f\u8fdb\u884c\u4e86\u6269\u5c55\uff0c\u5f53\u65f6\u539f\u6765\u7684\u90a3\u4e2a\u4eba\u8fd8\u540c\u65f6\u8d1f\u8d23\u6587\u4ef6\u7cfb\u7edf\u548c\u672c\u5730\u5316\u529f\u80fd\u7684\u5f00\u53d1\u3002\u300e\u7b2c\u4e00\u5e74\u6211\u4eec\u6269\u5145\u5230\u4e86\u5927\u7ea650\u4eba\u5de6\u53f3\u300f\uff0cLucovsky\u8bf4\uff0c\u300e\u540e\u6765\u5927\u6982\u4e00\u5e74\u4e4b\u5185\uff0c\u6211\u4eec\u7ec8\u4e8e\u62ff\u5230\u4e86\u7b2c\u4e00\u6279\u53ef\u4ee5\u5de5\u4f5c\u7684i860\u539f\u578b\u673a\uff0c\u4e8e\u662f\u7ec8\u4e8e\u53ef\u4ee5\u5728\u8fd9\u4e9b\u771f\u673a\u4e0a\u5f00\u53d1\u3001\u800c\u4e0d\u7528\u8dd1\u5728\u6a21\u62df\u5668\u4e0a\u4e86\u3002\u6211\u4eec\u5f00\u59cb\u5173\u6ce8\u4e0a\u4e0b\u6587\u5207\u6362\u6b21\u6570\uff0c\u4ee5\u6b64\u6765\u5224\u65adi860\u5230\u5e95\u6027\u80fd\u5982\u4f55\u3002\u5f88\u5feb\u6211\u4eec\u5c31\u53d1\u73b0i860\u8fd9\u4e1c\u897f\u4e0d\u884c\uff0c\u6240\u4ee5\u6211\u4eec\u5f00\u59cb\u5173\u6ce8MIPS\u67b6\u6784\u2014\u2014\u53e6\u4e00\u4e2aRISC\u8bbe\u8ba1\u3002\u300f<\/p>\n

In December 1989, the NT team made the decision to ditch the i860 and target the MIPS R3000 chip instead. “Within two or three months, we were booting NT on real hardware in Big Endian mode,” Lucovsky told us, “and our architecture really paid off. We had designed NT to be portable, and we proved it would work almost immediately when we moved to MIPS. We made the change without a lot of pain.”<\/p>\n

1989\u5e7412\u6708\uff0cNT\u56e2\u961f\u51b3\u5b9a\u629b\u5f03i860\uff0c\u8f6c\u800c\u5c06MIPS R3000\u82af\u7247\u4f5c\u4e3a\u76ee\u6807\u673a\u5668\u3002\u300e\u5927\u7ea6\u7528\u4e862\u52303\u4e2a\u6708\uff0c\u6211\u4eec\u5c31\u5c06NT\u8dd1\u5728\u4e86Big Endian\u6a21\u5f0f\u7684\u771f\u673a\u4e0a\u3002\u300fLucovsky\u8bf4\u9053\uff0c\u300e\u800c\u6211\u4eec\u5bf9\u7cfb\u7edf\u67b6\u6784\u7684\u52aa\u529b\u4e5f\u771f\u7684\u5f97\u5230\u4e86\u56de\u62a5\u3002\u6211\u4eec\u5c06NT\u8bbe\u8ba1\u4e3a\u53ef\u8fc1\u79fb\u7684\uff08\u5185\u6838\uff09\uff0c\u800c\u8f6c\u5411MIPS\u67b6\u6784\u540e\uff0cNT\u57fa\u672c\u4e0a\u5f88\u5feb\u5c31\u80fd\u5728\u4e0a\u9762\u8dd1\u8d77\u6765\u4e86\uff0c\u800c\u505a\u51fa\u8fd9\u4e00\u4fee\u6539\u5e76\u6ca1\u6709\u7ecf\u5386\u5f88\u591a\u82e6\u96be\u3002\u300f<\/p>\n

By this time, the NT team started expanding rapidly, with most of its members now coming from the ranks at Microsoft. The graphics team was greatly expanded, once a new style of doing graphics was created. They also started an NT port to the Intel i386, which was the mainstream PC processor at the time, but Lucovsky explained why it was important to the team that they didn’t target the i386 initially. “We stayed away from the 386 for a while to avoid getting sucked into the architecture,” he said. “We didn’t want to use non-portability assumptions.” If they had targeted Intel’s volume chip from day one, he said, they would have had a higher performing system initially, but it would have hurt NT in the long run, and made it harder to pursue new architectures as they did recently with the 64-bit Itanium versions of Windows Server 2003.<\/p>\n

\u5728\u8fd9\u671f\u95f4\uff0cNT\u56e2\u961f\u6025\u901f\u6269\u5f20\uff0c\u65b0\u52a0\u5165\u7684\u6210\u5458\u6765\u81ea\u5fae\u8f6f\u7684\u5404\u4e2a\u9636\u5c42\u3002\u5f53\u5bf9\u56fe\u5f62\u7ed8\u5236\u6709\u4e86\u4e00\u79cd\u65b0\u65b9\u6cd5\u540e\uff0c\u56fe\u50cf\u56e2\u961f\u5927\u5927\u6269\u5c55\u4e86\u3002\u540c\u65f6\uff0c\u56e2\u961f\u4e5f\u5f00\u59cb\u5c06NT\u8fc1\u79fb\u5230Intel i386\u4e0a\uff0c\u8fd9\u5728\u5f53\u65f6\u662f\u4e00\u6b3e\u4e3b\u6d41\u7684PC\u5904\u7406\u5668\uff0c\u4f46Lucovsky\u4e5f\u89e3\u91ca\u4e86\u4e3a\u4ec0\u4e48\u56e2\u961f\u6ca1\u6709\u4e00\u5f00\u59cb\u5c31\u4ee5i386\u4f5c\u4e3a\u76ee\u6807\u673a\u5668\u8fdb\u884c\u5f00\u53d1\u3002\u300e\u6211\u4eec\u907f\u5f00\u4e86386\u4e00\u6bb5\u65f6\u95f4\uff0c\u4ee5\u907f\u514d\u53d7\u5176\u67b6\u6784\u7684\u9650\u5236\uff0c\u300f\u4ed6\u8bf4\uff0c\u300e\u6211\u4eec\u4e0d\u60f3\u7528\u4e0a\u65e0\u6cd5\u8fc1\u79fb\u7684\u8bbe\u8ba1\u3002\u300fLucovsky\u8fd8\u8bf4\uff0c\u5982\u679c\u4e00\u5f00\u59cb\u5c31\u9488\u5bf9Intel\u7684\u91cf\u4ea7\u82af\u7247\u8fdb\u884c\u5f00\u53d1\uff0c\u53ef\u80fd\u6700\u521d\u4f1a\u5f00\u53d1\u6210\u4e00\u4e2a\u6027\u80fd\u8f83\u9ad8\u7684\u7cfb\u7edf\uff0c\u4f46\u957f\u4e45\u770b\u6765\u4f1a\u5bf9NT\u6709\u4e0d\u5229\u5f71\u54cd\uff0c\u4e5f\u963b\u6b62\u4e86NT\u9488\u5bf9\u65b0\u5904\u7406\u5668\u67b6\u6784\u7684\u8ffd\u6c42\uff0c\u6bd4\u5982\u4ed6\u4eec\u6700\u8fd1\u4e3a\u5c06Windows Server 2003\u8fc1\u79fb\u523064\u4f4dItanium\u5904\u7406\u5668\u4e0a\u6240\u505a\u7684\u4e8b\u60c5\u3002<\/p>\n

NT becomes Windows NT<\/strong><\/p>\n

\u5f53NT\u6210\u4e3aWindows NT<\/strong><\/p>\n

“By the spring of 1990, we had the MIPS version limping along and we started the 386 version in earnest,” Lucovsky said. “It was another huge growth spurt.” That May, Microsoft released Windows 3.0 and, suddenly, the world took notice. Windows was a smash success, and the obvious future of PC-based graphical computing. “We started looking at Windows 3.0 and said, ‘What if, instead of OS\/2, we did a 32-bit version of Windows?'” Lucovsky noted, casually throwing out the question on which the next decade of computing hinged. “Four guys–Steve Wood, Scott Ludwig, a guy from the graphics engine group, and myself–looked at the 16-bit Windows APIs and figured out what it would take to stretch them to 32-bit. We spent a month and a half prepping the API set, and then presented it to a 100-person design preview group to see what they thought.”<\/p>\n

\u300e\u52301990\u5e74\u6625\u5929\u65f6\uff0cMIPS\u7248\u672c\u5f00\u59cb\u8e52\u8dda\u5b66\u6b65\uff0c\u6211\u4eec\u4e5f\u5f00\u59cb\u70ed\u5fc3\u5730\u5f00\u53d1386\u7248\u672c\uff0c\u300fLucovsky\u8bf4\uff0c\u300e\u6b64\u65f6\u5219\u662f\u53e6\u4e00\u4e2a\u7a81\u98de\u731b\u8fdb\u7684\u589e\u957f\u3002\u300f\u5f53\u5e74\u4e94\u6708\uff0c\u5fae\u8f6f\u53d1\u5e03\u4e86Windows 3.0\uff0c\u7136\u540e\u5c31\u50cf\u662f\u7a81\u7136\u4e4b\u95f4\uff0c\u6574\u4e2a\u4e16\u754c\u90fd\u4e3a\u4e4b\u77a9\u76ee\uff08\u8bd1\u6ce8\uff1aWindows 1.0\u548c2.0\u7248\u672c\u90fd\u6ca1\u6709\u5f15\u8d77\u592a\u5927\u8f70\u52a8\uff0c\u524d\u8005\u5e73\u6de1\u65e0\u5947\uff0c\u540e\u8005\u6536\u83b7\u4e86\u4e00\u5b9a\u5f71\u54cd\uff0c\u4f46\u8fdc\u4e0d\u5982\u5f53\u65f6\u5176\u5b83\u516c\u53f8\u7684\u4ea7\u54c1\uff09\u3002Windows\u5927\u83b7\u6210\u529f\uff0c\u800c\u57fa\u4e8ePC\u7684\u56fe\u5f62\u5316\u8ba1\u7b97\u4e5f\u6210\u4e3a\u663e\u800c\u6613\u89c1\u7684\u672a\u6765\u3002\u300e\u6211\u4eec\u4ed4\u7ec6\u89c2\u6469\u4e86Windows 3.0\uff0c\u60f3\u5230\uff0c\u5982\u679c\u6211\u4eec\u4e0d\u518d\u5f00\u53d1OS\/2\uff0c\u800c\u662f\u505a\u4e00\u4e2a32\u4f4d\u7684Windows\u4f1a\u600e\u4e48\u6837\u5462\uff1f\u300fLucovsky\u4e00\u8fb9\u8bf4\uff0c\u4e00\u8fb9\u5c06\u5bf9\u5f53\u65f6\u800c\u8a00\u672a\u6765\u6570\u5341\u5e74\u8ba1\u7b97\u673a\u7684\u53d1\u5c55\u8109\u7edc\u505a\u51fa\u9884\u6d4b\u7684\u95ee\u9898\u629b\u51fa\u3002\u300e\u6709\u56db\u4e2a\u4eba\u2014\u2014Steve Wood\uff0cScott Ludwig\uff0c\u4e00\u4e2a\u56fe\u50cf\u5f15\u64ce\u7ec4\u6210\u5458\uff0c\u8fd8\u6709\u6211\u81ea\u5df1\u2014\u2014\u5f00\u59cb\u7814\u7a7616\u4f4d\u7684Windows API\uff0c\u5e76\u6478\u7d22\u51fa\u4e86\u5c06\u5176\u6269\u5c55\u81f332\u4f4d\u7684\u95e8\u8def\u3002\u6211\u4eec\u82b1\u4e86\u4e00\u4e2a\u534a\u6708\u7684\u65f6\u95f4\u4e3a\uff0832\u4f4d\u7684\uff09API\u96c6\u5408\u505a\u51c6\u5907\uff0c\u7136\u540e\u628a\u6210\u679c\u5c55\u793a\u7ed9\u4e00\u4e2a\u6709100\u4eba\u7684\u8bbe\u8ba1\u9884\u89c8\u56e2\u961f\uff0c\u6765\u503e\u542c\u4ed6\u4eec\u7684\u60f3\u6cd5\u3002<\/p>\n

The key characteristic of the new API, eventually named Win32, is that, though it was a new API, it looked and acted just like the 16-bit Windows APIs, letting developers easily move to the new system and port their applications. “We made it possible to move 16-bit applications to NT very easily,” Lucovsky said, “and these applications could take advantage of the unique features of NT, such as the larger address space. We also added new APIs that weren’t in the 16-bit version. We added major new functionality to complete the API, making it a complete OS API, but we did this using a style that would be familiar to the emerging body of Windows programmers.”<\/p>\n

\u65b0\u7248API\uff08\u6700\u7ec8\u88ab\u547d\u540d\u4e3aWin32\uff09\u7684\u4e00\u4e2a\u5173\u952e\u8c03\u6574\u662f\uff0c\u5c3d\u7ba1\u662f\u4e00\u5957\u65b0\u7684API\uff0c\u4f46\u4e0d\u8bba\u662f\u770b\u4e0a\u53bb\u8fd8\u662f\u7528\u8d77\u6765\u90fd\u4e0e16\u4f4d\u7684Windows API\u5f88\u76f8\u4f3c\uff0c\u4f7f\u5f97\u5f00\u53d1\u8005\u4eec\u8fc1\u79fb\u5230\u65b0\u7cfb\u7edf\u3001\u5e76\u5c06\u5e94\u7528\u7a0b\u5e8f\u8fdb\u884c\u8fc1\u79fb\u8f83\u4e3a\u7b80\u5355\u3002\u300e\u6211\u4eec\u4ee4\u5c0616\u4f4d\u5e94\u7528\u7a0b\u5e8f\u8fc1\u79fb\u5230NT\u4e0a\u8fd9\u4ef6\u4e8b\u6210\u4e3a\u53ef\u80fd\uff0c\u300fLucovsky\u8bf4\uff0c\u300e\u5e76\u4f7f\u8fd9\u4e9b\uff08\u8fc1\u79fb\u800c\u6765\u7684\uff09\u5e94\u7528\u7a0b\u5e8f\u53ef\u4ee5\u5229\u7528\u8d77NT\u7684\u72ec\u7279\u529f\u80fd\uff0c\u4f8b\u5982\u66f4\u5927\u7684\u5730\u5740\u7a7a\u95f4\u7b49\u7b49\u3002\u6211\u4eec\u4e5f\u589e\u52a0\u4e86\u4e0d\u572816\u4f4d\u7248\u672c\u4e2d\u7684API\u3002\u6211\u4eec\u589e\u52a0\u4e86\u91cd\u8981\u7684\u529f\u80fd\u6765\u8865\u5168API\u96c6\uff0c\u4f7f\u6574\u4e2aAPI\u4f5c\u4e3a\u64cd\u4f5c\u7cfb\u7edfAPI\u5b8c\u6574\u8d77\u6765\uff0c\u4e0d\u8fc7\u6240\u91c7\u7528\u7684\u98ce\u683c\u662f\u4e3a\u4e0d\u65ad\u6210\u957f\u4e2d\u7684Windows\u5e94\u7528\u5f00\u53d1\u8005\u56e2\u4f53\u6240\u719f\u6089\u7684\u3002\u300f<\/p>\n

The reaction within Microsoft was immediate. “They loved it,” he said, “when they saw how easy it would be. It was basically Windows on steroids, and not OS\/2, which used a completely different programming model.” Making NT a 32-bit Windows version instead of an OS\/2 product, however, introduced new issues, not all of which were technical. Microsoft had to get ISV and OEM approval, and of course alert IBM to the change. “We did an ISV preview with IBM, and had this deck of about 20 slides, and we said, ‘look, this is what we’re going to do.’ At first, they thought Win32 was a fancy name for OS\/2. Then you could just see it on their faces: ‘Wait a second, this isn’t OS\/2.'”<\/p>\n

\uff08\u65b0API\uff09\u5728\u5fae\u8f6f\u5185\u90e8\u7684\u53cd\u5e94\u662f\u7acb\u7aff\u89c1\u5f71\u7684\u3002\u300e\u4ed6\u4eec\u5f88\u559c\u6b22\uff0c\u300f\u4ed6\uff08Lucovsky\uff09\u8bf4\u9053\uff0c\u300e\u5f53\u4e86\u89e3\u5230\uff08\u9488\u5bf9\u65b0API\u8fdb\u884c\u5f00\u53d1\uff09\u6709\u591a\u5bb9\u6613\u4e4b\u540e\u3002\u57fa\u672c\u4e0a\u8fd9\u5c31\u662f\u6253\u4e86\u5174\u594b\u5242\u7684Windows\uff0c\u5e76\u4e14\uff08\u5b8c\u5168\uff09\u4e0d\u662fOS\/2\uff0c\u540e\u8005\u662f\u5b8c\u5168\u4e0d\u540c\u7684\u7f16\u7a0b\u6a21\u578b\u3002\u300f\u4e0d\u8fc7\uff0c\u5c06NT\u5f00\u53d1\u4e3aWindows\u768432\u4f4d\u7248\u672c\u2014\u2014\u800c\u4e0d\u662fOS\/2\u4ea7\u54c1\uff0c\u4e5f\u5f15\u5165\u4e86\u65b0\u95ee\u9898\uff0c\u5e76\u4e14\u4e0d\u662f\u6240\u6709\u7684\u95ee\u9898\u90fd\u662f\u6280\u672f\u65b9\u9762\u7684\u3002\u5fae\u8f6f\u9700\u8981\u53d6\u5f97ISV\uff08Independent Software Vendors\uff0c\u72ec\u7acb\u8f6f\u4ef6\u5f00\u53d1\u5546\uff0c\u6307\u4e00\u7c7b\u5229\u7528\u5df2\u6709\u7684\u8f6f\u786c\u4ef6\u5e73\u53f0\u5f00\u53d1\u7279\u5b9a\u5e94\u7528\u7a0b\u5e8f\u7684\u5382\u5546\uff0c\u4f8b\u5982Oracle\u7b49\uff09\u548cOEM\u5382\u5546\u4eec\u7684\u8ba4\u53ef\uff0c\u5f53\u7136\u4e5f\u9700\u8981\u63d0\u9192IBM\u6b63\u5728\u53d1\u751f\u7684\u53d8\u5316\uff08\u8bd1\u6ce8\uff1a\u5fae\u8f6f\u4ece1985\u5e74\u8d77\u4e0eIBM\u5408\u4f5c\u5f00\u53d1OS\/2\uff0c\u7531\u4e8e\u524d\u6587\u63d0\u5230\u7684Windows 3.0\u7684\u5927\u83b7\u6210\u529f\uff0c\u5fae\u8f6f\u6700\u7ec8\u4e0eIBM\u5206\u9053\u626c\u9573\uff09\u3002\u300e\u6211\u4eec\u4e0eIBM\u8fdb\u884c\u4e86\u4e00\u6b21ISV\u9884\u89c8\u4f1a\u8bae\uff0c\u9488\u5bf9\u53d8\u5316\u505a\u4e86\u5927\u7ea620\u5f20\u5e7b\u706f\u7247\uff0c\u7136\u540e\u8bf4\uff0c\u300c\u770b\uff0c\u8fd9\u5c31\u662f\u6211\u4eec\u8981\u505a\u7684\u4e8b\u60c5\u3002\u300d\u4e00\u5f00\u59cb\uff0c\u4ed6\u4eec\uff08IBM\u7684\u4eba\uff09\u4ee5\u4e3aWin32\u53ea\u662fOS\/2\u7684\u4e00\u4e2a\u82b1\u540d\uff0c\u4f46\u968f\u540e\u4f60\u5c31\u80fd\u4ece\u4ed6\u4eec\u7684\u8138\u4e0a\u770b\u51fa\u611f\u89c9\u4e8b\u60c5\u4e0d\u5bf9\u7684\u8868\u60c5\uff1a\u300c\u7b49\u7b49\uff0c\u8fd9\u597d\u50cf\u4e0d\u662fOS\/2\u3002\u300d\u300f<\/p>\n

The decision to drop OS\/2 for Windows forever damaged the relationship between the two companies. “But we had executive approval, and started the port,” Lucovsky said. “So instead of working on an OS\/2 subsystem for NT, we picked up Win32.” At that moment, he said, the product became Windows NT.<\/p>\n

\u653e\u5f03OS\/2 for Windows\u7684\u51b3\u5b9a\u5bf9\u4e24\u5bb6\u516c\u53f8\u4e4b\u95f4\u7684\u5173\u7cfb\u4ea7\u751f\u4e86\u4f24\u5bb3\u3002\u300e\u4f46\u6211\u4eec\u83b7\u5f97\u4e86\u6267\u884c\u51c6\u8bb8\uff0c\u5e76\u5f00\u59cb\u4e86\u8fc1\u79fb\u5de5\u4f5c\uff0c\u300fLucovsky\u8bf4\uff0c\u300e\u4e8e\u662f\u6211\u4eec\u9009\u62e9\u4e86Win32\uff0c\u800c\u4e0d\u662f\u505a\u4e00\u4e2aNT\u7684OS\/2\u5b50\u7cfb\u7edf\u3002\u300f\u5230\u90a3\u65f6\uff0c\u4ed6\uff08Lucovsky\uff09\u8bf4\uff0c\u8fd9\u4e2a\u4ea7\u54c1\u5f00\u59cb\u6210\u4e3aWindows NT\u4e86\u3002<\/p>\n

NT’s modular architecture paid off during this change as well. “Thanks to our microkernel architecture, with the kernel decoupled from application environments like POSIX and Win32, we didn’t have to change the kernel or start a new programming effort,” Lucovsky told us. “The deep guts of the scheduler didn’t have to change. We had C command line applications up and running within two weeks. This was September 1990.”<\/p>\n

NT\u7684\u6a21\u5757\u5316\u7ed3\u6784\u5728\u8fd9\u4e2a\u8f6c\u53d8\u4e2d\u4e5f\u6536\u5230\u4e86\u56de\u62a5\u3002\u300e\u611f\u8c22\u6211\u4eec\u7684\u5fae\u5185\u6838\u67b6\u6784\uff0c\uff08\u5728\u8fd9\u79cd\u67b6\u6784\u4e0b\uff09\u5185\u6838\u4e0e\u5e94\u7528\u7a0b\u5e8f\u73af\u5883\u2014\u2014\u4f8b\u5982POSIX\u548cWin32\u4e4b\u95f4\u662f\u76f8\u4e92\u5206\u79bb\u7684\uff0c\u6211\u4eec\u4e0d\u5fc5\u5bf9\u5185\u6838\u8fdb\u884c\u4fee\u6539\uff0c\u6216\u8005\u542f\u52a8\u9886\u4e00\u6b21\u7f16\u7a0b\u7684\u52aa\u529b\uff0c\u300fLucovsky\u544a\u8bc9\u6211\u4eec\uff0c\u300e\u8c03\u5ea6\u5668\u7684\u6df1\u5c42\u673a\u5236\u4e0d\u5fc5\u505a\u51fa\u6539\u53d8\u3002\u6211\u4eec\u5728\u4e24\u5468\u5185\u5c31\u5199\u597d\u4e86C\u8bed\u8a00\u64b0\u5199\u7684\u547d\u4ee4\u884c\u5e94\u7528\u5e76\u4f7f\u5176\u8dd1\u4e86\u8d77\u6765\uff0c\u90a3\u662f\u57281990\u5e74\u7684\u4e5d\u6708\u4efd\u3002\u300f<\/p>\n

Thompson elaborated on the importance of NT’s foundations. “Our core architecture is so solid, that we were able to take NT from 386-25’s in 1990 to today’s embedded devices, 64-way, 64-bit multiprocessor machines, and $1000 scale-out server blades. We’ve been able to deliver a whole array of services on it.”<\/p>\n

Thompson\u8be6\u7ec6\u9610\u8ff0\u4e86NT\u57fa\u7840\u7684\u91cd\u8981\u6027\u3002\u300e\u6211\u4eec\u6240\u64b0\u5199\u7684\u6838\u5fc3\u662f\u5982\u6b64\u7a33\u56fa\uff0c\u4ee5\u81f3\u4e8e\u53ef\u4ee5\u4ece1990\u5e74\u7684386-25\u4e00\u76f4\u7528\u5230\u5982\u4eca\u7684\u5d4c\u5165\u5f0f\u8bbe\u5907\u300164\u4f4d+64\u8def\u591a\u5904\u7406\u5668\u7cfb\u7edf\uff0c\u8fd8\u6709\u4ef7\u503c$1000\u7f8e\u5143\u7684\u53ef\u6269\u5c55\u5200\u7247\u670d\u52a1\u5668\u3002\u6211\u4eec\u53ef\u4ee5\u5728\u5176\u4e0a\u63d0\u4f9b\u79cd\u7c7b\u7e41\u591a\u7684\u670d\u52a1\u3002\u300f<\/p>\n

September 1990, truly, was the turning point for Windows NT. Not coincidentally, that’s also when Dave Thompson, previously heading Microsoft’s LANMAN for OS\/2 3.1 advanced development team, joined the NT team. “We threw the switch,” Thompson told us, “and the team went from 28 to about 300 people. We had our first real product plan.”<\/p>\n

1990\u5e74\u7684\u4e5d\u6708\u7740\u5b9e\u662fWindows NT\u7684\u4e00\u4e2a\u8f6c\u6298\u70b9\u3002\u5de7\u5408\u2014\u2014\u6216\u8005\u8bf4\u662f\u5fc5\u7136\u7684\u662f\uff0c\u8fd9\u4e5f\u662fDave Thompson\u2014\u2014\u66fe\u4efb\u5fae\u8f6f\u7684LANMAN for OS2 3.1\u9ad8\u7ea7\u5f00\u53d1\u7ec4\u7ecf\u7406\u2014\u2014\u52a0\u5165NT\u56e2\u961f\u7684\u65f6\u95f4\u3002\u300e\u6211\u4eec\u6273\u52a8\u4e86\u5f00\u5173\uff0c\u300fThompson\u544a\u8bc9\u6211\u4eec\uff0c\u300e\u7136\u540e\u56e2\u961f\u5c31\u4ece28\u4eba\u6269\u5c55\u5230\u4e86300\u4eba\u3002\u6211\u4eec\u8fd9\u624d\u6709\u4e86\u7b2c\u4e00\u4e2a\u771f\u6b63\u7684\u4ea7\u54c1\u89c4\u5212\u3002\u300f<\/p>\n

RTM and beyond<\/strong><\/p>\n

RTM\uff08Release To Manufacturing\uff09\u53ca\u672a\u6765<\/strong><\/p>\n

The first version of Windows NT, Windows NT 3.1, was released in July 1993 and named to match the version number of the then-current 16-bit Windows product. That NT version featured desktop and server editions and distributed security in the form of domains. Since then, the NT team has worked on a progression of releases, all developed on the same underlying code base.<\/p>\n

Windows NT\u7684\u7b2c\u4e00\u4e2a\u7248\u672c\uff0cWindows NT 3.1\uff0c\u4e8e1993\u5e747\u6708\u91ca\u51fa\uff0c\u5e76\u4e0e\u5f53\u65f6\u768416\u4f4dWindows\u4ea7\u54c1\u7ebf\u7248\u672c\u53f7\u9f50\u5934\u5e76\u8fdb\u3002\u8be5\u7248\u672c\u7684NT\u5305\u542b\u684c\u9762\u7248\u548c\u670d\u52a1\u5668\u7248\uff0c\u4ea6\u542b\u6709\u4ee5\u57df\u4e3a\u5f62\u5f0f\u7684\u5206\u5e03\u5f0f\u5b89\u5168\u8bbe\u8ba1\u3002\u4ece\u90a3\u65f6\u8d77\uff0cNT\u56e2\u961f\u7684\u6210\u5458\u4eec\u5f00\u59cb\u5728\u4e00\u7cfb\u5217\u53d1\u884c\u7248\u4e0a\u8fdb\u884c\u5f00\u53d1\uff0c\u800c\u6240\u6709\u8fd9\u4e9b\u7248\u672c\u90fd\u57fa\u4e8e\u76f8\u540c\u7684\u5e95\u5c42\u4ee3\u7801\u5e93\u3002<\/p>\n

The next release, Windows NT 3.5, was code-named Daytona, and shipped in September 1994. “Daytona was a very rewarding project,” Thompson said. “We focused on size and performance issues, and on “finishing” many of the first-release features of 3.1. Daytona also had significant functional improvements and enhancements.” The original themes for Daytona were size, performance, compression, and Netware compatibility. Two of those goals were emblematic of the time: DoubleSpace-style compression was a hot topic in the early 1990’s because disk space was at such a premium, and Netware was the dominant network operating system of the day. “We eventually dropped compression,” Thompson said, “but the Netware port was strategic. Novell was ambivalent about the NT desktop ? they didn’t know if they wanted to build a client. We offered our assistance, but they kept messing around and … well. We did our own. And it just blew them away. Ours was the better Netware client, and customers used ours for years, even after they finally did one. That client enabled the NT desktop, because Netware was the prevalent server in the market. We wouldn’t have been able to sell NT desktops otherwise.”<\/p>\n

\u4e0b\u4e00\u4e2a\u7248\u672c\uff0c\u4ee3\u53f7\u4e3aDaytona\u7684Windows NT 3.5\uff0c\u4e8e1994\u5e749\u6708\u53d1\u5e03\u3002\u300eDaytona\u662f\u4e00\u4ef6\u5f88\u6709\u4ef7\u503c\u7684\u9879\u76ee\uff0c\u300fThompson\u8bf4\uff0c\u300e\u6211\u4eec\u4e13\u6ce8\u4e8e\u5176\u4f53\u91cf\u548c\u6027\u80fd\uff0c\u5e76\u300c\u5b8c\u6210\u300d\u4e86\u8bb8\u591a\u5728NT 3.1\u4e2d\u9996\u6b21\u63a8\u51fa\u7684\u529f\u80fd\u3002Daytona\u4e5f\u540c\u65f6\u5305\u542b\u4e86\u91cd\u8981\u7684\u529f\u80fd\u578b\u6539\u8fdb\u548c\u589e\u5f3a\u3002\u300fDaytona\u6700\u521d\u7684\u8bbe\u8ba1\u4e3b\u9898\u662f\u5c3a\u5bf8\u3001\u6027\u80fd\u3001\u6570\u636e\u538b\u7f29\u548cNetware\u517c\u5bb9\u6027\u3002\u5176\u4e2d\u4e24\u4e2a\u76ee\u6807\u5728\u5f53\u65f6\u5177\u6709\u8c61\u5f81\u610f\u4e49\uff1aDoubleSpace\u5f0f\u7684\u6570\u636e\u538b\u7f29\u529f\u80fd\u57281990\u5e74\u4ee3\u65e9\u671f\u662f\u4e2a\u70ed\u95e8\u8bdd\u9898\uff0c\u56e0\u4e3a\u5f53\u65f6\u78c1\u76d8\u7a7a\u95f4\u8d35\u5230\u4e0a\u5929\uff1b\u6b64\u5916\uff0cNetware\u4e5f\u662f\u5f53\u65f6\u5360\u4e3b\u5bfc\u5730\u4f4d\u7684\u7f51\u7edc\u64cd\u4f5c\u7cfb\u7edf\u3002\u300e\u6211\u4eec\u6700\u7ec8\u653e\u5f03\u4e86\u6570\u636e\u538b\u7f29\u529f\u80fd\u7684\u5f00\u53d1\uff0c\u300fThompson\u8bf4\uff0c\u300e\u4f46\u9488\u5bf9Netware\u7684\u5bf9\u63a5\u662f\u5177\u6709\u6218\u7565\u610f\u4e49\u7684\u3002Novell\u5bf9NT\u684c\u9762\u7cfb\u7edf\u6709\u4e00\u79cd\u77db\u76fe\u5fc3\u6001\uff0c\u8bf4\u4e0d\u51c6\u81ea\u5df1\u662f\u5426\u8981\u53e6\u5916\u505a\u4e00\u4e2a\u5ba2\u6237\u7aef\u51fa\u6765\u3002\u6211\u4eec\u5c3d\u53ef\u80fd\u63d0\u4f9b\u4e86\u90aa\u4e4e\uff0c\u4f46\u4ed6\u4eec\u603b\u662f\u641e\u7838\uff0c\u6700\u540e\u2026\u2026\u6211\u4eec\u81ea\u5df1\u505a\u4e86\u4e00\u4e2a\u51fa\u6765\uff0c\u800c\u6211\u4eec\u81ea\u5df1\u7814\u53d1\u7684\u5ba2\u6237\u7aef\u8ba9\u4ed6\u4eec\u611f\u5230\u60ca\u8bb6\u4e0d\u5df2\u3002\u6211\u4eec\u81ea\u5df1\u7814\u53d1\u7684Netware\u5ba2\u6237\u7aef\u66f4\u52a0\u4f18\u79c0\uff0c\u5ba2\u6237\u4eec\u4e00\u7528\u5c31\u662f\u597d\u591a\u5e74\uff0c\u5373\u4fbf\u662f\u4ed6\u4eec\uff08Novell\uff09\u540e\u6765\u7ec8\u4e8e\u81ea\u5df1\u5f00\u53d1\u4e86\uff08\u5b98\u65b9\u7248\u7684\uff09\u4e00\u4e2a\u7248\u672c\u51fa\u6765\u4ea6\u662f\u5982\u6b64\u3002\u8fd9\u4e2a\uff08Netware\uff09\u5ba2\u6237\u7aef\u6210\u5c31\u4e86NT\u684c\u9762\u7cfb\u7edf\uff0c\u56e0\u4e3aNetware\u5728\u5f53\u65f6\u662f\u666e\u904d\u4f7f\u7528\u7684\u670d\u52a1\u5668\u6807\u51c6\uff0c\u5982\u679c\u4e0d\u8fd9\u4e48\u505a\uff0c\u6211\u4eec\u5c31\u5356\u4e0d\u52a8NT\u3002\u300f<\/p>\n

Daytona also benefited from new compiler technology which enabled Microsoft to compress the code size and enable realistic NT desktops on lower-end systems than the original version. “The results were measurable,” Thompson said.<\/p>\n

Daytona\u4e5f\u4ece\u65b0\u7684\u7f16\u8bd1\u6280\u672f\u4e2d\u53d7\u76ca\uff0c\u4f7f\u5f97\u5fae\u8f6f\u80fd\u538b\u7f29\u4ee3\u7801\u5c3a\u5bf8\uff0c\u5e76\u4f7f\u5f97\u5728\u4f4e\u7aef\u786c\u4ef6\u4e0a\u8fd0\u884cNT\u684c\u9762\u7cfb\u7edf\u6210\u4e3a\u53ef\u80fd\u2014\u2014\u800c\u8fd9\u5728\u4e4b\u524d\u662f\u65e0\u6cd5\u505a\u5230\u7684\u3002\u300e\u6548\u679c\u663e\u800c\u6613\u89c1\u300f\uff0cThompson\u8bf4\u3002<\/p>\n

Windows NT 3.51 was dubbed the Power PC release, because it was designed around the Power PC version of NT, which was originally supposed to ship in version 3.5. But IBM constantly delayed the Power PC chips, necessitating a separate NT release. “NT 3.51 was a very unrewarding release,” Thompson said, contrasting it with Daytona. “After Daytona was completed, we basically sat around for 9 months fixing bugs while we waited for IBM to finish the Power PC hardware. But because of this, NT 3.51 was a solid release, and our customers loved it.” NT 3.51 eventually shipped in May 1995.<\/p>\n

Windows NT 3.51\u88ab\u620f\u79f0\u4e3aPower PC\u7248\uff0c\u56e0\u4e3a\u8fd9\u4e2a\u7248\u672c\u662f\u56f4\u7ed5\u7740Power PC\u7248NT\u8bbe\u8ba1\u7684\uff0c\u540e\u8005\u539f\u672c\u8981\u75283.5\u8fd9\u4e2a\u7248\u672c\u53f7\u53d1\u5e03\u3002\u7136\u800cIBM\u5bf9Power PC\u82af\u7247\u4e00\u62d6\u518d\u62d6\uff0c\u4f7f\u5f97\u989d\u5916\u53d1\u884c\u4e00\u4e2a\u7248\u672c\u7684NT\u6210\u4e3a\u5fc5\u8981\u3002\u300eNT 3.51\u662f\u4e00\u4e2a\u975e\u5e38\u6ca1\u6709\u4ef7\u503c\u7684\u53d1\u884c\u7248\uff0c\u300fThompson\u8bf4\uff0c\u4e0eDaytona\u76f8\u6bd4\u8d77\u6765\u7684\u8bdd\u3002\u300e\u5b8c\u6210Daytona\u540e\uff0c\u6211\u4eec\u57fa\u672c\u4e0a\u662f\u75289\u4e2a\u6708\u7684\u65f6\u95f4\u7b49\u5f85IBM\u5b8c\u6210Power PC\u7684\u786c\u4ef6\u5f00\u53d1\uff0c\u5728\u6b64\u671f\u95f4\uff0c\u6211\u4eec\u5bf9bug\u8fdb\u884c\u4fee\u4fee\u8865\u8865\u3002\u4e0d\u8fc7\uff0c\u4e5f\u6b63\u56e0\u4e3a\u5982\u6b64\uff0cNT 3.51\u6210\u4e3a\u4e86\u4e00\u4e2a\u975e\u5e38\u7a33\u5b9a\u7684\u7248\u672c\uff0c\u5ba2\u6237\u4eec\u5f88\u559c\u6b22\u3002\u300fNT 3.51\u6700\u7ec8\u4e8e1995\u5e745\u6708\u53d1\u5e03\u3002<\/p>\n

Fittingly, the next NT release, Windows NT 4.0, became known as the Shell Update Release (SUR), another challenging task that would once again prove the benefits of NT’s module architecture. “We wanted to build a desktop that had the 95 shell but used NT technology,” Lucovsky told us. “We eventually moved the Win32 GUI components and hosted them as an in-process driver. Performance was one side effect. We had had problems taking that API and running it in a different process. So moving the code to the same context as the runtime solved a lot of issues. We didn’t have to do dead lock detection for GDI and USER. It was significant work, but it solved a lot of headaches.” NT 4.0, a watershed release for the product, shipped in July 1996.<\/p>\n

\u5f88\u6070\u5f53\u5730\uff0c\u4e0b\u4e00\u4e2aNT\u53d1\u884c\u7248\uff0cWindows NT 4.0\uff0c\u88ab\u79f0\u4e3a\u5916\u58f3\u66f4\u65b0\u7248\u672c\uff08Shell Update Release\uff0cSUR\uff09\uff0c\u8fd9\u662f\u53e6\u4e00\u9879\u5177\u6709\u6311\u6218\u6027\u7684\u5de5\u4f5c\uff0c\u540e\u6765\u53c8\u4e00\u6b21\u6210\u4e3aNT\u6a21\u5757\u5316\u67b6\u6784\u4f18\u52bf\u7684\u8bc1\u660e\u3002\u300e\u6211\u4eec\u60f3\u5f00\u53d1\u4e00\u6b3e\u684c\u9762\u7cfb\u7edf\uff0c\u5177\u5907Windows 95\u7684\u5916\u58f3\u754c\u9762\uff0c\u4f46\u4f7f\u7528NT\u7684\u6280\u672f\u3002\u300fLucovsky\u544a\u8bc9\u6211\u4eec\uff0c\u300e\u6211\u4eec\u6700\u7ec8\u5bf9Win32 GUI\u7ec4\u4ef6\u8fdb\u884c\u4e86\u8fc1\u79fb\uff0c\u5e76\u5c06\u5176\u8f6c\u5316\u4e3a\u4e00\u4e2a\u8fdb\u7a0b\u5185\u9a71\u52a8\u3002\u6027\u80fd\u95ee\u9898\u6210\u4e3a\u526f\u4f5c\u7528\u4e4b\u4e00\uff0c\u6211\u4eec\u66fe\u4e00\u5ea6\u5728\u8c03\u7528API\u5e76\u5728\u53e6\u4e00\u4e2a\u8fdb\u7a0b\u4e2d\u8fd0\u884c\u4e4b\u65f6\u9047\u5230\u4e86\u56f0\u96be\uff0c\u6240\u4ee5\u5c06\u76f8\u5173\u4ee3\u7801\u79fb\u52a8\u5230\u4e0e\u8fd0\u884c\u65f6\u540c\u4e00\u4e0a\u4e0b\u6587\u89e3\u51b3\u4e86\u5f88\u591a\u95ee\u9898\u3002\u6211\u4eec\u4e0d\u7528\u518d\u9762\u5bf9GDI\u548cUSER\u7684\u6b7b\u9501\u68c0\u6d4b\u4e86\u3002\u8fd9\u9879\u5de5\u4f5c\u5f88\u8270\u5de8\uff0c\u4f46\u786e\u5b9e\u89e3\u51b3\u4e86\u5927\u95ee\u9898\u3002\u300fNT 4.0\uff0c\u4f5c\u4e3aNT\u4ea7\u54c1\u7ebf\u4e2d\u7684\u4e00\u9053\u5206\u6c34\u5cad\uff0c\u4e8e1996\u5e747\u6708\u53d1\u5e03\u4e86\u3002<\/p>\n

Windows everywhere<\/strong><\/p>\n

Windows\u904d\u5929\u4e0b<\/strong><\/p>\n

With the next release, Windows NT would lose the NT name and become, simply, Windows. Thompson says the decision came from the marketing team. “A guy from the Windows [9x] marketing team moved over to NT marketing and said we should use Windows everywhere. We were all uncomfortable with the name change at first, because NT had a solid reputation. But because of the reliability push with Windows 2000, people started talking about how much better Windows 2000 was than ‘that old NT stuff,’ even though it was the same architecture. So it was actually kind of fortuitous how it happened.” Incidentally, Windows 2000 didn’t have a codename “because Jim Allchin didn’t like codenames,” Thompson says.<\/p>\n

\u5230\u4e0b\u4e00\u4e2a\u53d1\u884c\u7248\u65f6\uff0cWindows NT\u4ece\u540d\u5b57\u4e2d\u53bb\u6389\u4e86NT\u7684\u5b57\u6837\uff0c\u6210\u4e3a\u7b80\u7b80\u5355\u5355\u7684\u300eWindows\u300f\u3002Thompson\u8bf4\u8fd9\u9879\u51b3\u5b9a\u662f\u7531\u5e02\u573a\u56e2\u961f\u63d0\u51fa\u7684\u3002\u300e\u6709\u4e2a\u4eceWindows\uff089x\uff09\u5e02\u573a\u56e2\u961f\u6765\u7684\u4eba\u8c03\u5230\u4e86NT\u5e02\u573a\u56e2\u961f\uff0c\u63d0\u51fa\u6211\u4eec\u5e94\u5f53\u5728\u6240\u6709\u5730\u65b9\u4f7f\u7528\u300cWindows\u300d\u8fd9\u4e2a\u79f0\u547c\u3002\u4e00\u5f00\u59cb\u6211\u4eec\u5bf9\u6539\u540d\u8fd9\u4ef6\u4e8b\u90fd\u611f\u5230\u5f88\u4e0d\u9002\u5e94\uff0c\u6bd5\u7adfNT\u62e5\u6709\u575a\u5b9a\u7684\u4fe1\u8a89\u57fa\u7840\u3002\u4e0d\u8fc7\uff0c\u7531\u4e8e\u5bf9Windows 2000\u4fe1\u4efb\u7684\u63a8\u52a8\uff0c\u4eba\u4eec\u5f00\u59cb\u8c08\u8bbaWindows 2000\u6bd4\u300c\u90a3\u4e9b\u65e7\u7684NT\u7684\u4e1c\u897f\u300d\u6709\u591a\u4e48\u591a\u4e48\u597d\uff0c\u5373\u4fbf\u8fd9\u4e24\u4e2a\u5b9e\u9645\u57fa\u4e8e\u540c\u4e00\u79cd\u67b6\u6784\u3002\u6240\u4ee5\u6539\u540d\u8fd9\u4ef6\u4e8b\u5b9e\u9645\u4e0a\u4e5f\u6709\u5176\u5076\u7136\u6027\u3002\u300f\u987a\u4fbf\u4e00\u63d0\uff0cWindows 2000\u6ca1\u6709\u4ee3\u53f7\uff08codename\uff09\uff0c\u300e\u56e0\u4e3aJim Allchin\u4e0d\u559c\u6b22\u8fd9\u4e48\u505a\uff0c\u300fThompson\u8bf4\u3002<\/p>\n

Since the completion of Windows 2000, the biggest decision the Windows team made was to split the client and server releases with the Whistler products, which became Windows XP and Windows Server 2003. “This lets us focus on the server customers, who want it rock solid, rather than right now,” Thompson told us. “Desktop software has to ship in sync with [PC maker] sales cycles. There is no holiday rush with servers.”<\/p>\n

\u5728\u5b8c\u6210\u4e86Windows 2000\u4e4b\u540e\uff0cWindows\u56e2\u961f\u6240\u4f5c\u51fa\u7684\u6700\u5927\u51b3\u5b9a\u662f\u5728Whistler\u4ea7\u54c1\u7ebf\u4e2d\u533a\u5206\u4e2a\u4eba\u7248\uff08client\uff09\u548c\u670d\u52a1\u5668\u7248\uff08server\uff09\u4e24\u79cd\u53d1\u884c\u7248\uff0c\u540e\u6765\uff08Whistler\u4ea7\u54c1\u7ebf\u7684\u8fd9\u4e24\u4e2a\u53d1\u884c\u7248\uff09\u5206\u522b\u6210\u4e3a\u4e86Windows XP\u548cWindows Server 2003\u3002\u300e\u8fd9\u6837\u505a\u4f7f\u6211\u4eec\u80fd\u6bd4\u8fc7\u53bb\u66f4\u52a0\u4e13\u6ce8\u4e8e\u670d\u52a1\u5668\u7528\u6237\uff0c\u8fd9\u4e9b\u7528\u6237\u8981\u6c42\u7cfb\u7edf\u7a33\u82e5\u78d0\u77f3\uff0c\u300fThompson\u544a\u8bc9\u6211\u4eec\uff0c\u300e\u684c\u9762\u7248\u8f6f\u4ef6\u7684\u53d1\u5e03\u9700\u8981\u4e0ePC\u5236\u9020\u5546\u7684\u9500\u552e\u5468\u671f\u540c\u6b65\uff0c\u800c\u5bf9\u670d\u52a1\u5668\u6765\u8bf4\uff0c\u5e76\u6ca1\u6709\u4ec0\u4e48\u8d76\u7740\u5047\u671f\uff08\u51fa\u65b0\u54c1\uff09\u4e4b\u8bf4\u3002\u300f<\/p>\n

Windows Server 2003: The Road To Gold, Part Two: Developing Windows<\/strong><\/a><\/p>\n

Windows Server 2003\uff1a\u9ec4\u91d1\u4e4b\u8def\uff0c\u7b2c\u4e8c\u7bc7\uff1aWindows\u5f00\u53d1\u90a3\u4e9b\u4e8b<\/strong><\/p>\n

Paul Thurrott | Jan 30, 2001\uff082001\u5e741\u670830\u65e5\uff0c\u539f\u6587\u65e5\u671f\u5982\u6b64\uff08\u53ef\u81ea\u884c\u9a8c\u8bc1\uff09\uff0c\u4e0d\u8981\u95ee\u6211\u4e3a\u4ec0\u4e48\uff09<\/p>\n

One element about the NT family of operating systems–which evolved from Windows NT to Windows 2000, XP, and, now, Windows Server 2003–that has remained unchanged over the years, though the details have changed dramatically, is the build process. Somewhere deep in the bowels of Microsoft, virtually every day, at least one Windows product is compiled, or built, into executable code that can be tested internally by the dev, or development teams. For Windows Server 2003, this process is consummated in Building 26 on Microsoft’s sprawling Redmond campus, where banks of PCs and CD duplicating machines churn almost constantly under the watchful eyes of several engineers.<\/p>\n

NT\u5bb6\u65cf\u64cd\u4f5c\u7cfb\u7edf\u2014\u2014\u56ca\u62ec\u4e86\u4eceWindows NT\u5230Windows 2000\u3001XP\uff0c\u4ee5\u53ca\u6700\u8fd1\u7684Windows Server 2003\u2014\u2014\u6709\u4e00\u4e2a\u591a\u5e74\u6765\u672a\u66fe\u6539\u53d8\u7684\u8981\u7d20\uff08\u5c3d\u7ba1\u7ec6\u8282\u4e0a\u5927\u76f8\u5f84\u5ead\uff09\uff0c\u90a3\u5c31\u662f\u5f00\u53d1\u8fdb\u7a0b\u3002\u5fae\u8f6f\u5185\u90e8\u6df1\u5904\u7684\u67d0\u4e2a\u5730\u65b9\uff0c\u5dee\u4e0d\u591a\u6bcf\u5929\u90fd\u6709\u81f3\u5c11\u4e00\u4e2aWindows\u4ea7\u54c1\u88ab\u7f16\u8bd1\uff08\u6216\u6784\u5efa\uff09\u4e3a\u53ef\u6267\u884c\u7684\u4ee3\u7801\uff0c\u4ee5\u5728\u516c\u53f8\u5185\u90e8\u4f9b\u5f00\u53d1\u8005\u3001\u6216\u5f00\u53d1\u56e2\u961f\u8fdb\u884c\u6d4b\u8bd5\u3002\u5bf9\u4e8eWindows Server 2003\u800c\u8a00\uff0c\u8fd9\u4e00\u8fc7\u7a0b\u662f\u5728\u5fae\u8f6f\u904d\u5730\u5f00\u82b1\u7684Redmond\u56ed\u533a26\u53f7\u697c\u5706\u6ee1\u5b8c\u6210\u7684\uff0c\u5728\u90a3\u91cc\uff0c\u6709\u6210\u5806\u7684PC\u548cCD\u590d\u5236\u673a\u5668\u88ab\u597d\u51e0\u4f4d\u5de5\u7a0b\u5e08\u7559\u5fc3\u770b\u62a4\u7740\u3002<\/p>\n

The details of NT–excuse me, Windows–development have changed dramatically since the project first started in the late 1980’s. “Back in the early days, we started with 6 people,” Microsoft Distinguished Engineer and Windows Server Architect Mark Lucovsky told me. “Now there are 5000 member of the Windows team, plus an additional 5000 contributing partners, generating over 50 million lines of code for Windows Server 2003. Getting all those people going in the same direction, cranking out code, is an enormous task. Building the results of their work, compiling and linking it into the executable and other components that make up a Windows CD is a 12 to 13 hour process that is done every day of the week. It’s the biggest software engineering task ever attempted. There are no other software projects like this.” And Microsoft compiles the whole thing–all 50+ million lines of code, almost every single day, he said. “We’re evolving the development environment all the time,” Lucovsky noted.<\/p>\n

\u6709\u5173NT\u2014\u2014\u4e0d\u597d\u610f\u601d\uff0c\u662fWindows\u2014\u2014\u7684\u5f00\u53d1\u7ec6\u8282\uff0c\u81ea\u9879\u76ee\u6700\u521d\u4e8e1980\u5e74\u4ee3\u5f00\u59cb\u81f3\u4eca\uff0c\u5df2\u53d1\u751f\u4e86\u7ffb\u5929\u8986\u5730\u7684\u53d8\u5316\u3002\u300e\u65e9\u5148\u7684\u65f6\u5019\uff0c\u6211\u4eec\u662f\u4ece6\u4e2a\u4eba\u7684\u56e2\u961f\u5f00\u59cb\u7684\uff0c\u300f\u5fae\u8f6f\u5353\u8d8a\u7684\u5de5\u7a0b\u5e08\u548cWindows Server\u67b6\u6784\u5e08Mark Lucovsky\u544a\u8bc9\u6211\u3002\u300e\u73b0\u5728Windows\u56e2\u961f\u67095000\u4eba\uff0c\u53e6\u5916\u518d\u52a0\u4e0a5000\u540d\u8d21\u732e\u5408\u4f5c\u4f19\u4f34\uff0c\u4e3aWindows Server 2003\u521b\u4f5c\u51fa\u8d85\u8fc75000\u4e07\u884c\u4ee3\u7801\u3002\u7edf\u9886\u6240\u6709\u8fd9\u4e9b\u4eba\u671d\u7740\u4e00\u4e2a\u5171\u540c\u7684\u65b9\u5411\u524d\u8fdb\uff0c\u5171\u540c\u64b0\u5199\u4ee3\u7801\uff0c\u662f\u4e00\u9879\u8270\u5de8\u7684\u5de5\u4f5c\u3002\u5c06\u6240\u6709\u8fd9\u4e9b\u4eba\u7684\u5de5\u4f5c\u8fdb\u884c\u751f\u6210\uff0c\u7f16\u8bd1\u5e76\u8fde\u63a5\u6210\u4e3a\u6784\u6210Windows CD\u7684\u53ef\u6267\u884c\u6587\u4ef6\u548c\u5176\u5b83\u7ec4\u4ef6\uff0c\u662f\u6bcf\u5468\u6bcf\u5929\u90fd\u8981\u82b1\u4e0a12\u523013\u4e2a\u5c0f\u65f6\u53bb\u505a\u7684\u4e8b\u3002\u8fd9\u4e43\u662f\uff08\u6211\u4eec\uff09\u6240\u5c1d\u8bd5\u8fc7\u7684\u6700\u5927\u7684\u8f6f\u4ef6\u5de5\u7a0b\u4efb\u52a1\uff0c\u518d\u4e5f\u6ca1\u6709\u5176\u5b83\u7684\u8f6f\u4ef6\u5de5\u7a0b\u80fd\u4e0e\u4e4b\u76f8\u6bd4\u4e86\u3002\u300f\u5fae\u8f6f\u51e0\u4e4e\u6bcf\u4e00\u5929\u90fd\u4f1a\u628a\u6574\u4e2a\u9879\u76ee\u2014\u2014\u5168\u90e8\u76845000\u4e07\u884c\u4ee3\u7801\u8fdb\u884c\u4e00\u6b21\u7f16\u8bd1\uff0c\u4ed6\u8bf4\uff0c\u300e\u6211\u4eec\u65e0\u65f6\u4e0d\u523b\u90fd\u5728\u4fc3\u8fdb\u5f00\u53d1\u73af\u5883\u7684\u8fdb\u5316\uff0c\u300fLucovsky\u6307\u51fa\u3002<\/p>\n

“When we turn the crank, we compile the whole thing,” he said. “We have to be able to reproduce the system at any point in time as well. So developers check in code, we press a button, and out comes a system. We should be able to reproduce that [build] three years in the future, using the various tools, compilers, and scripts we used at that time.”<\/p>\n

\u300e\u6211\u4eec\u8f6c\u52a8\u6447\u628a\uff0c\u7136\u540e\u5c31\u6574\u4e2a\u7f16\u8bd1\u4e00\u904d\uff0c\u300f\u4ed6\u8bf4\uff0c\u300e\u4e5f\u53ef\u4ee5\u91cd\u65b0\u6784\u5efa\u4efb\u4f55\u65f6\u95f4\u8282\u70b9\u4e0a\u5f53\u65f6\u7cfb\u7edf\u7684\u6837\u5b50\u3002\u5f00\u53d1\u8005\u4eec\u7b7e\u5165\u4ee3\u7801\uff0c\u6211\u4eec\u6309\u4e00\u4e2a\u6309\u94ae\uff0c\uff08\u7f16\u8bd1\u597d\u7684\uff09\u7cfb\u7edf\u5c31\u4ece\u53e6\u4e00\u5934\u51fa\u6765\u4e86\u3002\u5373\u4f7f\u662f\u5728\u672a\u6765\u7684\u4e09\u5e74\uff0c\u6211\u4eec\u5e94\u8be5\u4e5f\u53ef\u4ee5\u7528\u5f53\u65f6\u90a3\u4e00\u5806\u5de5\u5177\u3001\u7f16\u8bd1\u5668\u548c\u811a\u672c\uff0c\u6765\u91cd\u65b0\u6784\u5efa\u4e4b\u524d\u6240\u7f16\u8bd1\u8fc7\u7684\u67d0\u4e2a\u7248\u672c\u3002\u300f<\/p>\n

David Thompson, corporate vice president of the Windows Server Product Group at Microsoft, elaborated on the process. “The key here is that we built up the system over the years, advancing it in three dimensions,” he said. “First is the product itself. Second is the way we engineer the product. And third is the way we interact with a broader and broader set of customers. The product evolution is pretty straightforward. The source code control system we use now is new, because we really pushed the scale of the previous version with Windows 2000. Mark [Lucovsky] personally lead the development of the new system and introduced it post-2000. We started with some acquired technology. We now do have a staged build [for the first time]. But every day the [staged builds] are rolled up into the total build. So we can scale but maintain stability–we know where we stand every day.”<\/p>\n

David Thompson\uff0c\u5fae\u8f6fWindows Server\u4ea7\u54c1\u7ec4\u7684\u6267\u884c\u526f\u603b\u88c1\uff0c\u8be6\u7ec6\u8bf4\u660e\u4e86\u6574\u4e2a\u8fc7\u7a0b\u3002\u300e\u5173\u952e\u70b9\u5728\u4e8e\uff0c\u5728\u5f00\u53d1\u8fd9\u5957\u7cfb\u7edf\u7684\u8fd9\u4e9b\u5e74\u95f4\uff0c\u6211\u4eec\u4ece\u4e09\u4e2a\u7ef4\u5ea6\u53bb\u5b8c\u5584\u5b83\uff0c\u300f\u4ed6\u8bf4\uff0c\u300e\u4e00\u662f\u4ea7\u54c1\u672c\u8eab\uff0c\u4e8c\u662f\u6211\u4eec\u7b56\u5212\u4ea7\u54c1\u7684\u65b9\u5f0f\uff0c\u4e09\u662f\u6211\u4eec\u4e0e\u4e0d\u65ad\u6269\u5c55\u7684\u7528\u6237\u7fa4\u8fdb\u884c\u4ea4\u6d41\u4e92\u52a8\u7684\u65b9\u5f0f\u3002\u4ea7\u54c1\u672c\u8eab\u7684\u8fdb\u5316\u5f88\u76f4\u63a5\u4e86\u5f53\u3002\u73b0\u5728\u4f7f\u7528\u7684\u6e90\u4ee3\u7801\u63a7\u5236\u7cfb\u7edf\u662f\u5168\u65b0\u7684\uff0c\u56e0\u4e3a\u4e3a\u4e86Windows 2000\uff0c\u6211\u4eec\u663e\u8457\u6269\u5c55\u4e86\u5176\u4f53\u91cf\u3002Mark\uff08Lucovsky\uff09\u72ec\u7acb\u9886\u5bfc\u4e86\u65b0\uff08\u4ee3\u7801\u63a7\u5236\uff09\u7cfb\u7edf\u7684\u7814\u53d1\uff0c\u5e76\u5728Windows 2000\u4e4b\u540e\u5c06\u5176\u5f15\u8fdb\u3002\u6211\u4eec\u9996\u5148\u4ece\u719f\u77e5\u7684\u6280\u672f\u5f00\u59cb\uff0c\u73b0\u5728\u6211\u4eec\uff08\u7b2c\u4e00\u6b21\uff09\u62e5\u6709\u4e86\u9636\u68af\u5f0f\u751f\u6210\uff0c\u4e0d\u8fc7\u6bcf\u5929\uff08\u9636\u68af\u5f0f\u751f\u6210\u7684\u7ed3\u679c\uff09\u90fd\u4f1a\u5e76\u5165\u4e3b\u7ebf\u3002\u7531\u6b64\u6211\u4eec\u53ef\u4ee5\u5728\u6269\u5f20\uff08\u7cfb\u7edf\u4f53\u91cf\uff09\u7684\u540c\u65f6\u4fdd\u6301\u7a33\u5b9a\u6027\u2014\u2014\u6211\u4eec\u5f88\u6e05\u695a\u81ea\u5df1\u6bcf\u5929\u6240\u5904\u7684\u4f4d\u7f6e\u3002\u300f<\/p>\n

Just eat it: Microsoft serves up dog food<\/strong><\/p>\n

\u5403\u5c31\u662f\u4e86\uff1a\u5fae\u8f6f\u7ed9\u5927\u5bb6\u6d3e\u996d<\/strong><\/p>\n

Lucovsky reminisced a bit about the early days, when the first NT prototypes were built in his office with only a single person overseeing the process. That person would simply send out an email to the NT team when a new build was ready, and then 50 people or so would “eat their own dog food,” testing the build on their own systems and run stress tests. “I used to just walk around the building and write down the problems we found,” Lucovsky said. “That’s how it was pre-NT 3.51. Now we have 7 builds labs. Dave [Thompson] has his own [build lab] for the 1200 people he oversees. The main build lab cranks out the official build, which goes out to thousands of people daily. Notification is automatic, and is sent out in multiple stages using the backbone servers across the campus. It’s all automated. Those little things have now scaled up.”<\/p>\n

Lucovsky\u56de\u5fc6\u4e86\u4e00\u4e0b\u65e9\u5e74\u95f4\u5728\u4ed6\u7684\u529e\u516c\u5ba4\u6784\u5efa\u7b2c\u4e00\u4e2aNT\u539f\u578b\u3001\u5e76\u4e14\u53ea\u6709\u4e00\u4e2a\u4eba\u76d1\u7763\u7740\u6574\u4e2a\u8fc7\u7a0b\u7684\u65e5\u5b50\u3002\u90a3\u4e2a\uff08\u505a\u76d1\u7763\u7684\uff09\u4eba\u53ea\u662f\u7b80\u5355\u5730\u53d1\u4e00\u5c01\u90ae\u4ef6\u7ed9NT\u56e2\u961f\uff0c\u544a\u8bc9\u5927\u5bb6\u65b0\u7f16\u8bd1\u7684\u7248\u672c\u51fa\u6765\u4e86\uff0c\u7136\u540e\u5927\u7ea6\u5c31\u4f1a\u670950\u4e2a\u4eba\u6765\u300e\u9886\u8d70\u81ea\u5df1\u90a3\u4efd\u996d\u300f\uff0c\u5230\u4ed6\u4eec\u81ea\u5df1\u7684\u673a\u5668\u4e0a\u6d4b\u8bd5\u65b0\u7f16\u8bd1\u7248\u672c\u3001\u8fd0\u884c\u538b\u529b\u6d4b\u8bd5\u7b49\u7b49\u3002\u300e\u6211\u66fe\u7ecf\u53ea\u9700\u8981\u5728\u5927\u697c\u91cc\u8f6c\u4e00\u8f6c\uff0c\u628a\u5927\u5bb6\u53d1\u73b0\u7684\u95ee\u9898\u8bb0\u4e0b\u6765\u800c\u5df2\uff0c\u300fLucovsky\u8bf4\uff0c\u300e\u90a3\u662fNT 3.51\u4e4b\u524d\u7684\u4e8b\u4e86\u3002\u73b0\u5728\u6211\u4eec\u67097\u4e2a\u6784\u5efa\u5b9e\u9a8c\u5ba4\uff0cDave\uff08Thompson\uff09\u81ea\u5df1\u5c31\u7ba1\u7740\u4e00\u4e2a\uff0c\u7edf\u7ba1\u7740\u7ea61200\u4eba\u7684\u56e2\u961f\u3002\u4e3b\u6784\u5efa\u5b9e\u9a8c\u5ba4\u751f\u6210\u5b98\u65b9build\uff0c\u6bcf\u5929\u5206\u53d1\u7ed9\u597d\u51e0\u5343\u4eba\uff0c\u901a\u77e5\u673a\u5236\u662f\u5168\u81ea\u52a8\u7684\uff0c\u901a\u8fc7\u6a2a\u8d2f\u6574\u4e2a\u56ed\u533a\u7684\u9aa8\u5e72\u670d\u52a1\u5668\u9010\u7ea7\u5206\u53d1\uff0c\u6574\u4e2a\u6d41\u7a0b\u90fd\u81ea\u52a8\u5316\u3002\u65e9\u5e74\u95f4\u7684\u90a3\u4e9b\u7b80\u5355\u7684\u4e8b\u60c5\u5982\u4eca\u6269\u5f20\u4e86\u4e0d\u5c11\u3002\u300f<\/p>\n","protected":false},"excerpt":{"rendered":"

\u539f\u6587\u94fe\u63a5\uff1ahttps:\/\/blogs.msdn.microsoft.com\/oldnewthing\/20031 […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[],"class_list":["post-2332","post","type-post","status-publish","format-standard","hentry","category-tont_history"],"_links":{"self":[{"href":"https:\/\/www.aoisnow.net\/blog\/wp-json\/wp\/v2\/posts\/2332","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.aoisnow.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.aoisnow.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.aoisnow.net\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.aoisnow.net\/blog\/wp-json\/wp\/v2\/comments?post=2332"}],"version-history":[{"count":0,"href":"https:\/\/www.aoisnow.net\/blog\/wp-json\/wp\/v2\/posts\/2332\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.aoisnow.net\/blog\/wp-json\/wp\/v2\/media?parent=2332"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.aoisnow.net\/blog\/wp-json\/wp\/v2\/categories?post=2332"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.aoisnow.net\/blog\/wp-json\/wp\/v2\/tags?post=2332"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}