To: Valley Girl who wrote (38611 ) 2/26/2000 1:58:00 PM From: rudedog Read Replies (2) | Respond to of 74651
VG - re: Crime #1: bullying boxmakers by forcing them to pay per-unit prices for the MSFT OS on all boxes built, even if some of these shipped with a different OS. Threatening to withhold the OS or favourable pricing on the OS if boxmakers didn't toe the line, i.e. if they started building Linux boxes or network appliances that didn't use an MSFT OS. My assessment: if this isn't illegal, it ought to be. Mind you it's OK if you're not a monopoly, which MSFT had not been officially ruled to be until recently. Reasonable remedy: injunctions restraining the scope of business arrangements between MSFT and boxmakers. I am aware of a number of actual contracts regarding sale of licenses to OEMs, as I was on the other side of the table in several discussions in '96 and '97. The structure was a lot different than the one suggested in the popular press. MSFT offered a range of buying options for OEMs based strictly on volume, running from programs known as "DSP" and "MOLP" which gave a 20% to 30% discount under "list price" on quantities as small as 5 licenses, up to the more substantial discounts (in the 50% range) offered to the big OEMs who sold in the millions. There was an additional business justification for the larger OEM discounts which I have not seen in the trial transcripts - the smaller buyers (such as those buying under "MOLP") have no responsibility for support - the end customer gets to call MSFT directly. The OEMs have to provide first-line support themselves, and only escalate for "level 3" problems - those that are not pilot error or a configuration issue, but an actual problem with MSFT software. The additional 20% discount seems like scant compensation for the expense of running a complete support team, but it is a business tradeoff - any OEM who wanted to take the lower discount in exchange for MSFT doing support had that choice at any time. The "per system" pricing model was also much discussed and not much understood. This was not a mandatory program, and was never the exclusive way that OEMs licensed MSFT OS products. It was an additional discount opportunity, based directly on the costs that MSFT incurred when they had to track which OEM products went out with a MSFT OS. MSFT said "here's another way you can track royalties due - ship MSFT OS on every box, or at least pay for it that way, and you will only need to report number of systems shipped. We'll give you an additional discount because we know that not EVERY system ships with a MSFT OS". Given that maybe 95% of desktops shipped with Windows at that time, with a tiny fraction shipping OS/2 or something else, that was probably a reasonable choice for many OEMs, since they got an additional 3% or so in discount. The reduced internal costs of tracking would have been a benefit also. For OEMs like DELL who shipped pretty much nothing but Windows, it was just free money. The policy had the additional benefit to MSFT that since OEMs had already paid for the OS, they might as well provide it with the systems. CPQ routinely shipped a Windows CD even with systems that had OS/2. This had the additional benefit that OEMs could ship utilities and configuration applications that needed Windows to run, without violating any license restrictions. For example, the CPQ disk array configuration utility, which has its own boot disks and operates completely outside of the OS, is used for OS/2, SCO, Solaris for X86, Linux, Unixware, and anything else that runs on a CPQ box. Should CPQ be required to write a bootable version of that application for every OS just so the customer can configure the disks? What about common "look and feel"? The fact that CPQ had a license for every system shipped made their work easier and reduced cost to the customer. Also the notion that MSFT would withhold the OS is more bunkum. The only discussion about that in the trial was not around the OS itself but around the Netscape browser, and was actually even narrower than that - the CPQ consumer division had done a deal with MSFT around a "bundle" for two of their product lines, where they got favorable pricing in exchange for featuring the MSFT browser. This is conceptually no different than the deals currently being done by AOL and others, where the manufacturer gets a discount for featuring AOL as the prefered ISP. According to testimony from CPQ executives, when the CPQ executive in charge of those products decided, after the licensing deal with CPQ was cut, to instead feature the Netscape browser, MSFT said that was not the deal, and they could not ship products until they cut a new deal, since they were in violation of the terms of the original agreement. CPQ could have shipped under their blanket agreement, but without the additional discount on the OS that they had gotten from the "bundle"... and in fact no shipments were delayed. The MSFT letter which informed CPQ that they would be shipping in violation of their agreement if they featured the Netscape browser was taken out of context, as best I can determine. Most of the OEMs used the press around this set of events to get more favorable terms from MSFT, and at the same time MSFT abandoned "per system" licensing, so the actual practice is years in the past already. This strikes me as an example of the government getting into a price discount discussion between MSFT and its customers when there was no problem to begin with.