ISA Configuration Utility Messages: Dell OptiPlex GX1 and GX1p Mini Tower Managed PC Systems

ISA Configuration Utility Messages: Dell™ OptiPlex™ GX1 and GX1p Mini Tower Managed PC Systems

	Overview		Configuration Manager Messages
	ICU Error Messages

Overview

The ISA Configuration Utility (ICU) and its Configuration Manager are capable of identifying problems and alerting you to them. Both utilities can alert you to problems with card configuration as well as problems that prevent proper operation of the utility. This appendix describes each type of message and lists the possible causes and actions you can take to resolve problems indicated by a message. See the following tables to locate your message and identify possible corrective actions.

ICU Error Messages

The ICU can display a variety of error messages while in operation. These messages alert you to problems that prevent the ICU from running correctly and inform you of resource conflicts that prevent the configuration of various cards in your computer. If you receive a message from the ICU, see the following table for suggestions on resolving any problems indicated by the message.

Message	Probable Cause	Corrective Action
Out of memory Memory allocation failed	Either of these messages can appear if the system runs out of memory during operation of the utility.	Disable any TSR programs or any unneeded device drivers.
Not enough memory to run the ICU	This message appears when you start the ICU if the system does not have enough memory to run the utility.	Disable any TSR programs or any unneeded device drivers.
Can't open index file. This file is required for ICU to run.	The ICU cannot find the index file for its database.	Make sure to switch to drive A before attempting to start the utility.
No Configuration Manager.	The device driver needed by the ICU is corrupted or is not correctly configured.	Verify that the following device statement appears in your config.sys file: device=drive:\directory\ drivers\dos\dwcfgmg.sys In this statement, drive and directory represent the drive and directory where the driver resides. The default is c:\plugplay.
At least one Plug and Play card in your system is not configured due to conflicts. These are marked "config err" in the list of configured cards. Due to conflicts, the ICU could only configure some Plug and Play cards in your system. Unconfigured cards are marked "config err" in the list of configured cards.	The Configuration Manager or the ICU cannot configure at least one Plug and Play expansion card because of resource conflicts with one or more cards.	You must reconfigure the conflicting card(s). To find the conflicting card, perform the following steps: Select the Plug and Play expansion card marked with config err, and then click the Modify button. The Card Configuration dialog box displays the functions assigned to the Plug and Play expansion card. Select a function and then click Settings. Click Cancel if the ICU does not display a message naming the conflicting card. Repeat step 2 until the ICU displays a message box naming the conflicting card and the resource(s) in conflict. See the following table entry for an explanation of this message box.
This device is unconfigurable because of a resource conflict with card card_name. The conflicting resource is resource_name. To fix, reconfigure the conflicting card.	The selected card is unconfigurable because one of its resources is already being used by another device.	Perform the following procedure: Make a note of the card name and the type of conflicting resource. Follow the procedure in "Modifying a Card" and change the value for resource_nameused by card_name.
The ICU has successfully configured all Plug and Play cards in your system. For the new configuration to take effect, save the configuration, then reboot your system.	The ICU has successfully configured all of the Plug and Play expansion cards that were not configured by the Configuration Manager.	To accept these settings, save the configuration information into NVRAM by selecting Exit from the File menu and then selecting Yes to save. You must reboot your system for these settings to take effect.
The loaded card is not a category card. Press OK to proceed.	The category you have chosen is not the correct category under which to add this card.	Select OK. The ICU automatically opens the correct category's dialog box. Continue the procedure for adding the card as described in "Adding a Listed Card" or "Adding an Unlisted Card."
No more DMA values can be added. No more interrupt values can be added. No more memory values can be added. No more I/O port values can be added.	No more values are available for the resource you are trying to add or modify.	The maximum number of values for each resource is as follows: 4 DMA channels 7 IRQ lines 9 memory address blocks 20 I/O ports To free values for the resource you are trying to add or modify, delete some of the values listed in the resource box for the card. If your card requires all of the values listed, contact your card manufacturer to resolve the issue.
The ICU detects a resource conflict between this card and conflicting_card. The conflicting resource was: resource.	You added or modified a card that now requires a resource value already in use by conflicting_card.	Try each of the following options until the problem is resolved: Modify the card you are adding so that it uses a different value for resource. See "Modifying a Card" for instructions. Modify conflicting_card so that it uses a different value for resource. See "Modifying a Card" for instructions. If conflicting_card is not the system board, remove it from the computer. See "Removing a Card" for instructions. Remove all expansion cards from the ICU, and then add them back one at a time, beginning with the new card and resolving resource conflicts as they arise. See "Removing a Card" and "Adding a Listed Card" or "Adding an Unlisted Card" for instructions. If you cannot resolve the resource conflict by any of the preceding methods, remove the new card. If you were modifying an existing card, reset the modified card to its previous resource value.
The configuration (.cfg) file used by the ICU for this card is now invalid or does not exist. Do you wish to load the file? No configuration (.cfg) file exists for the card being modified. Do you want to load one?	This message appears when you try to add a listed card and the configuration file for this card has been corrupted or deleted from the database. This message appears when you modify a card and its configuration file does not exist or has been deleted.	Use the following procedure: Insert the original ICU diskette into the diskette drive. You can create an ISA Configuration Utility diskette from the Dell ResourceCD. See "Preparing to Use the ICU." Change to the db subdirectory on the diskette drive. For example, type cd a:\db. Use a text editor to search the icu.ndx file for the card ID of the card you want to add or modify. The card ID forms part of the name of the configuration file. For example, if the card ID is ICU0200, the configuration file is!icu0200.cfg. Copy the configuration file from the original ICU diskette to the backup diskette.
This is an EISA system. Use an ECU, not the ICU, to configure your system.	This message appears if you attempt to run the ICU on an EISA system.	To use the ICU, you must load the utility onto a non-EISA system.
You have added a card using settings different from factory default. Reconfigure the card to the settings in the next display (see the card's manual) before installing it.	This message can appear in two situations: You added an ISA expansion card, selected OK, and the ICU had to use resource values different from the card's defaults to avoid conflicts. You added an ISA expansion card, selected Advanced, and chose resource values different from the card's defaults.	Make note of the new card configuration shown in the Card Resource Usage dialog box displayed after this message. Change jumper settings on the ISA expansion card to match the new card configuration.
NOTE: For the full name of an abbreviation or acronym used in this table, see the Glossary in the online* System User's Guide.*

Configuration Manager Messages

The Configuration Manager for the ICU identifies problems following system boot and generates messages if necessary. These messages alert you to any unsuccessful attempts to configure Plug and Play or Peripheral Component Interconnect (PCI) expansion cards, as well as any problems that interfere with the operation of the Configuration Manager. If you receive a message from the Configuration Manager, see the following table for suggestions on resolving any problems indicated by the message.

Message	Probable Cause	Corrective Action
Found Plug and Play ISA card: Plug and Play ISA Card Name.	This message appears at system start-up for each Plug and Play ISA expansion card recognized by the Configuration Manager.	Status message; no action is required.
NOTICE: Boot Device Not Active! CSN=Card Select Number.	A boot device was found to be inactive.	Status message; no action is required. The Configuration Manager automatically configures and activates the device.
One or more active devices have been reconfigured - system requires reboot. Press any key to reboot system.	You modified the resource values of one or more PCI or Plug and Play ISA expansion cards.	Reboot the system to reconfigure the card(s).
The Plug and Play ISA card has been successfully configured. Card Count Plug and Play ISA cards have been successfully configured.	The Configuration Manager has successfully configured the given number of cards.	If this message does not match the number of Plug and Play ISA expansion cards installed in your computer, reinstall any Plug and Play expansion cards not listed and reboot the system.
ERROR: Insufficient CM Memory	There is not enough memory available to the Configuration Manager for it to run.	Disable any TSR programs or any unneeded device drivers.
ERROR: Fatal BIOS error Internal Error Code.	A BIOS call failed with an internal error. The most likely cause is an incompatibility between the BIOS and the Configuration Manager.	See "Getting Help" in your Diagnostics and Troubleshooting Guide for instructions on obtaining technical assistance.
ERROR: Could not read NVS, Error=Internal Error Code.	An attempt to read the NVRAM failed.	See "Getting Help" in your Diagnostics and Troubleshooting Guide for instructions.
ERROR: Failed NVS write. Error=Internal Error Code.	An attempt to write to NVRAM failed.	Run the Dell Diagnostics to verify the integrity of your system NVRAM. See "Running the Dell Diagnostics" in your Diagnostics and Troubleshooting Guide for instructions. If you are unable to determine the cause of the error, see "Getting Help" in your Diagnostics and Troubleshooting Guide for instructions.
ERROR: Failed to activate device, CSN=Card Select Number.	A Plug and Play expansion card could not be activated.	Use the following procedure: Exit the ICU and turn off your system. Remove the Plug and Play expansion card that could not be activated. Follow steps 2 through 6 in "Removing an Expansion Card" and then return to this procedure. Reinstall the Plug and Play expansion card. Follow steps 5 through 10 in "Installing an Expansion Card" and then return to this procedure. If you still receive the error message, contact the manufacturer of the Plug and Play expansion card for assistance.
WARNING: Could not configure Plug and Play Card Name. WARNING: Could not configure PCI device, ID=DeviceID. Failed to configure Number of Total Count Plug and Play ISA devices. Use your system's configuration utility to resolve conflicts. Press any key to continue.	The card(s) mentioned are not fully configured due to resource conflicts.	If you have documentation that lists the allowable resource values for your Plug and Play or PCI expansion card, you can use the following procedure to locate and resolve the resource conflict. NOTE: If you do not have documentation listing the allowable resource values, see the corrective action for these messages. Start the ICU. Any Plug and Play or PCI expansion cards that could not be configured should be marked config err on the list of cards in the ICU window. Select the System Resources option from the View menu. The System Resource Usage dialog box displays all resources currently used by the system. Select one of the resources used by your Plug and Play or PCI expansion card, and click Used By Card. The Card Resources Usage dialog box identifies which device is using the resource. Repeat step 3 until you have identified all conflicting resources and the cards that use them. Modify the cards, as needed, to free the resources required by the unconfigured Plug and Play or PCI expansion card. See "Modifying a Card" for instructions.
WARNING: Could not configure Plug and Play Card Name. WARNING: Could not configure PCI device, ID=DeviceID. Failed to configure Number of Total Count Plug and Play ISA devices. Use your system's configuration utility to resolve conflicts. Press any key to continue.	The card(s) mentioned are not fully configured due to resource conflicts.	If you do not know the allowable resource values for your Plug and Play or PCI expansion card, use the following procedure to locate and resolve the resource conflict: Remove all card configurations from the ICU. See "Removing a Card" for instructions. Reboot your system. The ICU should automatically configure your Plug and Play or PCI expansion card. Add the ISA expansion cards back into the ICU, resolving any resource conflicts as they arise. See "Adding a Listed Card" for instructions. If your Plug and Play or PCI expansion card is not automatically configured when you reboot the system with all other cards removed, you should contact the manufacturer of the card or see "Getting Help" in your Diagnostics and Troubleshooting Guide.
WARNING: Boot Device conflict detected! CSN=Card Select Number Error=Error.	One of the devices is attempting to use one or more resources assigned to the system's boot device.	Perform the following procedure: Start the ICU. Identify the card marked config err. This card is attempting to use one or more resources required by the system's boot device. Follow the procedure for the preceding error message in this table.
*NOTE:For the full name of an abbreviation or acronym used in this table, see the Glossary in the online* System User's Guide.

Back to Contents Page