He has dismissed Novell's claims by granting Microsoft's motion for judgment as a matter of law. But not because of Microsoft's innocence: "I recognize that this conclusion may appear somewhat disturbing because arguably it rewards Microsoft for unsavory behavior in the applications market," the judge wrote. So despite the fact that the first jury was 11 to 1 for Novell, this judge has decided that no reasonable jury can rule for Novell, and it escapes on a technicality.

Yes, Novell can appeal. They surely can, if they want to. And they have now said they do intend to. The last time this same judge tried [PDF] something similar to this, Novell appealed, and he was overturned on appeal. So despite what you are reading in the media, this is not the end of this story. Litigation isn't like a football game. It's not over in a day, not until all the appeals are completed.

Jump To Comments

07/16/2012 - 509 - MEMORANDUM DECISION/OPINION re 396 Motion for Judgment as a Matter of Law. Signed by Judge J. Frederick Motz on 7/16/12 (alt) (Entered: 07/16/2012)

07/16/2012 - 510 - ORDER granting 396 Motion for Judgment as a Matter of Law. Signed by Judge J. Frederick Motz (alt) (Entered: 07/16/2012)

07/16/2012 - 511 - JUDGMENT in favor of Microsoft and against Novell - CASE CLOSED. Signed by Judge J. Frederick Motz (alt) (Entered: 07/16/2012)

Jump to Update.

The ideas the judge put forward in the hearing show up in the memorandum explaining his decision. For example, he states, tech naif that he seems to be, that Novell could have gotten its product to market in time for the launch of Windows 95 if they'd only used what they already had. Novell's testimony was that they tried, but what they had wasn't complete, and some of it had changed, and when they asked for help, they couldn't get any.^*

And then there is this:

First, as stated in section I, supra, there is no evidence that anyone at Novell made any complaint to anyone at Microsoft who could have reversed the decision to withdraw support for the namespace extension APIs.

Q: And what did you complain about?

A: I complained about being denied access to application programming interfaces that people at Novell -- at Microsoft had access to.

Q: Did you make such complaints on multiple occasions to Mr. Gates?

A: Yes, in person and in writing.

Q: And what if any reaction did Mr. Gates have to your complaints about undocumented calls and interfaces?

A: He refused to talk about it.

The judge also says that there is no way Novell could ever have challenged Microsoft in the middleware area, so it's not antitrust. Here's his reasoning:

Microsoft’s position is based upon the Findings of Fact made in the government case, upon which Novell’s claim is founded. Judge Jackson found that “[c]urrently, no middleware product exposes enough APIs to allow independent software vendors (“ISVs”) profitably to write full-featured personal productivity applications that rely solely on . . . APIs [of the middleware product itself].” Finding of Fact ¶ 28. In contrast, Novell argues the exposure of APIs that would result in “something less” than the writing of full-featured personal product applications is sufficient to constitute a threat to Microsoft’s monopoly. (Novell Opp’n at 89–90). This argument is based on the concept, expressed by Noll, that diminishing, as opposed to nearly eliminating, the barrier to entry that protected Microsoft’s monopoly in the PC operating systems market was itself sufficient. (Noll, Trial Tr. at 1926, Nov. 15, 2011). To the extent this testimony is based on the premise that other companies would produce similar middleware that, in combination with Novell’s products, would diminish the barrier to entry, there is no evidence such other products existed.

The findings made in the government case made clear that Microsoft possessed its monopoly by virtue of what Judge Jackson described as a “chicken-and-egg” problem. As Judge Jackson described:

The overwhelming majority of consumers will only use a PC operating system for which there already exists a large and varied set of high- quality, full-featured applications, and for which it seems relatively certain that new types of applications and new versions of existing applications will continue to be marketed at pace with those written for other operating systems. Unfortunately for firms whose products do not fit that bill, the porting of applications from one operating system to another is a costly process. Consequently, software developers generally write applications first, and often exclusively, for the operating system that is already used by a dominant share of all PC users. Users do not want to invest in an operating system until it is clear that the system will support generations of applications that will meet their needs, and developers do not want to invest in writing or quickly porting applications for an operating system until it is clear that there will be a sizeable and stable market for it.

Finding of Fact ¶ 30. Other findings made by Judge Jackson are to the same effect. See Findings of Fact ¶¶ 36, 37, 39, 40.22

In light of these findings, it cannot be reasoned, as Novell argues, that Microsoft’s operating systems monopoly would have been threatened by a middleware product that exposed only a limited number of APIs that permitted ISVs to write only a specialized set of applications to it. The barrier to entry that Judge Jackson found in the government case was created by a “chicken-and-egg” problem, and that problem arose because ISVs would write only to programs that supported full-featured personal productivity applications. See Finding of Fact ¶ 30. In other words, contrary to what Novell argues in support of what Microsoft has aptly described as its “watered-down version” of the third requirement, Microsoft’s monopoly in the PC operating systems market was threatened not by a product that exposed only a limited number of its own APIs but only by a product that exposed sufficient APIs to entice full-featured applications to be written to it. (See Microsoft Mem. at 77–78). Otherwise stated, diminishment of the barrier to entry is not sufficient because mere diminishment would not have affected the PC operating systems market. In order to constitute a realistic threat to Microsoft’s monopoly in that market, elimination (or, at least, near elimination) of the barrier to entry through development of full-featured applications using APIs from middleware that ran on operating systems other than Windows was required.

Well, I'm not surprised at all. I only hope that if Novell does appeal, it also asks for a new judge, so it needn't waste more time and money trudging uphill against the wind with this one, who for the second time now has ruled that no jury is required, that he can just hand Microsoft a win himself.

That, of course, is exactly why the US legal system has a hierarchy of appeals, because it does sometimes happen that a judge, for whatever reason, just can't see your case the way you think he should. And the truth is a judge can rule against you if he really, really wants to. He can find a way. But then the appeals court can address any unfairness or bias. They did so the last time this judge tried to hand Microsoft a win bypassing a jury trial, and they can do so again, if they feel it's justified. So it's not good news for Novell, for sure, but I doubt they are surprised, and it's not the end of the road.

___________
^*An excerpt from the testimony of Novell's witness Adam Harral:

Q. BY MR. JOHNSON: All right. Did you ever talk to Premier Support about the NameSpace extension functionality?

A. I did.

Q. Do you recall when you first spoke with Premier Support about this functionality? And we can put a time frame on it. Did you talk to Premier Support about this functionality prior to receiving the M6 beta?

A. I did not -- did I talk to them about it prior to receiving the M6 beta? There wouldn't have been any discussion with them prior about the beta except for probing for information on the extension. When we got M6, that we finally got the information that we had been told that we would have somebody compile against, build our code against.

So there would have been only small queries about having the documentation so we could proceed and hook in what we had already been working on.

Q. And how about after you received the M6 beta? Did you have conversation with Premier Support after about the NameSpace extension functionality?

A. Yes. Because of the lack -- we were not as concerned about the lack of documentation over a short period of time because having -- that was part of the reason for the Premier Support. In the past I had -- when we had things that needed clarification from Microsoft, we would call them, and sometimes they would get the developers who had actually worked on the Windows features together with us so that we could talk directly.

I remember one time that I spent a lot of time working on the presentation of menus. That was one of the -- as well as an architect, we had our own features that we worked on, as well. And I was working on menus, and the liaison that I had at the time I was discussing with the developer of Microsoft the things I was trying to solve. My Premier Support liaison said, this is really interesting to me. And he says, I'm taking notes on this.

And later on, he published an article in Microsoft Systems Journal. And so it was really neat that the liaisons were also a means of disseminating a lot of information about how to solve problems in the operating system.

And so that was -- after we had M6 we were not too concerned over the short-term because we had this access to Premier Support where we could engage them and try and solve any immediate issues that we had until we had the documentation.

Q. Can you give us any kind of estimate for how many times you personally spoke with Premier Support regarding the NameSpace extension functionality prior to October of '99 -- 1994?

A. I remember three times because I wasn't the only liaison. But I remember three times.

Q. Were other liaisons to your knowledge having similar conversations?

A. Yes. Especially one of the liaisons would have been, was in the WordPerfect mail group, Lynn Monson, and he was also a liaison. And the WordPerfect mail group was very, very interested in the extensions, as well. I know that he was having conversations with them.

Q. Prior to the launch of Windows 95, which occurred in August of 1995, did Microsoft ever provide the full documentation with the NameSpace extensions to Novell?

A. No, they did not.

Q. When did you find out, if you did, that the NameSpace extension functionality which was, had been partially provided in the M6 beta would no longer be provided by Microsoft?

A. I found out on a call to Microsoft to the Premier Support in around the October time frame. I -- we were -- we had a couple of issues that we needed clarification on, and one of them had to do with our file open dialog and some of the NameSpaces. And we approached Premier Support and asked the question, and they told us that the NameSpace extensions and what we were asking about was no longer something that they could discuss through Premier Support at Microsoft.

Q. Let me show you what has been marked Plaintiff's Exhibit 227, which is in the binder in front of you. Can you tell us what this document is?

A. This is the same terse document that we were looking at before. But it's from the next release of the beta.

Q. That would have been the M7 release?

A. I think it's the M7 release because it says at the top it's for the 10-28-1994.

Q. And did you review this documentation when it was provided by Microsoft?

A. Yes, we did. I did.

Q. And did this documentation provide the full documentation that Microsoft had told you would be coming in M7?

A. It did not. It, in fact -- some of the pieces that we had had been removed from it.

Q. What do you mean some of the pieces had been removed from it?

A. The ability for us to present our NameSpaces to Windows 95 shell for it to negotiate where we were going to place our NameSpace items, being able to store what the user did when they interacted with our NameSpace and being able to enhance the common dialogs were all missing.

