Changes between Version 1 and Version 2 of TestingStrategy


Ignore:
Timestamp:
Sep 23, 2008, 1:56:27 AM (17 years ago)
Author:
Lewis Rosenthal
Comment:

Entered data concerning PCI ID & how to determine

Legend:

Unmodified
Added
Removed
Modified

  • TestingStrategy

    v1 v2  
    1 == Testing Uniaud ==
     1[[PageOutline]]
     2
     3= Testing Uniaud =
    24
    35This page will contain various test scenarios to standardize the manner in which devices should be put under test to verify compatibility with Uniaud.
     6
     7== Device Identification ==
     8
     9This is fundamental to testing and also to raising a ticket.
     10
     11To properly identify the exact hardware in your system, follow these simple steps:
     12
     13  1. Download Veit Kannegieser's ported and customized version of Craig Harts PCI/PCI32 tool, pci.exe from
     14[http://hobbes.nmsu.edu/h-browse.php?dir=/pub/os2/util/misc Hobbes], in the /pub/util/misc directory. Look for
     15a file named pciXXXvka.zip. Where XXX is the version number.
     16  2. Unzip the package in a directory of your choice.
     17  3. From a command line, run PCI.EXE.
     18  4. Page through the results, looking for references to "Audio Controller" or something similar (this should be highlighted in yellow).
     19  5. Note the two parts of the PCI ID: the vendor code and the device. These are normally expressed as vvvv:dddd, but appear in the pci.exe output as
     20{{{
     21Vendor vvvvh
     22Device ddddh
     23}}}
     24where the h represents "hexadecimal," and is understood when using the afrementioned vvvv:dddd notation.
     25  6. You should also note the name of the device which follows the code on the Device line. The name usually includes a reference to the codec (e.g., AC'97).