Device-installation logging level
|
Types of messages recorded
|
Time stamps recorded?
|
0x00001000
|
Context and error
|
No
|
0x00002000
|
Context, error, and warning
|
No
|
0x00003000
|
Context, error, warning, and information
|
No
|
0x00004000
|
Context, error, warning, information, and verbose
|
No
|
0x00005000
|
Context, error, warning, information, verbose, and timing
|
Only in timing messages
|
0x00006000
|
Context, error, warning, information, and verbose
|
Yes
|
0x00007000
|
Context, error, warning, information, verbose, and timing
|
Yes
|
Note that you can use the 0x08000000 special flag to add time stamps to all messages.
9Appendix C: Section Markers
In an English-language log file, the section marker for the Windows installation header section looks like this:
[SetupAPI Log]
The format of the section marker for a device-setup class installation section, for some driver-installation sections, and for some device-removal sections looks like this:
[date time process-id.instance]
Here is an alternative format for the section marker of a driver-installation or device-removal section:
[date time process-id.instance suffix]
The following table defines the section-marker fields.
Field
|
Definition
|
Date
|
The date, formatted as yyyy/mm/dd, where yyyy is the 4-digit year, mm is the 2-digit month, and dd is the 2-digit day.
|
Time
|
The local time, based on a 24-hour clock and formatted as hh:mm:ss, where hh is the 2-digit hour, mm is the 2-digit minute, and ss is the 2-digit number of seconds.
|
process-id
|
The process identifier (PID) of the service.
|
Instance
|
An integer that uniquely identifies a driver-installation section. For example, two driver-installation sections that are created at the same time by the same process will have different Instance values.
|
Suffix
|
The string “Driver Install”. Note that some section markers include this suffix and some do not. The absence of a suffix is not significant.
|
Share with your friends: |
