1394 driver signing for Vista and 1394 Configuration ROM ASCII dat

Discussion in 'Windows Vista Drivers' started by anatolyk01, Aug 6, 2008.

  1. anatolyk01

    anatolyk01 Guest

    I am trying to create catalog file for proprietary 1394 device. The error
    complains about device description 1394\50C0&10001:

    B2.2.4.14: All IEEE 1394 devices must have textual descriptors for the
    vendor an
    d device IDs. Third-party 1394 function drivers must be installed through a
    ue PnP ID match in the specific hardware, for example,
    1394\VendorName&ModelName or 1394\UnitSpecId&UnitSwVersion. The hardware ID
    matches only on the form that is specific to a device. Class drivers must not
    install through either a class ID match or a compatible ID match in the INF.
    The following formats are not acceptable: 1394\<hex>, 1394\<hex>&<hex>

    The device configuration ROM indeed does not have textual descriptors of
    Vendor and Device ID, only hex OUI and hex model code. Is there way around
    this? If the only way is to reprogram configuration ROM, where is document
    specifying how to do that?
    anatolyk01, Aug 6, 2008
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.