DOCERR: Custom Input/Output Procedure for Compound Files

• Microsoft Windows Software Development Kit (SDK) version 3.1
• Microsoft Win32 Software Development Kit (SDK) versions 3.5, 4.0

SUMMARY

The first paragraph of the "Using Custom Input/Output Procedures" topic in the Win32 SDK "Overviews, Multimedia Services, Multimedia File Input/Output" section refers to a predefined I/O procedure for accessing compound files. This reference has nothing to do with OLE compound files and should be disregarded. It refers to a completely different and completely obsolete file format. There is no predefined I/O procedure for OLE compound files. Please see the documentation for the products listed at the beginning of this article for information about writing a custom I/O procedure.

MORE INFORMATION

The incorrect paragraph from the Win32 SDK appears below. The "Multimedia Programmer's Guide" from the Windows 3.1 SDK contains a similar paragraph under the "Using Custom I/O Procedures" topic.

Multimedia file I/O services use I/O procedures to handle the physical input and output associated with reading and writing to different types of storage systems, such as file-archival systems and database-storage systems. There are predefined I/O procedures for standard Microsoft Windows files and for memory files. In the future, there will be a predefined I/O procedure for accessing elements of compound files. Compound files consist of a number of individual files, called file elements, bound together in one physical file.