Lenovo ThinkPad 380ED ThinkPad 380 and 380D User's Guide - Page 213

Avoiding PC Card Resource Conflicts, OS/2 Warp, or refer to the READ.ME file of PC Card Director.

Get Lenovo ThinkPad 380ED PDF manuals and user guides View all Lenovo ThinkPad 380ED manuals
Add to My Manuals
Save this manual to your list of manuals

Page 213 highlights

Avoiding PC Card Resource Conflicts PC Card Director checks the resources for most devices used by the system to avoid resource conflicts, but it does not recognize all option devices used. Especially when you are using the expansion unit, there is a possibility that the I/O port address or IRQ level may conflict with the PC Card. Check the status of the PC Card by using PC Card Director. When the PC Card is set to "Ready," the resources used for that PC Card are displayed. Refer to the manuals supplied with the system or option adapters to check that the resources for the devices in the system or for the option adapters are not conflicting with the resources for the IRQ level, I/O port address, or memory window of the PC Card. If you are using OS/2 Warp Version 3 or later, you can check the assigned system resources using RMVIEW.EXE. If there is a conflict: If you are using OS/2 Warp Version 3 or later, use RESERVE.SYS to register those resources in OS/2. To set RESERVE.SYS, refer to the manuals or online help for OS/2 Warp, or refer to the READ.ME file of PC Card Director. If you are using Auto Configurator, change the enabling order or resource information using the Auto Configurator Utility. See "Starting the Auto Configurator Utility" on page 181. Change the parameter for the PC Card enabler. Refer to the manuals supplied with the PC Card. If you are using network cards, change the resource information for the PC Card stated in the PROTOCOL.INI or NET.CFG file. To change the configuration file for the network cards, refer to the manuals or READ.ME files of the PC Cards or network drivers. Appendix B. Advanced Information for PC Cards for OS/2 Warp 193

  • 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
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
Avoiding PC Card Resource Conflicts
PC Card Director checks the resources for most devices used by the
system to avoid resource conflicts, but it does not recognize all
option devices used.
Especially when you are using the expansion
unit, there is a possibility that the I/O port address or IRQ level may
conflict with the PC Card.
Check the status of the PC Card by using PC Card Director.
When
the PC Card is set to “Ready,” the resources used for that PC Card
are displayed.
Refer to the manuals supplied with the system or
option adapters to check that the resources for the devices in the
system or for the option adapters are not conflicting with the
resources for the IRQ level, I/O port address, or memory window of
the PC Card.
If you are using OS/2 Warp Version 3 or later, you can
check the assigned system resources using RMVIEW.EXE.
If there is a conflict:
If you are using OS/2 Warp Version 3 or later, use
RESERVE.SYS to register those resources in OS/2.
To set RESERVE.SYS, refer to the manuals or online help for
OS/2 Warp, or refer to the READ.ME file of PC Card Director.
If you are using Auto Configurator, change the enabling order or
resource information using the Auto Configurator Utility.
See “Starting the Auto Configurator Utility” on page
181.
Change the parameter for the PC Card enabler.
Refer to the
manuals supplied with the PC Card.
If you are using network cards, change the resource information
for the PC Card stated in the PROTOCOL.INI or NET.CFG file.
To change the configuration file for the network cards, refer to
the manuals or READ.ME files of the PC Cards or network
drivers.
Appendix B.
Advanced Information for PC Cards for OS/2 Warp
193