decoration decoration

When you want to know more...
For layout only
Site Map
About Groklaw
Legal Research
ApplevSamsung p.2
Cast: Lawyers
Comes v. MS
Gordon v MS
IV v. Google
Legal Docs
MS Litigations
News Picks
Novell v. MS
Novell-MS Deal
OOXML Appeals
Quote Database
Red Hat v SCO
Salus Book
SCEA v Hotz
SCO Appeals
SCO Bankruptcy
SCO Financials
SCO Overview
SCO v Novell
Sean Daly
Software Patents
Switch to Linux
Unix Books
Your contributions keep Groklaw going.
To donate to Groklaw 2.0:

Groklaw Gear

Click here to send an email to the editor of this weblog.

To read comments to this article, go here
The Goldfarb Declaration - Updated: MS Statement
Monday, October 09 2006 @ 03:27 PM EDT

I now have the Larry Goldfarb Declaration, and now that I've had a chance to read it in full, what he says is actually a great deal more damaging, if established, than the part IBM highlighted in its Memorandum in Support of Its Motion for Summary Judgment on SCO's Interference Claims. According to the Declaration, Richard Emerson was not the only Microsoft employee Goldfarb was dealing with in connection with the BayStar investment in SCO. He mentions by name two others, from two other departments. He says, "I had discussions with Kenneth Lustig, Microsoft's managing director of intellectual property and Tivanka Ellawala, from Microsoft's corporate development department regarding the SCO deal." If true, that would seem to rule out Mr. Emerson being on some kind of rogue mission.

You can see Mr. Lustig on this Directions on Microsoft chart of executives, showing him reporting to Marshall Phelps, who in turn is under Brad Smith, the Microsoft General Counsel and Secretary.

[Update: Oct. 9, 2006, 5:25 PM - I see Mr. Emerson is now on the board of directors of Clearwire. And LinkedIn shows Ellawala currently with Microsoft. Its summary says "Leads Corporate Development activities across the internet, media and wireless spaces at Microsoft. Memeber of 3-person Corporate Development leadership team responsible for all M&A, Strategic Investments and Joint Venture discussions at Microsoft."]

Goldfarb recounts conversations with David Boies as well, and Goldfarb, then considering investing in SCO back in 2003, says Boies told him that he thought IBM was going to settle quickly. Obviously that didn't happen. Later, when Goldfarb asked to see the evidence against IBM, so his consultants could evaluate the strength of SCO's claims, he says that Boies said he'd provide it but he never did. Eventually Boies stopped taking Goldfarb's phone calls, the Declaration relates. I'm wondering now if Mr. Boies will end up a witness in this case, if IBM's motion is denied and SCO gets to proceed with its interference claims. I'd venture a guess that SCO wishes it had never accused IBM of interfering with SCO's business relationship with BayStar. But let's let Goldfarb tell his own story and I'll get the PDF up as soon as I can. This is just one of more than 500 exhibits that IBM has provided the court in support of its various motions for summary judgment. It's number 165. I'll have the exhibits list up as text shortly as well.

Also, I thought you'd want to know that Ray Noorda died today, at 82, according to The Salt Lake Tribune. Todd Weiss at ComputerWorld has a more fitting tribute, with a link to the Canopy Group statement.

Update: Todd Bishop at the Seattle Post Intelligencer has Microsoft's response. Here is their statement:

Microsoft has no financial relationship with BayStar and never agreed to guarantee any of BayStar's $50 million investment in SCO. The BayStar declaration confirms that no guarantee was ever provided. Microsoft does have a deal with SCO that has been widely reported. We paid SCO for licensing rights to ensure IT interoperability for UNIX migration technology, currently in use in Microsoft Utilities for UNIX-based Applications.

Update: 6:00 PM October 10 - ZDNET has an article now too which is particularly useful, because it links to all the older happenings. As an aid, here is what BayStar said in 2004, when the Michael Anderer memo claiming a Microsoft funding connection surfaced:

An investment company has corroborated allegations of ties between the two firms fighting against open source. Investment company BayStar Capital has confirmed ties between two Linux foes, saying on Thursday that a Microsoft referral led to $50m (27.8m) in BayStar funding for the SCO Group. "Yes, Microsoft did introduce BayStar to SCO," a BayStar representative said on Thursday, declining to share further details and repeating the firm's earlier position that Microsoft did not actually invest money in the deal.

So the Declaration is consistent.


Alan L. Sullivan (3152)
Todd M. Shaughnessy (6651)
Amy F. Sorenson (8947) [address, phone, fax]

Evan R. Chesler (admitted pro hac vice)
David R. Marriott (7572)
[address, phone, fax]

Attorneys for Defendant/Counterclaim-Plaintiff
International Business Machines Corporation









