If you are going to install your Creative PnP card in a PnP system like Windows 95, you only need to "plug" the card into your personal computer and the card will "play" shortly after the system reboots.
However, if you want to install this card in a non-PnP environment such as DOS/Windows 3.1x or Windows 95 MS-DOS Mode, you need to use Creative PnP Configuration Manager (CTCM) and Creative PnP Configuration Utility (CTCU).
The information in this document is organized as follows:
Please read the README.TXT file in your PnP Configuration Manager diskette for the latest information on the software.
DEVICE=<C:\CTCM>\CTCM.EXEwhere <C:\CTCM> is the directory where you have installed CTCM.
This CTCM statement will be placed before all the statements that load other low-level device drivers (such as CTSB16.SYS and SBIDE.SYS) so that your Creative PnP cards will be configured before these device drivers try to use them.
If you add this line to CONFIG.SYS manually, please make sure that this line is placed after the statement (if any) that loads the other PnP configuration manager in your system.The installation program will also add the following line to the AUTOEXEC.BAT file:
SET CTCM=<C:\CTCM>where <C:\CTCM> and <C:\WINDOWS> are the directories where your CTCM/CTCU and Windows 3.1x files are installed respectively.<C:\CTCM>
\CTCU /S /W=<C:\WINDOWS>
After the installation, CTCM and CTCU will be invoked each time you boot your system. CTCM will scan for and configure any unconfigured Creative PnP cards. CTCU will run in silent mode and update the parameters needed by your Creative and Windows drivers. It will also update the BLASTER environment variable if it detects a Creative audio card in the system.
For more details on how the CTCM and CTCU commands work, please read the sections "Using CTCM" and "Using CTCU".
To configure Creative PnP cards in Windows 95 MS-DOS Mode, CTCM is required but CTCU is not necessary since CTCM can get both legacy (non-PnP) and PnP card settings from Windows 95. However, you do not need to install CTCM or CTCU in Windows 95 because the Creative Windows 95 software for your PnP card will install CTCM into your Windows 95 directory for you.
CTCM configures Creative PnP cards only. But it can work with or without another PnP configuration manager installed in the same system.
CTCU does not access the resource settings database used by ICM. So, do not use CTCU to change or disable your card settings if you already have ICM installed. Use ICU instead.To run CTCU in DOS/Windows 3.1x:
CTCU /S /W=<C:\WINDOWS>where <C:\WINDOWS> refer to the directory where your Windows 3.1x files are installed.
Parameter | Description |
/S | Notifies CTCU to run in silent mode. This means that CTCU will not display any messages or screens. It will simply update the parameters required by the Creative drivers. If you do not use the /S switch, CTCU will run in full-screen mode (see Figure 1). |
/W | Informs CTCU to update the PnP hardware information of your Windows
drivers in the SYSTEM.INI file. If you do not use this switch, CTCU will prompt you to enter the name of the directory where your Windows files can be found. |
You can use your mouse or keyboard to move around and select an item or action in CTCU.
Mouse Action
The instructions in the following sections are written with the assumption that you will use your mouse in CTCU.
You can use this section to view the resource settings of the PnP cards in your system and change the settings of Creative PnP cards only.When you select the PnP Cards section from the CTCU menu, the Plug and Play window (see Figure 2) will appear, listing the PnP cards in the system. Choosing a card here will, in turn, display a list of logical devices on that particular card.
To view the resources for a PnP device, select the device from the list and click the Resources button. The Resources window (see Figure 3) will appear.
To change the resource configuration, click the down arrow next to the Configuration box and then select a suitable configuration which has all the settings that your card needs.
To disable a logical device, click the Disable checkbox. A mark will appear in the box, informing CTCM not to configure this device the next time it runs.
Depending on the setting that you have chosen, one of the following windows will appear:
The Interrupt window (see Figure 5) displays the current interrupt resource setting and a list of possible settings. To change this setting, select one from the list and click the OK button. Make sure that the new setting does not conflict with the other cards' settings.
The Direct Memory Access window (see Figure 6) displays the current DMA resource setting and a list of possible settings. To change this setting, select one from the list and click the OK button. Make sure that the new setting does not conflict with the other cards' settings.
The Memory Range window (see Figure 7) displays the current 32-bit memory resource setting and a list of possible settings. To change this setting, select one from the list and click the OK button. Make sure that the new setting does not conflict with the other cards' settings.
Each of these windows has a Conflicting Devices message box which will inform you of any hardware conflicts that may result from the settings you have just selected for your card.To see the list of settings available in each window, click the down arrow on the right-hand side of the Choices box.
If the testing is not successful, you should reconfigure and test the setting again.CTCU supports the testing of Creative's audio and wavetable devices only.
You can use this section to enter, view or change the resource settings of all the legacy (non-PnP) cards in your system.When you select the Legacy Cards section from the CTCU menu, the Legacy window (see Figure 9) appears.
The Legacy window allows you to view and alter your existing card's resource settings by clicking one of the following buttons:
These resources are grouped by type and displayed in four boxes Input/Output range (I/O), Interrupt Request line (IRQ), Direct Memory Access channel (DMA), and 32-bit memory range (Mem).
You must enter the card's name in the Card Name field. The other fields can be left blank.
To re-install the same card, you have to enter the card's original settings again.
Alternatively, you can retain a card's resource settings by simply marking the settings for retrieval in the Change window (refer to the next section).
To store a card's system settings, mark the Card Removed checkbox in the Change window and click OK.
To re-install the card in future, simply unmark the checkbox to retrieve its original settings.Be very careful when you add or change resource information for a legacy card. Verify all the hardware settings of the legacy cards in your system. Filling in incorrect data may reserve resources which will not be used by any device!
You can use this section to view but not change the resource settings of the system devices in your computer.When you select the System Devices section from the CTCU menu, the System Device Resources window (see Figure 14) appears, listing all the resources used by your system devices.
These resources are grouped by type and displayed in four boxes input/output range (I/O), interrupt (IRQ), Direct Memory Access channel (DMA) and 32-bit memory range (Mem).
You can use this section to view but not change the resource settings of the PCI devices in your computer.When you select the PCI Devices section from the CTCU menu, the PCI Devices window (see Figure 15) appears.
This window allows you to view your existing PCI card's resource settings by clicking one of the following buttons:
Peripheral Component Interconnect (PCI) local bus is a newly developed bus system that utilizes a 32-bit data path running at a 33 MHz clock speed. This bus architecture yields a huge data transfer rate as compared to the standard ISA bus.
Before Plug and Play (PnP) was introduced, you can reserve system resources only by manually changing the settings of some dip switches or jumpers on a legacy (non-PnP) card. This can be quite difficult since you have to understand how the hardware settings correspond to the system resources that your card requires. It can also be very tedious since you may need to change the dip switch or jumper settings several times before your card can be configured without any hardware conflict.
With the emergence of Plug and Play (PnP), a revolutionary design philosophy and a new PC architecture specification, the PC, hardware cards, drivers and the operating system can now work together without such "user intervention".
You no longer need to change any hardware settings on your card before it can work properly in a PC. Instead, a PnP BIOS or software would find out the types of resources each card needs and allocate the resources accordingly.
Generally, a PnP card requires one of the following to work:
The PnP BIOS specification went through several revisions. The version 1.0a specification was finalized in May 1994, with further clarifications documented in October 1994. As a result, older PnP systems shipped are not fully compliant with this specification. So, there are some compatibility problems. For more details, please read the section "PnP in DOS/Windows 3.1x".
Some PnP system BIOS configure PnP cards automatically. Other BIOS give you an option in their setup utilities to disable their PnP configuration capability. Please refer to your system manual for more details.
Windows 95 is an example of a PnP operating system. When you install or upgrade to Windows 95 for the first time, it will automatically determine the resource settings of the existing cards in your system and allocate other resources to new PnP cards.
When you add a legacy card later, however, you will need to run the "Add New Hardware" wizard in Control Panel so that Windows 95 can detect this card. To avoid any conflicts that may be introduced by the hardware settings of this new legacy card, Windows 95 may also re-assign different resources to existing PnP cards.
A PnP configuration driver determines the resource settings of all your system devices and legacy cards, configures PnP cards, and provides relevant configuration information to other drivers or applications that access your PnP cards.
A PnP configuration utility allows you to view, enter or change the resource settings of the PnP and legacy cards in your system. The new or changed settings are then used by the PnP configuration driver to configure new PnP cards.
Intel Configuration Manager (ICM) and ISA Configuration Utility (ICU) are examples of a PnP configuration driver and a PnP configuration utility. For more details, please read the section "PnP in DOS/Windows 3.1x".
For more details on how you can start an MS-DOS Mode session in Windows 95, please refer to the documentation that comes with Windows 95.
Currently, a generic set of PnP configuration driver and utility that you can find in the market for the DOS/Windows 3.1x environment is ICM. Consisting of Intel Configuration Manager (ICM) and ISA Configuration Utility (ICU), this driver and utility set was developed by Intel Corporation as an interim solution to facilitate PnP configuration when a PnP operating system is not available. It may come pre-installed in your PC or bundled with your PnP cards.
However, due to the compatibility problem mentioned earlier (please refer to the note in the section "PnP Concepts"), you may encounter one of the following error message or problems when you use ICM version 1.43 to configure your PnP card:
CTCM can be loaded as a device driver through a statement in the CONFIG.SYS file. It can also be run from the DOS prompt. It configures Creative PnP cards only and provides configuration information to other drivers or DOS applications.
CTCU is used when your DOS/Windows 3.1x system does not have ICM and ICU. It allows you to perform the following functions on the devices in your system:
CTCM, on the other hand, configures Creative PnP cards with the same settings used by Windows 95. You need not run CTCU at all. CTCM also does not stay resident and thus, does not waste any memory space.
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.
Question | I have a PnP BIOS as well as a PnP operating system or a PnP configuration
driver and utility. Which one should I use to configure my PnP card? |
Answer | If you have a PnP operating system or a PnP configuration driver and
utility, it is better to let your PnP operating system or configuration driver
configure your PnP card. Try to set your BIOS so that it will not configure
PnP cards since it may not have access to the hardware setting information of
your legacy (non-PnP) cards and thus may give your PnP card some settings that
would conflict with those of existing legacy cards. |
Question | I have just upgraded my operating system from DOS/Windows 3.1x to Windows
95. But I do not have any Windows 95 software for my Creative PnP cards.
What must I do to configure these cards properly? |
Answer | Look for a CTCM.INF file in your CTCM directory. Right-click on the file
and select Install from the shortcut menu that appears. This program will
copy some drivers into your system to configure your PnP cards in MS-DOS Mode.
It will also convert into remarks all CTCM/CTCU statements in your CONFIG.SYS
and AUTOEXEC.BAT files as Windows 95 will take care of all PnP configurations
in its Windows and DOS box environments. |
Question | Must I remove ICM in order to use CTCM? |
Answer | No, you do not have to remove ICM to use CTCM. If both CTCM and ICM are
installed in your system, just make sure the CTCM statement in your CONFIG.SYS
file is placed after the ICM statement. |
Question | What should I do if I cannot configure my Creative PnP card using
ICM? |
Answer | If you cannot configure your PnP card using ICM, try removing ICM. Then
use CTCU and CTCM to change and reconfigure your card settings. For more details on using CTCU or CTCM, please refer to the sections "Using CTCM" and "Using CTCU". |
Question | Can I run CTCU to change or disable my card settings if I have ICM in my
system? |
Answer | No, do not use CTCU to change or disable your card settings since CTCU
does not access or update the resource settings database used by ICM. You should use ICU instead to change or disable your card settings if ICM is already loaded into your system. |
Question | How do I use CTCM to configure both legacy and PnP cards in DOS/Windows
3.1x? |
Answer | First, run CTCU to add the information on the hardware resource used by
your legacy cards. Next, run CTCM to configure your PnP card.
Alternatively, if you do not know your legacy cards' settings, use CTCU to change the settings of your PnP card. Then run CTCM and test whether your card works properly. This is a trial-and-error method since CTCM will not be "informed" about the resources that have been reserved by your legacy cards. You may need to try different combinations of settings before you can configure your PnP cards successfully, without any hardware conflicts with existing cards.
For more details on using CTCU or CTCM, please refer to the sections
"Using CTCM" and "Using CTCU". |
Question | My system hangs or reboots whenever I load CTCM. What should I
do? |
Answer | The memory area of your PnP BIOS machine is probably mapped by EMM386
using the HIGHSCAN option and thus, can get corrupted easily. When it does,
CTCM will not work properly. Your system may then hang or reboot whenever
you load CTCM.
To solve this problem, remove the HIGHSCAN option in the EMM386 statement in the CONFIG.SYS file. For example, change the statement DEVICE=<C:\dir>\EMM386.EXE HIGHSCAN <other parameters>where <C:\dir> is the directory in which your EMM386 program is installed and <other parameters> are the other parameters in the EMM386 statement. |