Table 7, Registry values for trace outputs, Multiplexer driver developer’s guide – Siemens 7 User Manual
Page 24
Multiplexer Driver Developer’s Guide
4.2 Settings Stored in the Windows Registry
s
Mux_Drv_DevGuide_v07
Page 24 of 36
2006-9-27
Confidential / Released
The following Registry values in the path
HKLM \System\CurrentControlSet\Services\winmux2k\Parameters are used to configure the TRACE out-
puts. These values are only valid for the debug version of the device driver.
Table 7: Registry values for trace outputs
Values
Data (Example)
Properties
DebugBaud
57600
Baud rate: used if DebugPort is different from 0.
DebugMask
0x0000003
DebugMask determine, which reports from the device driver
are printed to the DebugPort.
Masks:
0x0000001 Errors
0x0000002 Warnings
0x0000004 Information’s
0x0000008 PnP
0x0000010 Power management
0x0000020 Data control commands
0x0000040 Open/Close/Cleanup
0x0000080 Dispatch Device Control
0x0000100 Dispatch Read/Write
0x0000200 Submit control requests
0x0004000 framed data read/write
0x0008000 frequently traces submit/wrsupport
The mask 0x7 means, that all three traces are on.
The next masks are only for driver checks and represent
internal variables and states of the serial Multiplexer Device
driver.
0x0001 0000 Frame information, send and receive
0x0002 0000 Frame information, HDLC
0x0004 0000 Status information from virtual channels
0x0008 0000 Status information from Multiplexer control
channel
0x0010 0000 Output Names from WinMux2k functions
0x1000 0000 traces how and because a Request completed
0x2000 0000 traces V.24 signals and change of these sig-
nals
0x4000 0000 traces, in which state is the parser for scanning
the +++ sequence
0x8000 0000 traces states for scanning a Frame
DebugPort
0x0
0 Output from the driver is redirected to the kernel debugger.
(default value)
1...4: Output is redirected to a COM port