Q. And can you with reference to this document -- and this may be too difficult. But with reference to the document, can you tell us what had been taken away in terms of the APIs we had been discussing earlier?

A. So I guess in terms of what -- what was impacted?

Q. Yes.

A. Okay. So shared code would no longer be able to use the Windows 95 common dialogs to provide the features for all of the products that we were providing for and for the third-party people that were also licensing the technology. We would not have the ability to integrate the e-mail product, the image browser for showing graphics from our presentation product into the -- into the shell so everybody, everybody who would have lived in the shell would not have access to our features like they had in our -- in our file open dialog and places that we had inside of our product. And so if people were living outside, they wouldn't gain the advantage. If they were living inside, they would have those things.

But also because you couldn't provide the common dialogs the other question is, then, that also put at risk us being able to talk to Windows 95's regular shell extensions that it provided.

So now the question was, how do I get the recycle bin to show up? It's not just a directory. It's actually a place across multiple places. Am I going to have to rewrite the recycle bin and duplicate exactly what it does? Network neighborhood was a bringing together of all the networks. And now if I have -- I have code and shared code that can talk to a network, but how do I present those networks? How do I know what ones even the user has access to because all of that is already defined in the shell in that NameSpace. So I've got to go talk to that NameSpace to be able to represent the same view that they have out of the shell in my product.

And so we had a twofold problem. One was we couldn't expose what we had out to the customers who had lived in the shell; and we were having a problem getting all the new Windows 95 pieces from the shell into our product. And we became an either/or kind of world.

Q. During Microsoft's opening in this case to the jury, Microsoft's lawyer describes -- described the NameSpace extension APIs, as quote, four little APIs, close quote, out of approximately 2500 APIs within Windows 95. You've heard this stated that the NameSpace extension APIs were, quote, just a very small piece of what the operating system was being written to provide to companies like Novell, close quote.

Do you agree with Microsoft's lawyer that the NameSpace extension APIs were just four little APIs?

A. No; because when we were looking through the APIs before, we talked about -- I pointed out initialize shell extension. That's how you start up something that wants to live in the shell. It's one API. If you remove that, there would be no way to start up a shell, okay. So there are different weights to the importance of things.

We're not talking about changing the color that's the background of a picture, you know, of a little image on a desktop here. The browser APIs stopped anybody from finding a place to put things on the shell. The view APIs stop them from showing anything from the shell. The common dialog APIs stopped them from getting at those things in the common dialog and adding things for people beyond what the shell provided. And the persist just made sure they couldn't -- even if they could do that, they wouldn't be able to save it so that the user would have that same consistent view from one time to the next.

Those were -- the four removed APIs, that's the impact that we saw in removing those four little APIs. You can do something to my house, but if the thing you decide to do is remove the door and close it up, that's a pretty significant thing to do to your house.

Update: I have done the memorandum as text, and I'll point out a couple of things. First, the judge didn't believe Bill Gates' testimony either, that stability was the reason for undocumenting the APIs. The judge agrees that there was sufficient evidence that this was pretextual:

Here, although I am granting Microsoft's Rule 50 motion for the reasons stated in section V, I believe the text of Gates's email provides sufficient evidence upon which a jury could find that the reasons for the October 3, 1994 decision to withdraw support for the namespace extensions were pretextual. Therefore, if the only question raised by the Rule 50 motion were whether the jury was asked to weigh the factors that led Microsoft to make the October 3, 1994 decision, I would deny the Rule 50 motion.

Here it is, so you can make up your own mind:

*********************

IN THE UNITED STATES DISTRICT COURT
FOR THE DISTRICT OF UTAH
CENTRAL DIVISION

v.

MICROSOFT CORP.

Civil No. 2:04-cv-01045-JFM

___________________

OPINION

Novell, Inc. instituted this action against Microsoft under §4 of the Clayton Act, 15 U.S.C. §15, alleging violations of the Sherman Act, 15 U.S.C § §1-2.¹ Initially, Novell asserted three sets of claims: (1) that Microsoft violated §2 of the Sherman Act and caused antitrust injury to Novell by unlawfully monopolizing and attempting to monopolize the software applications market; (2) that Microsoft violated §2 of the Sherman Act and caused antitrust injury to Novell by unlawfully maintaining its monopoly in the operating systems market; and (3) that Microsoft violated §1 of the Sherman Act and caused antitrust injury to Novell by engaging in exclusionary agreements in unreasonable restraint of trade. Novell has abandoned the third claim, see Novell, Inc. v. Microsoft Corp., 429 F. App'x. 254, 258 n.7 (4th Cir. 2011), and the Fourth Circuit affirmed a ruling I made that Novell's monopolization and attempted

1

monopolization claims in the applications market are barred by limitations. See Novell, Inc. v. Microsoft Corp., No. MDL 1332, No. 05-cv-1087(JFM), 2005 WL 1398643, at *5 (D. Md. June 10, 2005), aff'd, 505 F.3d 302, 322 (4th Cir. 2007).² Thus, the only remaining claim is the second: that Microsoft violated §2 of the Sherman Act and caused antitrust injury to Novell by maintaining its monopoly in the operating systems market. For this claim, Novell advanced two somewhat different theories: the "franchise theory" and the "middleware theory." ³

That claim was tried to a jury. After an approximately eight-week trial, the jury hung and was unable to return a verdict.⁴ Now pending is Microsoft's motion under Fed. R. Civ. P. 50(b) for judgment as a matter of law. Although Novell presented evidence from which a jury could

2

have found that Microsoft engaged in aggressive conduct, perhaps to monopolize or attempt to monopolize the applications market, it did not present evidence sufficient for a jury to find that Microsoft committed any acts that violated §2 in maintaining its monopoly in the operating systems market. Therefore, Microsoft's Rule 50 motion will be granted.⁵

I.

In the mid-1990s, Microsoft, which for many years had possessed a monopoly in the PC operating systems market, was developing a new operating system. This operating system became known as Windows 95 and was released for sale to the public on August 24, 1995.⁶ Microsoft also sold a word processing application, Word, and a spreadsheet application, Excel. Beginning in 1990, Microsoft marketed these two applications together in an office productivity suite, Office. (Gibb, Trial Tr. at 823, Oct. 26, 2011; Frankenberg, Trial Tr. at 1080, Nov. 7, 2011).

WordPerfect, a word processing application, was originally developed by WordPerfect Corporation, a company located in Orem, Utah. WordPerfect competed with Word and was

3

particularly popular with customers who used character-based DOS operating systems. In the mid-1980s and early 1990s, WordPerfect was the acknowledged "king of the hill" on the DOS platform. (Peterson, Trial Tr. at 4667, Dec. 7, 2011; see Middleton, Trial Tr. at 4178 (Dec. 13, 2008 Video Dep.), Dec. 5, 2011). Although Microsoft manufactured and sold a character-based operating system known as MS-DOS, as early as 1984 it began concentrating on an alternative type of operating system, known as a graphic user interface ("GUI") system. (Gates, Trial Tr. at 2709, 2713, Nov. 21, 2011). As Microsoft developed Windows, its GUI-based operating system, Bill Gates, the Chief Executive Officer of Microsoft, attempted to persuade Pete Peterson, then a principal of WordPerfect, to write for Windows. ⁷ (Peterson, Trial Tr. at 4708-09, Dec. 7, 2011). WordPerfect, however, was reluctant to devote significant resources to developing applications to run on Windows because Peterson "was not going to put any effort into producing a product that would put another penny in Bill Gates' pocket." (Bushman, Trial Tr. at 3152-53, Nov. 28, 2011). In May 1990, Microsoft released Windows 3.0. WordPerfect did not release a Windows 3.0-compatible WordPerfect program until eighteen months later, in November 1991. (Middleton, Trial Tr. at 4187 (Dec. 13, 2008 Video Dep.), Dec. 5, 2011)

Novell announced its intent to purchase WordPerfect on March 21, 1994 and completed the purchase on June 24, 1994. At the same time, Novell purchased Quattro Pro, a spreadsheet application that had been developed by Borland, Inc., a company located in Scotts Valley, California. (Frankenberg, Trial Tr. at 1080, Nov. 7, 2011). Robert Frankenberg, who was the Chief Executive Officer of Novell after its purchase of WordPerfect and Quattro Pro, saw that GUI operating systems were the wave of the future, and he was more inclined than Peterson to

4

work with Microsoft and to develop versions of its applications for Windows. (Id. at 1040). The WordPerfect products for Windows had generally not been well received by the market, and Frankenberg recognized the need to improve those products. In November 1994, Novell released WordPerfect 6.1 for Windows, which met with favorable industry reviews. (See Pl.'s Exs. 239 & 241). Frankenberg also saw the need for Novell to market an office productivity suite, and in late December 1994 WordPerfect successfully released a Windows-compatible suite, PerfectOffice 3.0.⁸ (Frankenberg, Trial Tr. at 1012, Nov. 7, 2011). Although Frankenberg recognized that Microsoft had "a huge head start" in the suite market, in January of 1994 approximately 74% of users had yet to choose among the available suite products. (Id. at 1008-09, 1063; Pl.'s Ex. 412 at 2).

