DIFxApp 2.0 won't install my driver - it doesn't think it's signed
- From: "Bob K" <bobk123456@xxxxxxxxxxxxxxxx>
- Date: Sat, 23 Apr 2005 14:15:20 -0400
I thought I had this DIFxApp thing under control, but I just upgraded to
version 2.0 that was just released (I need the x64 support) and it seems to
have broken something. The install now aborts with the following log:
DIFXAPP: InstallDriverPackages
DIFXAPP: 'CustomActionData' property 'DIFxApp Version' is 2.0.
DIFXAPP: 'CustomActionData' property 'UI Level' is 5.
DIFXAPP: 'CustomActionData' property 'componentId' is
{33C87C1F-F8A4-4834-9F3D-A9026D067632}.
DIFXAPP: 'CustomActionData' property 'componentPath' is C:\Program
Files\company driver\Kernel_MF\.
DIFXAPP: 'CustomActionData' property 'flags' is 0x10.
DIFXAPP: 'CustomActionData' property 'installState' is 2.
DIFXAPP: 'CustomActionData' property 'ProductName' is driver.
DIFXAPP: 'CustomActionData' property 'ManufacturerName' is FBN Corporation.
DIFXAPP: INFO: ENTER: DriverPackageInstallW
DIFXAPP: INFO: Checking signature with catalog 'C:\Program Files\company
driver\Kernel_MF\driver.cat' ...
DIFXAPP: ERROR: Signature verification failed while checking integrity of
driver package 'driver.inf' ('C:\Program Files\company
driver\Kernel_MF\driver.inf'). (Error code 0xE0000244.)
DIFXAPP: INFO: Successfully removed {33C87C1F-F8A4-4834-9F3D-A9026D067632}
from reference list of driver store entry
DIFXAPP: INFO: RETURN: DriverPackageInstallW (0xE0000244)
DIFXAPP: ERROR encountered while installing driver package C:\Program
Files\company driver\Kernel_MF\driver.inf
DIFXAPP: InstallDriverPackages failed with error 0xE0000244
Action ended 7:46:31: InstallFinalize. Return value 3.
The driver is signed. If I use chktrust on the .cat file it reports that it
is properly signed. Is there any other utility that would be more
appropriate to use?
My only clue here is that maybe there is a file that is not included in the
signature that should be, or there is a file that is included that shouldn't
be.
How can I determine the problem?
My driver consists of a single .sys file. I also include a stripped .pdb
file. That means my .cdf file that creates the .cat file looks like:
[CatalogHeader]
name=driver.cat
[CatalogFiles]
driversys=driver.sys
driverinf=driver.inf
driverpdb=driver.pdb
I then sign the .cat file. The .inf file has an entry that points to the cat
file:
[Version]
Signature = "$Windows NT$"
Class = "Replication"
Provider = %Company%
DriverVer = 01/01/05,0.0.0.0
CatalogFile = driver.cat
DriverPackageType=FileSystemMinifilter
DriverPackageDisplayName=%DriverServiceDesc%
Any help or any idea on what to look for would be greatly appreciated!
This worked in DIFxApp 1.1!!!
Thanks!
Bob
.
- Follow-Ups:
- Prev by Date: Re: Shell Namespace vs. Device Driver
- Next by Date: Re: Get service pack name from a driver?
- Previous by thread: Shell Namespace vs. Device Driver
- Next by thread: RE: DIFxApp 2.0 won't install my driver - it doesn't think it's signed
- Index(es):
Relevant Pages
|
