Cannot install device driver on Windows 2003 R2

[JMcGinnis]

Reach out to see if you can help us, as we have reached the end of our expertise (in Stealth world).

We are attempting to build a install package using Install Shield 2008 (which uses DIFX 2.1).

The OS we are installing on is Windows 2003 R2 (SP2).

We attempted to install our first driver component (named SCSITMD). We have self-signed the driver package (SYS and INF file) and generated a CAT file using the same process that the guy uses :confused: (when doing manual USSL gens).

The installation appear to run to completion, but upon inspection, the driver has not been registered.

The SetupApi.Log file shows the following entries :

[2010/01/11 13:40:18 1844.3]
#-198 Command line processed: C:\WINDOWS\system32\MsiExec.exe -Embedding D9C1DB8424B103C88DC2D2DA16DDED24 M Global\MSI0000
#I440 File "C:\WINDOWS\system32\DRVSTORE\ScsiTmd_F5A782A87A9556162090B1E2906C4C2F6E5FDE8A\ScsiTmd.inf" (key "ScsiTmd.inf") is signed in Authenticode(tm) catalog "C:\WINDOWS\system32\DRVSTORE\ScsiTmd_F5A782A87A9556162090B1E2906C4C2F6E5FDE8A\ScsiTmd.cat". Error 0xe0000242: The publisher of an Authenticode(tm) signed catalog has not yet been established as trusted.
#W361 An unsigned, incorrectly signed, or Authenticode(tm) signed file "C:\WINDOWS\system32\DRVSTORE\ScsiTmd_F5A782A87A9556162090B1E2906C4C2F6E5FDE8A\ScsiTmd.cat" will be installed (Policy=Ignore). Error 0xe0000242: The publisher of an Authenticode(tm) signed catalog has not yet been established as trusted.
[2010/01/11 13:40:18 1844.7]
#-198 Command line processed: C:\WINDOWS\system32\MsiExec.exe -Embedding D9C1DB8424B103C88DC2D2DA16DDED24 M Global\MSI0000
#I442 A valid signature for file "C:\WINDOWS\system32\DRVSTORE\ScsiTmd_F5A782A87A9556162090B1E2906C4C2F6E5FDE8A\ScsiTmd.inf" (key "ScsiTmd.inf") was found in an installed Authenticode(tm) catalog "C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem4.CAT". Error 0xe0000242: The publisher of an Authenticode(tm) signed catalog has not yet been established as trusted.

It not clear if this issue is really prevent the driver from being installed. The driver will install manually without an issue, so all the necessary components should be present.

Not sure if you’re the right person to throw this at, but feel free to involve anyone else. I want to exhaust all possible resource within Unisys before having to go to Microsoft.

Thanks In Advance,

[Holger_G]

I never run a driver installation package based on DIFx on Windows Server 2003 but it should work as well since DIFx officially supports this OS.

A good catch would be to simply run DPInst.exe in the driver package directory and check the results. Most recent version of DIFx (includes DPInst.exe) can be found in the latest WDK.

You should also check the DIFx runtime options of your driver component. Activate 'Install unsigned driver files' and test it again.

[chriscw]

I was going to suggest including the Unsigned driver switch but I see someone else already did that.

I was interested in you comment "generated a CAT file using the same process that the guy uses (when doing manual USSL gens)." Can you tell me where I can find that information as it might help us with similar problems.

Thanks


Chris