mirror of
https://github.com/reactos/reactos.git
synced 2024-06-24 23:11:47 +00:00
[IOLOGMSG]
Add iologmsg.dll. It will be used to log IO events. svn path=/trunk/; revision=51681
This commit is contained in:
Eric Kohl
parent
6dd99f1f9b
commit
5c840249e9
|
|
@ -75,6 +75,7 @@
|
|||
<property name="BASEADDRESS_ITSS" value="0x66370000" />
|
||||
<property name="BASEADDRESS_ITIRCL" value="0x663a0000" />
|
||||
<property name="BASEADDRESS_INETMIB1" value="0x666f0000" />
|
||||
<property name="BASEADDRESS_IOLOGMSG" value="0x669a0000" />
|
||||
<property name="BASEADDRESS_INITPKI" value="0x66b00000" />
|
||||
<property name="BASEADDRESS_WSHTCPIP" value="0x677b0000" />
|
||||
<property name="BASEADDRESS_CRYPT32" value="0x67ab0000" />
|
||||
|
|
|
|||
6
reactos/dll/win32/iologmsg/iologmsg.rbuild
Normal file
6
reactos/dll/win32/iologmsg/iologmsg.rbuild
Normal file
|
|
@ -0,0 +1,6 @@
|
|||
<module name="iologmsg" type="win32dll" baseaddress="${BASEADDRESS_IOLOGMSG}" installbase="system32" installname="iologmsg.dll" entrypoint="0" unicode="true">
|
||||
<include base="iologmsg">.</include>
|
||||
<include base="ntiologc" root="intermediate">.</include>
|
||||
<dependency>ntiologc</dependency>
|
||||
<file>iologmsg.rc</file>
|
||||
</module>
|
||||
9
reactos/dll/win32/iologmsg/iologmsg.rc
Normal file
9
reactos/dll/win32/iologmsg/iologmsg.rc
Normal file
|
|
@ -0,0 +1,9 @@
|
|||
#include <windows.h>
|
||||
|
||||
#define REACTOS_VERSION_DLL
|
||||
#define REACTOS_STR_FILE_DESCRIPTION "I/O Log Message Dll\0"
|
||||
#define REACTOS_STR_INTERNAL_NAME "iologmsg\0"
|
||||
#define REACTOS_STR_ORIGINAL_FILENAME "iologmsg.dll\0"
|
||||
#include <reactos/version.rc>
|
||||
|
||||
#include "ntiologc.rc"
|
||||
|
|
@ -169,6 +169,9 @@
|
|||
<directory name="inseng">
|
||||
<xi:include href="inseng/inseng.rbuild" />
|
||||
</directory>
|
||||
<directory name="iologmsg">
|
||||
<xi:include href="iologmsg/iologmsg.rbuild" />
|
||||
</directory>
|
||||
<directory name="iphlpapi">
|
||||
<xi:include href="iphlpapi/iphlpapi.rbuild" />
|
||||
</directory>
|
||||
|
|
|
|||
|
|
@ -20,4 +20,8 @@
|
|||
<module name="neteventmsg" type="messageheader">
|
||||
<file>netevent.mc</file>
|
||||
</module>
|
||||
|
||||
<module name="ntiologc" type="messageheader">
|
||||
<file>ntiologc.mc</file>
|
||||
</module>
|
||||
</group>
|
||||
365
reactos/include/reactos/mc/ntiologc.mc
Normal file
365
reactos/include/reactos/mc/ntiologc.mc
Normal file
|
|
@ -0,0 +1,365 @@
|
|||
;
|
||||
; iologmsg.mc MESSAGE resources for iologmsg.dll
|
||||
;
|
||||
|
||||
MessageIdTypedef=NTSTATUS
|
||||
|
||||
SeverityNames=(Success=0x0:STATUS_SEVERITY_SUCCESS
|
||||
Informational=0x1:STATUS_SEVERITY_INFORMATIONAL
|
||||
Warning=0x2:STATUS_SEVERITY_WARNING
|
||||
Error=0x3:STATUS_SEVERITY_ERROR
|
||||
)
|
||||
|
||||
FacilityNames=(RpcRuntime=0x2:FACILITY_RPC_RUNTIME
|
||||
RpcStubs=0x3:FACILITY_RPC_STUBS
|
||||
IO=0x4:FACILITY_IO_ERROR_CODE
|
||||
MCA=0x5:FACILITY_MCA_ERROR_CODE
|
||||
)
|
||||
|
||||
LanguageNames=(English=0x409:MSG00409)
|
||||
|
||||
|
||||
;
|
||||
; message definitions
|
||||
;
|
||||
|
||||
; Facility=IO
|
||||
|
||||
; IO Error messages
|
||||
|
||||
MessageId=1
|
||||
Severity=Success
|
||||
Facility=IO
|
||||
SymbolicName=IO_ERR_RETRY_SUCCEEDED
|
||||
Language=English
|
||||
A retry succeeded.
|
||||
.
|
||||
|
||||
MessageId=2
|
||||
Severity=Error
|
||||
Facility=IO
|
||||
SymbolicName=IO_ERR_INSUFFICIENT_RESOURCES
|
||||
Language=English
|
||||
Insufficient resources.
|
||||
.
|
||||
|
||||
MessageId=3
|
||||
Severity=Error
|
||||
Facility=IO
|
||||
SymbolicName=IO_ERR_CONFIGURATION_ERROR
|
||||
Language=English
|
||||
Driver or device is incorrectly configured for %1.
|
||||
.
|
||||
|
||||
MessageId=4
|
||||
Severity=Error
|
||||
Facility=IO
|
||||
SymbolicName=IO_ERR_DRIVER_ERROR
|
||||
Language=English
|
||||
Driver detected an internal error in its data structures for %1.
|
||||
.
|
||||
|
||||
MessageId=5
|
||||
Severity=Error
|
||||
Facility=IO
|
||||
SymbolicName=IO_ERR_PARITY
|
||||
Language=English
|
||||
A parity error was detected on %1.
|
||||
.
|
||||
|
||||
MessageId=6
|
||||
Severity=Error
|
||||
Facility=IO
|
||||
SymbolicName=IO_ERR_SEEK_ERROR
|
||||
Language=English
|
||||
The device, %1, had a seek error.
|
||||
.
|
||||
|
||||
MessageId=7
|
||||
Severity=Error
|
||||
Facility=IO
|
||||
SymbolicName=IO_ERR_BAD_BLOCK
|
||||
Language=English
|
||||
The device, %1, has a bad block.
|
||||
.
|
||||
|
||||
MessageId=8
|
||||
Severity=Error
|
||||
Facility=IO
|
||||
SymbolicName=IO_ERR_OVERRUN_ERROR
|
||||
Language=English
|
||||
An overrun occurred on %1.
|
||||
.
|
||||
|
||||
MessageId=9
|
||||
Severity=Error
|
||||
Facility=IO
|
||||
SymbolicName=IO_ERR_TIMEOUT
|
||||
Language=English
|
||||
The device, %1, did not respond within the timeout period.
|
||||
.
|
||||
|
||||
MessageId=10
|
||||
Severity=Error
|
||||
Facility=IO
|
||||
SymbolicName=IO_ERR_SEQUENCE
|
||||
Language=English
|
||||
The driver detected an unexpected sequence by the device, %1.
|
||||
.
|
||||
|
||||
MessageId=11
|
||||
Severity=Error
|
||||
Facility=IO
|
||||
SymbolicName=IO_ERR_CONTROLLER_ERROR
|
||||
Language=English
|
||||
The driver detected a controller error on %1.
|
||||
.
|
||||
|
||||
MessageId=12
|
||||
Severity=Error
|
||||
Facility=IO
|
||||
SymbolicName=IO_ERR_INTERNAL_ERROR
|
||||
Language=English
|
||||
The driver detected an internal driver error on %1.
|
||||
.
|
||||
|
||||
MessageId=13
|
||||
Severity=Error
|
||||
Facility=IO
|
||||
SymbolicName=IO_ERR_INCORRECT_IRQL
|
||||
Language=English
|
||||
The driver was configured with an incorrect interrupt for %1.
|
||||
.
|
||||
|
||||
MessageId=14
|
||||
Severity=Error
|
||||
Facility=IO
|
||||
SymbolicName=IO_ERR_INVALID_IOBASE
|
||||
Language=English
|
||||
The driver was configured with an invalid I/O base address for %1.
|
||||
.
|
||||
|
||||
MessageId=15
|
||||
Severity=Error
|
||||
Facility=IO
|
||||
SymbolicName=IO_ERR_NOT_READY
|
||||
Language=English
|
||||
Insufficient resources.
|
||||
.
|
||||
|
||||
MessageId=16
|
||||
Severity=Error
|
||||
Facility=IO
|
||||
SymbolicName=IO_ERR_INVALID_REQUEST
|
||||
Language=English
|
||||
The request is incorrectly formatted for %1.
|
||||
.
|
||||
|
||||
MessageId=17
|
||||
Severity=Error
|
||||
Facility=IO
|
||||
SymbolicName=IO_ERR_VERSION
|
||||
Language=English
|
||||
The wrong version of the driver has been loaded.
|
||||
.
|
||||
|
||||
MessageId=18
|
||||
Severity=Error
|
||||
Facility=IO
|
||||
SymbolicName=IO_ERR_LAYERED_FAILURE
|
||||
Language=English
|
||||
The driver beneath this one has failed in some way for %1.
|
||||
.
|
||||
|
||||
MessageId=19
|
||||
Severity=Error
|
||||
Facility=IO
|
||||
SymbolicName=IO_ERR_RESET
|
||||
Language=English
|
||||
The device, %1, has been reset.
|
||||
.
|
||||
|
||||
MessageId=20
|
||||
Severity=Error
|
||||
Facility=IO
|
||||
SymbolicName=IO_ERR_PROTOCOL
|
||||
Language=English
|
||||
A transport driver received a frame which violated the protocol.
|
||||
.
|
||||
|
||||
MessageId=21
|
||||
Severity=Error
|
||||
Facility=IO
|
||||
SymbolicName=IO_ERR_MEMORY_CONFLICT_DETECTED
|
||||
Language=English
|
||||
A conflict has been detected between two drivers which claimed two overlapping
|
||||
memory regions.
|
||||
Driver %2, with device <%3>, claimed a memory range with starting address
|
||||
in data address 0x28 and 0x2c, and length in data address 0x30.
|
||||
.
|
||||
|
||||
MessageId=22
|
||||
Severity=Error
|
||||
Facility=IO
|
||||
SymbolicName=IO_ERR_PORT_CONFLICT_DETECTED
|
||||
Language=English
|
||||
A conflict has been detected between two drivers which claimed two overlapping
|
||||
Io port regions.
|
||||
Driver %2, with device <%3>, claimed an IO port range with starting address
|
||||
in data address 0x28 and 0x2c, and length in data address 0x30.
|
||||
.
|
||||
|
||||
MessageId=23
|
||||
Severity=Error
|
||||
Facility=IO
|
||||
SymbolicName=IO_ERR_DMA_CONFLICT_DETECTED
|
||||
Language=English
|
||||
A conflict has been detected between two drivers which claimed equivalent DMA
|
||||
channels.
|
||||
Driver %2, with device <%3>, claimed the DMA Channel in data address 0x28, with
|
||||
optinal port in data address 0x2c.
|
||||
.
|
||||
|
||||
MessageId=24
|
||||
Severity=Error
|
||||
Facility=IO
|
||||
SymbolicName=IO_ERR_IRQ_CONFLICT_DETECTED
|
||||
Language=English
|
||||
A conflict has been detected between two drivers which claimed equivalent IRQs.
|
||||
Driver %2, with device <%3>, claimed an interrupt with Level in data address
|
||||
0x28, vector in data address 0x2c and Affinity in data address 0x30.
|
||||
.
|
||||
|
||||
MessageId=25
|
||||
Severity=Error
|
||||
Facility=IO
|
||||
SymbolicName=IO_ERR_BAD_FIRMWARE
|
||||
Language=English
|
||||
Insufficient resources.
|
||||
The driver has detected a device with old or out-of-date firmware. The
|
||||
device will not be used.
|
||||
.
|
||||
|
||||
MessageId=26
|
||||
Severity=Warning
|
||||
Facility=IO
|
||||
SymbolicName=IO_WRN_BAD_FIRMWARE
|
||||
Language=English
|
||||
The driver has detected that device %1 has old or out-of-date firmware.
|
||||
Reduced performance may result.
|
||||
.
|
||||
|
||||
MessageId=27
|
||||
Severity=Error
|
||||
Facility=IO
|
||||
SymbolicName=IO_ERR_DMA_RESOURCE_CONFLICT
|
||||
Language=English
|
||||
The device could not allocate one or more required resources due to conflicts
|
||||
with other devices. The device DMA setting of '%2' could not be
|
||||
satisified due to a conflict with Driver '%3'.
|
||||
.
|
||||
|
||||
MessageId=28
|
||||
Severity=Error
|
||||
Facility=IO
|
||||
SymbolicName=IO_ERR_INTERRUPT_RESOURCE_CONFLICT
|
||||
Language=English
|
||||
The device could not allocate one or more required resources due to conflicts
|
||||
with other devices. The device interrupt setting of '%2' could not be
|
||||
satisified due to a conflict with Driver '%3'.
|
||||
.
|
||||
|
||||
MessageId=29
|
||||
Severity=Error
|
||||
Facility=IO
|
||||
SymbolicName=IO_ERR_MEMORY_RESOURCE_CONFLICT
|
||||
Language=English
|
||||
The device could not allocate one or more required resources due to conflicts
|
||||
with other devices. The device memory setting of '%2' could not be
|
||||
satisified due to a conflict with Driver '%3'.
|
||||
.
|
||||
|
||||
MessageId=30
|
||||
Severity=Error
|
||||
Facility=IO
|
||||
SymbolicName=IO_ERR_PORT_RESOURCE_CONFLICT
|
||||
Language=English
|
||||
The device could not allocate one or more required resources due to conflicts
|
||||
with other devices. The device port setting of '%2' could not be
|
||||
satisified due to a conflict with Driver '%3'.
|
||||
.
|
||||
|
||||
MessageId=31
|
||||
Severity=Error
|
||||
Facility=IO
|
||||
SymbolicName=IO_BAD_BLOCK_WITH_NAME
|
||||
Language=English
|
||||
The file %2 on device %1 contains a bad disk block.
|
||||
.
|
||||
|
||||
MessageId=32
|
||||
Severity=Warning
|
||||
Facility=IO
|
||||
SymbolicName=IO_WRITE_CACHE_ENABLED
|
||||
Language=English
|
||||
The driver detected that the device %1 has its write cache enabled. Data corruption may occur.
|
||||
.
|
||||
|
||||
MessageId=33
|
||||
Severity=Warning
|
||||
Facility=IO
|
||||
SymbolicName=IO_RECOVERED_VIA_ECC
|
||||
Language=English
|
||||
Data was recovered using error correction code on device %1.
|
||||
.
|
||||
|
||||
MessageId=34
|
||||
Severity=Warning
|
||||
Facility=IO
|
||||
SymbolicName=IO_WRITE_CACHE_DISABLED
|
||||
Language=English
|
||||
The driver disabled the write cache on device %1.
|
||||
.
|
||||
|
||||
MessageId=36
|
||||
Severity=Informational
|
||||
Facility=IO
|
||||
SymbolicName=IO_FILE_QUOTA_THRESHOLD
|
||||
Language=English
|
||||
A user hit their quota threshold on volume %2.
|
||||
.
|
||||
|
||||
MessageId=37
|
||||
Severity=Informational
|
||||
Facility=IO
|
||||
SymbolicName=IO_FILE_QUOTA_LIMIT
|
||||
Language=English
|
||||
A user hit their quota limit on volume %2.
|
||||
.
|
||||
|
||||
MessageId=38
|
||||
Severity=Informational
|
||||
Facility=IO
|
||||
SymbolicName=IO_FILE_QUOTA_STARTED
|
||||
Language=English
|
||||
The system has started rebuilding the user disk quota information on
|
||||
device %1 with label "%2".
|
||||
.
|
||||
|
||||
MessageId=39
|
||||
Severity=Informational
|
||||
Facility=IO
|
||||
SymbolicName=IO_FILE_QUOTA_SUCCEEDED
|
||||
Language=English
|
||||
The system has successfully rebuilt the user disk quota information on
|
||||
device %1 with label "%2".
|
||||
.
|
||||
|
||||
MessageId=40
|
||||
Severity=Warning
|
||||
Facility=IO
|
||||
SymbolicName=IO_FILE_QUOTA_FAILED
|
||||
Language=English
|
||||
The system has encounted an error rebuilding the user disk quota
|
||||
information on device %1 with label "%2".
|
||||
.
|
||||
Loading…
Reference in a new issue