#Descargar image mastering api 2.0 iso#

The MSBurnEngineObj expects that the contents of the stash will be in a specific known format. The stash is then passed on to the MSBurnEngineObj (through IMSBurnEngine) when a burn is requested from the lower level engine. The MSDiscStashObj represents (through IDiscStash) a raw file up to 800 MB in size that is used by MSDiscMasterObj to create images of the audio or data discs to be burned. They are minimally documented to clarify architecture only. The remaining two objects: MSDiscStashObj and MSBurnEngineObj are internal interfaces accessed by IMAPI. This includes such properties as writer speed or other burn parameters. In addition, applications can access generic properties of a recorder through the IDiscRecorder interface. An application uses the pointers to the IDiscRecorder interfaces on those objects to select which device will be used by IMAPI to record a CD. Every CD-R or CD-R/W device that is compatible with IMAPI will have a corresponding MSDiscRecorder object. MSDiscRecorder objects are accessed through IDiscRecorder interfaces. This includes such properties as volume name or legacy file name. Applications can access generic properties of the IJolietDiscMaster Interface. While it is expected that every application will be able to find and talk to IDiscMaster and IDiscRecorder, it is not expected that every application will know about or understand the specific format interfaces. The IJolietDiscMaster and IRedbookDiscMaster interfaces are returned to an application through the IDiscMaster interface when a format is selected, and they allow specific control of the content of a data or audio disc respectively. Applications use the IDiscMaster interface to open IMAPI, enumerate supported formats (Joliet and Redbook), select a format, get a list of recorders, select a recorder, and finally start a burn. There may be multiple MSDiscMasterObj objects instantiated on a system, but only one application may access a recorder at a time. Of these, the MSDiscMasterObj is the only object with multiple interfaces besides IUnknown. The four main objects are as follows: MSDiscMasterObj, MSDiscRecorderObj, MSDiscStashObj, and MSBurnEngineObj.

As such, descriptions of the four main COM objects and their interfaces are included in this document. This document focuses on a description of the Adaptec implementation of IMAPI for Microsoft. The API architecture allows for future expansion of the supported format set.

#Descargar image mastering api 2.0 iso#

The specific formats to be supported are Redbook audio and data discs with both Joliet and ISO 9660. The Image Master API (IMAPI) allows an application to “stage” and “burn” a simple audio or data image to on a CD-R or CD-R/W devices.