MZ@ !L!This program cannot be run in DOS mode. $Rؕ3}3}3}H̴3}H̱3}Rich3}PEL!  1@.rsrc@@H8P (x@~Xp0H`xP   ( 8 H X h x           ( 88|-HCNH R`TN ]-,Tl2p($j4 @MUIMINIREPORTTEMPLATE.HTMLT5E#|6& +7d>wL+. MUI en-US.List interfaces, providers and tracing state. Starts tracing. X %1!s! Starts tracing. Usage: trace start [[scenario=]<scenario1,scenario2>] [[globalKeywords=]keywords] [[globalLevel=]level] [[capture=]yes|no] [[capturetype=]physical|vmswitch|both] [[report=]yes|no|disabled] [[persistent=]yes|no] [[traceFile=]path\filename] [[maxSize=]filemaxsize] [[fileMode=]single|circular|append] [[overwrite=]yes|no] [[correlation=]yes|no|disabled] [capturefilters] [[provider=]providerIdOrName] [[keywords=]keywordMaskOrSet] [[level=]level] [[[provider=]provider2IdOrName] [[providerFilter=]yes|no]] [[keywords=]keyword2MaskOrSet] [[perfMerge=]yes|no] [[level=]level2] ... Defaults: capture=no (specifies whether packet capture is enabled in addition to trace events) capturetype=physical (specifies whether packet capture needs to be enabled for physical network adapters only, virtual switch only, or both physical network adapters and virtual switch) report=no (specifies whether a complementing report will be generated along with the trace file) persistent=no (specifies whether the tracing session continues across reboots, and is on until netsh trace stop is issued) maxSize=250 MB (specifies the maximum trace file size, 0=no maximum) fileMode=circular overwrite=yes (specifies whether an existing trace output file will be overwritten) correlation=yes (specifies whether related events will be correlated and grouped together) perfMerge=yes (specifies whether performance metadata is merged into trace) traceFile=%%LOCALAPPDATA%%\Temp\NetTraces\NetTrace.etl (specifies location of the output file) providerFilter=no (specifies whether provider filter is enabled) Provider keywords default to all and level to 255 unless otherwise specified. For example: netsh trace start scenario=InternetClient capture=yes Starts tracing for the InternetClient scenario and dependent providers with packet capture enabled for physical network adapters only. Tracing will stop when the "netsh trace stop" command is issued or when the system reboots. Default location and name will be used for the output file. If an old file exists, it will be overwritten. netsh trace start provider=microsoft-windows-wlan-autoconfig keywords=state,ut:authentication Starts tracing for the microsoft-windows-wlan-autoconfig provider Tracing will stop when the "netsh trace stop" command is issued or when the system reboots. Default location and name will be used for the output file. If an old file exists, it will be overwritten. Only events with keyword 'state' or 'ut:authentication' will be logged. netsh trace show provider command can be used to display supported keywords and levels. Capture Filters: Capture filters are only supported when capture is explicitly enabled with capture=yes. Use 'netsh trace show CaptureFilterHelp' to display a list of supported capture filters and their usage. Provider Filters: Provider filters are supported by multiple providers and are enabled with providerFilter=Yes after every provider. Use 'netsh trace show ProviderFilterHelp' to display a list of supported provider filters for each provider and their usage.Stops tracing. [ %1!s! Stops tracing. Remarks: Stops a network tracing session currently in progress )Converts a trace file to an HTML report.  %1!s! Converts a trace file to an HTML report. Usage: convert [input=]tracefilename.etl [[output=]filename] [[dump=]CSV|XML|EVTX|TXT|No] [[report=]yes|no] [[overwrite=]yes|no] [[tmfpath=]pathname] Parameters: Tag Value input - Input ETL trace file output - Output file name (defaults to input name) dump - Output format (default = TXT) report - Generates an HTML report (default = no) overwrite - Overwrites existing files (default = no) tmfpath - Path to tmf files for decoding WPP traces Remarks: Converts the input ETL file to the specified format. Start a diagnose session. j %1!s! Starts a diagnose session. Usage: diagnose [scenario=]<scenarioname> [[namedAttribute=]<attributeValue>] [[saveSessionTrace=]<yes|no>] [[report=]<yes|no>] [[capture=]<yes|no>] Defaults: saveSessionTrace=no (defaults to 'yes' if report=yes is specified) capture=no report=no Remarks: Starts a diagnose session 9Normalizes or filters a trace file to a new output file.  %1!s! Normalizes or filters a trace file to a new output file. Usage: trace correlate [input=]tracefilename.etl [output=]newtracefilename.etl [[filter=]Activity_ID] [[overwrite=]yes|no] [[retaincorrelationevents=]yes|no] [[retainpii=]yes|no] [[retainglobalevents=]yes|no] Parameters: Tag Value input - Input ETL trace file output - Output file name filter - Output only events related to this Activity GUID overwrite - Overwrites existing files retaincorrelationevents - Retains correlation events retainpii - Retains events containing personally identifiable information retainglobalevents - Retains global events Defaults: filter=none overwrite=no retaincorrevents=no retainpii=yes retainglobalevents=yes Remarks: Filter activity ID is a GUID expressed in the form {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx} Personally identifiable information includes packet capture events .Merges trace files and adds symbols metadata.  %1!s! Merges trace files and adds symbols metadata. Usage: merge input1.etl input2.etl ... output.etl Parameters: A list of ETL files to merge The last file in the list is an output Remarks: Merges the files and injects symbols and PerfTrack metadata. Shows tracing configuration. ' %1!s! Shows tracing configuration. Shows available scenarios. W %1!s! Shows a list of available scenarios that may be used with the start command. Shows scenario information.  %1!s! Shows scenario information. Usage: trace show scenario [name=]<scenarioname> Remarks: This displays additional information about a scenario including any attributes that may be required by the 'diagnose command and the list of providers that would be enabled for the specified scenario, along with the default keywords and levels that would be applied. Shows available providers. PAW %1!s! Shows a list of available providers that may be used with the start command. Shows provider information. G %1!s! Shows provider information that can be used with the start command. Usage: trace show provider [name=]<providerIdOrName> Remarks: This displays the keywords and levels that the specified provider supports. These keywords and levels may be used while starting a tracing session. !List global keywords and levels. %1!s! Shows a list of global keywords and levels that may be used with the start command. Usage: trace show globalKeywordsAndLevels List available interfaces. N %1!s! Shows a list of network interfaces. Usage: trace show interfaces *List supported capture filters and usage. \ %1!s! List supported capture filters and usage. Usage: trace show CaptureFilterHelp Show helper class information. %1!s! Shows helper class name, description and list of dependent helper classes. This also lists possible root causes and repairs that may be returned by the helper class. Usage: trace show helperclass [name=]<helperclassname> +List supported provider filters and usage. ^ %1!s! List supported provider filters and usage. Usage: trace show ProviderFilterHelp Z Trace configuration: ------------------------------------------------------------------- File location = %1!s! b Available scenarios (%1!d!): -------------------------------------------------------------------  Entry Point: %1!ws!  Providers --------- a Available Providers (%1!d!) ------------------------------------------------------------------- + Name: %1!s! Provider Guid: %2!s! g Levels (value) - %1!d! element(s) ------------------------------------------------------------------- h Keywords (mask) - %1!d! element(s) ------------------------------------------------------------------- *Tracing session was successfully stopped. Status: Running Trace File: %1!s! Append: %2!s! Circular: %3!s! Max Size: %4!s! Report: %5!s! s Provider: Name: %1!s! Provider Guid: %2!s! Level: %3!s! Keywords: %4!s! s Provider: Name: %1!s! Provider Guid: %2!s! Default Level: %3!s! Default Keywords: %4!s! Report location = %1!s! Q Input file: %1!s! Dump file: %2!s! Dump format: %3!s! Report file: %4!s! x Description: %1!ws! Interface GUID: %2!S! Interface Index: %3!d! Interface Luid: 0x%4!I64X! Attribute Name Type Required Description -------------- ---- -------- ----------- PA Root causes found: %1!d! - Root cause #%1!d! -------------- %2!ws!  Repairs available: %1!d! 1 Repair #%1!d! ---------- %2!ws!  Diagnosing '%1!ws!' ... done  Description: %1!ws!  NDF Trace File: '%1!ws!' NDF Report File: '%1!ws!' *Generating data collection and report ... Generating dump ... done failed (error=0x%1!X!)  Capture Filters: Capture filters are only supported when capture is explicitly enabled with capture=yes. Supported capture filters are: CaptureInterface=<interface name or GUID> Enables packet capture for the specified interface name or GUID. Use 'netsh trace show interfaces' to list available interfaces. e.g. CaptureInterface={716A7812-4AEE-4545-9D00-C10EFD223551} e.g. CaptureInterface=!{716A7812-4AEE-4545-9D00-C10EFD223551} e.g. CaptureInterface="Local Area Connection" Ethernet.Address=<MAC address> Matches the specified filter against both source and destination MAC addresses. e.g. Ethernet.Address=00-0D-56-1F-73-64 Ethernet.SourceAddress=<MAC address> Matches the specified filter against source MAC addresses. e.g. Ethernet.SourceAddress=00-0D-56-1F-73-64 Ethernet.DestinationAddress=<MAC address> Matches the specified filter against destination MAC addresses. e.g. Ethernet.DestinationAddress=00-0D-56-1F-73-64 Ethernet.Type=<ethertype> Matches the specified filter against the MAC ethertype. e.g. Ethernet.Type=IPv4 e.g. Ethernet.Type=NOT(0x86DD) e.g. Ethernet.Type=(IPv4,IPv6) Wifi.Type=<Management|Data> Matches the specified filter against the Wifi type. Allowed values are 'Management' and 'Data'. If not specified, the Wifi.Type filter is not applied. Note: This capture filter does not support ranges, lists or negation. e.g. Wifi.Type=Management Protocol=<protocol> Matches the specified filter against the IP protocol. e.g. Protocol=6 e.g. Protocol=!(TCP,UDP) e.g. Protocol=(4-10) IPv4.Address=<IPv4 address> Matches the specified filter against both source and destination IPv4 addresses. e.g. IPv4.Address=157.59.136.1 e.g. IPv4.Address=!(157.59.136.1) e.g. IPv4.Address=(157.59.136.1,157.59.136.11) IPv4.SourceAddress=<IPv4 address> Matches the specified filter against source IPv4 addresses. e.g. IPv4.SourceAddress=157.59.136.1 IPv4.DestinationAddress=<IPv4 address> Matches the specified filter against destination IPv4 addresses. e.g. IPv4.DestinationAddress=157.59.136.1 IPv6.Address=<IPv6 address> Matches the specified filter against both source and destination IPv6 addresses. e.g. IPv6.Address=fe80::5038:3c4:35de:f4c3\%%8 e.g. IPv6.Address=!(fe80::5038:3c4:35de:f4c3\%%8) IPv6.SourceAddress=<IPv6 address> Matches the specified filter against source IPv6 addresses. e.g. IPv6.SourceAddress=fe80::5038:3c4:35de:f4c3\%%8 IPv6.DestinationAddress=<IPv6 address> Matches the specified filter against destination IPv6 addresses. e.g. IPv6.DestinationAddress=fe80::5038:3c4:35de:f4c3\%%8 CustomMac=<type(offset,value)> Matches the specified filter against the value at the specified offset starting with the MAC header. Note: This capture filter does not support ranges, lists or negation. e.g. CustomMac=UINT8(0x1,0x23) e.g. CustomMac=ASCIISTRING(3,test) e.g. CustomMac=UNICODESTRING(2,test) CustomIp=<type(offset,value)> Matches the specified filter against the value at the specified offset starting with the IP header. Note: This capture filter does not support ranges, lists or negation. e.g. CustomIp=UINT16(4,0x3201) e.g. CustomIp=UINT32(0x2,18932) CaptureMultiLayer=<yes|no> Enables multi-layer packet capture. Note: This capture filter does not support ranges, lists or negation. PacketTruncateBytes=<value> Captures only the the specified number of bytes of each packet. Note: This capture filter does not support ranges, lists or negation. e.g. PacketTruncateBytes=40  Note: Multiple filters may be used together. However the same filter may not be repeated. e.g. 'netsh trace start capture=yes Ethernet.Type=IPv4 IPv4.Address=157.59.136.1' Filters need to be explicitly stated when required. If a filter is not specified, it is treated as "don't-care". e.g. 'netsh trace start capture=yes IPv4.SourceAddress=157.59.136.1' This will capture IPv4 packets only from 157.59.136.1, and it will also capture packets with non-IPv4 Ethernet Types, since the Ethernet.Type filter is not explicitly specified. e.g. 'netsh trace start capture=yes IPv4.SourceAddress=157.59.136.1 Ethernet.Type=IPv4' This will capture IPv4 packets only from 157.59.136.1. Packets with other Ethernet Types will be discarded since an explicit filter has been specified. Capture filters support ranges, lists and negation (unless stated otherwise). e.g. Range: 'netsh trace start capture=yes Ethernet.Type=IPv4 Protocol=(4-10)' This will capture IPv4 packets with protocols between 4 and 10 inclusive. e.g. List: 'netsh trace start capture=yes Ethernet.Type=(IPv4,IPv6)' This will capture only IPv4 and IPv6 packets. e.g. Negation: 'netsh trace start capture=yes Ethernet.Type=!IPv4' This will capture all non-IPv4 packets. Negation may be combined with lists in some cases. e.g. 'netsh trace start capture=yes Ethernet.Type=!(IPv4,IPv6)' This will capture all non-IPv4 and non-IPv6 packets. 'NOT' can be used instead of '!' to indicate negation. This requires parentheses to be present around the values to be negated. e.g. 'netsh trace start capture=yes Ethernet.Type=NOT(IPv4)' $ Name: %1!ws! Description: %2!ws! PAj Dependent Helper Classes: Helper Class Name Description ----------------- ----------- U Root Cause %1!d!/%2!d! ---------------- Description: %3!ws! ID: %4!ws! ] Repair %1!d!/%2!d! ------------ Description: %3!ws! ID: %4!ws! Input file: %1!s! Output file: %2!s! Filter: %3!s! Overwrite: %4!s! RetainCorrelationEvents: %5!s! RetainPII: %6!s! RetainGlobalEvents: %7!s! Correlating traces ... YThe trace file and additional troubleshooting information have been compiled as "%1!s!". Generating data collection ... Merging traces ...  Provider Filters: Provider filters are supported by multiple providers and are enabled with providerFilter=Yes after every provider. Supported providers are: Provider: Microsoft-Windows-Ras-NdisWanPacketCapture RoutingDomain=<GUID> Enables packet capture for the specified routing domain. Use 'Get-NetCompartment' to list available routing domains. Note: This provider filter supports lists and negations. e.g.netsh trace start provider=Microsoft-Windows-Ras-NdisWanPacketCapture providerFilter=Yes RoutingDomain="{11111111-1111-1111-1111-111111111001}" e.g.netsh trace start provider=Microsoft-Windows-Ras-NdisWanPacketCapture providerFilter=Yes RoutingDomain="(<GUID1>,<GUID2>)" e.g.netsh trace start provider=Microsoft-Windows-Ras-NdisWanPacketCapture providerFilter=Yes RoutingDomain=!"(<GUID1>,<GUID2>)" VPN.UserName=<UserName/InterfaceName> Enables packet capture for specified user or interface name. Note: This provider filter does not support ranges, lists or negation. e.g.netsh trace start provider=Microsoft-Windows-Ras-NdisWanPacketCapture providerFilter=Yes VPN.UserName="UserXXX"  Provider: Microsoft-Windows-TCPIP TCP.AnyPort=<PORT>, TCP.SourcePort=<PORT>, TCP.DestinationPort=<PORT> Allows traces to be collected on ports specified by rules. Any combination of the above filters can be applied. TCP.AnyPort will allow traces to be collected if either the source or destination port match. Note: These provider filters support lists, ranges, and negations. e.g.netsh trace start provider=Microsoft-Windows-TCPIP providerFilter=Yes TCP.SourcePort=80 TCP.DestinationPort=1234 e.g.netsh trace start provider=Microsoft-Windows-TCPIP providerFilter=Yes TCP.AnyPort=(80,443) e.g.netsh trace start provider=Microsoft-Windows-TCPIP providerFilter=Yes TCP.SourcePort=!(900-1000) ProcessId=<Process ID> Enables ETW traces for the described process IDs. Note: This provider filter supports ranges, lists, and negations. e.g.netsh trace start provider=Microsoft-Windows-TCPIP providerFilter=Yes ProcessId=987 e.g.netsh trace start provider=Microsoft-Windows-TCPIP providerFilter=Yes ProcessId=(1,5,8,9) e.g.netsh trace start provider=Microsoft-Windows-TCPIP providerFilter=Yes ProcessId=!(100-200) IPv4.Address=<IPv4 Address> IPv4.SourceAddress=<IPv4 Address> IPv4.DestinationAddress=<IPv4 Address> Enables ETW traces for the described IPv4 address or addresses. IPv4.Address will allow traces if either the source or destination address match the filter. Source and destination filters can be used simultaneously. Note: These provider filters support lists, ranges, and negations. e.g.netsh trace start provider=Microsoft-Windows-TCPIP providerFilter=Yes IPv4.Address=(2.0.0.0-3.0.0.0) e.g.netsh trace start provider=Microsoft-Windows-TCPIP providerFilter=Yes IPv4.SourceAddress=(2.0.0.0,3.0.0.0) e.g.netsh trace start provider=Microsoft-Windows-TCPIP providerFilter=Yes IPv4.DestinationAddress=!(2.0.0.0) IPv6.Address=<IPv6 Address> IPv6.SourceAddress=<IPv6 Address> IPv6.DestinationAddress=<IPv6 Address> Enables ETW traces for the described IPv6 address or addresses. IPv6.Address will allow traces if either the source or destination address match the filter. Source and destination filters can be used simultaneously. Note: These provider filters support lists, ranges, and negations. e.g.netsh trace start provider=Microsoft-Windows-TCPIP providerFilter=Yes IPv6.Address=(2001::1-2001::ffff) e.g.netsh trace start provider=Microsoft-Windows-TCPIP providerFilter=Yes IPv6.SourceAddress=(2001::1-2001::ffff) e.g.netsh trace start provider=Microsoft-Windows-TCPIP providerFilter=Yes IPv6.DestinationAddress=!(2001::ffff) RoutingDomain=<GUID> Enables packet capture for the specified routing domain. Use 'Get-NetCompartment' to list available routing domains. Note: This provider filter supports lists and negations. e.g.netsh trace start provider=Microsoft-Windows-TCPIP providerFilter=Yes RoutingDomain="{B1062982-2B18-4B4F-B3D5-A78DDB9CDD49}" e.g.netsh trace start provider=Microsoft-Windows-TCPIP providerFilter=Yes RoutingDomain="(<GUID1>,<GUID2>)" e.g.netsh trace start provider=Microsoft-Windows-TCPIP providerFilter=Yes RoutingDomain=!"(<GUID1>,<GUID2>)" Note: Provider filters usage is similar to Capture filters unless stated otherwise. Use 'netsh trace show CaptureFilterHelp' to display the capture filters' usage Z The following providers support provider filtering. Provider specific help can be viewed with the following commands: Microsoft-Windows-TCPIP 'netsh trace show providerFilterHelp Microsoft-Windows-TCPIP' Microsoft-Windows-Ras-NdisWanPacketCapture 'netsh trace show providerFilterHelp Microsoft-Windows-Ras-NdisWanPacketCapture' PA Other adapter %1: Ethernet adapter %1: Token Ring adapter %1: FDDI adapter %1: Loopback adapter %1: PPP adapter %1: SLIP adapter %1: Tunnel adapter %1: Wireless LAN adapter %1: Unknown adapter %1:PA1Invalid value "%2!s!" for command option "%1!s!".2Invalid value "%2!s!" for command option "%1!s!". COne or more parameters for the command are not correct or missing. File "%1!s!" already exists. *A tracing session is already in progress. 3Failed to start the tracing session (error=%1!d!). 5Circular mode requires a non-zero MaxSize parameter. 1There is no trace session currently in progress. 4Failed to stop the tracing session (error=0x%1!x!). *'%1!s!' is not a valid or known provider. /Overwrite=yes is not allowed with Append mode. ?The inbox capture driver could not be started (error=0x%1!x!). tThe '%1!s!' application has locked the Network Configuration database. Please close that application and try again. !'%1!s!' is not a valid scenario. PThe scenario '%1!s!' could not be added to the tracing session (error=0x%2!x!). TPacket Capture providers could not be added to the tracing session (error=0x%1!x!). eThe required correlation provider (%1!s!) could not be added to the tracing session (error=0x%2!x!). ?The specified keywords are not valid for the provider '%1!s!'. PA;The specified level is not valid for the provider '%1!s!'. +The specified file '%1!s!' does not exist. #Conversion failed (error=0x%1!x!). !'%1!s!' is not a valid operator. '%1!s!' is not a valid range. %1!s! is not a valid interface. '%1!s!' is not a valid type. :Capture filters are only allowed when capture is enabled. *See 'trace %1!s! help' for detailed help. !'%1!s!' is a required parameter. ,Network Diagnostics failed (error=0x%1!x!). =The registry entry for '%1!s!' is not valid (error=0x%2!x!). AReport=yes is not allowed when SaveSessionTrace=no is specified. I'%1!ws!' is not a valid helper class or may not be correctly installed. 1<Unavailable - check helper class registration> $Correlation failed (error=0x%1!x!). ! Activity "%1!s!" was not found. CInvalid value "%2!s!" for command option "%1!s!" - Must be a GUID. +The specified path '%1!s!' does not exist. @The CaptureType switch is only allowed when capture is enabled. BThis CaptureType is not applicable to this system's architecture. NVirtual Switch capture can be enabled only after installing the Hyper-V role. $Trace merge failed (error=0x%1!x!). %%1!s! is not a valid routing domain. HWarning: The inbox capture driver could not be stopped (error=0x%1!x!). AWarning: Session information could not be saved (error=0x%1!x!). 3Warning: Report generation failed (error=0x%1!x!). }Warning: An instance of the 'NT Kernel Logger' is already running. System information will not be added to the trace file. RWarning: System information could not be added to the trace file (error=0x%1!x!). KWarning: Helper class attributes could not be retrieved (error=0x%1!08X!). .Warning: The NDF trace file is not available. xWarning: Some events were not captured due to high volume of events. Please consider using filters to reduce the volume :Warning: Report generation is not supported in safe mode. 7Warning: Packet capture is not supported in safe mode. PAOffOn3%systemroot%\pla\Reports\Report.System.NetTrace.xml0%systemroot%\pla\Rules\Rules.System.NetTrace.xmlYesNo2%systemroot%\system32\NetTrace.PLA.Diagnostics.xmlNetwork DiagnosticsThis data collector set collects network related data on your local system. The data to be collected includes network component traces, registry keys, system hardware information that can help troubleshoot network related problems.Microsoft Windows Network Trace MicrosoftPANetwork information collectorDisabledPA00L 0 0tPP ac4Start Stop Send Critical Error Warning Information Verbose \Microsoft-Windows-Networking-Correlation pMicrosoft-Windows-Networking-Correlation/Diagnostic `Dummy event for standard level enumeration HSource Provider: %1 Context: %2 HSource Provider: %1 Context: %2 HSource Provider: %1 Context: %2 4VS_VERSION_INFO@%@%?StringFileInfo040904B0LCompanyNameMicrosoft CorporationRFileDescriptionNetwork Trace Helperr)FileVersion6.3.9600.16384 (winblue_rtm.130821-1623): InternalNamenettrace.dll.LegalCopyright Microsoft Corporation. All rights reserved.JOriginalFilenamenettrace.dll.muij%ProductNameMicrosoft Windows Operating SystemBProductVersion6.3.9600.16384DVarFileInfo$Translation  Basic Network Configuration Information
General Configuration
OS Information
Credential Providers
 
Network Configuration
Environment Information
Adapter Information
DNS Information
Neighbor Information
 
Wireless Configuration
WLAN Auto-Config Eventlog
 
Windows Connect Now
WCN Information
 
Windows Firewall
Windows Firewall Configuration
Windows Firewall Effective Rules
Connection Security Eventlog
Connection Security Eventlog (Verbose)
Firewall Eventlog
Firewall Eventlog (Verbose)
 
Winsock Configuration
Winsock LSP Catalog
 
File Sharing
File Sharing Configuration
 
Registry Key Dumps
Credential Providers
Credential Provider Filters
API Permissions
WlanSvc HKLM Dump
WinLogon Notification Subscribers
Network Profiles
 
Trace Files
Primary Event Trace Log (ETL)
PADPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADD