CREATIVE AWE64 - Manual (Page 83)

16
Why Use CTCM and CTCU?
There are several reasons why we offer CTCM and CTCU:
1. CTCM provides a consistent method for configuring all
Creative PnP cards. It works with or without PnP BIOS or
ICM. If your PnP BIOS or ICM has already configured your
PnP card(s), CTCM will simply retain those settings.
2. If the PnP BIOS or ICM did not configure your Creative PnP
cards properly, due to incompatibility problems similar to
those mentioned in the section “PnP in DOS/Windows 3.1x” in
page 14, CTCM may be able to allocate resources to these
cards.
3. You need not reboot your system after using CTCU to change
Creative PnP card settings, if you do not have any DOS device
drivers (e.g., SBIDE.SYS or CTSB16.SYS) loaded. You only
need to run CTCM to reconfigure the card. This is possible
because CTCM can be activated from the DOS prompt, unlike
ICM.
Limitations of CTCM and CTCU
If you use a non-PnP operating system like DOS/Windows 3.1x and
do not have a PnP BIOS or ICM, your PnP card works like a
software-configurable card.
In such an environment, CTCM needs to know which resources have
been reserved by all the legacy and PnP cards, and system devices in
your system before it can allocate conflict-free resources to your new
Creative PnP card.
CTCM can get the resource settings of PnP cards and system devices
from the PnP cards and BIOS. But you need to use CTCU to enter the
resource settings of all the legacy cards in your PC, and then run
CTCM to configure your Creative PnP card.
You may still encounter hardware conflicts if the resource settings
specified through CTCU are incomplete or wrong. If this happens, use
CTCU to select a different group of resources for the Creative PnP
card that caused the conflict. You may need to try a few combinations
until you find one that works. This can be tedious, but it is easier than
the legacy way of changing dip switches or jumpers.