Dell OptiPlex GX1p Dell OptiPlex GX1 and GX1p Midsize Managed PC Systems Refe - Page 145

icu0200.cfg

Page 145 highlights

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. You can get a copy of the configuration file from the original ISA Configuration Utility Diskette that you used to create the backup ICU diskette. Use the following procedure: This message appears when you modify a card and its configuration file does not exist or has been deleted. For example, type cd a:\db. 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. 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. ISA Configuration Utility Messages B-5

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174

ISA Configuration Utility Messages
B-5
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 config-
uration 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.
You can get a copy of the configuration file from
the original
ISA Configuration Utility Diskette
that
you used to create the backup ICU diskette. Use
the following procedure:
º·
,QVHUW²WKH²RULJLQDO²
,6$±&RQILJXUDWLRQ±
8WLOLW\±’LVNHWWH
²LQWR²GULYH²$·
»·
&KDQJH²WR²WKH²
GE
²VXEGLUHFWRU\²RQ²WKH²GLVµ
NHWWH²GULYH·
For example, type
cd a:\db
.
¹·
8VH²D²WH[W²HGLWRU²WR²VHDUFK²WKH²
LFX´QG[
²ILOH²
IRU²WKH²FDUG²,’²RI²WKH²FDUG²\RX²ZDQW²WR²DGG²
RU²PRGLI\·
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
.
¾·
&RS\²WKH²FRQILJXUDWLRQ²ILOH²IURP²WKH²
RULJLQDO²,&8²GLVNHWWH²WR²WKH²EDFNXS²
GLVNHWWH·²
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 fac-
tory 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 dif-
ferent 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.
7DEOH±%¶´µ±±&RQILJXUDWLRQ±8WLOLW\±0HVVDJHV
±ºFRQWLQXHG»
0HVVDJH
3UREDEOH²&DXVH
&RUUHFWLYH²$FWLRQ
NOTE: For the full name of an abbreviation or acronym used in this table, see the Glossary in the online
System User’s Guide
.