On June 10, 1994, shortly before Novell finalized its purchase of WordPerfect Corporation and Quattro Pro, Microsoft provided independent software vendors ("ISVs"), including WordPerfect, with the Milestone 6 beta version of Windows 95. (See Harral, Trial Tr. at 434-35, Oct. 24, 2011). Novell was extremely enthusiastic about Windows 95 when it was released in beta form to ISVs. Frankenberg testified that Windows 95 was a significant step forward and that Novell was "very excited and very interested" in it. (Frankenberg, Trial Tr. at 1225-26, Nov. 8, 2011). He further testified that Novell's business strategy was to "take advantage of the capabilities in Windows 95." (Id. at 1226). The testimony of other Novell witnesses was to the same effect. (Harral, Trial Tr. at 253-54, 256-57, Oct. 20, 2011; Richardson, Trial Tr. at 607, Oct. 25, 2011; Gibb, Trial Tr. at 788, Oct. 26, 2011; Noll, Trial Tr. at 1911, Nov. 15, 2011).

5

On October 3, 1994, Microsoft withdrew support for the part of this beta version making namespace extension application programming interfaces ("APIs") accessible to ISVs. (See Pl.'s Ex. 1). Prior to the hearing on the Rule 50 motion, Novell contended that the act of withdrawing support for the namespace extension APIs was itself an unlawful act because beta versions of a release cannot be modified except to fix bugs discovered during the course of the beta process. Novell did not, however, press this argument at the Rule 50 hearing. Its reason for not doing so is clear. Although one Novell software developer, Adam Harral, did so suggest, (Harral, Trial Tr. at 303, Oct. 20, 2011), all of the other evidence was to the contrary. Microsoft's licensing agreement with WordPerfect/Novell provided that the beta version "may be substantially modified prior to first commercial shipment," and that WordPerfect "assume[d] the entire risk with respect to the use of the beta." (Def.'s Ex. 18 at 1 ¶2; Def.'s Ex. 19 ¶2). Moreover, numerous witnesses, including Frankenberg and other persons who during the relevant time frame had been employed by Novell, testified that they understood the beta versions of Windows 95 "could change" and "might change" prior to commercial release. (Frankenberg, Trial Tr. at 1201, 1204-05, 1209, Nov. 8, 2011; Larsen, Trial Tr. at 3603, 3654-58, Nov. 30, 2011). Novell's expert witnesses likewise agreed with this proposition. (Alepin, Trial Tr. at 1555-56, Nov. 10, 2011; Noll, Trial Tr. at 1878, Nov. 15, 2011).

The parties dispute the reasons that Microsoft decided, on October 3, 1994, to withdraw support for the namespace extension APIs. Microsoft argues it had legitimate "stability" and "robustness" concerns, particularly because, as Novell's own technical expert, Ronald Alepin, conceded, an ISV that wrote a bad program using the namespace extension APIs could cause Windows 95 to crash. (Alepin, Trial Tr. at 1601-02, Nov. 10, 2011; see Gates, Trial Tr. at 2781-82, Nov. 21, 2011). Moreover, according to Microsoft, there was an internal debate at

6

Microsoft between the Windows team and another team, working on what was known as the "Cairo Shell," about the design of the namespace extension APIs. (Gates, Trial Tr. at 2792-93, Nov. 21, 2011; Muglia, Trial Tr. at 3385-90, 3397-3400, Nov. 29, 2011; Nakajima, Trial Tr. at 3763-64, 3768-71, Dec. 1, 2011; Belfiore, Trial Tr. at 4269-71, 4278-80, Dec. 5, 2011). Finally, Microsoft contends that the namespace extension APIs did not provide the functionalities Gates had contemplated. (Gates, Trial Tr. at 2786-87, 2800-04, Nov. 21, 2011; Pl.'s Ex. 1).

Novell argues that all of the reasons Microsoft articulated for the October 3, 1994 decision were pretextual, and that, as revealed in an internal email Gates authored, the real reason for withdrawing support for the namespace extension APIs was to provide a competitive advantage to Microsoft's own office productivity suite, Office. (See Pl.'s Ex. 1). In the October 3, 1994 email announcing the withdrawal decision, Gates stated: "I have decided that we should not publish these extensions. We should wait until we have a way to do a high level of integration that will be harder for the likes of Notes [a Lotus product], WordPerfect to achieve, and which will give Office a real advantage." (Id.).⁹

According to Novell, Gates's decision to withdraw support for the namespace extension

7

APIs was consistent with a plan that had been discussed and adopted by Microsoft executives in June 1993, at a retreat at Gates's estate on Hood Canal. That plan called for Windows 95 to be shipped with limited extensibility, reserving for Microsoft's applications the functionality that the namespace extension APIs provided. (See Pl.'s Ex. 61). The plan's purpose was to give Microsoft's applications "a very significant lead over [Microsoft's] competitors, and make [Microsoft's] competitors' products look 'old.'" (Id. at MS 00971223). Microsoft was concerned that if the extensibility were not withheld from ISVs, Word and Excel would have to "battle against their competitors on even turf. Given that Lotus and WordPerfect have largely caught up, [Word and Excel] almost certainly lose ground – if not in market share, then in margins." (Pl.'s Ex. 62 at MX 1389851).¹⁰

After Microsoft withdrew support for the namespace extension APIs in October 1994, Novell was confronted with three options: (1) to continue to write its own programs using the namespace extension APIs that were no longer supported by Microsoft but were still accessible to ISVs in possession of the beta version; (2) to use Microsoft's common file open dialog (instead of the namespace extension APIs), which remained available to ISVs after the withdrawal of support for the namespace extension APIs; or (3) to write its own customized file open dialog. (See Harral, Trial Tr. at 342-44, Oct. 20, 2011). Although it explored the first option, Novell concluded that it could not use the previously released documentation for the namespace extension APIs because Microsoft was no longer providing any assistance for writing programs based upon those APIs. (Id. at 345-46). Novell also concluded that the second option

8

was unsatisfactory because to use it would "impose[] the standards of the operating system" on developers. (Id. at 271). Specifically, using Microsoft's common file open dialog would have caused Novell to stop providing features that it had provided to its customers in the past, thereby "disenfranchis[ing] [its] customer base." (Harral, Trial Tr. at 504, Oct. 24, 2011; Richardson, Trial Tr. at 629-30, Oct. 25, 2011; see Gibb, Trial Tr. at 891, Oct. 26, 2011). Therefore, in January 1995 Novell stopped trying to reproduce the lost functionality and chose the third option, beginning to write its own customized file open dialog by having two developers, Harral and Richardson, work around the clock, sometimes in excess of 80 hours per week, under Gibb's supervision. (See Harral, Trial Tr. at 350-54, Oct. 20, 2011).

When Gates decided to withdraw support for the namespace extension APIs, some Microsoft executives were concerned that the decision would not be well received by ISVs. In that regard, Brad Silverberg wrote an email to other Microsoft executives, including Gates, on October 5, 1994, predicting there would be a "firestorm of protests" from ISVs, including WordPerfect, that were using the shell extensions. (Pl.'s Ex. 220 at MX 5103184). However, shortly before Silverberg's email was written, Brad Struss, who headed the Windows 95 team for Microsoft's Development Relations Group and worked closely with Novell, reported that Novell "ha[d] not begun any work on IShellFolder, IShellView, etc.," i.e. the namespace extensions. (Def.'s Ex. 17 at MX 6109491). Struss's email also included the results of a survey Microsoft conducted of major ISVs to ascertain if ISVs in fact were using the namespace extension APIs. (Id.). On October 12, 1994, after the decision to withdraw support for the namespace extension APIs was made, Struss advised Microsoft executives by email that Microsoft was "notifying ISVs about the namespace api changes." (Def.'s Ex. 3 at MX 6055840). He reported that "WP [WordPerfect] . . . appear[s] to be OK with this." (Id.). Struss also testified at trial that he told

9

others at Microsoft "what [he] knew to be true or what had been communicated to [him] from WordPerfect, which is that they were not using it and they were not dependent upon it." (Struss, Trial Tr. at 3270, Nov. 28, 2011).

Novell presented no witness to rebut this testimony or to contradict what was said in the October 12 email. There also is no evidence in the record that Novell ever complained to Microsoft about Microsoft's decision to withdraw support for the namespace extension APIs. Further, there is no evidence that any top-level executive at Novell was involved in the decision-making process concerning the choice of the third option, i.e., writing of customized code for WordPerfect. Frankenberg testified that any action that could jeopardize the timely release of WordPerfect or Quattro Pro would have been referred to some or all of four senior executives: Ad Rietveld, Executive Vice President of the Novell Applications Group; Dave Moon, Senior Vice President of the Business Applications Group; Mark Calkins, Vice President and General Manager of the Business Applications Group; and Glenn Mella, Vice President of Marketing. (Frankenberg, Trial Tr. at 1140-42, 1179-80, Nov. 7-8, 2011). Moreover, Frankenberg agreed that in any business or organization faced with an important decision, a formal memorandum would normally be presented to the senior executives laying out the concerns, issues, and considerations facing that business and making some strategic or tactical choice. (Id. at 1181, Nov. 8, 2011). Novell presented no evidence that any such memorandum was ever written, and Frankenberg testified that he knew of no evidence that Calkins, Mella, Moon, or Rietveld were presented with a decision about how to respond to Gates's decision to withdraw support for the namespace extension APIs. (Id. at 1181-82).¹¹ Instead, Novell assigned responsibility for supervising the writing of code for a custom file open dialog for WordPerfect and Quattro Pro to

10

Gibb, a middle manager, who, in turn, assigned the responsibility for writing the code to Harral and Richardson.

Microsoft sought commitments from several of the most important ISVs to ship their Window 95-compatible applications within 90 days of the release of Windows 95. (See Pl.'s Ex. 148). Frederick Warren-Boulton, Novell's economic expert, testified that if Novell's product was shipped according to that timeframe, the application would have been "in pretty good shape," and that his damage calculations are based on the assumption that Novell could have released their product according to the agreement, but for the alleged anticompetitive conduct. (Warren-Boulton, Trial Tr. at 2417-24, Nov. 17, 2011).

According to Novell, because it took one year for Novell to write its customized file open dialog, Novell was unable to meet that timetable. (Novell Mem. Opp'n Rule 50 Mot. ("Novell Opp'n") at 69, ECF No. 501). Microsoft strongly disputes this assertion. It argues Quattro Pro--the spreadsheet component of PerfectOffice--was not ready to be released to manufacturing until well into 1996, and that this explains the delay in Novell's marketing of PerfectOffice. (See Microsoft Mem. Supp. Rule 50 Mot. ("Microsoft Mem.") at 48, ECF No. 494). An internal Novell memorandum indicated that although in late 1994 Novell had been considering a September 30, 1995, release date for PerfectOffice for Windows 95, the Quattro Pro team then "believe[d] this [was] barely achievable with all their resources and with no additional functionality." (Def.'s Ex. 211). On March 1, 1995, Bruce Brereton, Novell's Vice President of the Business Applications Unit, wrote in an email that because Quattro Pro believed that "December 30 is a more realistic date," Novell had decided to "move . . . the Storm [PerfectOffice for Windows 95] RTM [release to manufacturer] date back by one month (to December 30) and have put WP on the same time-line as Storm." (Def.'s Ex. 221).

11

In light of Brereton's email, Frankenberg testified that as of March 1, 1995 the plan became to get PerfectOffice out, i.e., released to manufacturing, on December 30, 1995. (Frankenberg, Trial Tr. at 1220-21, Nov. 8, 2011). In March 1995 a "markets requirement report" prepared by the applications group ranked "Quattro Pro delivering late" as the highest "overall risk" for the PerfectOffice development project. (Def.'s Ex. 223 at 41). David LeFevre, who was then an employee of Novell (he subsequently became an employee of Microsoft), testified that he attended daily meetings in 1995 with Gibb and others where the matters discussed included "all the different product challenges" of releasing PerfectOffice in a timely manner. (LeFevre, Trial Tr. at 4037, Dec. 2, 2011). According to LeFevre, "the product that was causing the biggest problem was Quattro Pro." (Id. at 4045-47).

Karl Ford, then the lead developer for the user interface in WordPerfect for Windows 95, also attended regularly scheduled meetings in 1995, and he learned that "the schedule" was at risk because of Quattro Pro. (Ford, Trial Tr. at 3691-92, 3699-3700, Nov. 30, 2011). The problem of having Quattro Pro ready to be released to manufacturing became even more severe toward the end of 1995, when many developers left Quattro Pro for other employment in Silicon Valley, the area where Scotts Valley--home of Quattro Pro--was located. (See Def.'s Ex. 230). On December 23, 1995, four months after the release of Windows 95, Brereton wrote an email to Frankenberg and others reporting that "this past Thursday/Friday about 15 additional people [at Quattro Pro] submitted their resignations," leaving the Quattro Pro development team in Scotts Valley, California with "just 2 people." (Id.). In January 1996, Nolan Larsen, an executive of Novell, traveled to Scotts Valley and found that it "was kind of a train wreck" and that "[t]hose people who had not resigned were kind of walking around a little bit shell shocked. So it was – it was very chaotic." (Larsen, Trial Tr. at 3620, Nov. 30, 2011). Larsen and LeFevre testified

12

that Quattro Pro was not ready to be shipped by March 1996. (Id. at 3624-25; LeFevre, Trial Tr. at 4062-63, Dec. 2, 2011).

Gibb, however, testified that Quattro Pro was not "critical path" because the delay in the development of shared code on which Harral and Richardson were working was the only issue holding up the release. (Gibb, Trial Tr. at 804-07, Oct. 26, 2011). Ultimately, Quattro Pro and PerfectOffice were not released until May 1996, after the sale to Corel Corporation in March 1996. As described in section III, infra, according to Novell, this delay prevented WordPerfect and PerfectOffice from obtaining a sizeable share of the Windows 95-compatible word processing and suite markets. This, in turn, Novell argues, prevented Novell products from becoming successful "middleware," which could have been an effective competitor with Windows 95 in the operating systems market.

On November 8, 2004, Novell and Microsoft entered into a settlement agreement under which any claims not pled in Novell's draft complaint in this action, filed Nov. 12, 2004, were released. (See Settlement Agreement, Holley Decl. Supp. Microsoft Mem., Ex. A, ECF No. 497). The complaint in this action asserted claims for damages suffered by Novell's "lost sales of office productivity applications and a diminution in value of Novell's assets, reputation and goodwill in amounts to be proven at trial." (Compl. ¶155). The complaint further alleged, in the prayer for relief, that Microsoft maintained its monopoly in three specific markets, the operating systems market, the word processing applications market, and the spreadsheet applications market. (Id. at 67).

II.

A Rule 50 motion "test[s] whether there is a legally sufficient evidentiary basis for a reasonable jury to find for the moving party." Keylon v. City of Albuquerque, 535 F.3d 1210,

13

1215 (10th Cir. 2008). Judgment as a matter of law is appropriate "only if the evidence points but one way and is susceptible to no reasonable inferences which may support the opposing party's position." Tyler v. RE/MAX Mountain States, Inc., 232 F.3d 808, 812 (10th Cir. 2008) (citing Finley v. United States, 82 F.3d 966, 968 (10th Cir. 1996)); see Miller v. Auto. Club of N.M., Inc., 420 F.3d 1098, 1131 (10th Cir. 2005) ("Judgment as a matter of law is only appropriate when 'a party has been fully heard on an issue and there is no legally sufficient evidentiary basis for a reasonable jury to find for that party on that issue.'") (quoting Fed. R. Civ. P. 50(a)(1)). All reasonable inferences are drawn in favor of the non-moving party, and the court does not "weigh the evidence, pass on the credibility of witnesses, or substitute [its] conclusions for that of the jury." Miller v. Eby Realty Grp., LLC, 396 F.3d 1105, 1110 (10th Cir. 2005). The decisive question is whether "the plaintiff has arguably proven a legally sufficient claim." Dillon v. Mountain Coal Co., 569 F.3d 1215, 1219 (10th Cir. 2009).

III.

Novell's theory may be briefly stated. According to Novell, Microsoft violated §2 of the Sherman Act when it decided in October 1994 to withdraw support for the namespace extension APIs, a decision that Novell asserts led to Microsoft's maintenance of its monopoly in the operating systems market.¹² This decision was made personally by Gates, who was motivated by a desire to provide time for Microsoft to catch up with Novell and Lotus in development of its office productivity applications, Word, Excel, and Office. (See Pl.'s Ex. 1). As a result of Microsoft's decision, Novell could no longer use the namespace extension APIs and lost valuable time in developing WordPerfect, Quattro Pro, and PerfectOffice. (See Rule 50 Hr'g Tr.

14

at 172-74, ECF No. 507). Novell was not able to put those applications on the market until May 1996. (See Warren-Boulton, Trial Tr. at 2090, Nov. 16, 2011). This had the effect of preventing WordPerfect and PerfectOffice from becoming effective competitors with Word and Office in the applications market. Moreover, in the longer run, by preventing Novell's applications from being widely used with Windows 95, the decision to withdraw support for the namespace extension APIs prevented WordPerfect and PerfectOffice (and two other Novell programs, AppWare and OpenDoc) from being accepted in the market as middleware. (See Rule 50 Hr'g Tr. at 119-27). If Novell's products had been accepted in the market as middleware, ISVs would have begun to write programs using APIs exposed by the Novell applications, thereby reducing the barrier to entry into the PC operating systems market and threatening Microsoft's monopoly in that market. (Id. at 194-96).

Microsoft argues that this theory is unique and unprecedented because it is based upon conduct that occurred in one market, the software applications market, to assert a Sherman Act §2 claim in an entirely different market, the operating systems market. (See id. at 6). That alone, according to Microsoft, is fatal to Novell's claim. (Id.). Novell counters that although Microsoft, through Gates, was motivated by a desire to disadvantage Novell's applications in favor of Microsoft's own applications, its conduct was intentional, and a jury could appropriately find that its conduct had anticompetitive effects in the operating systems market. (Id. at 165-68). According to Novell, that is sufficient to establish a §2 violation.

I need not decide this issue because, even assuming Novell's argument is correct, its claim nevertheless fails for three separate and independent reasons: (1) Microsoft's conduct was not anticompetitive within the meaning of the Sherman Act; (2) Novell did not present sufficient evidence from which a jury could find that its products would have been successfully developed

15

as middleware; and (3) there is no underlying business reality to the claims. Each of these reasons is examined in section V. Before discussing those issues, however, I will first address two arguments made by Microsoft that I believe lack merit.

IV.¹³

A.

Microsoft argues it has articulated legitimate business reasons for the decision Gates made on October 3, 1994, to withdraw support for the namespace extension APIs and that the fact-finder is not to weigh the factors that led to a particular decision in assessing whether that decision was a violation of antitrust laws. (See Microsoft Mem. at 110 (citing Aspen Skiing Co. v. Aspen Highlands Skiing Corp., 472 U.S. 585, 597, 605 (1985); Multistate Legal Studies v. Harcourt Brace Jovanovich Legal & Prof'l Publ'ns, 63 F.3d 1540, 1550 (10th Cir. 1995))). The fallacy in that contention is that in this case, the jury was not asked to weigh the factors that Microsoft articulated in support of the October 3, 1994 decision, but rather to decide whether those articulated reasons were pretextual in light of Gates's email suggesting the decision was made to give Microsoft application developers time to catch up with Microsoft's major competitors, Novell and Lotus. Fact-finders are frequently called upon to answer this question of pretext, particularly in the field of employment discrimination law. See, e.g., Reeves v. Sanderson Plumbing Prods., 530 U.S. 133, 153-54 (2000) (holding that a plaintiff "introduced enough evidence for a jury to reject [the defendant's explanation]" as pretextual); Townsend v. Lumbermens Mut. Cas. Co., 204 F.3d 1232, 1243-44 (10th Cir. 2002) (holding that a jury "could reasonably have found" a defendant employer's stated reasons for demoting an employee "were

16

pretextual, potentially entitling him to a finding of discrimination").

Here, although I am granting Microsoft's Rule 50 motion for the reasons stated in section V, I believe the text of Gates's email provides sufficient evidence upon which a jury could find that the reasons for the October 3, 1994 decision to withdraw support for the namespace extensions were pretextual. Therefore, if the only question raised by the Rule 50 motion were whether the jury was asked to weigh the factors that led Microsoft to make the October 3, 1994 decision, I would deny the Rule 50 motion.

B.

As stated in section I, supra, on November 8, 2004, Microsoft and Novell entered into a settlement agreement pursuant to which Novell released any and all claims it had against Microsoft with the exception of claims asserted in a draft complaint that became the complaint in this action. In Count I of the complaint (the only count remaining in the case), Novell alleged that as a result of Microsoft's alleged misconduct, it "was damaged by, without limitation, lost sales of office productivity applications and a diminution in the value of Novell's assets, reputation, and goodwill in amounts to be proven at trial." (Compl. §155). The term "office productivity applications" is defined earlier in the complaint as "word processing and spreadsheet applications." (Id. §24).

Microsoft argues that because the only Novell applications allegedly damaged by Microsoft's alleged misconduct were the word processing application, WordPerfect, and spreadsheet application, Quattro Pro, Novell released Microsoft from any claim that it had for damages to Novell's office productivity suite, PerfectOffice. (See Microsoft Mem. at 126-27). Microsoft also points out that the complaint does not refer in any way to the suite market. (See id. at 128-30).

17

In entering into the release--which certainly was a significant business transaction-- Microsoft had the right to rely upon the language of the release and the language of the draft complaint referred to in the release. Those documents made no reference whatsoever to PerfectOffice. Moreover, in deciding to enter into the settlement agreement, Microsoft may have considered the omission of any reference to PerfectOffice to be significant because, as the evidence at trial established, by 1994 it was clear that the office suite market stood separate and apart from the word processing and spreadsheet applications markets. (See Gibb, Trial Tr. at 823, Oct. 26, 2011; Frankenberg, Trial Tr. at 1080, Nov. 7, 2011). As Frankenberg's testimony highlighted during the trial, Novell as well as Microsoft understood the importance of the suite market in 1994. Frankenberg testified that in 1994 approximately three-quarters of the suite market was open, and Novell was planning to make substantial inroads into it. (See Frankenberg, Trial Tr. at 1008-09, 1063, Nov. 7, 2011; Pl.'s Ex. 412 at 2).

Nevertheless, Microsoft's argument fails. The complaint referred not only to damages resulting from lost sales of office productivity applications but also damages resulting from "a diminution in the value of Novell's assets, reputation, and goodwill in amounts to be proven at trial." (Compl. §155). Novell's damages expert, Frederick Warren-Boulton, did not calculate damages on a product-by-product basis but instead on the basis of the decrease in the sales price paid to Novell by Corel, allegedly caused by Microsoft's withdrawal of support for the namespace extension APIs. (See Warren-Boulton, Trial Tr. at 2094-98, Nov. 16, 2011). This decrease in sales price falls well within the "diminution in value" category of damages referred to in the complaint and thus was not released by the agreement entered into November 8, 1994.

18

V.¹⁴

I will now discuss the three reasons Microsoft's Rule 50 motion should be granted.

A.

A monopolist is free "to exercise [its] own independent discretion as to parties with whom [it] will deal." Verizon Commc'ns, Inc. v. Law Offices of Curtis V. Trinko, LLP, 540 U.S. 398, 408 (2004); see United States v. Colgate & Co., 250 U.S. 300, 307 (1919). It is well established that a monopolist generally has no duty to cooperate with its competitors. See, e.g., Trinko, 540 U.S. at 408; Aspen Skiing, 472 U.S. at 600; Image Technical Servs., Inc., v. Eastman Kodak Co., 125 F.3d 1195, 1209 (9th Cir. 1997). In accordance with this principle, Novell's counsel properly conceded during the hearing on Microsoft's Rule 50 motion that it would not have been unlawful for Microsoft to keep the namespace extension APIs to itself and never disclose them to ISVs. (Rule 50 Hr'g Tr. at 191-92). Novell argues, however, that Microsoft's conduct was anticompetitive within the meaning of §2 of the Sherman Act because when it decided to withdraw support for the namespace extension APIs in October 1994, it intentionally made a decision that had an adverse effect upon competition in the operating systems market. (See id. at 165-68).

The distinction Novell seeks to draw is unpersuasive. A decision not to publish the namespace extension APIs in the first place is as "intentional" as a decision to withdraw support for the namespace extension APIs after they have been published. Therefore, the principle that a monopolist generally has no duty to cooperate with a competitor governs unless the act of withdrawing support for the namespace extension APIs was itself anticompetitive.¹⁵

19

The decision to withdraw support for the namespace extension APIs therefore did not constitute a violation of §2 of the Sherman Act unless it was made deceptively for an anticompetitive purpose or unless, by making it, Microsoft terminated a previously existing profitable relationship.¹⁶ See, e.g., Aspen Skiing, 472 U.S. at 599-604; Four Corners Nephrology Assocs., P.C. v. Mercy Med. Ctr. of Durango, 582 F.3d 1216, 1224-25 (10th Cir. 2009); Christy Sports, LLC v. Deer Valley Resort Co., 555 F.3d 1188, 1197 (10th Cir. 2009).

Any deception claim necessarily is based upon the premise that Microsoft withdrew support for the namespace extension APIs because it knew that Novell was using those APIs in the development of its applications and that, by withdrawing support for those APIs, Microsoft knew that Novell would fall behind schedule. There is no evidence to support this premise.¹⁷

20

First, as just stated, because of the undisputed industry practice, Microsoft had no reason to believe that Novell was relying upon the documentation for the namespace extension APIs contained in the beta version Microsoft released to ISVs. (See Def.'s Ex. 17 at MX 6109491). Second, the evidence establishes that shortly before the decision to withdraw the namespace extension APIs was made, Brad Struss of Microsoft was advised that Novell was not yet using the namespace extension APIs, (id.), and that after the decision, he contacted Novell and was notified that "WP . . . appear[s] to be OK with this." (Def.'s Ex. 3 at MX 6055840). Likewise, Struss testified at trial that he told others at Microsoft "what [he] knew to be true or what had been communicated to [him] from WordPerfect, which is that they were not using it and they were not dependent upon it." (Struss, Trial Tr. at 3270, Nov. 28, 2011). Novell did not rebut this evidence in any way, and there is no evidence that Novell made any contemporaneous complaint to anyone at Microsoft about withdrawal of support for the namespace extension APIs.

The claim that Microsoft purposely destroyed a preexisting profitable business relationship is equally flawed. Preliminarily, it should be noted that Aspen Skiing, upon which Novell bases its argument, has been characterized by the Supreme Court as being "at or near the outer boundary of §2 liability." Trinko, 540 U.S. at 409. The facts in Aspen Skiing were unusual, involving a defendant's exploitation of a situation largely bestowed upon it by Mother Nature. The defendant owned three mountains in a ski resort area and engaged in sharp business practices to prevent the owner of the fourth mountain from competing effectively for skiing

21

business. See Aspen Skiing, 472 U.S. at 589-95. In contrast, what Novell is asserting here is that Microsoft could not withdraw from Novell a product that was the result of Microsoft's own ingenuity and that Novell believed would give it optimal advantage in its competition with Microsoft in the applications market.

There is no evidence that Microsoft withdrew support for the namespace extension APIs for the purpose of terminating its relationship with Novell. The final version of Windows 95 made available to all ISVs, including Novell, contained Microsoft's common file open dialog, and Novell never advised Microsoft that this dialog was insufficient for its own purposes. (See Harral, Trial Tr. at 502, Oct. 24, 2011; Gibb, Trial Tr. at 847-49, Oct. 26, 2011; Alepin, Trial Tr. at 1604, Nov. 10, 2011). Moreover, after it withdrew support for the namespace extension APIs, Microsoft continued to provide assistance to Novell and never terminated their relationship. (Struss, Trial Tr. at 3253-54, 3259-69, Nov. 28, 2011; Def.'s Ex. 2 at MX 6062581; see Frankenberg, Trial Tr. at 1131, Nov. 7 , 2011 (stating that he is "sure" people in the operating system group at Microsoft were trying to help WordPerfect/Novell produce a great application for Windows 95)).

For these reasons, Novell has not created a jury question on the issue of whether Microsoft's conduct was anticompetitive.

B.

The evidence is undisputed that during 1995 Novell's focus was on writing office productivity programs that would run on Windows 95. In Novell's view, Microsoft's new operating system was a "significant step forward" and a "wonderful evolution" in technology. (Harral, Trial Tr. at 253-54, 256-57, Oct. 20, 2011; Frankenberg, Trial Tr. at 1225-26, Nov. 8, 2011; see Gibb, Trial Tr. at 788, Oct. 26, 2011; Noll, Trial Tr. at 1911, Nov. 15, 2011).

22

Therefore, as Frankenberg acknowledged, in the short term Microsoft's share of the operating systems market would have increased, not decreased, if it had not withdrawn support for the namespace extension APIs. (See Frankenberg, Trial Tr. at 1226-28, Nov. 8, 2011; Noll, Trial Tr. at 1949-50, Nov. 15, 2011).¹⁸

Therefore, Novell's theory necessarily is that the anticompetitive effects it alleges did not occur until sometime after 1995. Novell has never specified exactly when those effects did occur. Novell sold WordPerfect to Corel in March 1996, and there is no evidence that by that time there was any operating system on the market comparable to Windows 95 to which Novell planned to write its applications or for which those applications could have been written. That fact, however, may not be dispositive because Novell's damages claim is based upon the alleged diminution in the value of its assets caused by Microsoft's conduct. Presumably, Corel would

23

have paid more for what it bought if by that time Microsoft had not, as Novell alleges, effectively destroyed Novell's applications and prevented them from being cross-platformed to other operating systems then under development. Therefore, I will assume, as Novell implicitly argues, that within a reasonable period of time after Windows 95 was put on the market (say two or three years), another operating system would have come into existence to which Novell's office productivity products could have been written.¹⁹

In asserting that it could and would have written to an operating system other than Windows 95 within a reasonable period of time after 1995, Novell relies upon two theories: the "franchise theory" and the "middleware theory."

(1)

First, Novell recognized that Windows 95 was a superior operating system, constituting a

24

"significant step forward." (Frankenberg, Trial Tr. at 1225-26, Nov. 8. 2011). In light of that fact, there is no basis for inferring that office productivity applications Novell developed that did not draw upon the superior functionality of Windows 95 would have been as successful as the applications that ran on Windows 95.

Second, historical data disprove Novell's claim. WordPerfect was extremely popular in the 1980s and early 1990s when it ran on many non-Microsoft operating systems. (Peterson, Trial Tr. at 4667, Dec. 7, 2011; see Middleton, Trial Tr. at 4178 (Dec. 13, 2008 Video Dep.), Dec. 5, 2011). However, this popularity did not diminish Microsoft's share of the PC operating systems market, which was approximately 90% during that period. (Noll, Trial Tr. at 1329-30, Nov. 15. 2011; Murphy, Trial Tr. at 4722-23, Dec. 7, 2011; Finding of Fact §35). On this record, it cannot reasonably be inferred that if in the years after 1995 Novell's applications ran on operating systems other than Windows, that fact would have challenged Microsoft's monopoly in the PC operating systems market.

(2)

As to the first requirement, assuming that within a reasonable period of time after 1995 effective operating systems would have come into existence to which Novell's office

25

productivity applications could have been written, there is no basis for inferring that Novell's office productivity applications written for Windows 95 via the namespace extension APIs could have been effectively ported to those systems. This is so because the namespace extension APIs were, as Novell's own technical expert testified, "platform specific" to Windows. (Alepin, Trial Tr. at 1482-83, 1532-33, Nov. 9-10, 2011; see Murphy, Trial Tr. at 4783-84, Dec. 7, 2011; Bennett, Trial Tr. at 5023, Dec. 12, 2011 (stating that "namespace extension APIs . . . [were] a unique component of Windows 95")).

As to the second requirement, although the parties agree that the dominant operating system was Windows 95, they disagree as to the meaning of ubiquity. Microsoft contends it means that Novell's software had to run on "all or nearly all PCs running the 'dominant operating system.'" (Microsoft Mem. at 73-75; Microsoft Reply Supp. Rule 50 Mot. at 37-39, ECF No. 503). Novell argues that "something less than that" might be sufficient "by weakening, though not eliminating, the applications barrier to entry." (Novell Opp'n at 90 (quoting Noll, Trial Tr. at 1926, Nov. 15, 2011)). Novell provided no evidence as to what this lesser threshold might be.

