Creative AWE32 - Hardware Detection And Initialization

To Next Page

To Previous Page

SB AWE32 Developer's Information Pack PART II DOS Real/Protected Mode API •• 11

PART II DOS Real/Protected Mode

API

Overview

This chapter gives an overview of the DOS object modules and the sample applications. Note that this

chapter does not attempt to cover programming the Sound Blaster. Please refer to “Sound Blaster

Developer Kit for Sound Blaster Series, 2nd Edition” if you need more information on programming the

Sound Blaster.

The object modules are provided in five memory models; SMALL, COMPACT, MEDIUM, LARGE and

FLAT. The object module files are :

MIDIENG.OBJ MIDI engine. Contains all MIDI channel message services.

SYSEX.OBJ SysEx parser

SFHELP1.OBJ SoundFont helper module 1

SFHELP2.OBJ SoundFont helper module 2 shared by SBKLOAD.OBJ and

WAVLOAD.OBJ

EMBED.OBJ General MIDI preset module

MIDIVAR.OBJ MIDI variables, used by all modules

HARDWARE.OBJ EMU8000 hardware initialization module

SBKLOAD.OBJ SoundFont bank loader module

WAVLOAD.OBJ Wave PCM loader module

NRPN.OBJ Non-Registered Parameter Number interpreter.

NRPNVAR.OBJ Data buffers use by Non-Registered Parameter Number interpreter.

HARDWARE.OBJ, SBKLOAD.OBJ, WAVLOAD.OBJ and SFHELP2.OBJ are discardable after they

have been used. For example, in a TSR program, after you have initialized the SB AWE32 hardware and

loaded your SoundFont bank file, you can mark portions of your code that must stay resident (the MIDI

engine, the embedded General MIDI preset data and any SoundFont preset data), and discard the

hardware and the SoundFont loader module.

A sample application is included in this information package.