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

Home NTDEV

Before Posting...

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

More Info on Driver Writing and Debugging


The free OSR Learning Library has more than 50 articles on a wide variety of topics about writing and debugging device drivers and Minifilters. From introductory level to advanced. All the articles have been recently reviewed and updated, and are written using the clear and definitive style you've come to expect from OSR over the years.


Check out The OSR Learning Library at: https://www.osr.com/osr-learning-library/


Inf2Cat error in VS2015

otalotal Member Posts: 3

Hello
I am porting a driver from VS2012 on window 7 to VS2015 on windows 10.
I cant get over the last error in the project :

Errors:
1> 22.9.1: vmewinproppage.dll in [vmewinclassinstallercopyfiles] of \vmewin.inf is missing or cannot be decompressed from source media. Please verify all path values specified in SourceDisksNames, SouceDisksFiles, and CopyFiles sections resolve to the actual location of the file, and are expressed in terms relative to the location of the inf.
1> 22.9.1: vmewinproppage.dll in [vmewin_device_coinstaller_copyfiles] of \vmewin.inf is missing or cannot be decompressed from source media. Please verify all path values specified in SourceDisksNames, SouceDisksFiles, and CopyFiles sections resolve to the actual location of the file, and are expressed in terms relative to the location of the inf.
1>
1> Warnings:
1> None
1>x64\Win7Debug\inf2catOutput.log : Inf2Cat error -2: "Inf2Cat, signability test failed." Double click to see the tool output.

this is the only driver with DLL included , and I dont understand the problem after checking the directories.