In any event, under either definition of ubiquity, the evidence is clear that Novell's office productivity applications would never have been ubiquitous on Windows 95. In 1995, prior to the release of Windows 95, WordPerfect had roughly a 15% share of the Windows-compatible word processing market, and PerfectOffice had less than a 5% share of the Windows-compatible suite market.²⁰(See Holley Decl. Supp. Microsoft Mem., Exs. G & K, ECF Nos. 495-7, 495-11). WordPerfect's share of the word processing market at the end of 1994 was substantially

26

greater--approximately 36%--if one includes the installed base of PCs using the DOS platform. (See Pl.'s Ex. 599A at tbl. 13). However, 36% is only 36%, and it is entirely speculative to assume, as Novell apparently does, that its applications would have increased to a substantially greater number of computers using Windows if Microsoft had not withdrawn support for the namespace extension APIs.²¹ This assumption is made even more speculative by the fact that an internal Novell memorandum dated April 14, 1995, stated that "only 30% of th[e] WordPerfect for DOS installed base is remaining with WordPerfect as they transition to a Windows word processor." (Def.'s Ex. 224 at 20).

The parties also disagree about the meaning of the third requirement. Microsoft argues that to constitute middleware, an application must "expose a sufficiently broad set of APIs to enable ISVs profitably to develop full-featured personal productivity applications that rely solely upon those APIs exposed by the middleware." (Microsoft Mem. at 70 (emphasis added)). Novell, on the other hand, relying upon the testimony of Roger Noll, its antitrust expert, and