Civl No. 2:03CV-0294 DAK

Honorable Dale A. Kimball

Magistrate Judge Brooke C. Wells

1. I, Lawrence R. Goldfarb, declare as follows:

1. This declaration is submitted in connection with the lawsuit entitled The SCO Group, Inc. v. International Business Machines Corporation, Civil No. 2:03CV-0294 DAK (D. Utah 2003). Unless stated otherwise, i make this declaration based upon personal knowledge.

2. I am one of the founders and managing members of BayStar Capital Management, LLC ("BayStar"). I have served as a managing member of BayStar since 1998. BayStar is the sole general partner of BayStar Capital II, L.P. (the "Fund"), an investment fund formed in 2001.

4. No one from IBM ever had any communications with me or, to my knowledge, anyone at BayStar relating to SCO. As I discuss below, BayStar terminated its relationship with SCO for multiple reasons. BayStar's decision to terminate its relationship with SCO had nothing whatsoever to do with any communications with or conduct of IBM.

5. In late 2003, the Fund and aligned investors invested a total of $50 million in SCO. I was one of the three managing members of BayStar who approved the investment, and I was intimately involved with all details of the transaction.

6. Sometime in 2003, I was approached by Richard Emerson (Microsoft's senior vice president for corporate development and stratedy) about investing in SCO, a company about which I knew little or nothing at the time. Mr. Emerson stated that Microsoft wished to promote SCO and its pending lawsuit about IBM and the Linux operating system. But Microsoft did not want to be seen as attacking IBM or Linux. For that reason, Microsoft wanted to further its interest through independent investors like BayStar.

7. I did some research on SCO, and had conversations with Mr. Emerson about it as well. In the course of my research about SCO, I became concerned that SCO might be merely a litigation company. As a result, Mr. Emerson and I discussed a variety of investment structures wherein Microsoft would "backstop," or guarantee in some way, BayStar's investment. In addition, I had discussions with Kenneth Lustig, Microsoft's managing director of intellectual property and Tivanka Ellawala, from Microsoft's corporate development department regarding the SCO deal. As part of these discussions, Microsoft assured me that it would in some way guarantee BayStar's investment in SCO. However, Microsoft would not agree to put anything in writing on this point.

8. The other managing members of BayStar and I met with Darl McBride of SCO and heard his pitch about SCO's business and SCO's lawsuit against IBM. We also discussed SCO's lawsuit with David Boies from SCO's outside law firm, Boies, Schiller & Flexner LLP. Mr. Boies informed me that he believed that IBM would settle the case fairly quickly.

9. As a result of Microsoft's and SCO's assurances, the other managing members of Bay Star and I voted unanimously to make the $50 million investment in SCO. the transaction was completed on October 16, 2003.

10. Not long after making the investment, I became very concerned about it. Among other things, it became clear to me that the BayStar investment was used primarily to pay David Boies' law firm. Beyond that, SCO's stock price declined, Microsoft stopped returning my phone calls and emails, and to the best of my knowledge, Mr. Emerson was fired from Microsoft.

11. I was also very concerned about SCO's high cash burn rate and whether its UNIX products were viable in the marketplace.

12. Thereafter, I had meetings with David Boies and asked him to provide me the evidence supporting SCO's case against IBM, so that my consultants could analyze the strength of the claims. Mr. Boies promised to provide the evidence but never did. Eventually Mr. Boies stopped returning my calls.


14. Having received no satisfactory response from SCO, I determined that BayStar's obligations to its investors required the Fund to get out of this investment. I negotiated the terms of the deal to retire the investment on behalf of BayStar. SCO's outside law firm, negotiated the settlement on behalf of SCO, including the financial terms of the deal. 15. Ultimately, BayStar, on behalf of the Fund, agreed to sell its SCO Preferred Shares back to SCO for $13 million cash payments to BayStar and the issuance of shares of SCO common stock.

16. BayStar's decision to redeem its shares in SCO and retire its investment in SCO had nothing whatsoever to do with IBM or any representative of IBM. No one from IBM ever contacted me or anyhone else at BayStar about SCO, BayStar's investment in SCO, or anything else. Other than one investment that involved IBM years before BayStar's investment in SCO (and in connection with submitting this declaration), I have had no dealings with IBM or any of its representatives.

17. I declare under penalty of perjury that the foregoing is true and correct.

Executed September 13, 2006.
Larkspur, California

Lawrence R. Goldfarb

  View Printable Version

Groklaw © Copyright 2003-2013 Pamela Jones.
All trademarks and copyrights on this page are owned by their respective owners.
Comments are owned by the individual posters.

PJ's articles are licensed under a Creative Commons License. ( Details )