/build/static/layout/Breadcrumb_cap_w.png

Can't create a Catalog file from Legacy driver .INF

Hello All!

In the package there are two drivers that are installed into system.
Both drivers are of 1394 type (Some kind of Camera Firewire PnP drivers).

Both Drivers are Unsigned.

I took both drivers and appropriate .INF files and tried to follow Driving Signing guide like it's described here: http://technet.microsoft.../en-us/library/dd919238(WS.10).aspx
Added "DriverVer" and "Catalog" entries.

When I execute "inf2cat.exe" tool to generate catalog file from these .INF files it fails with error:

=============================================================================
Errors:
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 unique 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 "Inf2cat.exe" tool doesn't "LIKE" Driver description entry in the INF files which look like this:

[IS1394_04]
%IS1394_04.DeviceDesc%=IS1394_04.INSTALL, 1394\E026&1D


I'm not Windows Driver expert and I don't know whether I'm allowed to change those HEX values for Vendor Name and Device name.
Any help would much appreciated as I'm totally stuck with this problem.


Here are contents of one .INF file:



; INF file for KODAKIS1394_04.sys

[Version]
Signature="$Windows NT$"
Class=IS1394_04
ClassGUID={F1060D97-49FD-436D-B544-187997EE5010}
Provider=%IS1394_04.Provider%

[Manufacturer]
%IS1394_04.Manufacturer%=IS1394_04

[ClassInstall32]
AddReg=IS1394_04.AddClassReg

[IS1394_04]
%IS1394_04.DeviceDesc%=IS1394_04.INSTALL, 1394\E026&1D

; TODO: Add an optional Tag File to ensure that the end user
; has specified the correct path to the diskette, CD-ROM,
; or network drive. See the INF File Reference in the
; DDK documentation for more information on SourceDisksNames
; sections.
[SourceDisksNames]
1=%IS1394_04.DriverDiskName%,"",1

[SourceDisksFiles]
KODAKIS1394_04.sys=1

[PreCopySection]
HKR,,NoSetupUI,,1

[DestinationDirs]
IS1394_04.CopyFiles = 10,system32\drivers ; WINDOWS\SYSTEM32\DRIVERS

[IS1394_04.INSTALL]
;CopyFiles=IS1394_04.CopyFiles
AddReg=IS1394_04.AddRegLoader

[IS1394_04.AddClassReg]
HKR,,,,%IS1394_04.ClassName%

[IS1394_04.AddRegLoader]
HKR,,DevLoader,,*ntkern
HKR,,NTMPDriver,,KODAKIS1394_04.sys

[IS1394_04.INSTALL.NT]
;CopyFiles=IS1394_04.CopyFiles
AddReg=IS1394_04.AddRegLoader

[IS1394_04.INSTALL.NT.Services]
AddService = IS1394_04,0x00000002,IS1394_04_Service_Inst

[IS1394_04_Service_Inst]
ServiceType = 1 ;%SERVICE_KERNEL_DRIVER%
StartType = 3 ;%SERVICE_AUTO_START%
ErrorControl = 1 ;%SERVICE_ERROR_NORMAL%
ServiceBinary = %10%\system32\drivers\KODAKIS1394_04.sys
DisplayName = %IS1394_04.DeviceDesc%


[IS1394_04.CopyFiles]
KODAKIS1394_04.sys


;---------------------------------------------------------------;

[Strings]
IS1394_04.Provider="KODAK"
IS1394_04.Manufacturer="KODAK"
IS1394_04.DeviceDesc="KODAK IS1394_04 Camera"
IS1394_04.ClassName="KODAK Scientific Camera"
IS1394_04.DriverDiskName="KODAK IS1394_04 System Installation Diskette"

0 Comments   [ + ] Show comments

Answers (0)

Be the first to answer this question

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