Toshiba Satellite L25-S1192 Satellite L20-L25 User's Guide (PDF) - Page 164

A plan of action, Resolving hardware conflicts on your own

Page 164 highlights

164 If Something Goes Wrong Resolving a hardware conflict A plan of action The smooth operation of the system depends on the interaction of all devices, programs, and features. If the system or one of its attached devices is not working, resolving the problem can be time-consuming and frustrating. The recommended procedure for getting multiple devices to work together is to add and set up one device at a time. After you add each device, test it to make sure it and all previously connected devices work. The device most recently connected to the system is the one most likely to be causing a hardware conflict. Resolving hardware conflicts on your own Computer components need resources to accomplish a task. A device, such as a disk drive or a modem, needs a channel to the computer's Central Processing Unit (CPU). It also needs a direct channel to the computer's memory to store information as it works. These channels of communication are commonly referred to as system resources. Interrupt Request Channel The channel to the CPU is called an Interrupt Request (IRQ) because it interrupts what the processor is doing and requests some of the processor's time. If two or more devices use the same IRQ, the processor does not know which device is asking for attention. This causes a hardware conflict. Direct Memory Access Similarly, the data required by the device is stored in a specific place or address in memory called the Direct Memory Access (DMA). The DMA provides a dedicated channel for adapter cards to bypass the microprocessor and access memory directly. If two or more devices use the same DMA, the data required by one device overwrites the data required by the other, causing a hardware conflict.

  • 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
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256

164
If Something Goes Wrong
Resolving a hardware conflict
A plan of action
The smooth operation of the system depends on the
interaction of all devices, programs, and features. If the
system or one of its attached devices is not working,
resolving the problem can be time-consuming and frustrating.
The recommended procedure for getting multiple devices to
work together is to add and set up one device at a time. After
you add each device, test it to make sure it and all previously
connected devices work.
The device most recently connected to the system is the one
most likely to be causing a hardware conflict.
Resolving hardware conflicts on your own
Computer components need resources to accomplish a task.
A device, such as a disk drive or a modem, needs a channel to
the computer’s Central Processing Unit (CPU). It also needs a
direct channel to the computer’s memory to store information
as it works. These channels of communication are commonly
referred to as system resources.
Interrupt Request Channel
The channel to the CPU is called an Interrupt Request (IRQ)
because it interrupts what the processor is doing and requests
some of the processor’s time. If two or more devices use the
same IRQ, the processor does not know which device is
asking for attention. This causes a hardware conflict.
Direct Memory Access
Similarly, the data required by the device is stored in a
specific place or address in memory called the Direct
Memory Access (DMA). The DMA provides a dedicated
channel for adapter cards to bypass the microprocessor and
access memory directly. If two or more devices use the same
DMA, the data required by one device overwrites the data
required by the other, causing a hardware conflict.