Comments

  • Peter_Viscarola_(OSR)Peter_Viscarola_(OSR) Administrator Posts: 9,160

    Your INF has bugs. Did you “double click to see the tool,output?”

    Peter

    Peter Viscarola
    OSR
    @OSRDrivers

  • otalotal Member Posts: 3

    the same INF file can be build for windows 7 using VS2012.
    what do you mean : double click to see tool,output?

  • Peter_Viscarola_(OSR)Peter_Viscarola_(OSR) Administrator Posts: 9,160

    I mean: Read the contents of the VS error window which says:

    1>x64\Win7Debug\inf2catOutput.log : Inf2Cat error -2: "Inf2Cat, signability test failed." Double click to see the tool output.

    Peter

    Peter Viscarola
    OSR
    @OSRDrivers

  • Tim_RobertsTim_Roberts Member - All Emails Posts: 14,836
    via Email
    otal wrote:
    > 1> 22.9.1: vmewinproppage.dll in [vmewinclassinstallercopyfiles] of \vmewin.inf is missing or cannot be decompressed from source media. Please verify all path values specified in SourceDisksNames, SouceDisksFiles, and CopyFiles sections resolve to the actual location of the file, and are expressed in terms relative to the location of the inf.
    >
    > 1> 22.9.1: vmewinproppage.dll in [vmewin_device_coinstaller_copyfiles] of \vmewin.inf is missing or cannot be decompressed from source media. Please verify all path values specified in SourceDisksNames, SouceDisksFiles, and CopyFiles sections resolve to the actual location of the file, and are expressed in terms relative to the location of the inf.

    I assume you understand what the message is trying to tell you. Both of
    the CopyFiles sections mentioned there have a line referring to
    vmewinproppage.dll.  Inf2cat did not find that file in the same folder
    as the INF, or if that file is mentioned in a [SourceDisksFiles]
    section, in the subdirectory specified.

    Windows 7 drivers weren't built with VS2012.  Were you using something
    like ddkbuild.bat?  Are you still trying to use ddkbuild.bat, or have
    you gone to a full vcxproj build?

    I notice that the message refers to \vmewin.inf.  That's suspicious. 
    Did it actually copy the INF to the root of your hard disk?  If so, then
    you are may be referring to a vcxproj variable that is no longer present.

    Tim Roberts, [email protected]
    Software Wizard Emeritus

  • mahendrashravanmahendrashravan Member Posts: 16

    I am facing similar issue,

    Inf2Cat Tool Output:
    ..........................
    Signability test failed.
    
    Errors:
    22.9.1: wausb.sys in [copydrvfiles] of WaUsb\wausb.inf is missing or cannot be decompressed from source media.  Please verify all path values specified in SourceDisksNames, SouceDisksFiles, and CopyFiles sections resolve to the actual location of the file, and are expressed in terms relative to the location of the inf.
    22.9.1: wausb.dll in [copydllfiles] of WaUsb\wausb.inf is missing or cannot be decompressed from source media.  Please verify all path values specified in SourceDisksNames, SouceDisksFiles, and CopyFiles sections resolve to the actual location of the file, and are expressed in terms relative to the location of the inf.
    22.9.1: wausb.dll in [copywow64dllfiles] of WaUsb\wausb.inf is missing or cannot be decompressed from source media.  Please verify all path values specified in SourceDisksNames, SouceDisksFiles, and CopyFiles sections resolve to the actual location of the file, and are expressed in terms relative to the location of the inf.
    
    Warnings:
    None
    

    I have placed the required .dll file at the same location as inf file, still seeing the same error.

    Also, this code building process was migrated using DDKBuild.bat to full vcxproj build.

    Can you please tell me, What I am doing wrong here?

  • Tim_RobertsTim_Roberts Member - All Emails Posts: 14,836

    You have resurrected a 4-year-old thread, instead of starting a new one.

    How can you have one copy of wausb.dll in both 64-bit and Wow64? Perhaps you should show us your INF and your directory tree.

    Tim Roberts, [email protected]
    Software Wizard Emeritus

  • mahendrashravanmahendrashravan Member Posts: 16

    Sorry for reopening the discussion again.

    this is my INF file

    /**************************************************************************/
    
    [Version]
    Signature=$Windows NT$
    Class=WAUSB
    ClassGUID={02CD7357-C6B4-4B0F-A27A-0326A7527B9E}
    Provider=%WA_STR%
    CatalogFile=wausb.cat
    DriverVer=04/09/2019,1.9.12.0
    DriverPackageType=PlugAndPlay
    ;----------------------------------------------------------------------------
    
    [SourceDisksNames]
    1 = %DiskId1%,,,\i386
    
    [SourceDisksNames.x86]
    1 = %DiskId1%,,,\i386
    
    [SourceDisksNames.amd64]
    1 = %DiskId1%,,,\amd64
    
    [SourceDisksFiles]
    wausb.sys   = 1,,
    wausb.dll   = 1,,
    
    [SourceDisksFiles.amd64]
    wausb.sys   = 1,,
    wausb.dll   = 1,,
    wausb32.dll     = 1,,
    
    [DestinationDirs]
    DefaultDestDir=10
    CopyDLLFiles = 11
    CopyWOW64DLLFiles = 10, SysWOW64
    CopyDrvFiles = 12
    
    ;----------------------------------------------------------------------------
    
    [ClassInstall32]
    AddReg=ClassAddReg
    
    [ClassAddReg]
    HKR,,,%REG_SZ%,%DeviceClassName%
    HKR,,Icon,,"-20"
    HKR,,NoInstallClass,,1
    
    ;-----------------------------------------------------------------------------
    
    [Manufacturer]
    %WAMfg%=DeviceList, NTx86, NTamd64
    
    [DeviceList]
    "WA CP50" = DriverInstall, USB\VID_0770&PID_1110
    "WA CP100/200" = DriverInstall, USB\VID_0770&PID_0008
    "WA CP150" = DriverInstall, USB\VID_0770&PID_1111
    
    [DeviceList.NTx86]
    "WA CP50" = DriverInstall, USB\VID_0770&PID_1110
    "WA CP100/200" = DriverInstall, USB\VID_0770&PID_0008
    "WA CP150" = DriverInstall, USB\VID_0770&PID_1111
    
    [DeviceList.NTamd64]
    "WA CP50" = DriverInstall, USB\VID_0770&PID_1110
    "WA CP100/200" = DriverInstall, USB\VID_0770&PID_0008
    "WA CP150" = DriverInstall, USB\VID_0770&PID_1111
    
    [DriverInstall]
    CopyFiles=CopyDrvFiles
    CopyFiles=CopyDLLFiles
    
    [DriverInstall64]
    CopyFiles=CopyDrvFiles
    CopyFiles=CopyDLLFiles
    CopyFiles=CopyWOW64DLLFiles
    
    [CopyDrvFiles]
    wausb.sys
    
    [CopyDLLFiles]
    wausb.dll
    
    [CopyWOW64DLLFiles]
    wausb.dll, wausb32.dll
    
    [DriverInstall64.Services]
    AddService=WAUsb,%SPSVCINST_ASSOCSERVICE%,DriverService
    
    [DriverInstall.Services]
    AddService=WAUsb,%SPSVCINST_ASSOCSERVICE%,DriverService
    
    [DriverService]
    DisplayName    = %DESCRIPTION_STR%
    ServiceType    = %SERVICE_KERNEL_DRIVER%
    StartType      = %SERVICE_DEMAND_START%
    ErrorControl   = %SERVICE_ERROR_NORMAL%
    ServiceBinary  = %12%\wausb.sys
    
    ;------------------------------------------------------------------------------
    
    [Strings]
    WAMfg =             "WA"
    WA_STR =            "WA"
    DESCRIPTION_STR=    "WA Generic USB Driver"
    USBDEVDESC =        "WA USB Devices"
    DiskId1 =           "WA Driver Installation Disk #1"
    DeviceClassName =   "WA USB Devices"
    
    
    ;------------------------------------------------------------------------------
    
    ;Handy macro substitution
    SERVICE_KERNEL_DRIVER = 1
    SERVICE_DEMAND_START =  0X03
    SERVICE_ERROR_NORMAL =  1
    REG_EXPAND_SZ =         0X00020000
    REG_DWORD =             0X00010001
    FLG_ADDREG_TYPE_DWORD = 0X00010001
    REG_MULTI_SZ =          0X00010000
    REG_SZ =                0X00000000
    DEVICECHARACTER_FLAGS=  0x00000100
    DELFLG_IN_USE1 =        0x00010000
    SPSVCINST_ASSOCSERVICE = 0x00000002
    

    Below is the Release Directory structure

    x64 
    |--> Release
           |--> WaUsb
           |     |--> WaUsb.inf
           |     |--> WaUsb.sys
           |--> WaUsb.cer
           |--> WaUsb.dll
           |--> WaUsb.exp
           |--> WaUsb.inf
           |--> WaUsb.lib
           |--> WaUsb.pdb
           |--> WaUsb.sys
    
  • Tim_RobertsTim_Roberts Member - All Emails Posts: 14,836

    But that's not the directory structure described by the INF. The INF expects x86 and amd64 subdirectories (as it should for a combined 32/64 INF).

    Tim Roberts, [email protected]
    Software Wizard Emeritus

Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. Sign in or register to get started.

Upcoming OSR Seminars
OSR has suspended in-person seminars due to the Covid-19 outbreak. But, don't miss your training! Attend via the internet instead!
Kernel Debugging 13-17 May 2024 Live, Online
Developing Minifilters 1-5 Apr 2024 Live, Online
Internals & Software Drivers 11-15 Mar 2024 Live, Online
Writing WDF Drivers 20-24 May 2024 Live, Online