Software Deployment

There are serveral ways but for me the most succesvol is the following. This is a litte help to get in de right direction.

The only condition is that you're drivers are signed.
Checked that with sigverif.exe.

Put the drivers like sys inf etc in the INSTALLDIR.

In wise:
1) Make a custom action Execute Program from installation of the driver

2) include the following
Executable File DPINST.exe
Commandline arguments /S /LM /PATH "[INSTALLDIR]
Put it in the sequence that suites you well. Condition like NOT REMOVE.

3) Make a custom action Execute Program from installation for removing the driver

4) include the following :
Executable File DPINST.exe
Commandline arguments /S /U "[INSTALLDIR]nameoftheinfile.inf
Put it in the sequence that suites you well. Condition like REMOVE~="All"

Thanks for your reply.

I am aware of DPinst.exe and know how to use it, but my issue is that these drivers are unisgned and they are not installing when using the following commandline. (even though DPInst says successfully installed)

Dpinst.exe /s /LM

when the dpinst.exe is in the same folder as the .inf file.

If anyone needs me to add the contents of the inf file so they can try it out too I can?

You can download the drivers here - http://www.zylomed.com/download/olympusdrvs/

Please help - I'm getting a headache from it!

Rgds,
Mark

When installing manualy maybe a idea to capture it.
Then you know where the files are placed. Then installing them with dpinst?

Ya, I've done that. It captures the 2 inf files and even when using DPInst.exe I still get the same issue.

The setupapi.log for a successful install using the Windows hardware/driver wizard is as follows (at least the relevant section).
I can't replicate this using DPInst.exe -
***************************************************************
[2010/05/19 17:05:53 2904.2]
#-199 Executing "C:\WINDOWS\system32\rundll32.exe" with command line: rundll32.exe newdev.dll,ClientSideInstall \\.\pipe\PNP_Device_Install_Pipe_0.{196F9623-E534-4B6E-BE87-96003C3CCC60}
#I060 Set selected driver.
#-019 Searching for hardware ID(s): usb\vid_07b4&pid_020d&rev_0100,usb\vid_07b4&pid_020d
#-018 Searching for compatible ID(s): usb\class_ff&subclass_ff&prot_ff,usb\class_ff&subclass_ff,usb\class_ff
#I022 Found "USB\VID_07B4&PID_020D" in C:\WINDOWS\inf\vnusb.inf; Device: "VN Series Device"; Driver: "VN Series Device"; Provider: "OLYMPUS IMAGING CORP."; Mfg: "OLYMPUS IMAGING CORP."; Section name: "VNUSB.INSTALL".
#I087 Driver node not trusted, rank changed from 0x00000001 to 0x00008001.
#I023 Actual install section: [VNUSB.INSTALL.NT]. Rank: 0x00008001. Effective driver date: 03/30/2003.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [VNUSB.INSTALL] in "c:\windows\inf\vnusb.inf".
#I320 Class GUID of device remains: {67E64D25-AC39-40BF-B8D5-4D97A9E80182}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#I060 Set selected driver.
#-019 Searching for hardware ID(s): usb\vid_07b4&pid_020d&rev_0100,usb\vid_07b4&pid_020d
#-018 Searching for compatible ID(s): usb\class_ff&subclass_ff&prot_ff,usb\class_ff&subclass_ff,usb\class_ff
#I022 Found "USB\VID_07B4&PID_020D" in C:\WINDOWS\inf\vnusb.inf; Device: "VN Series Device"; Driver: "VN Series Device"; Provider: "OLYMPUS IMAGING CORP."; Mfg: "OLYMPUS IMAGING CORP."; Section name: "VNUSB.INSTALL".
#I087 Driver node not trusted, rank changed from 0x00000001 to 0x00008001.
#I023 Actual install section: [VNUSB.INSTALL.NT]. Rank: 0x00008001. Effective driver date: 03/30/2003.
#-019 Searching for hardware ID(s): usb\vid_07b4&pid_020d&rev_0100,usb\vid_07b4&pid_020d
#-018 Searching for compatible ID(s): usb\class_ff&subclass_ff&prot_ff,usb\class_ff&subclass_ff,usb\class_ff
#I022 Found "USB\VID_07B4&PID_020D" in c:\windows\inf\vnusb.inf; Device: "VN Series Device"; Driver: "VN Series Device"; Provider: "OLYMPUS IMAGING CORP."; Mfg: "OLYMPUS IMAGING CORP."; Section name: "VNUSB.INSTALL".
#I087 Driver node not trusted, rank changed from 0x00000001 to 0x00008001.
#I023 Actual install section: [VNUSB.INSTALL.NT]. Rank: 0x00008001. Effective driver date: 03/30/2003.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [VNUSB.INSTALL] in "c:\windows\inf\vnusb.inf".
#I320 Class GUID of device remains: {67E64D25-AC39-40BF-B8D5-4D97A9E80182}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-124 Doing copy-only install of "USB\VID_07B4&PID_020D\5&26921BA2&0&2".
#W334 Failed to verify catalog when scanning file queue. Error 1168: Element not found.
#E360 An unsigned or incorrectly signed file "c:\windows\inf\vnusb.inf" for driver "VN Series Device" will be installed (Policy=Ignore). Error 1168: Element not found.
#E360 An unsigned or incorrectly signed file "c:\windows\inf\vnusb.inf" for driver "VN Series Device" will be installed (Policy=Ignore). Error 1168: Element not found.
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [VNUSB.INSTALL.NT.Interfaces] from "c:\windows\inf\vnusb.inf".
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Doing full install of "USB\VID_07B4&PID_020D\5&26921BA2&0&2".
#I121 Device install of "USB\VID_07B4&PID_020D\5&26921BA2&0&2" finished successfully.
***************************************************************
***************************************************************

If the driver is unsigned by the manufacturer then sign it yourself - read this thread and this one.

You'll then be able to dpinst the driver.

Hope this helps,

Dunnpy

It infuriates me that we're at Windows 7 and these drongo vendors are STILL releasing unsigned drivers. It ain't rocket science, so what's the deal?

These days, as a matter of course, I fire off an email to the development director or equivalent, asking that very question. I do it so often I have a boilerplate email saved in my Drafts folder. What percentage reply, do you imagine?

Hi Mark,

I packaged this and used a VBScript CA to install the drivers as a custom action using the following 2 command lines:

c:\windows\system32\rundll32.exe syssetup,SetupInfObjectInstallAction DefaultInstall 128 C:\Program Files\Olympus\Drivers\DW90USB.INF
c:\windows\system32\rundll32.exe syssetup,SetupInfObjectInstallAction DefaultInstall 128 C:\Program Files\Olympus\Drivers\VNUSB.INF

Package works fine but unsigned drivers are allowed here (Win XP) so if it is a signing issue then I guess you'll have the same result as with DPInst in your environment - i.e. it still won't work

Hope it helps,
Rob.

maybe other sugestion when the drivers are installed by setup.exe is trying to found out how to (de)install the executable silent and then wrap it with the msi. But lack driversigning is a hard to avoid.