Release Notes for Windows Media Format 11 SDK

  • Article

September 2006

This documentation provides late-breaking or other information that supplements the documentation for the Windows Vista release of the Windows Media Format 11 SDK.

Contents

Setup issues

Multiple delivery vehicles

Separate installation directories

Redistributable runtime libraries

Windows Portable Devices applications for Windows XP

Minimum system requirements

Known issues

Setup Reboot return code does not work properly in setup quite mode installation

IWMDRMSecurity::PerformSecurityUpdate method only individualizes if set to force individualization

Use of content enabler to renew revoked components requires a privacy statement

Implementations of IMFMediaEventGenerator in the Windows Media DRM Client Extended APIs do not always generate an event if operations fail

Legal notice

Setup issues

Multiple delivery vehicles

There are two delivery vehicles for the Windows Media Format 11 Software Development Kit (SDK): the Windows SDK install package and the Windows Media Format SDK install package.

Separate installation directories

There are separate installation directories for the Windows Media Format 11 SDK installation package and the Windows SDK installation package.

  • For the Windows Media Format 11 SDK, the default installation directory is SystemDrive:\WMSDK\WMFSDK11.
  • For the Windows SDK (also known as the Platform SDK), the default installation directory is SystemDrive:\Program Files\Microsoft SDKs\Windows\v6.0.

Redistributable runtime libraries

  • The Windows Media Format SDK redistributable runtime libraries are only available as part of the Windows Media Format SDK install package, and can be found in the \WMSDK\WMFSDK11\Redist folder.

Windows Portable Devices applications for Windows XP

  • If you are creating a Windows Portable Devices (WPD) application for the Microsoft Windows XP operating system, you must distribute the Windows Format 11 Software Development Kit (SDK) redistributable runtime libraries along with your application.
  • For information about creating a WPD application, see the WPD SDK at https://go.microsoft.com/fwlink/?LinkId=72083.

Minimum system requirements

The following software is required to use the Windows Media Format 11 SDK:

  • Operating system

    Requirement: Microsoft Windows XP or Windows Vista

Known issues

Library Linking Error

The msvcrt.lib library must be linked into an application before the stub library to avoid any linker errors.

IWMDRMSecurity::PerformSecurityUpdate method only individualizes if set to force individualization

In this preliminary release of the Windows Media Format 11 SDK, the only way to perform individualization by using the IWMDRMSecurity::PerformSecurityUpdate method is to use the WMDRM_SECURITY_PERFORM_FORCE_INDIV flag. If you call the method passing the WMDRM_SECURITY_PERFORM_INDIV flag, the component should automatically detect whether individualization needs to be performed and, if so, perform it. However, the automatic detection is not functional in this release.

Use of content enabler to renew revoked components requires a privacy statement

If you create an application that uses the methods of the IWMDRMSecurity2 interface to renew revoked components, you must clarify the process to the user. This clarification must be made because the update process sends information from the client computer to a Microsoft Web site.

When you call IMFContentEnabler::AutomaticEnable, the content enabler launches the default browser with the address of the update service on the Microsoft Web site. A unique identifier that identifies the revoked component is sent to the update service. The service then redirects the browser to a Web page from which the user can download and install the new version of the revoked component.

Implementations of IMFMediaEventGenerator in the Windows Media DRM Client Extended APIs do not always generate an event if operations fail

Several of the objects of the Windows Media DRM Client Extended APIs implement the Media Foundation event model to support asynchronous procedures. The documentation does not note that these implementations do not always generate an event. If you write your code to wait for an event without additional logic, your application might enter an infinite loop.

The Media Foundation interface, IMFMediaEventGenerator, is inherited by IWMDRMEventGenerator, which adds support for a cancellation cookie that can be used to cancel an asynchronous procedure in process. Each asynchronous method includes a parameter for the cancellation cookie, which is the address of an IUnknown pointer that is set when the method returns.

When you call an asynchronous event and it returns, you should check the cancellation cookie. If no cookie has been set, then the initial processing for the procedure failed and no events will be generated.

Information in this document, including URL and other Internet Web site references, is subject to change without notice and is provided for informational purposes only.  The entire risk of the use or results of the use of this document remains with the user, and Microsoft Corporation makes no warranties, either express or implied.  Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, e-mail address, logo, person, places or events is intended or should be inferred.  Complying with all applicable copyright laws is the responsibility of the user.  Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.

Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document.  Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.

© 2006 Microsoft Corporation. All rights reserved.

Microsoft, MS-DOS, Windows, Windows NT, Windows Server, Windows Vista, Active Directory, ActiveSync, ActiveX, Direct3D, DirectDraw, DirectInput, DirectMusic, DirectPlay, DirectShow, DirectSound, DirectX, Expression, FrontPage, HighMAT, Internet Explorer, JScript, Microsoft Press, MSN, Outlook, PlaysForSure logo, PowerPoint, Visual Basic, Visual C++, Visual InterDev, Visual J++, Visual Studio, WebTV, Windows Media, Win32, and Win32s are either registered trademarks or trademarks of Microsoft Corporation in the U.S.A. and/or other countries.

All other trademarks are property of their respective owners.