[This is preliminary documentation and subject to change.]
The CreateNtmsMediaPool function creates a new application media pool.
DWORD WINAPI CreateNtmsMediaPool(
HANDLE hSession,
LPCTSTR lpPoolName,
LPNTMS_GUID lpMediaType,
DWORD dwAction,
LPSECURITY_ATTRIBUTES lpSecurityAttributes,
LPNTMS_GUID lpPoolId
);
Value | Meaning |
---|---|
NTMS_OPEN_EXISTING | Opens an existing media pool by name. Returns ERROR_INVALID_PARAMETER if the pool does not exist. |
NTMS_OPEN_ALWAYS | Opens an existing media pool or creates the pool if it does not exist. |
NTMS_CREATE_NEW | Creates a new media pool. Returns ERROR_ALREADY_EXISTS if the pool exists. |
Scratch, Foreign, and Import media pools are created by RSM and cannot be created with the CreateNtmsMediaPool function.
RSM media pools are organized as a hierarchy separated by the "\" character. The Application, Scratch, Foreign, and Import media pools exist at the root of the hierarchy. RSM creates and manages the Scratch, Foreign, and Import pools. RSM creates a Scratch media pool for each media type available.
Application-specific media pools are created by applications. Applications create media pools for their own use under the root application pool. These media pools have file system-like names. Only the end-point of the name contains media and policy. An application can define pools such as \MyApp\Pool1 and \MyApp\Pool2. This conveys the hierarchy to the user interface and avoids duplicate names. Each pool level must be created individually; first MyApp and then Pool1 and Pool2, much like folders and files.
Windows NT: Requires version 5.0 or later.
Windows: Unsupported.
Windows CE: Unsupported.
Header: Declared in ntmsapi.h.
Import Library: Use ntmsapi.lib.
Media Services Functions, AllocateNtmsMedia, DeleteNtmsMediaPool, GetNtmsObjectSecurity, SetNtmsObjectSecurity