| 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 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. Only attach a formatted trace file if the developer asks for it. |
| | 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 formatted trace. The testlog log file is always required unless your system traps or won't boot. 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. Only attach a formatted trace file if the developer asks for it. |
| | 4 | |
| | 5 | If you cannot create a testlog log, at a minimum you must include the bldlevel output for the driver you are using. Also, include the PCI Vendor ID and Device ID of your hardware in the ticket (ie. the section from PCI.EXE that relates to your NIC). If the driver traps, please, include the trap screen. |
