On 2/15/2012 11:44 PM, Christos wrote:
> You caught me by surprise !! a pleasant one indeed !! :-)
> I didnt knew that there is such a neat feature like the 'InstallDriver', as
> I've seen you've placed it, a few days ago in the package.
Yes, they are new. ;)
> Its a well needed one !!
Yes. Most end-users are not going to be able to use a generic installer
to any extent.
> Since that one exists, then of course the filter solution is not required.
> I guess by using this feature, from your distributed libusbK-3.0.5.*-bin.7z
> , the signature issues in W7/64 bit systems are also taken into
> consideration since your distributed *.sys are signed right?
> Or even better if the InstallDriver works in a similar way as Pete's zadig,
> though for specific VID/PID which is exactly what we need.
Yes, the client installers include "dpscat.exe". This creates the
self-signed .cat files for all .infs in the working directory. It's
purpose is only to eliminate the ugly windows warning. You can omit this
entirely, but you would also have to enable "legacyMode" in dpinst.xml.
> And your example shows that we can even use it for multiple VID/PID thus
> covering any bootloading issues, its very clever by all means.
Yes. It will also do multiple .inf files at once. Really, you could
just put both of your .inf files in the generated client installer and
run re-pack-files.cmd. However, I think it would be better to use the
One pitfall I've found is that if the catalog generation fails on WXP(32
bit), the entire installation fails. On Win7(64bit) and Vista(64bit),
it will display the ugly unsigned warning but ultimately the
installation will still succeed.
So, to make your installations more robust, I would sugggest adding
the /LM switch (legacyMode) to the dpinst32 line in 7zDP_LZMA.cfg: