| 1 | = Troubleshooting the USB Drivers = |
| 2 | |
| 3 | If you open a ticket, additional information will almost always be necessary. The two most common things are a testlog log file and a formmated trace. You can save a lot of time by attaching these two things to your ticket when you open it, rather than waiting for the developer to ask for them. |
| 4 | |
| 5 | This page contains instructions for creating a testlog log file and a formatted trace file. |
| 6 | |
| 7 | == Capturing A testlog log file == |
| 8 | |
| 9 | Download the testlog log file creator here |
| 10 | |
| 11 | open a command window and execute the testlog command |
| 12 | {{{ |
| 13 | testlog usb |
| 14 | }}} |
| 15 | |
| 16 | Attach the created log file to your ticket. |
| 17 | |
| 18 | == Capturing a Startup Trace file == |
| 19 | 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. |
| 20 | |
| 21 | To create a startup trace file, do the following: |
| 22 | |
| 23 | == Capturing a Runtime Trace file == |
| 24 | |
| 25 | 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. |
| 26 | |
| 27 | To create a runtime trace file, do the following: |
| 28 | |
| 29 | == Creating a Trap Dump == |
| 30 | |
| 31 | Steven Levine already wrote a [http://home.earthlink.net/~steve53/os2diags/TrapDumpRef.txt detailed description] how to do this. |