= Troubleshooting the USB Drivers =

Make sure all of your USB drivers are the same version and make sure that your CONFIG.SYS is loading the correct drivers. You should not mix versions since the drivers are designed to work together and changes in some drivers might not be compatible with older versions of other drivers.  At the very least, make sure that USBEHCD.SYS, USBOHCD.SYS, USBUHCD.SYS, and USBD.SYS are all the same version. And make sure that USBHID.SYS, USBKBD.SYS, and USBMOUSE.SYS are all the same version.

If you open a ticket, additional information will almost always be necessary. The two most common things are a testlog log file and a formatted trace.  The testlog log file is always required. You can save a lot of time by attaching the testlog log file to your ticket when you open it, rather than waiting for the developer to ask for it. Since there are many types of trace files that could be needed, do not arbitrarily attach a random trace file to your ticket. Instead wait for the developer to ask for a specific trace file.

This page contains instructions for creating a testlog log file and a formatted trace file.

== Capturing A testlog log file ==

If you don't already have the current version of testlog.cmd, you can download it here: [http://88watts.net/download/testlog-2.08.zip testlog-2.08.zip]

Open a command window and execute the testlog command
   {{{
testlog usb
   }}}

Attach the created log file to your ticket. Do not ZIP the log file.

== Capturing a Startup Trace file ==

A startup trace file is for a problem that occurs on startup, rather than for a problem that occurs after the system has been running for a while.

To create a startup trace file, do the following:

1) Add the following line to your config.sys:
{{{
  TRACEBUF=512 /M=NOWRAP,QUEUED,NODTI /D=ALL
}}}
2) Add the appropriate "TRACE=ON <trace code>" line to your config.sys.
  For USBUHCD.SYS the trace code is 224[[br]]
  For USBOHCD.SYS the trace code is 225[[br]]
  For USBEHCD.SYS the trace code is 226[[br]]
  For example, to trace the USBEHCD.SYS driver you would add the following line:
{{{
  TRACE=ON 226
}}}
  To trace both the USBEHCD.SYS driver and the USBUHCD.SYS driver, you would
  add the following line:
{{{
  TRACE=ON 224,226
}}}
  To trace both the USBEHCD.SYS driver and the USBOHCD.SYS driver, you would
  add the following line:
{{{
  TRACE=ON 225,226
}}}

3) Reboot to enable tracing. 

4) To capture the trace dump, open a command window and type:
{{{
   TRACEFMT
}}}
From the file menu choose Save Formatted... and save the trace to a file of your choice.

5) Attach file you created to your ticket.

== Capturing a Runtime Trace file ==

A runtime trace file is for problems that occur after the system is up and running. It is not for problems that occur at startup.

To create a runtime trace file, do the following:

1) Add the following line to your config.sys:
{{{
  TRACEBUF=512 /M=WRAP,QUEUED,NODTI /D=ALL
}}}
2) Add the appropriate "TRACE=ON <trace code>" line to your config.sys.
  For USBUHCD.SYS the trace code is 224[[br]]
  For USBOHCD.SYS the trace code is 225[[br]]
  For USBEHCD.SYS the trace code is 226[[br]]
  For example, to trace the USBEHCD.SYS driver you would add the following line:
{{{
  TRACE=ON 226
}}}
  To trace both the USBEHCD.SYS driver and the USBUHCD.SYS driver, you would
  add the following line:
{{{
  TRACE=ON 224,226
}}}
  To trace both the USBEHCD.SYS driver and the USBOHCD.SYS driver, you would
  add the following line:
{{{
  TRACE=ON 225,226
}}}

3) Reboot to enable tracing. 

4) To capture the trace dump, open a command window and type:
{{{
   TRACEFMT
}}}
From the file menu choose Save Formatted... and save the trace to a file of your choice.

5) Attach file you created to your ticket.

== Creating a Trap Dump ==

Steven Levine already wrote a [http://home.earthlink.net/~steve53/os2diags/TrapDumpRef.txt detailed description] how to do this.