2 ; iologmsg.mc MESSAGE resources for iologmsg.dll
5 MessageIdTypedef=NTSTATUS
7 SeverityNames=(Success=0x0:STATUS_SEVERITY_SUCCESS
8 Informational=0x1:STATUS_SEVERITY_INFORMATIONAL
9 Warning=0x2:STATUS_SEVERITY_WARNING
10 Error=0x3:STATUS_SEVERITY_ERROR
13 FacilityNames=(RpcRuntime=0x2:FACILITY_RPC_RUNTIME
14 RpcStubs=0x3:FACILITY_RPC_STUBS
15 IO=0x4:FACILITY_IO_ERROR_CODE
16 MCA=0x5:FACILITY_MCA_ERROR_CODE
19 LanguageNames=(English=0x409:MSG00409)
33 SymbolicName=IO_ERR_RETRY_SUCCEEDED
41 SymbolicName=IO_ERR_INSUFFICIENT_RESOURCES
43 Insufficient resources.
49 SymbolicName=IO_ERR_CONFIGURATION_ERROR
51 Driver or device is incorrectly configured for %1.
57 SymbolicName=IO_ERR_DRIVER_ERROR
59 Driver detected an internal error in its data structures for %1.
65 SymbolicName=IO_ERR_PARITY
67 A parity error was detected on %1.
73 SymbolicName=IO_ERR_SEEK_ERROR
75 The device, %1, had a seek error.
81 SymbolicName=IO_ERR_BAD_BLOCK
83 The device, %1, has a bad block.
89 SymbolicName=IO_ERR_OVERRUN_ERROR
91 An overrun occurred on %1.
97 SymbolicName=IO_ERR_TIMEOUT
99 The device, %1, did not respond within the timeout period.
105 SymbolicName=IO_ERR_SEQUENCE
107 The driver detected an unexpected sequence by the device, %1.
113 SymbolicName=IO_ERR_CONTROLLER_ERROR
115 The driver detected a controller error on %1.
121 SymbolicName=IO_ERR_INTERNAL_ERROR
123 The driver detected an internal driver error on %1.
129 SymbolicName=IO_ERR_INCORRECT_IRQL
131 The driver was configured with an incorrect interrupt for %1.
137 SymbolicName=IO_ERR_INVALID_IOBASE
139 The driver was configured with an invalid I/O base address for %1.
145 SymbolicName=IO_ERR_NOT_READY
147 Insufficient resources.
153 SymbolicName=IO_ERR_INVALID_REQUEST
155 The request is incorrectly formatted for %1.
161 SymbolicName=IO_ERR_VERSION
163 The wrong version of the driver has been loaded.
169 SymbolicName=IO_ERR_LAYERED_FAILURE
171 The driver beneath this one has failed in some way for %1.
177 SymbolicName=IO_ERR_RESET
179 The device, %1, has been reset.
185 SymbolicName=IO_ERR_PROTOCOL
187 A transport driver received a frame which violated the protocol.
193 SymbolicName=IO_ERR_MEMORY_CONFLICT_DETECTED
195 A conflict has been detected between two drivers which claimed two overlapping
197 Driver %2, with device <%3>, claimed a memory range with starting address
198 in data address 0x28 and 0x2c, and length in data address 0x30.
204 SymbolicName=IO_ERR_PORT_CONFLICT_DETECTED
206 A conflict has been detected between two drivers which claimed two overlapping
208 Driver %2, with device <%3>, claimed an IO port range with starting address
209 in data address 0x28 and 0x2c, and length in data address 0x30.
215 SymbolicName=IO_ERR_DMA_CONFLICT_DETECTED
217 A conflict has been detected between two drivers which claimed equivalent DMA
219 Driver %2, with device <%3>, claimed the DMA Channel in data address 0x28, with
220 optinal port in data address 0x2c.
226 SymbolicName=IO_ERR_IRQ_CONFLICT_DETECTED
228 A conflict has been detected between two drivers which claimed equivalent IRQs.
229 Driver %2, with device <%3>, claimed an interrupt with Level in data address
230 0x28, vector in data address 0x2c and Affinity in data address 0x30.
236 SymbolicName=IO_ERR_BAD_FIRMWARE
238 Insufficient resources.
239 The driver has detected a device with old or out-of-date firmware. The
240 device will not be used.
246 SymbolicName=IO_WRN_BAD_FIRMWARE
248 The driver has detected that device %1 has old or out-of-date firmware.
249 Reduced performance may result.
255 SymbolicName=IO_ERR_DMA_RESOURCE_CONFLICT
257 The device could not allocate one or more required resources due to conflicts
258 with other devices. The device DMA setting of '%2' could not be
259 satisified due to a conflict with Driver '%3'.
265 SymbolicName=IO_ERR_INTERRUPT_RESOURCE_CONFLICT
267 The device could not allocate one or more required resources due to conflicts
268 with other devices. The device interrupt setting of '%2' could not be
269 satisified due to a conflict with Driver '%3'.
275 SymbolicName=IO_ERR_MEMORY_RESOURCE_CONFLICT
277 The device could not allocate one or more required resources due to conflicts
278 with other devices. The device memory setting of '%2' could not be
279 satisified due to a conflict with Driver '%3'.
285 SymbolicName=IO_ERR_PORT_RESOURCE_CONFLICT
287 The device could not allocate one or more required resources due to conflicts
288 with other devices. The device port setting of '%2' could not be
289 satisified due to a conflict with Driver '%3'.
295 SymbolicName=IO_BAD_BLOCK_WITH_NAME
297 The file %2 on device %1 contains a bad disk block.
303 SymbolicName=IO_WRITE_CACHE_ENABLED
305 The driver detected that the device %1 has its write cache enabled. Data corruption may occur.
311 SymbolicName=IO_RECOVERED_VIA_ECC
313 Data was recovered using error correction code on device %1.
319 SymbolicName=IO_WRITE_CACHE_DISABLED
321 The driver disabled the write cache on device %1.
325 Severity=Informational
327 SymbolicName=IO_FILE_QUOTA_THRESHOLD
329 A user hit their quota threshold on volume %2.
333 Severity=Informational
335 SymbolicName=IO_FILE_QUOTA_LIMIT
337 A user hit their quota limit on volume %2.
341 Severity=Informational
343 SymbolicName=IO_FILE_QUOTA_STARTED
345 The system has started rebuilding the user disk quota information on
346 device %1 with label "%2".
350 Severity=Informational
352 SymbolicName=IO_FILE_QUOTA_SUCCEEDED
354 The system has successfully rebuilt the user disk quota information on
355 device %1 with label "%2".
361 SymbolicName=IO_FILE_QUOTA_FAILED
363 The system has encounted an error rebuilding the user disk quota
364 information on device %1 with label "%2".