Windows System Software -- Consulting, Training, Development -- Unique Expertise, Guaranteed Results

Before Posting...
Please check out the Community Guidelines in the Announcements and Administration Category.

PCISIG PCIe Configuration test won't run?

Pavel_APavel_A Member Posts: 2,674
PCISIG PCIe Configuration test won't run?

I'm in a trouble with the PCIe configuration space test, from
http://pcisig.com/developers/compliance-program

Before pointing out (rightfully) that this forum is not PCISIG support, please read...
here's some weird, driver related issue here.

The test app is installed on a Win7 SP1 32-bit pro, per the instructions (from MSDN, clean, no updates).
Installed the test driver, also per the instructions.
When I run the "PCIECV application", it immediately exits with message "User Interface failed to intialize".

The only clue is the eventlog entry in Application log, every time when I run the app:

Source: Windows Error Reporting
Event 1001
"Fault bucket, type 0
Event Name: PnPDriverImportError
Responce: Not available
P1: x86
P2: 00000002
P3: pciesw.inf
P4: <long hex>
P5:

and there's path to a Report.wer file with following content:

---------begin---------
Version=1
EventType=PnPDriverImportError
EventTime=130830782333203125
Consent=1
ReportIdentifier=.............
Response.type=4
Sig[0].Name=Architecture
Sig[0].Value=x86
Sig[1].Name=Win32 error
Sig[1].Value=00000002
Sig[2].Name=Inf name
Sig[2].Value=pciesw.inf
Sig[3].Name=Driver Package hash
Sig[3].Value=f4531ecabc39f9627886fa1246862acd4587d342
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
FriendlyEventName=Could not install driver software
ConsentKey=PnPDriverImportError
AppName=Driver software installation
AppPath=C:\Program Files\PCIECV App\PCIECVApp.exe
ReportDescription=Windows could not copy all of the files needed to install this device driver software. This sometimes happens when the driver software was not designed for this version of Windows.
------end---------

Here, PCIECVApp.exe is the test app and pciesw.inf is the INF file of its driver,
all installed by the test installer.

What means "the driver software was not designed for this version of Windows"?
Is this because of SP1?
The test instruction says to install on Win7, but I don't have Win7 without SP1.

The inf is root enumerated, class "system" and hw. id "root\pciesw".
Version 03/23/2011, by Intel.

Will be very grateful for any insight.

-- pa

Comments

  • Tim_RobertsTim_Roberts Member - All Emails Posts: 13,007
    xxxxx@fastmail.fm wrote:
    > I'm in a trouble with the PCIe configuration space test, from
    > http://pcisig.com/developers/compliance-program
    > ...
    > The test app is installed on a Win7 SP1 32-bit pro, per the instructions (from MSDN, clean, no updates).
    > Installed the test driver, also per the instructions.
    > When I run the "PCIECV application", it immediately exits with message "User Interface failed to intialize".
    > ...
    > ReportDescription=Windows could not copy all of the files needed to install this device driver software. This sometimes happens when the driver software was not designed for this version of Windows.
    > ...
    > What means "the driver software was not designed for this version of Windows"?
    > Is this because of SP1?

    Or because of a 32-bit/64-bit conflict. Are you comfortable posting the
    INF file? Are you running as administrator?

    --
    Tim Roberts, xxxxx@probo.com
    Providenza & Boekelheide, Inc.

    Tim Roberts, [email protected]
    Providenza & Boekelheide, Inc.

  • Pavel_APavel_A Member Posts: 2,674
    Tim,

    thank you for reply. I've found the reason of this error,
    it is because the inf has the CatalogFile line, but the .cat referenced
    there is not present.
    Deleted the CatalogFile line, deleted the driver package using dpinst
    -d , reinstalled it using device manager, and now the app runs fine.
    On 32-bit Win7 unsigned driver is ok.

    Perhaps this INF did not cause errors with the RTM Win7, but SP1 does
    not like CatalogFile directive without a corresponding cat file.

    Hope this fix may help people who need to do PCISIG tests.

    Thanks again,
    -- pa
  • Pavel_APavel_A Member Posts: 2,674
    > deleted the driver package using dpinst -d

    Correction: using pnputil -d

    -- pa
Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Upcoming OSR Seminars
Developing Minifilters 29 July 2019 OSR Seminar Space
Writing WDF Drivers 23 Sept 2019 OSR Seminar Space
Kernel Debugging 21 Oct 2019 OSR Seminar Space
Internals & Software Drivers 18 Nov 2019 Dulles, VA