United States v. Microsoft Corp.

159 F.R.D. 318, 1995 U.S. Dist. LEXIS 1654, 1995 WL 59480
CourtDistrict Court, District of Columbia
DecidedFebruary 14, 1995
DocketCiv. A. No. 94-1564
StatusPublished
Cited by8 cases

This text of 159 F.R.D. 318 (United States v. Microsoft Corp.) is published on Counsel Stack Legal Research, covering District Court, District of Columbia primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
United States v. Microsoft Corp., 159 F.R.D. 318, 1995 U.S. Dist. LEXIS 1654, 1995 WL 59480 (D.D.C. 1995).

Opinion

MEMORANDUM OPINION 1

SPORKIN, District Judge.

The issue before this Court is whether the entry of a proposed antitrust consent decree between Microsoft Corporation and the United States is in “the public interest.”2 Microsoft is the world’s largest developer of computer software. On July 15, 1994, the Government filed a complaint charging Microsoft with violating Sections 1 and 2 of the Sherman Anti-Trust Act. 15 U.S.C. §§ 1-7 (1973). On the same day the parties filed a proposed consent judgment.3

I. Background

The Government filed the complaint and proposed judgment after a four-year investigation of Microsoft. The Federal Trade Commission (“FTC”) initiated the investigation in 1990. According to Microsoft, but not confirmed by the Government, the FTC considered a wide range of practices including: (1) that Microsoft gave its developers of applications software information about its operating systems software before providing it to other applications developers; (2) that Microsoft announced that it was developing a non-existent version of operating software to dissuade Original Equipment Manufacturers (“OEMs”) from leasing a competitor’s operating system; (3) that Microsoft required OEMs that licensed its operating system software also to license Microsoft applications; and (4) that Microsoft licensed its operating systems to OEMs on a per processor basis.4 Microsoft asserts that before the FTC investigation was completed, it was expanded to include every aspect of Microsoft’s business.5

There was never a majority vote among the FTC commissioners to file an administrative complaint against Microsoft. In late 1993, after a 2-2 deadlock by the commissioners, no administrative action was filed, and the FTC suspended its investigation of Microsoft.

Following the suspension of the FTC investigation, Assistant Attorney General Bin[322]*322gaman, the head of the Antitrust Division of the Department of Justice, decided to revive the investigation. In June, 1994 Microsoft and the Department of Justice initiated settlement negotiations. Approximately a month later the parties came to agreement and filed a proposed judgment with the Court.6

II. The Complaint

The complaint charges that Microsoft violated Sections 1 and 2 of the Sherman AntiTrust Act. 15 U.S.C. §§ 1-7. The primary allegations in the complaint concern licensing agreements between Microsoft and OEMs of personal computers (“PCs”). The complaint also addresses provisions of non-disclosure agreements (“NDAs”) between Microsoft and other developers of applications software, known as independent software developers (“ISVs”). The complaint narrowly tailors the relevant product market to the market for certain operating systems software for x86 microprocessors. The geographic market is not limited.

In order to understand the complaint, one must understand something about computers, microprocessors, and operations and applications software. A microprocessor is the “brain” of the computer. The x86 microprocessor, or chip, runs IBM and IBM-elone PCs. These chips are primarily, but not exclusively, made by Intel.7 Operating systems software acts as the central nervous system for a personal computer, linking up the keyboard, monitor, disk drive and other components. Applications software enables the PC user to perform a variety of tasks including word processing and database management. Applications software operates on top of the PC’s operating system and must be designed to function with that operating system. As a result, ISVs who design applications software need information about an operating system’s codes in order to design their software. Microsoft designs both operating systems (e.g., MS-DOS) and applications (e.g., Microsoft Word, a word processing program).

Microsoft has a monopoly on the market for PC operating systems. Microsoft’s share of the operating systems market identified in the complaint is consistently well above 70%.8 According to Microsoft’s 1993 Annual Report, as of June 30, 1993, 120 million PCs ran on Microsoft’s MS-DOS. Microsoft also developed and sells Windows, a sophisticated operating system that runs on top of MS-DOS or a similar operating system. Windows allows a PC user to run more than one application at a time and shift between them. Windows is known as a “graphical user interface.” Approximately 50 million PCs now use Windows. Microsoft generally does not sell its operating systems directly to consumers. Instead, it licenses its operating systems to OEMs for inclusion in the PCs they make.9

Microsoft, the Justice Department, and a number of competitors who oppose the entry of the decree all agree that it is very difficult to enter the operating systems market. There are two main reasons for this, each of which reinforces the other. First, consumers do not want to buy PCs with an operating system that does not already have a large installed base because of their concern that there will not be a wide range of applications software available for that operating system. The second, complementary reason why there are large barriers to entry into the operating systems market is that ISVs do not want to spend time and money developing applications for operating systems that do not have a large installed base. They perceive that demand for that software will be low. As a result, OEMs have little incentive [323]*323to license an operating system that does not have a large installed base and include it in their PCs.

In addition to these “natural” barriers to entry, the complaint identifies Microsoft’s use of per processor licenses and long term commitments as “exclusionary and anti-competitive contract terms to maintain its monopoly.” A per processor license means that Microsoft licenses an operating system to an OEM which pays a royalty to Microsoft for each PC sold regardless of whether a Microsoft operating system is included in that PC. In other words, under a per processor license, if an OEM sells some PCs with a competitor’s operating system installed (e.g., IBM’s OS/2), and others with MS-DOS installed, the OEM would pay Microsoft royalties for all PCs sold. In effect, the OEM pays twice every time it sells a PC with a non-Microsoft operating system — once to the company that licensed the operating system to the OEM and once to Microsoft. The complaint charges that per processor licenses discourage OEMs from licensing competing operating systems and/or cause OEMs to raise the price for PCs with a competing operating system to recoup the fee paid to Microsoft.

The complaint further alleges that Microsoft’s use of long-term licensing agreements with or without minimum commitments, and the rolling over of unused commitments unreasonably extended some licensing agreements with Microsoft. These practices allegedly foreclosed OEMs from licensing operating systems from Microsoft’s competitors.

The other anticompetitive practice cited in the complaint is the structure of Microsoft’s non-disclosure agreements (“NDAs”) with ISVs during the development of its new Windows operating system.10

Free access — add to your briefcase to read the full text and ask questions with AI

Related

In Re Microsoft Corp. Antitrust Litigation
699 F. Supp. 2d 730 (D. Maryland, 2010)
Covad Communications Co. v. Bell Atlantic Corp.
398 F.3d 666 (D.C. Circuit, 2005)
Gravity Inc v. Microsoft Corp
309 F.3d 193 (Fourth Circuit, 2002)
No. 01-2458
309 F.3d 193 (Fourth Circuit, 2002)
United States v. Microsoft Corp.
980 F. Supp. 537 (District of Columbia, 1997)

Cite This Page — Counsel Stack

Bluebook (online)
159 F.R.D. 318, 1995 U.S. Dist. LEXIS 1654, 1995 WL 59480, Counsel Stack Legal Research, https://law.counselstack.com/opinion/united-states-v-microsoft-corp-dcd-1995.