Sponsored Content
Special Forums News, Links, Events and Announcements UNIX and Linux RSS News Microsoft and Incompatibility: 1991-2010 -- And a Novell Smoking Gun Post 302482150 by Linux Bot on Monday 20th of December 2010 05:30:02 PM
Old 12-20-2010
Microsoft and Incompatibility: 1991-2010 -- And a Novell Smoking Gun

Another gruesome exhibit is now finished as text in our collection of Comes v. Microsoft exhibits, Exhibit 1116 [PDF].
It's a Microsoft memo from 1991, regarding a suggested attack plan to beat out IBM's OS/2, written by Joseph Krawczak, currently group program manager for Outlook at Microsoft. Here are just three damning sentences from the confidential memo:
Pursue a product development strategy that prevents IBM from claiming Windows compatibility. Prevent Windows applications from running correctly on OS/2....
Reposition OS/2 as impractical and incompatible in the minds of customers.
Nice. First quietly create incompatibilities to make sure that Microsoft applications wouldn't run right on OS/2. Then tell the world that they shouldn't buy OS/2 because Microsoft applications wouldn't run right on OS/2.
But 1991 is a long time ago, I hear some of you say, and there is a new Microsoft. Oh? Let's see if that's so by highlighting one of the recent Novell filings with the SEC, its work agreement with Microsoft titled "Improving Microsoft-Novell Interoperability through Open XML" and dated March of this very year.
It's regarding work Microsoft was willing to pay Novell to do to make Microsoft's cynically misnamed Open XML seem like it allows interoperability. Novell has been at work since March to make Novell's version of OpenOffice.org interoperate, sort of, but as you will see not completely with Microsoft Office 2010 so that it would at least look like Open XML works and that somebody is implementing it.
What a role for Novell to agree to play. We've had our suspicions for years, since Microsoft and Novell entered into its patent peace agreement and technical work agreement, and now we know that everything we suspected Novell was doing with its version of OpenOffice.org, it was. It is. This is the smoking gun. And the work agreement runs through November of 2011, so this story isn't over yet.

More...
 
pdb2mdb(1)						      General Commands Manual							pdb2mdb(1)

NAME
pdb2mdb - Program Database to Mono Debugging Symbol converter. SYNOPSIS
pdb2mdb pdb_file DESCRIPTION
This tool is used to convert debugging symbols generated by Microsoft's compilers into debugging symbols that can be consumed by Mono's runtime. Program Database files are files that end with the extension .pdb and are associated with a library or executable (a .dll or .exe file). This format was until recently not documented so Mono used its own file format for storing debugging information, the Mono debugging for- mat. Just like PDB files Mono Debugging information is stored in files that reside side-by-side with a program executable or a library. You can use the pdb2mdb tool to transform these PDB files into MDB files that Mono can then consume to debug programs or provide line-num- ber information for stack traces or exceptions. LICENSE
The pdb2mdb tool is released under the terms of the Microsoft Public License (MS-PL). JB Evain wrote the tool. The PDB reading support came from Microsoft Common Compiler Infrastructure. SEE ALSO
mono(1), mdb(1) WEB SITE
http://www.mono-project.com 23 April 2009 pdb2mdb(1)
All times are GMT -4. The time now is 04:14 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy