The "Drivers" column shows you detailed data about the drivers that implement
the device.
Depending on the type of the device, the following information may be shown:
- Media control driver: The MCD is responsible for interpreting
multimedia commands that are sent from an application to a device. It is up
to the MCD to take further action depending on the command that was sent.
The name listed here will correspond to a
DLL
in the MMOS2 directory.
- Vendor-specific driver: If installed, the VSD usually gets called
from the MCD for implementing functions for a certain hardware. This architecture
allows MMPM/2 to keep the MCD's fairly generic, while the hardware-specific
code will usually be in the VSD.
For example, the "waveaudio" devices are usually implemented by a generic
MCD, while the actual work on the sound card is done in a VSD (which will in
turn communicate with a device driver).
- Physical device driver: The PDD is responsible for actually working
on the hardware. Since this has to be done at ring 0, especially if interrupts
need to be processed, this layer is necessary.
Not all devices will need a PDD. Typically this is the case for sound cards,
which need to handle interrupts and DMA.
- Parameters: these are additional parameters from the ASCII
MMPM2.INI
file in your MMOS2 directory that were specified for
the device. This is device-specific, but appears to be related to what was
specified for a device in the "Multimedia Setup" object.