27

Ronald Alepin, its technical expert, contends that the third element is satisfied if the application "expose[s] a wide range of APIs and sophisticated functionality to developers." (Novell Opp'n at 28). Novell concedes that if Microsoft's interpretation of the meaning of the third element is correct, Microsoft is entitled to judgment as a matter of law because Novell did not present evidence to show that its software exposed sufficient APIs of its own to allow ISVs to write full-featured personal products applications to it. (Trial Tr. at 5436-37, 5439, Dec. 15, 2011). Thus, on this issue, whether Microsoft is entitled to judgment in its favor on the Rule 50 motion turns on the meaning of the third requirement.

Microsoft's position is based upon the Findings of Fact made in the government case, upon which Novell's claim is founded. Judge Jackson found that "[c]urrently, no middleware product exposes enough APIs to allow independent software vendors ("ISVs") profitably to write full-featured personal productivity applications that rely solely on . . . APIs [of the middleware product itself]." Finding of Fact §28. In contrast, Novell argues the exposure of APIs that would result in "something less" than the writing of full-featured personal product applications is sufficient to constitute a threat to Microsoft's monopoly. (Novell Opp'n at 89-90). This argument is based on the concept, expressed by Noll, that diminishing, as opposed to nearly eliminating, the barrier to entry that protected Microsoft's monopoly in the PC operating systems market was itself sufficient. (Noll, Trial Tr. at 1926, Nov. 15, 2011). To the extent this testimony is based on the premise that other companies would produce similar middleware that, in combination with Novell's products, would diminish the barrier to entry, there is no evidence such other products existed.

