SB AWE32 Developer's Information Pack
PART III Windows Driver API
••
53
Copyright
Creative Technology Ltd., 1994-1996
Version 3.00
Specify a word data type. The application should fill the word with the
desired User Bank number. The valid range of User Bank numbers is 1 to
127.
Note : By default, the driver will remember any user banks that are loaded
using this message. Driver will reload user banks after system reboot unless
the high bit of the User Bank number is set when sending this message.
lParam2
Specify a far pointer to CBufferObject, LPBUFFEROBJECT. When the
application calls the manager, the following fields are used:
Member
Remarks
m_Size
Indicates the size of buffer area.
m_Flag
Indicates if buffer contains a path name.
m_Buffer
Far pointer to a buffer area.
The m_Flag field is used to indicate whether the User Bank will be loaded
from a file or from a chunk of memory buffer. The value of m_Flag should be
either OPER_MEMORY or OPER_FILE where OPER_MEMORY indicates
loading from memory buffer pointer by the m_Buffer and OPER_FILE
indicates loading from a file.
hUserID
Current ID assigned to the application by the AWE Manager during
initialization.
Remarks
The following are some important points to note when using this function.
The location passed in as pointer must be valid memory locations allocated
by the parent application. If the locations are invalid, it is possible to trip a
General Protection Fault in Windows.
It is recommend that the application use the macro defined by this API
library. The OPER_FILE and OPER_MEMORY are constant macros used to
distinguish between file loading or memory operations.
Return
The return value will be AWE_NO_ERR if the operation is successful, and
an error code otherwise. Possible errors are:
AWE_ERR_USERID_INVALID
AWE_ERR_DEVICE_BUSY
AWE_ERR_PATHNAME_INVALID
AWE_ERR_USER_OBJ_INVALID
AWE_ERR_UBANK_INVALID
AWE_ERR_RESOURCE_INSUFFICIENT
AWE_ERR_SYSMEM_INSUFFICIENT
AWE_ERR_DRAM_INSUFFICIENT
See Also
AWE_LOAD_USER_INSTR, AWE_CLEAR_USER_BANK