ISA Configuration Utility Messages
A-5
No configuration
(.cfg) file exists for
the card being modi-
fied. Do you want to
load one?
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?
This message appears when
you modify a card and its con-
figuration file does not exist or
has been deleted.
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.
You can get a copy of the configuration file
from the ISA Configuration Utility Diskette. Use
the following procedure:
1.
Insert the ISA Configuration Utility Dis-
kette into drive A.
2.
Change to the db subdirectory on the dis-
kette drive.
For example, type
cd a:\db
.
3.
Use a text editor to search the icu.ndx file
for the card ID of the card you want to add
or modify.
The name of the configuration file is part
of this card ID. For example, if the card ID
is
ICU0200
, the configuration file is
!icu0200.cfg.
4.
Copy the configuration file from the dis-
kette into the directory containing the
ICU on your hard-disk drive.
This is an EISA sys-
tem. 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 differ-
ent from factory
default. Reconfigure
the card to the set-
tings 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 dif-
ferent from the card’s
defaults.
Make a note of the new card configuration
shown in the Card Resource Usage dialog box
displayed after this message. Change jumper set-
tings on the ISA expansion card to match the new
card configuration.
Table A-1. Configuration Utility Messages
(Continued)
Message
Probable Cause
Corrective Action
NOTE: For the full name of an abbreviation or acronym used in this table, see the Glossary in your online System User’s Guide.
93816BK0.BK : 93816aa0.frm Page 5 Monday, September 16, 1996 1:21 PM
