A file name may be truncated when you use the Image Mastering API v2.0 (IMAPI v2) to perform optical burning on a Windows Server 2003-based computer

Consider the following scenario:

• On a Windows Server 2003-based computer, you have a program that uses the Image Mastering API v2.0 (IMAPI v2) engine to perform optical burning.
• On this computer, you have a file whose name is longer than 108 characters. For example, the file name is 120 characters.
• You use the program to burn this file to a CD or to a DVD by using the Universal Disk Format (UDF) format.
  
  Note The maximum file name length for UDF is 127 characters. Therefore, the name of the file that you try to burn does not exceed the UDF limitation.

However, after the file is burned, the file name is truncated to 108 characters. This issue may cause program failures if the program assumes that the file name is not truncated after a file is burned to a CD or to a DVD.

In IMAPI v2, the limitation on the file name length is overly restrictive.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must have Windows Server 2003 Service Pack 2 installed.

Restart requirement

You have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other previously released hotfixes.

Registry information

To use this hotfix, you do not have to make any changes to the registry.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Server 2003 with SP2, x86-based versions

Windows Server 2003 with SP2 and Windows XP with SP2, x64-based versions

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

IMAPI is the optical burning engine in Windows products. Version 2 of IMAPI extends Windows Vista support for DVD media to Windows XP and to Windows Server 2003.

Microsoft has learned that some OEMs are incurring sizable support costs that are associated with multiple optical burn engines being installed on customer systems. Therefore, some OEMs will require ISVs to migrate to IMAPI v2 to reduce the number of burn engines that are shipped. IMAPI v2 lets ISVs use only one set of APIs for optical burning that includes DVD burning capabilities for the following operating systems:

• Windows Vista
• Windows XP
• Windows Server 2003

For more information about IMAPI v2, click the following article number to view the article in the Microsoft Knowledge Base: For more information, click the following article number to view the article in the Microsoft Knowledge Base: