76. When Novell asked Microsoft why it removed the Explorer interfaces and browsing extensions, Microsoft claimed that it did not have the time and resources to complete their development. But in fact, the Explorer interfaces and browsing extensions had been complete and functional before Microsoft removed them. Microsoft's real reasons for pulling the interfaces and browsing extensions were twofold: to delay the development of Novell's software programs and products, including WordPerfect, which had to be reworked to function through a different set of interfaces designed for Microsoft's software programs and products; and to hide the more advanced capabilities of Novell's office productivity applications from users of Windows 95. Novell had no choice but to spend more than a year recreating the functionality of Windows' integrated browsing functions. As Gates knew and intended, withdrawing the documentation of the browsing APIs caused Novell, in Microsoft's own words, to re-invent the wheel and divert resources from innovations on behalf of consumers. Microsoft's applications developers, by contrast, had unfettered access to the integrated browsing extensions all along. 77. Thereafter, when Microsoft released Windows 95 and Office 95, at virtually the same time, Microsoft suddenly reversed course and documented the programming interfaces. Doing so voided the alternatives that Microsoft previously forced Novell to expend an entire year developing and, at the precise moment when WordPerfect needed to enter the market, forced Novell to spend additional time designing basic functions of WordPerfect all over again. 78. Microsoft's anti-competitive integration of browsing functions into Windows delayed the release of Novell's office productivity applications for Windows 95. These acts also degraded the functionality of Novell's applications, which never were able to provide Novell's customers with as robust an implementation of the browsing extensions as they otherwise could have provided. In short, "Microsoft's conduct with respect to browsers is a prominent and immediate example of the pattern of anticompetitive practices undertaken by Microsoft with the purpose and effect of maintaining its PC operating system monopoly and extending that monopoly to other related markets," including the office productivity applications markets alleged herein. Gov't Compl. 1 13. By virtue of Microsoft's anti-competitive integration of browsing functions into Windows 95, for which Microsoft was held liable in the Government Suit, Novell's applications were delayed in reaching the markets and provided consumers with less value. 79. In addition to documentation of the crucial browsing extensions, Microsoft withheld other technical specifications concerning Windows 95, and in some instances affirmatively misrepresented the specifications, further delaying Novell's delivery of WordPerfect and related applications for the Windows 95 platform. 80. Microsoft refused to publish the APIs that were used to place items on the Windows Clipboard, although its own developers had the documentation. The Clipboard provided a location for storing information until it was "pasted" into another application. Novell ultimately had to forgo this functionality in its applications because the expenditure of time and resources required to duplicate the hidden APIs was prohibitive, so Novell could not provide the same richness of data integration that Microsoft's applications could provide. 81. Further, Microsoft misrepresented that Windows 95 would operate as an exclusively "32-bit" system, meaning it would process 32 bits of data at once. A bit --short for binary digit - is the smallest unit of information a computer can hold. The beta versions of Windows 95 indicated that it would be an entirely 32-bit system, rather than a 16-bit system, as all previous versions of Windows were. This representation was critical, because applications written for a 32-bit operating system would not function properly on a 16-bit system. Novell relied upon Microsoft's representations and developed its applications to run on an entirely 32-bit system. After Novell completed its PerfectOffice 3.0 suite of office productivity applications, including WordPerfect and Quattro Pro, Microsoft disclosed that Windows 95 would not be a purely 32-bit system. Microsoft's deception forced Novell to expend considerable time and resources to redesign its applications, significantly delaying their release. Microsoft's own applications developers knew that Windows 95 would not be an entirely 32-bit operating system and, as a consequence, Microsoft was able to release its office productivity applications almost immediately upon the release of Windows 95. 82. Through these and other anticompetitive acts, Microsoft put Novell "on a treadmill," forcing Novell's developers to expend significant time obtaining information and creating functionalities that Microsoft gave to its own applications developers through secret documentation of hidden APIs. 83. In addition to withholding technical information, Microsoft created and controlled new "industry" standards and established unjustified certification requirements to delay the release of Novell's applications and to impair their performance for Novell's customers. 84. First, as discussed above, Microsoft excluded from the markets the "OpenDoc" technology for sharing information among applications, by using its monopoly power to force a different standard upon the industry. Because CIL was designing OpenDoc to run across multiple platforms, including MS-DOS, DR-DOS, Windows, OS/2, and Macintosh, OpenDoc threatened the applications barrier to entry that protected Microsoft's Windows monopoly. 85. Microsoft responded to this competitive threat by preventing CIL from making OpenDoc compatible with Windows 95. For example, Microsoft routinely required all ISVs to execute nondisclosure agreements as a condition of receiving the information they needed to develop their applications. These agreements, however, contained terms that uniquely targeted ISVs who were members of CIL, by preventing their employees who worked on OpenDoc from receiving Windows 95 betas or specifications, which effectively prevented CIL from initially developing OpenDoc for Windows 95. In addition, Microsoft required ISVs working with a Windows 95 beta to agree that they would not work on OpenDoc for two years. While Microsoft eventually dropped this requirement, its impact had immediate anticompetitive effects on OpenDoc's development. 86. Further, Microsoft unilaterally announced that OLE would be incorporated directly into Windows, instead of existing independently of the operating system as a technology to be adopted or rejected by ISVs, depending on their assessments of its technical merit. Microsoft then required OLE-compatibility as a condition of Microsoft's certification of an application's compatibility with Windows 95. This certification requirement was a significant barrier to entry into the applications markets, because Microsoft represented to the industry that any application lacking the certification could not be trusted to run on Windows 95. By exploiting this barrier to entry, Microsoft forced ISVs to make their applications OLE-compatible. Furthermore, Microsoft ensured that only applications using its tools, and not those of its competitors, would reach customers. This anticompetitive behavior by Microsoft is similar to the behavior described in the Government Suit with respect to Microsoft's efforts to force ISVs to use Microsoft's implementation of Java. "Specifically, in the First Wave agreements that it signed with dozens of ISVs in 1997 and 1998, Microsoft conditioned early Windows 98 and Windows NT betas, other technical information, and the right to use certain Microsoft seals of approval on the agreement of those ISVs to use Microsoft's version of the Windows [Java virtual machines] as the 'default.' Findings of Fact T 401. 87. There was no valid technical or business reason for requiring OLE-compatibility as a condition of the Windows 95 certification; OpenDoc was even more capable of providing the same linking and embedding functions, and in the absence of the certification requirement and other anticompetitive acts, OpenDoc and OLE would have continued to compete on their technical merits. Indeed, Microsoft initially announced that applications using OpenDoc would be deemed OLE-compatible, and would receive Microsoft's certification for Windows 95, because OpenDoc was a "superset" of OLE, meaning it provided every function of OLE, and more. Later, after Novell, other ISVs and CIL were far advanced in their efforts to develop and use OpenDoc, Microsoft announced that applications using OpenDoc would not receive automatic certification, and might not receive certification at all. 88. Seeing that Microsoft's anticompetitive acts would ensure the demise of OpenDoc, ISVs were left with no choice but to adopt Microsoft's proprietary OLE protocol as the de facto industry standard for linking and embedding. Even after making OLE the industry standard, however, Microsoft still withheld specifications and final, debugged versions of OLE until after Microsoft released its competing applications. Microsoft's anticompetitive acts concerning OLE further increased the "time-to-market" lead that Microsoft's office productivity applications unlawfully achieved over Novell's applications. 89. Second, Microsoft required office productivity applications seeking Windows 95 certification to be compatible with the very different Windows NT, which is an operating system for larger and more powerful computers that are used as "servers" to link numerous PCs (and peripherals) across an organization into a network. There was no justification for this requirement. Further, Windows 95 and Windows NT were so dissimilar that an application running on one system could not run on the other without substantial modification. Novell expended significant development resources to make its applications compatible with Windows NT, resulting in further delay in the release of Novell's applications for Windows 95. 90. Third, Microsoft unilaterally made the proprietary Rich Text Format ("RTF") of Microsoft Word the standard file format for text-based documents in applications developed for Windows. Upon capturing the standard, Microsoft strategically withheld the specification to injure competitors, including Novell. 91. As Microsoft knew, a truly standard file format that was open to all ISVs would have enhanced competition in the market for word processing applications, because such a standard allows the exchange of text files between different word processing applications used by different customers. A user wishing to exchange a text file with a second user running a different word processing application could simply convert his file to the standard format, and the second user then could convert the file from the standard format into his own word processor's format. Thus, a law firm, for instance, could continue to use WordPerfect (which was the favorite word processor of the legal profession), so long as it could convert and edit client documents created in Microsoft Word, if that is what clients happened to use. Microsoft knew that if it controlled the convertibility of documents through its control of the RTF standard, then Microsoft would be able to exclude competing word processing applications from the market and force customers to adopt Microsoft Word, as it soon did. 92. The specifications for RTF were readily available to Microsoft's applications developers, because RTF was the format they themselves developed for Microsoft's office productivity applications. Microsoft withheld the RTF specifications from Novell, however, forcing Novell to engage in a perpetual, costly effort to comply with a critical "industry standard" that was, in reality, nothing more than the preference of its chief competitor, Word. Indeed, whenever Word changed its own file format, Microsoft unilaterally and identically changed the RTF standard for Windows, forcing Novell and other ISVs constantly to redevelop their applications. In this mariner, Microsoft gave Word a permanent, insurmountable lead in time-to-market, and made document conversions difficult for users otherwise interested in running non-Microsoft applications. Many WordPerfect users were thus forced to switch to Microsoft Word, which predictably monopolized the word processing market. 93. Fourth, Microsoft unilaterally announced that other features of Word were to be considered Windows standards. One important example is the "tool bar," which typically runs across the top of the PC's screen in applications operating on Windows. Microsoft's tool bar originated in the Microsoft Office applications, such as Word and Excel, while ISVs such as Novell developed competing features, such as WordPerfect's more widely admired "button bar." Unable to design a better feature than WordPerfect's, Microsoft simply declared its toolbar to be the Windows standard, supplanting WordPerfect's button bar and other competitors' offerings. As in the case of RTF, Microsoft forced Novell to delay its time-to-market while redeveloping its applications to an inferior standard. Because these standards were lifted directly from Microsoft's own applications, those applications, by definition, were always "compatible" with the standards. 94. Fifth, Microsoft made other inferior features de facto industry standards, by preventing Novell and other competitors from presenting certain of their own features, such as Novell's QuickFinder, on the desktop. The government alleged and the Court held in the Government Suit that Microsoft was liable for excluding the features of certain other ISVs from the desktop in the same manner. See 253 F.3d at 62, 64; Findings of Fact 1212-214; Gov't Compl. 11 24-25. 95. QuickFinder, Novell's search technology, was faster and more advanced than Microsoft's own "find" capability. QuickFinder enabled users to create search criteria across the computer's different storage devices and to search files by name, text, and date. Because Microsoft prevented Novell from presenting QuickFinder on the desktop, QuickFinder could only be used when running WordPerfect; Microsoft's own finder technology, with exclusive display on the desktop, could be used anywhere in the computing environment, gaining an unfair advantage over Novell's otherwise superior technology.
~ Merkey v The Internet et al Docs ~ Yahoeuvre ~ tuxrocks.com (SCO cases legal docs) ~ scofacts.org ~ eagle.petrofsky.org ~ Zen's Den ~ Yahoo SCOX Message Board ~ Lamlaw ~ Microsoft Watch ~ Groklaw ~ Korgwal - a Groklaw mirror ~ nosoftwarepatents.com ~ Flame Warriors ~ SCOXE Wars ~ Get your Merkey Number here! ~ Digital Law Online
Make a new account