Although in other circumstances conduct directed at reducing a barrier to entry might constitute a violation of §2 of the Sherman Act, under the facts of this case, I find Novell's

28

reasoning to be unpersuasive. The findings made in the government case made clear that Microsoft possessed its monopoly by virtue of what Judge Jackson described as a "chicken-and-egg" problem. As Judge Jackson described:

The overwhelming majority of consumers will only use a PC operating system for which there already exists a large and varied set of high- quality, full-featured applications, and for which it seems relatively certain that new types of applications and new versions of existing applications will continue to be marketed at pace with those written for other operating systems. Unfortunately for firms whose products do not fit that bill, the porting of applications from one operating system to another is a costly process. Consequently, software developers generally write applications first, and often exclusively, for the operating system that is already used by a dominant share of all PC users. Users do not want to invest in an operating system until it is clear that the system will support generations of applications that will meet their needs, and developers do not want to invest in writing or quickly porting applications for an operating system until it is clear that there will be a sizeable and stable market for it.

In light of these findings, it cannot be reasoned, as Novell argues, that Microsoft's

29

operating systems monopoly would have been threatened by a middleware product that exposed only a limited number of APIs that permitted ISVs to write only a specialized set of applications to it. The barrier to entry that Judge Jackson found in the government case was created by a "chicken-and-egg" problem, and that problem arose because ISVs would write only to programs that supported full-featured personal productivity applications. See Finding of Fact ¶ 30. In other words, contrary to what Novell argues in support of what Microsoft has aptly described as its "watered-down version" of the third requirement, Microsoft's monopoly in the PC operating systems market was threatened not by a product that exposed only a limited number of its own APIs but only by a product that exposed sufficient APIs to entice full-featured applications to be written to it. (See Microsoft Mem. at 77-78). Otherwise stated, diminishment of the barrier to entry is not sufficient because mere diminishment would not have affected the PC operating systems market. In order to constitute a realistic threat to Microsoft's monopoly in that market, elimination (or, at least, near elimination) of the barrier to entry through development of full-featured applications using APIs from middleware that ran on operating systems other than Windows was required.

In sum, Novell did not present sufficient evidence from which a reasonable jury could find that its applications could have successfully developed into middleware that threatened Microsoft's monopoly in the operating systems market.

C.

30

that the claim Novell asserts is a lawyers' construct and is not based on an underlying business reality.²³

First, as stated in section I, supra, there is no evidence that anyone at Novell made any complaint to anyone at Microsoft who could have reversed the decision to withdraw support for the namespace extension APIs.

Second, as also stated in section I, there is no evidence that any top-level executive was involved in the decision-making process concerning the writing of shared code for WordPerfect. Frankenberg testified that any action that could jeopardize the timely release of WordPerfect or Quattro Pro would generally have been referred to some or all of four senior executives. (Frankenberg, Trial Tr. at 1140-42, 1179-80, Nov. 7-8, 2011). Novell presented no evidence that any memorandum was written to those executives, and Frankenberg testified that he knew of no evidence whatsoever that any of the four executives were presented with a decision about how to respond to Gates's decision to withdraw support for the namespace extension APIs. (Id. at 1181-82, Nov. 8, 2011). Instead, Novell assigned responsibility for writing shared code for

