Re: Generating inf file for multiple devices.

Greetings,

That should work just fine for your .inf file.

dpscat.exe is meant to be run on the customer's PC at the time of 
installation. It is not part of the install creation process. It creates 
a self-signing certificate on the client PC then signs the driver 
package just before it is installed.

Now you need to run "re-pack-files.cmd". This will combine all of your 
driver install files into a self-extracting .exe. This self-extracting 
.exe has a small, installer like, script that it runs after extracting 
it's files. See '7zDP_LZMA.cfg'. Maybe this will help you better 
understand how and when dpscat.exe comes into play.

Regards,
Travis

On 8/6/2014 11:50 PM, Pradeepa Senanayake wrote:
> Thank you very much for the explanation. I don't know whether I did in 
> the correct way but I made the INF file such that it can be used to 
> install both the devices.
>
> I did as follows,
>
> [Strings]
> DeviceName1 = "Device1"
> DeviceName2 = "Device2"
> DeviceName3 = "Device3"
> ...
> DeviceID1 = "VID_xxxx&PID_0009"
> DeviceID2 = "VID_xxxx&PID_000B"
> DeviceID3 = "VID_xxxx&PID_000C"
>
> ...
> ...
>
> [LUsbK_DeviceGroup]
> %DeviceName1%=LUsbK_Device, USB\%DeviceID1%
> %DeviceName2%=LUsbK_Device, USB\%DeviceID2%
> %DeviceName3%=LUsbK_Device, USB\%DeviceID3%
>
> ; For XP and later
> [LUsbK_DeviceGroup.NTX86]
> %DeviceName1%=LUsbK_Device, USB\%DeviceID1%
> %DeviceName2%=LUsbK_Device, USB\%DeviceID2%
> %DeviceName3%=LUsbK_Device, USB\%DeviceID3%
>
> [LUsbK_DeviceGroup.NTAMD64]
> %DeviceName1%=LUsbK_Device, USB\%DeviceID1%
> %DeviceName2%=LUsbK_Device, USB\%DeviceID2%
> %DeviceName3%=LUsbK_Device, USB\%DeviceID3%
>
> Then I ran the 'dpscat' application and generated the CAT file. I 
> think it does self signing too. (Which I still cannot understand)
>
> Then I installed the driver. It is working for now. But is this the 
> correct approach?
>
> ​
> Ekkehard <[email protected] 
> <mailto:[email protected]>> wrote:
>
>     Travis wrote
>     > Method #2
>     > The driver install tool is capable of installing multiple .INFs
>     at once
>     > as if they were one. You should only need to create an installer for
>     > each device then copy all of the .inf files into a single
>     install folder.
>
>
>     Thats my favorite way to do.
>     The only thing to keep in mind is, if the driver changes (due to
>     an update)
>     the inf files must me updated, either manually or with a rebuild
>     of each
>     single installer.
>
>
> This method looks easy, ​I prefer a single INF file.​
>
> Just curious, apart from signing what other tasks does the installer 
> carry out?
>
> ​I'm going through this 
> http://www.osronline.com/showthread.cfm?link=223734​ really long 
> thread to understand the signing process also. I'm trying to figure 
> out how the certificate trust chain is linked. It should link with 
> some trusted certificate and from where does that come from is a 
> mystery to me.
>
>
> Best Regards,
> Pradeepa Senanayake.
>
> ​
>
>
>
> ------------------------------------------------------------------------------
> Infragistics Professional
> Build stunning WinForms apps today!
> Reboot your WinForms applications with our WinForms controls.
> Build a bridge from your legacy apps to the future.
> http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
>
>
> _______________________________________________
> Libusb-win32-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel


------------------------------------------------------------------------------
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls. 
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
_______________________________________________
Libusb-win32-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel