|
|
|
| Authored by: foulis on Wednesday, May 30 2012 @ 02:24 PM EDT |
<p
align=right><b>PLAINTIFF'S<br>EXHIBIT<br><u>2860</
u></b><br>Comes v. Microsoft</p>
<b>From:</b> John Gailey<br>
<b>Date:</b> Thu, Mar 5, 1998 2:43 PM<br>
<b>Subject:</b> Re: Outlook Icon on Desktop</p>
* Outlook 97 (part of Office97) included a new version of MAPI (de facto
messaging API) which caused GroupWise to not run correctly.<br>
* Outlook 98 (beta - it will ship later this month) included a new version of
MAPI which caused GroupWise to not run at all.<br>
* All office productivity applications, such as Microsoft Office and Corel
WordPerfect Suite, use MAPI to integrate with messaging products such as
GroupWise. With the Outlook 98 beta II installed, Microsoft Office would only
communicate with Outlook and would not recognize GroupWise.<br>
* Outlook 97, a MAPI-compliant application, would not run with GroupWise at all
until we made specific changes to support it - a conflict with the MAPI
"standard" specification.<br>
* Outlook 97 uses MAPI to store and retrieve calendaring data, which many
customers desire, Groupwise also supports calendaring data and we desired
interoperability. We asked Microsoft for details on the calendaring formats so
we could interchange data and functionality and were told that this information
would not be available. The inability to interoperate with Outlook clients
causes many customers to standardize on a single vendor.<br>
* Microsoft is placing the Outlook icon on the desktop, and in fact, does so by
replacing the original "Inbox" icon that shipped as part of
Windows95.<br>
* Microsoft continues to deliver new capabilities in components such as
COMCTL32.DLL that all products can use to obtain a common look and feel with
other products (especially to be consistent with Microsoft desktop
applications.) They have allowed companies such as Novell to re-distribute these
kinds of DLLs. With the IE4 release, significant changes were made to these
controls and re-distribution was revoked unless we agreed to distribute the
entire IE4 product. For the specific COMCTL32.DLL case, Microsoft has finally
relented and will allow re-distibution (after we had already implemented our own
version.) This has put us at a dis-advantage[sic].<br>
* A new control that is "packaged" as part of the IE4 release is an
HTML rendering control. We are using this as a key product feature. Outlook98
also uses this capability. However, Outlook uses extended features -
specifically authoring of HTML - that is not available to us. We asked Microsoft
if we could use the extended features and were told that these new APIs were not
yet available because they were "not ready for prime-time." Again,
this puts us at a disadvantage.</p>
- John Gailey</p>
<p align=right>NWA 000081</p>
<hr>
<br>
Ryan Richards - Re: Outlook Icon on Desktop<br>
<p align=right>Page 1<br><br>CONFIDENTIAL</p>
<blockquote><b>From:</b> John Gailey<br>
<b>To:</b> Ryan Richards<br>
<b>Date:</b> 3/5/98 2:43 PM<br>
<b>Subject:</b> Re: Outlook Icon on Desktop</p>
I don't know specifically what David is referring to - sorry. There are a couple
of things i do know....</p>
* Outlook 97 (part of Office97) included a new version of MAPI (de facto
messaging API) which caused GroupWise to not run correctly.<br>
* Outlook 98 (beta - it will ship later this month) included a new version of
MAPI which caused GroupWise to not run at all.<br>
* All office productivity applications, such as Microsoft Office and Corel
WordPerfect Suite, use MAPI to integrate with messaging products such as
GroupWise. With the Outlook 98 beta II installed, Microsoft Office would only
communicate with Outlook and would not recognize GroupWise.<br>
* Outlook 97, a MAPI-compliant application, would not run with GroupWise at all
until we made specific changes to support it - a conflict with the MAPI
"standard" specification.<br>
* Outlook 97 uses MAPI to store and retrieve calendaring data, which many
customers desire, Groupwise also supports calendaring data and we desired
interoperability. We asked Microsoft for details on the calendaring formats so
we could interchange data and functionality and were told that this information
would not be available. The inability to interoperate with Outlook clients
causes many customers to standardize on a single vendor.<br>
* Microsoft is placing the Outlook icon on the desktop, and in fact, does so by
replacing the original "Inbox" icon that shipped as part of
Windows95.<br>
* Microsoft continues to deliver new capabilities in components such as
COMCTL32.DLL that all products can use to obtain a common look and feel with
other products (especially to be consistent with Microsoft desktop
applications.) They have allowed companies such as Novell to re-distribute these
kinds of DLLs. With the IE4 release, significant changes were made to these
controls and re-distribution was revoked unless we agreed to distribute the
entire IE4 product. For the specific COMCTL32.DLL case, Microsoft has finally
relented and will allow re-distibution (after we had already implemented our own
version.) This has put us at a dis-advantage[sic].<br>
* A new control that is "packaged" as part of the IE4 release is an
HTML rendering control. We are using this as a key product feature. Outlook98
also uses this capability. However, Outlook uses extended features -
specifically authoring of HTML - that is not available to us. We asked Microsoft
if we could use the extended features and were told that these new APIs were not
yet available because they were "not ready for prime-time." Again,
this puts us at a disadvantage.</p>
- John Gailey</p>
>>>Ryan Richards 02/23 10:03
AM>>><br>
John,</p>
I'm preparing a submission to the DOJ regarding Microsoft practices that are
harming Novell. David Bradford recently stated to me that Microsoft has placed
the Outlook icon on the Windows desktop and that certain other code is being
placed in Windows (95, 98, and NT) that make it difficult to access GroupWise.
I'm trying to track down exactly what has happened. Could you, or someone else
from GroupWise give me more information on this? Who could I call and talk to
about what Microsoft is doing to disadvantage GroupWise and what remedies we
should seek?</p>
Thanks,<br>
Ryan<br>
</blockquote>
<p align=right>NWA 000082</p>
[ Reply to This | Parent | # ]
|
|
|
|
|