31

WordPerfect and Quattro Pro to a middle manager, Gibb, who, in turn, assigned the responsibility to only two programmers, Harral and Richardson. However valiant the efforts of Harral and Richardson, if being ready to release WordPerfect, Quattro Pro, and PerfectOffice within 90 days of Microsoft's release of Windows 95 was as critical as Novell now claims it to have been, Novell clearly would have implemented a different development plan.

Third, although Gibb testified that Quattro Pro was "code complete" in time for the release of Quattro Pro and PerfectOffice within 90 days of Microsoft's release of Windows 95,²⁴ because of the mass exodus of programmers at Novell's facility in Scotts Valley, California, Quattro Pro was not ready for release to manufacturing until 1996. (Gibb, Trial Tr. at 806-09, Oct. 26, 2011; Frankenberg, Trial Tr. at 1145, Nov. 7, 2011; Def.'s Ex. 230).

Fourth, if, as Novell now argues, the 90-day period after the release of Windows 95 was critical to the success of WordPerfect, Quattro Pro, and PerfectOffice, Novell could have released those products using Microsoft's common file open dialog. In fact, Ford and LeFevre testified that they urged Gibb to pursue that option. (Ford, Trial Tr. at 3710-11, Nov. 30, 2011; LeFevre, Trial Tr. at 4041-43, Dec. 2, 2011).

In short, no reasonable jury could find, on the basis of the evidence presented at trial, that Microsoft's withdrawal of support for the namespace extension APIs caused Novell's failure to develop its applications within 90 days of the release of Windows 95.

32

VI.

Date: July 16, 2012

____/s/___________________
J. Frederick Motz
United States District Judge

__________________
¹ This case was brought in the wake of the 1998 government antitrust enforcement action against Microsoft. That action ultimately resulted in a ruling, supported by factual findings made by Judge Thomas Penfield Jackson, that Microsoft violated §2 of the Sherman Act by monopolizing and attempting to monopolize the operating systems market. See United States v. Microsoft Corp., 87 F. Supp. 2d 30 (D.D.C. 2000), aff'd in part, 253 F.3d 34 (D.C. Cir. 2001). Novell's claim that it was injured by virtue of Microsoft's monopolization of the operating systems market was tolled while the government action was pending because it overlapped with the government's claim in that action. Some of Judge Jackson's factual findings in the government case have been granted collateral estoppel effect in this action. (See Oct. 4 Court Correspondence, ECF No. 163; Trial Tr. at 143-57, 167-97, Oct. 18 & Nov. 14, 2011). In this Opinion, I refer to Judge Jackson's findings as Factual Finding ¶___.

² The Fourth Circuit had jurisdiction to review the limitations question because this action had been transferred to the District of Maryland for resolution of pretrial issues pursuant to the Multidistrict Litigation Act. See 28 U.S.C. §1407. I served as the trial judge in the action under an intercircuit assignment to the District of Utah, the district in which the case was filed. In the District of Maryland pretrial proceedings, the case number for this action was No. 05-cv-1087-JFM. In the District of Utah, its case number is No. 2:04-cv-01045-JFM. ECF references in this Opinion are to the Utah docket.

³ I discuss these theories in section V.B. In the government case, Judge Jackson defined "middleware" as software that "relies on the interfaces provided by the underlying operating system while simultaneously exposing its own APIs to developers." Finding of Fact §28. The D.C. Circuit accepted this definition, writing that middleware simply refers to "software products that expose their own APIs." Microsoft, 253 F.3d at 53. The products Novell developed that it alleges constitute middleware are PerfectFit (the shared code written into WordPerfect and PerfectOffice), AppWare (which was included in PerfectOffice), and OpenDoc.

⁴ After the jury hung, I interviewed the jurors and permitted counsel to do so as well. It appears undisputed that eleven of the twelve jurors would have returned a verdict in favor of Novell on the issue of liability. However, in light of what jurors said after the trial, it would be entirely speculative to assess the amount of damages the jury would have awarded had it not hung on the issue of liability. It might have taken into account in awarding damages not only weaknesses in Novell's damages claim but weaknesses in its liability claim as well. In any event, the fact that a majority of the jurors would have returned a verdict of liability in favor of Novell does not relieve me of the responsibility to rule on independent claims or on Microsoft's Rule 50(b) motion. See Noonan v. Midland Capital Corp., 453 F.2d 459, 463 (2d Cir. 1972) ("If the position of some jurors favoring plaintiff is enough [to prevent a judge from granting a Rule 50(b) motion], there could never be a judgment for insufficiency of the evidence notwithstanding a verdict."); Stewart v. Walbridge, Aldinger Co., 882 F. Supp. 1441, 1443 (D. Del. 1995) ("[T]he fact that the jury was unable to reach a unanimous verdict does not in any way affect this Court's duty to rule on the [Rule 50(b)] motion.").

⁵ This Opinion does not contain extensive citations to Tenth Circuit antitrust law because I have concluded that the facts governing my ruling are so case specific that the proper disposition of the Rule 50 motion requires close examination of the evidence in this case rather than comparison of this case to others. I note, however, my holding entirely accords with the Tenth Circuit's view that, as a general matter, a tough-minded business decision that adversely affects competition does not constitute an ipso facto violation of the Sherman Act. See Christy Sports, LLC v. Deer Valley Resort Co., 555 F.3d 1188, 1198 (10th Cir. 2009).

⁶ Windows 95 was launched at a gala event at Microsoft's corporate headquarters. Gary Gibb, who managed the development of the versions of Novell's office productivity applications for Windows 95, attended the event. He testified that he was displeased because he was not invited into the tent where Jay Leno, a television personality, was serving as the master of ceremonies. It was apparent to Gibb that Microsoft was using the event to market not only Windows 95 but also Microsoft's own office productivity applications, which ran on Windows 95. (Gibb, Trial Tr. at 818, Oct. 26, 2011). Gibb's perception of the event reflects that in 1995, Novell was concerned that what Microsoft was attempting to do was to use Windows 95 to increase its share of the applications market, not to maintain its monopoly in the operating systems market.

⁷ At the same time, some executives at Microsoft encouraged developers to write for another operating system, OS/2, rather than for Windows. (See Peterson, Trial Tr. at 4708, Dec. 7, 2011). Novell relies upon this evidence to infer that Microsoft, in pursuit of monopoly power, was talking from both sides of its mouth.

⁸ PerfectOffice 3.0 did not achieve a sizeable market share. (See Noll, Trial Tr. at 1915, Nov. 15, 2011). However, this may well have been due to the fact that many consumers were not buying new applications during 1994 and the first seven months of 1995 because they were awaiting the release of Windows 95 and applications written to it.

⁹ There is additional evidence that by October 1994 Gates was concerned about competition from Lotus and Novell. For example, Gates wrote an email, after watching a demonstration of Novell's new technology at a conference held in Scottsdale, Arizona on September 20, 1994, stating that "Novell [was] a lot more aware of how the world [was] changing than I thought they were." (Pl.'s Ex. 222; see Pl.'s Exs. 17, 31-33, 54, 72, 88, 91, 127, 201). There also was evidence that other executives at Microsoft perceived Novell's products to constitute middleware threats to Microsoft's operating system. Brad Silverberg, a senior Microsoft executive, wrote in an email dated June 15, 1993 that "our competitors are going to do everything they can to fragment windows, they will build their own middleware to claim api ownership." (Pl.'s Ex. 54 at MS 0185884). Likewise, John Ludwig of Microsoft wrote an internal email in which he stated, inter alia, that "our worst nightmare is novell/lotus being successful at establishing their 'middleware' as a standard. [O]urs ought to be ubiquitously available to forestall this. [O]ur huge advantage vis-a-vis novell is our end-user franchise, we shouldn't cast aside this advantage." (Id.; see Pl.'s Exs. 32 at MS 7079459, 33 at MS 5011635, 44 at MS 7080466-67).

¹⁰ As Novell's counsel acknowledged in closing argument, the Hood Canal plan was never implemented in light of the fact that Excel, Word, and Office did not use the functionality provided by the namespace extension APIs. (Trial Tr. at 5324-25, Dec. 13, 2011). However, Novell contends the Hood Canal plan is relevant in casting light upon the reason for Gates's decision to withdraw support for the namespace extension APIs on October 3, 1994. That contention is not unreasonable.

¹¹ Rietveld, Calkins, Moon, and Mella did not testify at trial.

¹² To repeat, Novell's theory is not that the October 3, 1994 decision had an anticompetitive effect in the applications market in violation of §2. Any claim based upon that theory is, as stated above, barred by limitations.

¹³ Microsoft also makes several arguments to the effect that Novell did not present sufficient evidence of damages. These arguments are, however, in large part merely different iterations of other contentions I address in section V.

¹⁴ Some of the facts stated in section I are repeated in sections IV and V in connection with the portions of the legal analysis to which they pertain.

¹⁵ Prior to the hearing on the Rule 50 motion, Novell contended that the act of withdrawing support for the namespace extension APIs was itself an unlawful act because beta versions of a release cannot be modified except to fix bugs discovered during the course of the beta process. However, as I noted in section I, supra, Novell did not press this contention at the Rule 50 hearing, and it is unsupported by the evidence.

¹⁶ Microsoft argues that while deception may give rise to a common law tort, it cannot, as a matter of law, form the basis for a Sherman Act claim. Although deception usually sounds in tort, see Restatement (Second) of Torts §526 (1977) (defining fraudulent misrepresentation/deceit), I see no reason it could not also give rise to an antitrust claim if the purpose of the deception is to mislead a competitor into taking action (or not taking action) that would substantially change the competitive environment. Microsoft distinguishes cases in which deceptive conduct has given rise to antitrust liability on the grounds that such cases typically involve deception of third parties, not competitors. See Am. Prof'l Testing Serv., Inc. v. Harcourt Brace Jovanovich Legal & Prof'l Publ'n, Inc., 108 F.3d 1147, 1151 (9th Cir. 1997); Int'l Travel Arrangers, Inc. v. W. Airlines, 623 F.2d 1255, 1260-63 (8th Cir. 1980). Those cases, however, do not turn on the identity of the party deceived but on whether the challenged conduct in fact harmed competition. See Rambus, Inc., v. Fed. Trade Comm'n, 522 F.3d 456, 464 (D.C. Cir. 2008) ("Deceptive conduct--like any other kind--must have an anticompetitive effect in order to form the basis of a monopolization claim. . . . Cases that recognize deception as exclusionary hinge, therefore, on whether the conduct impaired rivals in a manner tending to bring about or protect a defendant's monopoly power.").

¹⁷ What the evidence, specifically Gates's email announcing the decision to withdraw support for the namespace extension APIs, does suggest is that Microsoft was attempting to buy time for its own office productivity application developers to catch up, so that eventually Microsoft could use the enhanced technology created by Windows 95 as effectively (and potentially, by integration of the applications and the operating system, more effectively) as its major competitors, including Novell. That, however, is quite different from imputing to Microsoft knowledge that Novell needed the namespace extension APIs to develop its own applications. Of course, in fact, as the evidence established, Novell could have used Microsoft's common file open dialog, which remained available to it after support for the namespace extension APIs was withdrawn, to develop its applications. According to Novell, those programs simply would not be as good as they could have been if Microsoft had continued to make its own technology available to Novell.

¹⁸ Novell argues that Microsoft's willingness to sacrifice the short-term profits it would have earned from increased sales of Windows 95 to customers who would buy the operating system if it ran Novell's applications constituted a classic hallmark of anticompetitive behavior because monopolists are assumed to be rational, and the sacrifice of short-term profits can be explained only by the desire to reap long-term gains by maintaining the monopoly. See, e.g., Reazin v. Blue Cross & Blue Shield of Kan., Inc., 635 F. Supp. 1287, 1309 (D. Kan. 1986), aff'd, 899 F.2d 951 (10th Cir. 1990). The flaw in this argument is that there is no evidence that Microsoft sacrificed any short-term profits by withdrawing support for the namespace extension APIs. Novell's own theory is that support for the APIs were withdrawn to prevent a decline of sales of Microsoft's office productivity programs (Word, Excel, and Office) because Novell and Lotus would have been able to put products superior to them on the market if support for the namespace extension APIs had not been withdrawn. Thus, assuming that Microsoft's revenues from the sale of Windows 95 might have slightly declined because a limited number of purchasers would not buy Windows 95 unless there were Novell applications made for Windows 95, there is no basis for inferring that the decline of revenues would not have been more than offset by an increase of revenues in the sales of Word, Excel, and Office.

I recognize that this conclusion may appear somewhat disturbing because arguably it rewards Microsoft for unsavory behavior in the applications market. Nevertheless, the reasoning is sound. Although the proposition upon which Novell relies makes eminent sense as a matter of theory, it is based upon a factual inference about how a rational actor would behave, and here the evidence does not support the inference. Moreover, Novell has only itself to blame for the quandary in which it finds itself because it was its own delay in filing this action that resulted in its claims in the applications market being barred by limitations. See Novell, 2005 WL 1398643, at *5.

¹⁹ Although I accept this assumption, it is problematic. While the evidence is undisputed that historically WordPerfect had been cross-platformed to various operating systems, (see Harral, Trial Tr. at 216, Oct. 20, 2011; Gibb, Trial Tr. at 776-77, 781, Oct. 26, 2011; Frankenberg, Trial Tr. at 994-97, Nov. 7, 2011), this is not an instance in which it can reasonably be said that the past is a prologue of the future, particularly in light of the technological breakthrough that Novell acknowledges Windows 95 achieved. Likewise, although Harral and Gibb testified that looking into the future Novell intended to make the PerfectOffice suite cross-platform after the initial release of PerfectOffice for Windows 95, (Harral, Trial Tr. at 371, Oct. 24, 2011; Gibb, Trial Tr. at 787, Oct. 26, 2011), mere intent and aspiration do not provide sufficient evidence that, in fact, Novell's applications would have been cross-platform. Moreover, although one of Novell's experts testified that Linux "became a full-fledged, commercial product" in 1996, (Noll, Trial Tr. at 1961, Nov. 15, 2011), the version of WordPerfect for Linux that Corel released in the spring of 1996 was an older version of WordPerfect that did not contain the same shared code as the version of WordPerfect developed for Windows 95. (Murphy, Trial Tr. at 4914-16, Dec. 8, 2011). As such, it was inferior to the WordPerfect application that ran on Windows 95. (Id.).

²⁰ According to Microsoft expert Kevin Murphy, these market share numbers must be further reduced by approximately 50% because office suites or any of their component applications were installed on only one-half of all PCs. (Murphy, Trial Tr. at 4750, Dec. 7, 2011).

²¹ Novell's reliance upon the DOS installed base also raises a significant question as to whether Novell assigned the claims asserted in this action to Caldera, Inc. when it sold its DOS business to Caldera. In the Asset Purchase Agreement it made with Caldera, Novell transferred "all of Novell's right, title, and interest in and to any and all claims or causes of action held by Novell at the Closing Date and associated directly or indirectly with any of the DOS Products or Related Technology." (See Asset Purchase Agreement, Holley Decl. Supp. Microsoft Mem., Ex. P, at 4-5, ECF No. 495-16). I previously ruled that this assignment encompassed the operating systems monopoly claim asserted in this action because the claim asserted here arose in the operating systems market in which DOS had competed. See In re Microsoft Corp. Antitrust Litig., 699 F. Supp. 2d 730, 739 (D. Md. 2010). The Fourth Circuit reversed my ruling. See Novell, Inc. v. Microsoft Corp., 419 F. App'x. 254, 261 (4th Cir. 2011). I remain bound by that decision. If the Tenth Circuit finds resolution of the issue to be necessary to its decision on Microsoft's Rule 50 motion, however, it may conclude that the law of the case doctrine does not apply and that it may revisit the Fourth Circuit's ruling because the evidence presented at trial is more extensive than was the evidence in the summary judgment record upon which the Fourth Circuit relied. Specifically, the Tenth Circuit might decide that because, as the record now reflects, Novell's claim depends in large part upon the conversion of its share of the DOS installed base into a significant share of the Windows market, that claim is "associated directly or indirectly with . . . the DOS Product or Related Technology" and thus was transferred to Caldera.

²² The barrier to entry issue was eloquently described, from a business point of view, in an email sent on August 17, 1997, by Jeff Raikes, then a Microsoft executive, to Warren Buffett. (Pl.'s Ex. 360 at MS-PCA 1301176). In the email, Raikes wrote of the importance of "widen[ing] the moat," i.e. increasing the barrier to entry, by tying together Microsoft's applications and Windows. I admitted the email into evidence despite the fact that it was not written until after the events that gave rise to this action on the ground that the jury might find it reflected the views of Microsoft's executives during the relevant time period.

Novell referred to the email at trial and has likewise referred to it in opposing Microsoft's Rule 50 motion. In the event that the Tenth Circuit reverses my ruling that Microsoft's Rule 50 motion should be granted, it would be helpful in the retrial of this case if the Tenth Circuit were to decide whether the Raikes email was properly admitted. It would also be helpful, in the event of a reversal of my Rule 50 ruling, if the Tenth Circuit resolved a disagreement between the parties as to the proper causation standard. Microsoft contends that the standard that should be applied is whether its decision to withdraw support for the namespace extension APIs "contributed significantly to its continued monopoly power." (Microsoft Mem. at 82). Conversely, Novell contends that the appropriate standard is whether Microsoft's decision was "reasonably capable of contributing significantly" to Microsoft's monopoly power. (Novell Opp'n at 94-95). In reaching my decision, I have not found it necessary to resolve this issue.

²³ This statement is not meant as an unfavorable observation about Novell's counsel. They have skillfully and energetically pursued a claim that I have concluded is not supported by the evidence. It is not, however, frivolous. Likewise, my statement is not intended to reflect badly upon Novell. The evidence presented at trial showed that Novell simply did not believe the deadline of bringing applications to market within 90 days of the release of Windows 95--a deadline that was dictated solely by marketing considerations--was material to the success of Novell's applications. The tradition and culture at WordPerfect had been to develop better products than WordPerfect's competitors, and to depend upon the high quality of those products to achieve market success. Therefore, it is not surprising that Gibb, Harral, and Richardson-- who had been employed by WordPerfect prior to its sale to Novell--would have been primarily concerned about delivering the best software applications they could write, even if that entailed some delay. Unfortunately, economic realities, including cost-cutting measures Novell felt compelled to take, were collapsing the world to which they had been accustomed and were destroying Novell's ability to provide hand-tailored products and services to its customers. (Frankenberg, Trial Tr. at 1097-98, Nov. 7, 2011; Bushman, Trial Tr. at 3161-62, Nov. 28, 2011; Acheson, Trial Tr. at 3968, 3972, Dec. 2, 2011; LeFevre, Trial Tr. at 4024-26, Dec. 2, 2011; Def.'s Exs. 15-16).

²⁴ Gibb's testimony that Quattro Pro was code complete in time for Quattro Pro and PerfectOffice to be released on schedule is subject to serious question, in light of the facts stated in section I, supra.

33